ExcelTerritory mapIvory theme

Sales territories around Munich

Wedge-shaped territories sharing exact edges, coloured by category with revenue in the popup. Shared edges are what make a territory map look designed: independently drawn polygons leave slivers and overlaps that read as sloppiness.

Start an editable copy with this data and your current map styling.

Loading Excel data
Territory geometry generated around real Munich coordinates; account and revenue figures are synthetic.

What to look at

  • Territories share edges exactly, with no slivers or gaps between them.
  • Categorical colour with the territory name as a centroid label.
  • An Excel workbook with a header row is read straight from the first sheet.

Source columns

These fields describe the example data. CSV and Excel use first-row headers; GIS formats store geometry and feature properties. Required geometry depends on the map type.

ColumnTypeExample
territorytextNorth East
accountsnumber318
revenue_knumber2840
ownertextL. Silva

Rebuild it with your own data

  1. 1

    Get your Excel file ready

    The example fields are territory, accounts, revenue_k, owner. For CSV or Excel, put headers in the first row. GIS files carry geometry and feature properties. Prepare any grid, catchment or route geometry before import.

  2. 2

    Drop it into the studio

    MapCrafter detects the geometry, counts the features, and shows the layers it found.

  3. 3

    Style the imported layer

    Pick which column drives colour, and which drives size or width where relevant.

  4. 4

    Pick a basemap theme

    Ivory is used here. 15 other basemaps are available, including official OpenFreeMap styles. Switch using Layers & basemap.

  5. 5

    Share or export

    Publish a link, embed the map, or export a PNG at print resolution.

Questions about this example

What file format does this territory map use?
This example illustrates Excel data. The live preview uses GeoJSON geometry. MapCrafter reads Excel directly, along with Excel, CSV, KML, KMZ, GPX, GeoJSON, TopoJSON and zipped Shapefile. No conversion step and no desktop software.
What columns does the source data need?
The file used here has 4 columns: territory, accounts, revenue_k, owner. For tabular imports, supply coordinate columns, WKT or GeoJSON geometry, or address columns for an explicit geocoding step. Polygon and line files carry their geometry separately from these attributes.
Can I use my own data with this map type?
Yes. Open the studio, drop in your file, and MapCrafter detects the geometry and applies a starting style. Then style the layer and choose which property drives colour, size or width. The studio can render a point heatmap, but grids, routes and catchment polygons must be prepared before import.
Can I export or share the finished map?
Each map can be published to a short share link, embedded in another page with an iframe, or exported as a print-resolution PNG. The cleaned-up geometry can also be exported as GeoJSON. All of that is available on the free tier.
Where does the data in this example come from?
Territory geometry generated around real Munich coordinates; account and revenue figures are synthetic.

More catchment maps examples

Gallery (314)

Last updated 2026-10-22