Troubleshooting
Map shows grey strips after opening/closing a panel
This should resolve automatically — the panel fires a map resize event after its animation completes. If you still see grey strips, zoom in or out slightly to force a re-render.
Geocoding is slow or fails
pitchmappr geocodes through the provider your organization's admin has configured (MapTiler or OpenCage). If no provider is set up for your organization, geocoding is turned off and you'll need to enter latitude/longitude manually.
If geocoding fails or seems stuck:
- Check your internet connection
- Wait a few seconds and try again (the geocoding provider may be rate-limited or temporarily busy)
- For a large paste, make sure you haven't exceeded the 200-line paste limit (CSV import has no per-file row limit — only the 1,000-location project total applies)
- Include lat/lon in your CSV to bypass geocoding entirely
Export is blurry at low zoom
At very low zoom levels (z2–z4, showing the whole world), even Hi-Res PNG may appear softer because the vector tiles have less detail at global scale. For sharper results, zoom in closer to your area of interest or use Focus Mode.
Focus Mode boundaries look jagged
Enable High resolution boundaries in the Focus Theme section. This loads a more detailed boundary dataset (Natural Earth 50m or 10m) that produces smoother edges at higher zoom levels.
Fonts don't load (offline use)
DM Sans and IBM Plex Mono are loaded from Google Fonts. If you're offline, the browser falls back to system fonts. This affects appearance but not functionality.
I closed the tab without saving
When you're signed in, your work saves to your account automatically as you go, so closing the tab or refreshing won't lose changes that have already saved — watch the header badge flip to "Saved". The standalone map tool, opened outside your account, has no server save; there, use Export JSON to keep your work.
The header badge reads "Unsaved" while a change is being stored and "Saved" once it's safe. In the signed-in app this happens automatically as you work.
My map looks tilted or rotated
The map can be rotated and tilted, and it is easy to do by accident — right-click-dragging (or Ctrl-dragging) the map, or a two-finger drag on a trackpad, rotates and tilts it. To straighten it: click the lock button in the map's control rail (the padlock, between the recenter and tools buttons). Locking snaps the map back to square (north-up, flat) and prevents any further rotation. New maps are locked by default, so this only happens if you unlocked rotation first. The recenter button and the reset options also return the map to square. If you want to rotate a map for a deck — for example an angled, tilted look — click the padlock to unlock, then right-click-drag to rotate and tilt; that angle is kept when you save the project or a view.
Markers disappear after switching themes
Switching base map themes rebuilds the map style, which can briefly cause markers to flicker. They should reappear within a second. If they don't, open the Data panel and click View all to reset the map bounds.
CSV import skips rows unexpectedly
A row is skipped only when both its address and its label are empty — there is no other skip rule. Out-of-range lat/lon values do not skip the row: it still imports, and it gets geocoded from its address text instead.
The Import CSV dialog shows column mapping, not a per-row preview, so check the toast that appears after importing — it reports how many rows actually landed (e.g. "clients.csv: 12 rows imported").
Focus Mode doesn't activate for a country
Make sure you're in Focus Mode (not Regular Mode) via the toggle at the top of the Map panel. If the country dropdown appears greyed out, switch the mode toggle first.
Hi-Res export takes a very long time
Hi-Res PNG re-renders the entire map at 2–4× resolution from vector tiles. On slower connections, tile loading can take 5–10 seconds. The export waits for all tiles to finish before capturing. If it seems stuck, check your network connection.
Project JSON won't load
The file may be from an older schema version. pitchmappr supports automatic migration from v3 → v4. If the file uses an unrecognized schema or is corrupted, the load will fail with a toast error. Make sure you're loading a .json file that was exported from pitchmappr (not a generic JSON file).