Running one lookup is easy. Running the same lookup on two thousand rows is the part that eats an afternoon. The bulk CSV tool takes a spreadsheet of coordinates, applies a single analysis to every row, and hands back a results table you can download.
You choose what gets added: the administrative hierarchy each point sits in, how far it is from the nearest border or the nearest coastline, the nearest city, town or village, or — for files with a second coordinate pair per row — the distance from each source to its destination.
There is also a sixth option that works the other way round: instead of looking your rows up against our data, zone tagging matches them against boundaries you supply. Upload your territories, catchments or districts alongside the CSV and every row comes back labelled with the zone it falls in.
How it works
Your CSV needs a SourceLatitude and a SourceLongitude column, plus an optional Location column for your own labels. Point-to-point runs also need DestinationLatitude and DestinationLongitude on each row. Two ready-made templates are downloadable from the panel so the column names are right first time.
Zone tagging needs one more thing: the zone file itself, dropped into the second uploader. Shapefile (zipped), GeoJSON, KML, KMZ and GeoPackage are all accepted, and once it is read you pick which of its attributes should name each zone — so the results say "North West" rather than "polygon 4". A zone file can hold up to 50,000 polygons.
Once the file is checked, the run is submitted as a background job instead of being processed while you wait in the browser. Results appear in the results view that matches the operation you picked, where the whole table can be downloaded as a CSV with the new columns appended. Zone tagging results add a count of points per zone, a separate CSV per zone, and a row for everything that fell outside every zone.
How to use the Bulk CSV Lookup
- 1
Start from a template
Open the MapGO workspace, choose CSV from the Upload tools, and download either the single-point or the point-to-point template so your columns match what the tool expects.
- 2
Fill in your coordinates
Put one location per row, with latitude and longitude in decimal degrees. Add your own Location column if you want your labels carried through to the results.
- 3
Upload the file
Drop the CSV into the uploader. Rows are checked before anything is submitted, so invalid coordinates are flagged rather than silently processed.
- 4
Pick the operation
Choose Location Hierarchy, Distance to Border, Distance to Coastline, Nearest City / Town / Village, or Tag by my zones. Files containing destination columns get the Point to Point Distance option instead.
- 5
Add your zone file, for zone tagging
Zone tagging only: drop in your boundaries as a zipped Shapefile, GeoJSON, KML, KMZ or GeoPackage, then choose which of its columns should name each zone.
- 6
Collect the results
Submit the run and let it process in the background. The matching results view lists the finished job and lets you download the enriched table as a CSV.
What people use it for
Enriching a customer or asset list
Turn a column of coordinates into country, region and municipality names so the list can be grouped, filtered and reported on.
Risk and insurance screening
Add distance to the nearest coastline or border to a whole portfolio of addresses in one run instead of checking them one at a time.
Logistics and route measurement
Measure every source-to-destination pair in a route list at once, or attach the nearest town to each depot or delivery point.
Data cleaning and QA
Catch swapped, truncated or out-of-range coordinates by checking which country each row actually lands in before the data is used.
Assigning a list to your own territories
Tag thousands of customers, sites or jobs with the sales territory, delivery zone or catchment each one falls in, and get a count per zone alongside the tagged file.
Screening against boundaries only you have
Run a whole portfolio against flood outlines, exclusion zones or service areas you supply, and see immediately which rows fell outside every one of them.
Frequently asked questions
- What columns does my CSV need?
- SourceLatitude and SourceLongitude are required, and a Location column is optional for your own labels. Point-to-point runs also need DestinationLatitude and DestinationLongitude on each row. Downloadable templates cover both layouts.
- How many rows can one file have?
- The per-upload cap depends on your plan: 1,000 rows on Starter, 5,000 on Pro and 10,000 on Business. Zone tagging is capped far higher — 5,000, 20,000 and 100,000 respectively — because matching a row against a file you supplied costs much less than a lookup against our boundary data. Larger jobs can be split across several uploads, within your monthly row allowance.
- Can I tag rows against my own zones?
- Yes — choose Tag by my zones and upload your boundaries alongside the CSV, as a zipped Shapefile, GeoJSON, KML, KMZ or GeoPackage holding up to 50,000 polygons. You pick which of its attributes names each zone, and every row comes back labelled with the zone it falls in.
- What do I get back from a zone tagging run?
- Three things: the full table with a zone column added, a count of how many points landed in each zone (with a separate row for anything outside them all), and a CSV per zone if you want the rows split up. A point inside two overlapping zones is counted in both. The downloadable files are kept for seven days; the counts stay indefinitely.
- Is there a monthly limit as well?
- Yes. Rows are counted against your plan's monthly allowance across the calendar month, and an upload that would take you past it is rejected before it runs rather than part-processed.
- Do I need a paid plan?
- Yes, bulk CSV runs are available on paid plans only. The individual tools — hierarchy, border distance, coastline distance, point-to-point and zone tagging on the map — can be used one job at a time without a subscription.
- How do I get the results?
- Each operation has its own results view in the dashboard. Open the one matching your run and download the completed table as a CSV with the new columns added to your original rows.