Learn the map pieces before you drive the machine
Welcome to the Atlasemoji map workshop. This page teaches how maps work — not just how to look at them, but how to build them, describe them, publish them, and eventually interact with them through tools like the Developer Workbench and API Explorer.
By the time you finish this page, you will understand what a map really is, how the Earth is described using latitude and longitude, how satellites help determine location, how computers describe map shapes, how those shapes become routes and areas, how Atlasemoji organizes map objects, and how developers can work with those objects through an API.
🌍 Step 1 — What a map really is
A map is a model of the world. Instead of showing the whole Earth at full size, it represents places using symbols.
- Points show locations.
- Lines show movement or connection.
- Shapes show areas.
Maps also combine layers of information. One map might show cities and roads. Another might show hiking trails, wildlife migration, weather systems, or a historical route. Modern digital maps can combine all of those ideas at once.
That is why the same map system can show a bus route, a wildfire boundary, a football play, a hiking trail, or a historical journey.
📍 Step 2 — Latitude and longitude
Every location on Earth can be described using two numbers: latitude and longitude.
Latitude measures how far north or south you are.
Longitude measures how far east or west you are.
Example: Seattle
- Latitude: 47.6062
- Longitude: -122.3321
Together, those two numbers identify one exact place on Earth.
🛰 Step 3 — How phones know where you are
Many people say “GPS,” but GPS is only one satellite navigation system.
Phones and navigation devices use GNSS, which stands for Global Navigation Satellite System.
Major systems include:
- GPS — United States
- Galileo — Europe
- GLONASS — Russia
- BeiDou — China
- NavIC — India
- QZSS — Japan
Your phone listens to signals from several satellites. By measuring how long those signals take to arrive, it can calculate your position very precisely.
🗺 Step 4 — Maps need a data language
Computers need a consistent way to describe places. Two important formats help make that possible:
- JSON
- GeoJSON
JSON is a general way to organize information. GeoJSON is JSON with geography inside it. Together they make it possible to describe map objects clearly and consistently.
📦 Step 5 — JSON: the internet’s organized list
JSON stands for JavaScript Object Notation. It is a structured way to organize information so computers can exchange it easily.
{
"city": "Seattle",
"population": 733000,
"waterfront": true
}Important pieces:
- Curly braces
{}hold an object. - Square brackets
[]hold a list. - Key-value pairs look like
"title": "Seattle".
Many APIs use JSON to exchange information.
🌎 Step 6 — GeoJSON: JSON with geography
GeoJSON is JSON that describes map objects. It tells a map:
- what kind of thing something is
- where it is located
Three shapes are used most often:
- Point — one location
- LineString / Polyline — a path
- Polygon — a closed area
GeoJSON is one of the easiest ways to turn ideas about places into data that a map can read.
Try changing the map object
Helpful hint: start by changing the title. Then change the coordinates. Then switch from point to line, or line to polygon.
What this is
What that means
This looks like GeoJSON, but the shape is incomplete or unusual.
A line is just a line until you attach meaning to it. That is how the same app can show a football play, a school bus path, a hiking route, a trade route, or a fault line.
📍 Point
A point marks a single location.
Examples:
- a café
- a mountain peak
- a museum
- a bus stop
{
"type": "Point",
"coordinates": [-122.3321, 47.6062]
}Important rule: GeoJSON uses longitude first, then latitude.
➖ LineString (Polyline)
A LineString is a sequence of connected points.
Examples:
- a hiking trail
- a migration route
- a shipping lane
- a historical journey
{
"type": "LineString",
"coordinates": [
[-122.3321, 47.6062],
[-122.3355, 47.6088],
[-122.3401, 47.6109]
]
}A line has a beginning and an end.
🔺 Polygon
A polygon is a closed shape that defines an area.
Examples:
- a park
- a lake
- a city boundary
- a wildfire perimeter
{
"type": "Polygon",
"coordinates": [[
[-122.3390, 47.6050],
[-122.3300, 47.6050],
[-122.3300, 47.6110],
[-122.3390, 47.6110],
[-122.3390, 47.6050]
]]
}Important rule: the last coordinate must match the first coordinate to close the shape.
📦 Feature and FeatureCollection
GeoJSON objects usually appear inside a Feature.
{
"type": "Feature",
"properties": {
"title": "Seattle",
"emoji": "📍"
},
"geometry": {
"type": "Point",
"coordinates": [-122.3321, 47.6062]
}
}Several features can be grouped together in a FeatureCollection. That lets one dataset include places, routes, and areas all at once.
🧭 Step 7 — Waypoints and routes
A waypoint is simply a meaningful location.
Examples:
- a campsite
- a historic event location
- a survey measurement point
- a chapter in a journey
Waypoints connected together can form a route.
That route might represent a migration path, a caravan trade route, a road trip, a river, or a story unfolding through time.
🧱 Step 8 — Geohashing
When maps contain millions of points, searching the whole Earth would be slow.
Geohashing solves this by dividing the planet into grid squares. Each square receives a short code.
9q8yyNearby locations often share similar prefixes. That makes it easier for software to quickly find nearby data.
🗂 Step 9 — Atlasemoji manifests
Atlasemoji organizes map objects using something called a manifest.
A manifest is a structured description of a map object. One manifest can generate several useful surfaces:
- GeoJSON
- a live map embed
- a postcard preview
- a static image
- an API response
This allows one piece of map data to appear in several useful contexts.
🖼 Step 10 — Static maps vs embedded maps
Sometimes you want a live interactive map.
That might appear inside a webpage using an iframe or a dedicated map view.
Other times you want a static image.
For example:
- a social media preview
- a printable map
- a postcard
Atlasemoji supports both live and static surfaces.
⚙️ Step 11 — Talking to a map with an API
An API is a way for software to ask another computer to do something.
For example:
- create a waypoint
- fetch a route
- generate GeoJSON
- produce a map embed
- render a static preview
Requests are usually sent using JSON. Responses often come back as JSON too.
Swagger, also called OpenAPI, provides a visual interface that lets developers explore and test those requests.
Step 12 — Before touching the API
Before you start using the Developer Workbench or Swagger, it helps to know:
- how to read JSON
- how to tell a point from a polyline
- that polygons must close
- that longitude usually comes before latitude in GeoJSON
- that one map object can have several useful surfaces
Once those ideas click, the API becomes a practical creative tool.
🧪 Map Experiments
Try small interactive lessons that show how map data works. Change an input, click a button, and watch the geometry appear on a real map.
Latitude / Longitude Flip Checker
Humans often say latitude then longitude. GeoJSON uses longitude first. Type a place, then flip it for the map.
Close the Polygon
A polygon must start and end with the same coordinate.
[ [-122.3390, 47.6050], [-122.3300, 47.6050], [-122.3300, 47.6110], [-122.3390, 47.6110], ????? ]
Mini Mission Builder
Build your first real map object. Choose a mission, fill in the blanks, and watch the geometry appear on the map.
Helpful hint: for points, the form uses latitude and longitude separately, but GeoJSON stores them as [longitude, latitude].
- A Feature with Point geometry
- Useful for landmarks, stops, sites, and single events
{
"type": "Feature",
"properties": {
"title": "Treasure",
"emoji": "🏴☠️"
},
"geometry": {
"type": "Point",
"coordinates": [
-122.3321,
47.6062
]
}
}Shape Classifier
- café
- museum
- bus stop
Layer Stack Demo
Maps are built from layers. Big shapes can cover smaller ones depending on which layer is drawn on top.
Geohash Bucket Explorer
Click a bucket. Nearby buckets often share similar prefixes. This is how software narrows the search before looking closely.
🧪 Step 13 — Practice Mission
Let’s try building a route. Long ago, Chumak traders from Ukraine traveled south to gather salt. Your mission is to represent that journey as a LineString.
- Kyiv: Latitude 50.45, Longitude 30.52
- The Steppe: Latitude 48.45, Longitude 32.05
- Salt Mines: Latitude 46.48, Longitude 30.72
Helpful hint: GeoJSON wants longitude first, then latitude.
- Flip the coordinates into GeoJSON order.
- Paste the sample into the editor.
- Look at the line and explain what kind of shape it is.
- Take the next step into the Developer Workbench.
🚀 Next step
Once these ideas feel familiar, the next tools become much more powerful.
Atlasemoji provides two main developer tools:
A friendly environment for experimenting with manifests, GeoJSON, embeds, static images, and map outputs.
The full Swagger / OpenAPI interface for inspecting routes, parameters, responses, and the Atlasemoji API contract.