Let your app start a map conversation with Atlasemoji
Atlasemoji is not just a place to read maps. It can also receive geometry, organize it, and help turn a small dataset into a bigger, more useful map.
This quick start shows a tiny GeoJSON, the API call that sends it, and the next few things Atlasemoji can do with it.
A point, line, or polygon leaves your app as GeoJSON.
The API reads the structure and turns it into something the map can use.
That geometry can become a waypoint, a route, a workspace asset, or part of a published output.
Start with a tiny GeoJSON
GeoJSON is a practical way to describe geography with plain structured data. This example contains one point. That is enough to begin a real exchange between your app and Atlasemoji.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"title": "First waypoint",
"emoji": "📍",
"kind": "demo-point"
},
"geometry": {
"type": "Point",
"coordinates": [-122.335167, 47.608013]
}
}
]
}A single place on earth, defined by coordinates.
Human meaning such as a title, emoji, category, or labels.
A standard wrapper that lets you send one or many mapped features together.
Send it to Atlasemoji
Your app sends the GeoJSON to an API. Atlasemoji reads the geometry and turns it into something that can appear on a map surface and fit into a larger workflow.
POST /api/import/geojson
Content-Type: application/json
{
"title": "My first Atlasemoji route",
"geojson": {
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"title": "First waypoint",
"emoji": "📍",
"kind": "demo-point"
},
"geometry": {
"type": "Point",
"coordinates": [-122.335167, 47.608013]
}
}
]
}
}curl -X POST "https://atlasemoji.com/api/import/geojson" \
-H "Content-Type: application/json" \
-d '{
"title": "My first Atlasemoji route",
"geojson": {
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"title": "First waypoint",
"emoji": "📍",
"kind": "demo-point"
},
"geometry": {
"type": "Point",
"coordinates": [-122.335167, 47.608013]
}
}
]
}
}'{
"ok": true,
"routeId": "route_demo_123",
"featureCount": 1,
"message": "GeoJSON imported successfully"
}What Atlasemoji can do with it
A small GeoJSON does not have to stay small. Once Atlasemoji has the geometry, it can become part of a larger spatial workflow.
Turn a single point into a readable place in a story or route.
Group connected geometry so movement and order become clear.
Bring it into Workspaces so it can be edited, styled, layered, and reused.
Move from raw geometry toward something shareable, structured, and searchable.
Try changing one thing
Small changes are the fastest way to learn what an API conversation is really doing.
Change the coordinates and send the request again.
Edit the title so you can see how properties carry meaning.
Send two points instead of one and watch the dataset become more interesting.
Try a custom field like source, category, or lesson.
A better mental model
Do not think of this as only calling an endpoint.
Think of it as a conversation.
Here is a small piece of geography.
I can structure it, display it, and connect it to a bigger map.
Now I want to style it, layer it, publish it, or connect it to a story.