Territory mapping features

The current TerritoryKit builder focuses on importing coordinate-ready data, drawing editable territories, analyzing what falls inside each zone, and exporting useful results.

Open Map Builder

Import the data you already have

Start with CSV, XLSX, XLS, KML, or KMZ files instead of rebuilding your project in a new format.

Draw boundaries that fit reality

Create free-form polygons or circles rather than being limited to predefined administrative regions.

Revise plans quickly

Rename, recolor, reshape, duplicate, merge, split, or delete territories without rebuilding the map.

Measure every zone

See how many locations fall inside each territory and compare the results across the map.

Go beyond total counts

Group records by a chosen field to understand how categories are distributed within each territory.

Make overlaps visible

Identify records that fall inside more than one territory instead of leaving conflicts hidden.

Keep layers organized

Separate point data, analysis territories, and reference geography so complex projects stay manageable.

Save and continue later

Export a portable TerritoryKit project file and reopen it when you are ready to continue.

Take the results with you

Export territory metrics and point membership as CSV, or export zone geometry as GeoJSON or KML.

Supported imports

TerritoryKit imports CSV, XLSX, XLS, KML, KMZ, and portable project JSON files. Spreadsheet imports use latitude and longitude columns selected during import; KML and KMZ can create point, zone, or reference layers depending on the source geometry.

Territory editing

Create polygon and circle territories, then rename, recolor, reshape, duplicate, merge, split, or delete zones where the current builder supports those actions. Multiple point, zone, and reference layers can stay visible or hidden as the plan changes.

Zone totals and overlap behavior

The analytics panel compares a selected point layer against a selected zone layer. It reports per-zone totals, category breakdowns using a chosen field, unassigned records, and points that fall in more than one territory. Boundary points are counted as inside the zone.

Exports and project workflow

Export metrics CSV, point membership CSV, zone geometry as GeoJSON or KML, and a portable TerritoryKit project file that can be imported later. Current limitations: no address geocoding, route planning, drive-time polygons, shapefile import, real-time collaboration, cloud save, or CRM synchronization.

Relevant guides

Create a territory map · Map CSV latitude and longitude data · Find overlapping territories

Build your first territory map

Bring your coordinates, draw the zones you need, and see the results as the map changes.

Open Map Builder

No account required