Purpose Statement
This article guides agencies on how to properly configure and use the ArcGIS Sync Tool and Hydrant Import Tool for hydrant data management. It helps users understand key differences, field mapping requirements, and best practices to ensure accurate, reliable hydrant data within First Due.
Background Information
Agencies manage hydrant data in two primary ways within First Due:
Hydrant Import Tool (one-time/static upload)
ArcGIS Sync Tool (automated, scheduled updates via REST service)
Choosing the correct method depends on:
Data ownership (internal vs external)
Data update frequency
Integration with municipal or GIS systems
Understanding how these tools interact with hydrant identifiers and mapped fields is critical to avoiding data conflicts, duplication, or unintended overwrites.
Required Permissions
Users will typically need the following permissions:
Hydrants Module Access
Data Import / Import Wizard Access
ArcGIS Sync Configuration Permissions
Admin or Data Manager Role (recommended)
Contact your system administrator if access to import tools or integrations is restricted.
Step-by-Step Guide
1. Determine Your Hydrant Data Management Method
Identify whether your agency:
Manages hydrant data internally → use Import Tool
Receives data from GIS/municipality → use ArcGIS Sync
Confirm whether your data source includes a reliable REST service
2. Prepare Hydrant Data for Import (If Using Import Tool)
Ensure data is formatted as a .csv file
If needed:
Open file in Excel
Select Save As → CSV (Comma Delimited)
Validate:
Hydrant count matches expectations
Each column has clearly understood data
Data aligns with First Due field structure
3. Map Hydrant Identifier Fields
Ensure correct mapping of identifiers to prevent duplication or data issues:
Hydrant Identifying Fields
| Hydrant Identifiers | Unique Requirement? | Null Value Accepted? | Suggested Use Case |
|---|---|---|---|
| First Due ID | Yes - First Due creates this | Yes (should be populated during import) | System-generated primary ID |
| Facility ID | No | Yes | Used when hydrants are tied to facilities |
| Hydrant ID (Xref_id) | Yes | Yes (not recommended) | Agency’s internal hydrant identifier |
4. Configure ArcGIS Sync Field Mapping
Map fields from your REST service to First Due fields carefully.
Important:
ArcGIS Sync will overwrite matching fields in First Due
No bidirectional sync exists
Avoid mapping fields that are updated by field personnel (e.g., flow test data)
5. Validate Mappable Fields
Use the following standards when configuring field mappings:
Mappable Fields Table (Preserved)
| Field | Expected Value | Example |
|---|---|---|
| Hydrant ID Column | Up to 32 characters (required) | AFD-1234 |
| Barrel Size | Numeric (2 decimals) | 10 |
| Facility ID | Up to 32 characters | 101-2 |
| Fire District | Up to 50 characters | Station 126 |
| Flow Hydrant Rate | Number | 900 GPM |
| Hydrant Address | Free text (255 chars) | 123 Main Street |
| Hydrant ID | Up to 32 characters | FD-102 |
| Hydrant Status | Import: in_service/out_of_service ArcGIS: "1" = In Service | operational |
| Hydrant Type | Must match system setup | Private Hydrant |
| Last Flow Test Date | Timestamp | 01/01/2025 |
| Location Description | Up to 128 characters | Behind the rock |
| Placement | Free text | South side |
| Main Size | Number | 12 |
| Manufacturer | Up to 128 characters | Mueller |
| Notes | Free text | Hidden by bushes |
| Number of Outlets | Number | 3 |
| Latitude | Decimal (7 places) | 31.9159550 |
| Longitude | Decimal (7 places) | -81.0736890 |
| Private | Boolean | TRUE |
| Residual Pressure | Number | 55 |
| Serviced Date | Date | 08/27/2025 |
| Shift | Matches system setup | B-Shift |
| Station | Matches system setup | Station 126 |
| Outlet Sizes | Numeric | 2.25 / 5.25 |
| Static Pressure | Number | 1234.12 |
| Steamer Port | Text | Threaded |
| Year Installed | 4-digit year | 1975 |
6. Perform Import or Activate Sync
Import Tool:
Upload CSV via Import Wizard
Map fields
Validate and complete import
ArcGIS Sync:
Configure REST service connection
Map fields
Set sync schedule
Monitor initial sync results
Best Practices
General
Always validate identifier fields before import or sync
Use consistent, unique hydrant identifiers
Test with a small dataset before full deployment
ArcGIS Sync
Do NOT map fields maintained by First Due users (e.g., inspections, flow tests)
Ensure REST service data is clean and reliable
Understand that sync will overwrite mapped fields
Import Tool
Use for agencies managing hydrants internally
Maintain data directly within First Due after import
Avoid re-importing without matching identifiers
Data Preparation
Confirm hydrant counts match real-world expectations
Ensure all columns are clearly understood and necessary
Troubleshooting & FAQs
Q: Why are duplicate hydrants being created?
A: Identifier mismatch (Hydrant ID or Xref_id) between imports.
Q: Why is my data being overwritten?
A: ArcGIS Sync is updating mapped fields from the REST service.
Q: Can First Due push updates back to ArcGIS?
A: No—bidirectional sync is not currently supported.
Q: Why isn’t my ArcGIS sync working?
A: Protected REST services (requiring login credentials) are not supported.
Q: Can I still use Flow Tests with ArcGIS Sync?
A: Yes, but avoid mapping those fields in the sync configuration.
Additional Considerations
Use Case Guidance
Use Import Tool if:
You manage hydrant data internally
No reliable GIS data source exists
Use ArcGIS Sync if:
Hydrant data is maintained externally
You have access to a public REST service
Data Ownership Strategy
Clearly define:
Who owns hydrant data (agency vs municipality)
Which system is the “source of truth”