Every landmark has an ID — a short, stable identifier that's separate from its display name. It's how the map links to the landmark in a shareable URL, and how a spreadsheet import matches rows to landmarks. Because other things point at it, an ID is worth setting once and leaving alone.
Where the ID is used
| Used by | How |
|---|---|
| Deep-links | A URL ending ?location=ID opens the map with that landmark selected — ideal for sharing a direct link to one place |
| CSV import | Imported rows are matched to landmarks by ID, so re-importing updates the right ones instead of creating duplicates |
| Directions & references | Anything that refers to a landmark by ID (for example a saved route endpoint) relies on the ID staying the same |
Set or change an ID
-
Open the landmark
In the Landmarks tab, expand the landmark.
-
Edit the 'ID (unique)' field
The ID sits just under the Title. Keep it unique across the map — no two landmarks should share an ID.
-
Prefer letters, numbers and dashes
A short, readable ID like
receptionorroom-204makes for tidy shareable links.
Why changing an ID breaks links
?location=old-id URL, a QR code printed with the old ID, or a CSV keyed on it will all stop matching — the map no longer knows which landmark that ID meant.If you must rename an ID, do it before you share links or print QR codes, and remember to update any spreadsheet you import from so its column still matches. When in doubt, change the Title (which is safe to edit freely) and leave the ID as it is.
Title vs. ID
| Field | Safe to change? | Purpose |
|---|---|---|
| Title | Yes, any time | The human-readable name shown to visitors |
| ID (unique) | Avoid once links exist | The stable identifier links, imports and references depend on |