Data Tab
The Data tab is your primary data entry point. This is where you add individual locations, batch-import location lists, manage datasets, and organize your map's content. Every location marker on your map originates from controls in this tab.
pitchmappr uses a dataset-based organization model. Each dataset is an independent group of locations that share the same marker color, shape, and visibility settings. You can have multiple datasets in a single project (e.g. "Current Offices" in blue circles and "Target Acquisitions" in orange diamonds), and each dataset can be shown or hidden independently.
Add Location
The simplest way to get a location on your map. Enter a place name, click Add, and a marker appears. Under the hood, the text you enter is sent to a geocoding service (Nominatim by default) that converts place names to latitude/longitude coordinates.
| Feature | Control | Description |
|---|---|---|
| Location search | Text input | Enter a city name, address, or place to geocode and add as a marker on the map. Supports a range of input formats: simple place names (e.g. "Tokyo"), city and country (e.g. "Munich, Germany"), full street addresses (e.g. "123 Main St, New York, NY"), or landmarks (e.g. "Eiffel Tower"). Max 200 characters. The geocoding service resolves your input to the most likely match and places a marker at those coordinates immediately. Press Enter or click the Add button to submit. If you get the wrong location (e.g. "Paris" matched Paris, Texas instead of Paris, France), try being more specific. |
| Add button | Button | Triggers the geocoding search and adds the resolved location to the current dataset as a marker. If geocoding fails (no results found), an error message appears in the toast notification area at the bottom of the screen. The new marker is immediately visible on the map and added to the location list. |
| Map label override | Text input | Optional custom label that replaces the geocoded name on the map. By default, whatever the geocoding service returns (e.g. "New York") is used as the map label. This field lets you override that with your own text (e.g. "NYC HQ", "Main Office", "Target A"). Max 100 characters. If left empty, the geocoded name is used. The original geocoded name is always preserved in the data — the override only changes what's displayed on the map. |
| Set as HQ | Checkbox | Marks this location as the headquarters or primary location. HQ locations get special visual treatment: they're rendered as star-shaped markers (when "HQ as star" is enabled in the Markers tab) in a distinct HQ color that differs from normal dataset markers. Only one location per project can be HQ. Setting a new location as HQ automatically clears the HQ status from whichever location previously held it. |
| Dataset selector | Dropdown | Chooses which dataset the new location belongs to. Each dataset has its own marker color, shape, and visibility settings. The dropdown lists all current datasets. New locations are added to the selected dataset and inherit its marker styling. If you only have one dataset (the default), all locations go into that single group. |
Import Locations
For adding many locations at once, the Import section provides two batch methods plus a location list for managing existing markers.
| Feature | Control | Description |
|---|---|---|
| One per line | Button → modal | Opens a text input modal for batch-importing locations. Enter one location name per line, up to 200 names per import (the maxImportNames limit). Each line is geocoded sequentially with a progress bar showing completion status. Successfully geocoded locations are added as markers to the currently active dataset. Lines that fail geocoding (no results found) are reported in the status area so you can identify and fix them. This is the fastest way to add a moderate number of locations when you have a simple list of names. |
| CSV file | Button → modal | Opens a file picker for importing locations from CSV, TSV, or TXT files. The import dialog guides you through mapping your file's columns to pitchmappr fields. At minimum, your file needs a column with location names (which are geocoded). Optionally, you can include latitude and longitude columns (which skips geocoding entirely and uses your coordinates directly), custom label columns, and a dataset column (which auto-creates datasets based on the values in that column). This is the best method for large imports or when you already have coordinate data from another source. |
| View Locations list | Display (collapsible) | Shows up to 50 locations in a scrollable list, sorted with HQ first, then in the order they were added. Each row displays the location name, a color chip showing the dataset color, and action buttons. Provides an overview of all your data and quick access to edit or manage individual locations. If you have more than 50 locations, the list is capped for performance. |
| Per-location edit label | Click-to-edit | Click on any location name in the list to edit its map label inline. A text field appears in place, letting you type a new label and confirm with Enter or a checkmark button. Changes are reflected immediately on the map. The label override is independent from the original geocoded name — your original data is preserved, and clearing the label reverts to the geocoded name. |
| Per-location pan | Button (target icon) | Centers the map on the selected location without changing the zoom level. Useful for quickly navigating to a specific marker when you have many locations spread across a large area. The map smoothly pans to center on the location's coordinates. |
| Per-location remove | Button (X icon) | Permanently deletes the location from the project. The marker is removed from the map and the location is removed from its dataset. This action is immediate and cannot be undone (there's no confirmation dialog for individual location removal). |
| Per-location HQ toggle | Star button | Toggles the HQ (headquarters) status of the selected location. The star icon is highlighted in the HQ color when active. Only one location can be HQ at any time — toggling a new one automatically clears the previous HQ. HQ status affects the marker's shape (star instead of circle/diamond) and color (uses the global HQ color instead of the dataset color). |
| Reset view | Button | Resets the map to its initial default viewport: a world view at zoom level 2, centered at coordinates [10, 25]. Does not change any data, settings, or layer visibility — only the map viewport. Useful when you've zoomed in far and want to quickly return to a global overview. |
| View all | Button | Adjusts the map viewport to fit all marker locations into the visible area with appropriate padding. The map zooms and pans to a level where every location marker is visible on screen. Useful after adding many locations or after importing a batch, so you can see the full geographic spread of your data at a glance. |
| Clear all | Button → confirmation modal | Opens a confirmation dialog before permanently deleting ALL locations from ALL datasets. This is a destructive action that cannot be undone. The datasets themselves (their names, colors, shapes) are preserved — only the location data within them is cleared. Use this when you want to start over with the same project settings but fresh location data. |
Dataset Settings
Datasets let you organize locations into groups that can be styled and toggled independently. Each dataset has its own marker color, shape, visibility toggle, and optional size override. Common uses include separating "Current Offices" from "Planned Offices", distinguishing "Buy-side" from "Sell-side" locations, or grouping locations by region or business unit.
| Feature | Control | Description |
|---|---|---|
| New dataset name | Text input + button | Creates a new dataset with the name you enter. Max 60 characters. Each new dataset starts empty and becomes available in the dataset selector (Section 4.1) for new location additions. The dataset is initialized with default marker styling (circle shape, next available color from the active color scheme). You can create as many datasets as needed for your project. |
| Dataset visibility | Checkbox per dataset | Toggles all markers belonging to a dataset on or off on the map. When unchecked, the dataset's markers are hidden from the map display. However, hidden markers ARE still included in exports unless you use per-view dataset visibility overrides (see Section 6.2). This toggle is useful for temporarily hiding a dataset while you work on others, or for simplifying the map view during editing. |
| Remove dataset | Button per dataset | Deletes a dataset and reassigns all its locations to the first remaining dataset. At least one dataset must always exist, so the delete button is hidden when only one dataset remains. The locations within the deleted dataset are not lost — they're moved to the first remaining dataset and inherit that dataset's marker styling. Only the grouping changes. |