How to Use OpenStreetMap element history in Notion
Returns earlier versions of a map object in version order. Use it to trace how a road, building, or public place changed, rather than inspecting only its current record.
Prompts to try with OpenStreetMap element history in Notion
Copy an example into Notion, or ask in your own words.
Each Monday, use OpenStreetMap element history for the retained Tower Bridge map object. Summarize any versions added since the previous check.
Every Monday at 9am: use OpenStreetMap element history to look this up and give me the result as a table.
Pull the latest numbers from OpenStreetMap element history and tell me what changed since last week.
Check OpenStreetMap element history and summarize what you find in three bullet points.
Pull the newest data from OpenStreetMap element history and give me the result as a table.
How to set up OpenStreetMap element history in Notion
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send Notion this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Allow custom MCP servers
A workspace owner opens Settings › Connections, then the Manage tab, and turns on Enable custom MCP servers. Where members may install only approved connections, also add Spiral under Approved connections › Add approved connection › Custom MCP server with the URL below.
- Add Spiral to a custom agent
Open the custom agent (or create one), then Settings › Tools & Access › Add connection › Custom MCP server. Paste this URL, name it Spiral, keep OAuth and click Connect.
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Notion never sees it, and you can remove it under Settings › Connected apps in the console.
- Run OpenStreetMap element history in a workflow step
Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds OpenStreetMap element history, prices it and runs it each time the step fires.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run OpenStreetMap element history
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "openstreetmap-org/places/element_history", "input": { "id": 1, "type": "node" } }'
Then paste one of the prompts above: Notion finds OpenStreetMap element history on Spiral, shows the price and runs it.
OpenStreetMap element history providers and prices
Spiral runs OpenStreetMap element history through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Notion for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| ID | a number from 1 | Numeric OSM element id. | |
| Type | node, way, or relation | OSM element type. |
Every API field of OpenStreetMap · Element history is on its tool page: open its card above.
What can you do with OpenStreetMap element history in Notion?
Maintain a recurring map-quality brief for a public district. Compare each OpenStreetMap retrieval with the previous run and surface changes in the records or evidence returned.
Investigate an unexpected map change
Compare a changed public feature with its earlier versions, surrounding map data, nearby edit sessions, and reported map problems.
Review accessibility mapping
Inspect available accessibility tags on public amenities, compare saved records, trace relevant edits, and collect map reports for human review.
Check an administrative boundary
Locate a municipality, inspect its mapped boundary and nearby features, then review object history and edit sessions when the boundary changes.
Investigate a station map discrepancy
Compare saved station-area records with current objects, inspect the surrounding block, and use history, edit sessions, and issue reports to explain discrepancies.
More on OpenStreetMap element history and Notion
Overview
OpenStreetMap element history in other agents
Questions about OpenStreetMap element history in Notion
Can Notion use OpenStreetMap element history?
Yes. Add Spiral to Notion as an MCP server, and Notion can find and run OpenStreetMap element history like any built-in tool.
How much does OpenStreetMap element history cost in Notion?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Notion plan is separate.
Do I need an Alexandria account to use OpenStreetMap element history in Notion?
No. Spiral runs OpenStreetMap element history on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up OpenStreetMap element history in Notion?
About two minutes: allow custom MCP servers, then add Spiral to a custom agent, then sign in to Spiral and approve.
Does Notion wait while OpenStreetMap element history runs?
OpenStreetMap element history runs in the background. Notion starts the run, checks on it and gives you the json when it's ready.
Which parts of the world does OpenStreetMap cover?
OpenStreetMap has worldwide scope, including roads, trails, cafés, and railway stations. Its records come from a community of contributors.
Does worldwide coverage mean every local feature is mapped?
No. OpenStreetMap's accuracy documentation says basic map coverage is still being built in many areas, so a local result set cannot establish that every feature is present.
How frequently are OpenStreetMap changes distributed?
OpenStreetMap publishes minute, hourly, and daily change files. Those replication intervals do not establish one refresh schedule for every service that uses the data.
Are these map images or underlying geographic records?
OpenStreetMap's editing API exposes raw geographic data. Nodes, ways, and relations describe the underlying features rather than a rendered map image.
Is an OpenStreetMap number enough to identify a feature?
No. Nodes, ways, and relations have separate ID spaces, so retain the object type alongside the number.
Start using OpenStreetMap element history in Notion
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Notion:
set up https://spiral.ai/SKILL.md


