CSV import format
Import on the Geofences page turns a list of addresses into circular geofences, up to 500 at a time. This page covers the file format and what the preview tells you. Geofences covers the steps.
Columns
Only address is required. The first row must name the columns, in any order.
| Column | What to put in it |
|---|---|
address | The full street address, with city and state or postcode |
name | The geofence's name. Left empty, it's the address up to the first comma |
buffer | The circle's radius in whole meters, from 1 to 10,000. Left empty, it's 100 |
tags | Tags for this geofence, separated by semicolons |
SpatialFlow also accepts addr for address, buffer_meters for buffer, and tag for tags, and ignores any other columns. A file with a single column is read as a list of addresses.
Put an address in double quotes when it contains a comma:
address,name,buffer,tags
"100 Example Ave, Springfield IL",North yard,150,yard;night-shift
"200 Sample Rd, Springfield IL",,100,
The second row gets the name 200 Sample Rd. Download CSV template on the import page gives you a file with these columns.
Apply tags to all rows adds tags to every row that has none of its own. A row with its own tags keeps only those.
Paste addresses skips the file: paste one address per line, up to 500 lines.
Preview statuses
Preview addresses looks up every row and marks it:
| Status | What it means | Imported? |
|---|---|---|
| OK | Found | Yes |
| Dedup | A geofence already exists at that address or within 50 meters | Only if you choose Override duplicate |
| Error | Not found, or the row has a problem such as a missing address | No |
| Skipped | You chose Skip row | No |
Some OK rows carry a warning. Check them on the map before you commit:
| Warning | What it means |
|---|---|
| Low confidence | The match is uncertain |
| Interpolated | The street number was estimated from a range of numbers on that street |
| Ambiguous | Several places matched, and SpatialFlow picked one |
Each row's menu has Skip row, Restore row, Override duplicate, Re-geocode and Adjust pin. You can also edit a row's address and look it up again.
The commit button counts what it will create, for example Commit 12 geofences.
After the import
Import complete lists the geofences created, the duplicates, and the rows that failed. Download error report saves the failed rows as a CSV file with the row number, the address, and the reason. Fix those addresses in your original file, remove the rows that worked, and import it again.
If the address service stops partway through a large import, the page says which row it stopped at, and Retry remaining rows picks up from there.
From your own system
To create geofences from a dispatch, TMS or CRM system instead of by hand, use the Bulk create geofences API. The TMS address recipe walks through an example.