If your agency already has a hydrant list in a spreadsheet, you can import the whole thing at once. The importer is also safe to re-run -- if a hydrant number already exists, the record is updated rather than duplicated.

Before you start: Save your spreadsheet as CSV. The file must be 10 MB or smaller. The required columns are hydrant_number, latitude, and longitude. Anything else is optional.

Step by step

  1. From the menu, click Hydrants.
  2. Click Import.
  3. Click Download template if you would like a blank CSV with the supported column headers. Fill it in and save.
  4. Click Choose file and select your CSV.
  5. Click Upload.
  6. Watch the progress indicator. When the import finishes, the screen shows the number of hydrants imported, the number skipped, and any errors.

Supported columns

The importer recognizes the most common header names. Examples:

  • hydrant_number (also accepted: hydrant id, hydrant_id, hydrant #, hydrant no)
  • address, city, state, zip, cross_street
  • latitude, longitude
  • status, type, ownership
  • color_code (also accepted: color)
  • main_size, barrel_size, number_of_ports
  • make (also accepted: manufacturer), model
  • year_installed, installed_date, replacement_year
  • zone, station_number, district, service_responsibility, valve_location
  • notes (also accepted: comments)

What the importer does

  • Reads each row, validates the required fields, and creates a hydrant.
  • If a hydrant with the same number already exists in your agency, the row updates that hydrant instead of creating a duplicate.
  • Normalizes common variations -- for example, in service, active, and open all become active.
  • Reports up to 20 errors at the end, with the row number and the reason for each failure.

Tips

  • If a row is missing latitude or longitude, it is skipped. Fix the spreadsheet and re-upload.
  • After the import finishes, open the map to confirm every hydrant landed where you expect.
  • You can re-run the import as many times as you need. Existing hydrants are updated, not duplicated, so a re-upload after a column fix is safe.