How to map CSV latitude and longitude data

Direct answer

A CSV can be mapped when each row has usable latitude and longitude values. TerritoryKit lets you pick those columns, previews the rows, and creates a point layer for territory analysis.

Requirements

• A modern desktop browser.
• CSV, XLSX, XLS, KML, KMZ, or a TerritoryKit project file.
• For spreadsheet points, usable latitude and longitude columns.

Numbered workflow

1. Open the map builder.
2. Import your file and review any validation warnings.
3. Select latitude and longitude columns for spreadsheet data.
4. Draw or import the territory boundaries you want to compare.
5. Open analytics, choose the point layer and zone layer, and inspect totals or overlaps.
6. Export the result you need for reporting or downstream work.

Small example

A fictional CSV might include columns for site_id, latitude, longitude, segment, and status. Download the sample CSV to try it.

Supported formats and limitations

TerritoryKit supports CSV, XLSX, XLS, KML, KMZ, project import, metrics CSV, point membership CSV, GeoJSON, KML, and project export. It does not geocode addresses, optimize territories, plan routes, create drive-time polygons, or sync with cloud services.

Troubleshooting

If records do not appear, confirm that latitude and longitude are numeric and in separate columns. If a KML or KMZ imports only reference geography, check whether the source actually contains points or polygons. If analytics look empty, confirm that the selected point layer and zone layer overlap geographically.

FAQ

Are boundary points counted? Yes, points directly on a territory boundary are treated as inside. Can I continue later? Yes, export a portable project file and import it again.

Related content

Research and program planning · All guides