To assist agencies in field mapping when using the Hydrant Upload Tool or the ArcGIS Sync Tool.
These fields should be mapped according to client data. First Due ID's are created for all hydrants. Make sure you are mapping any accurate and useful identifiers to the correct fields.
Hydrant Identifiers | Unique Requirement? | Null Value Accepted? | Suggested Use Case |
First Due ID | Yes - First Due creates this | Yes - But values should be added during import | First Due created ID, not editable by clients. Best ID number to display if other ID numbers are not coming from a clean source or multiple sources |
Facility ID | No - Multiple Hydrants can be associated with a Facility ID | Yes - First Due ID will be used as primary if other ID does not come from source data. (Note: not all hydrants are associated with a Facility) | Hydrants that are associated with a facility, building, complex, etc.
This ID is helpful in those scenarios |
Hydrant ID (Xref_id) | Yes | Yes - First Due ID is available still if this field is blank. Null values should be addressed though | Fire Departments internal, common knowledge Hydrant Identifier |
Hydrant Import vs ArcGIS Tool: Major Differences
Hydrant Imports are "static" and are typically completed once.
Agencies that utilize the hydrant import tool typically:
• Manage all hydrant data within First Due. This included status changes, changes to details, or addition/removal of hydrants.
• Do not have access to reliable or up-to-date hydrant rest services.
• Run Flow Testing and Service Testing within First Due - maintain hydrants and are responsible for tracking status.
The ArcGIS Sync tool updates the client hydrant list from a Rest Service on a schedule. These layers will OVERWRITE data that is entered into First
Due via the UI if the included fields in the sync conflict with data entered in First Due. We DO NOT currently offer a bidirectional sync - agencies
should not expect data they enter via the UI to be maintained if that field is included in the list of fields that are updated from an ArcGIS sync.
The ArcGIS tool is typically used:
• By agencies that have access to accurate and reliably updated hydrant information from a municipal water department or similar agency.
• Are not responsible for hydrant maintenance, hydrant status changes and other hydrant maintenance schedules.
Please note: Agencies that use an ArcGIS sync are still able to use our Flow Test, Service Test and Work Order tools - but it is important that we do not
map fields via an ArcGIS Sync to fields that are updated by agency personnel performing Flow Testing.
Best Practices for Importing Hydrants
Suggestions for Agencies Using the Tool for the first time:
File Formatting: To use the Import Wizard tool, hydrant information should be converted into a .csv file. If your current set of hydrant data was not
provided as a .csv file, please contact the member of your team that provided you with the data and ask for assistance with getting this conversion
completed.
• If your hydrant information can already be opened within Excel - you can likely complete this conversion yourself.
Simply open the file in Excel > select "Save As" > Choose the option that contains ".csv" you may notice the wording "Comma Delimited".
• Once you have saved your file as a .csv, you should be able to upload the document via the import wizard. Before you do - please check
out the suggestions below to avoid errors/confusion.
Data: One of the most important steps you can take before uploading your hydrant data is to confirm a few items:
• Does the number of hydrants included in the file match the number of hydrants that are present within your response area?
If not, it is important to confirm why this number is higher or lower than you would expect.
• Does each column of data meet the following standards:
You understand what this data represents (this will be important during the import process)
• Does the column contain data that is important or required to your agency?
Is there a clear correlation to where this data should be mapped within First Due?
Existing Agencies Updating their Hydrant Data:
Agencies looking to update their hydrant information need to ensure that the NEW hydrant information they are hoping to add or update via a new
import has the same exact identifier. Any discrepancy in these Identifiers will result in a new hydrant being created - not the hydrant being updated.
Mappable Fields
Below you will find all expected values for the mappable fields in the ArcGIS Sync Tool.
Field | Expected Value |
Barrel Size | Any number (two decimal places allowed) |
Facility ID | Up to 32 characters |
Fire District | Up to 50 characters |
Flow Hydrant Rate | Number (This is Flow Hydrant #1 value) |
Hydrant Address | Free Text up to 255 characters (does not match to database) |
Hydrant ID | Up to 32 characters (almost always a number) |
Hydrant Status | *Hydrant Upload Tool: in_service / out_of_service
ArcGIS Sync: "1" = In Service / Any other value = Out of Service |
| Hydrant Type | Must match one of the Hydrant Types created in Setup |
Last Flow Test Date | Timestamp without time zone |
Location description | Up to 128 characters |
Main Size | Number |
Manufacturer | Up to 128 characters |
Model | Up to 128 characters |
Notes | Free Text |
Number of Outlets | Number |
Latitude | 2-3 numbers (decimal) 7 numbers |
Longitude | 2-3 numbers (decimal) 7 numbers |
Private | Boolean |
Residual Pressure | Number (with up to 2 decimal places) |
Serviced/Inspected Date | Timestamp without time zone (yyyy-mm-dd) |
Shift | Matches agency setup for personnel shifts |
Station | Matches agency setup for stations |
Size of Outlet 2 | Number (with up to 2 decimal places) |
Size of Outlet 3 | Number (with up to 2 decimal places) |
Static Pressure | Number (with up to 2 decimal places) |
Steamer Port | Up to 128 characters |
Year Installed | 4 number year |
Hydrant Zone ID | Agency created value |
Nearest Occupancy | Matches occupancy data inside First Due |