Upload GeoJSON, shapefiles, KML or a spreadsheet of coordinates. Style it until it explains itself, run the analysis right next to the map, and share the result as a link, an embed or an API call — no desktop GIS, no export-and-email round trip.
One place to hold the data, the styling, the analysis and the thing you actually send to someone.
Every layer carries its own symbology. Paint it flat, split it by the values of a property, or grade a numeric column into classes with quantile or equal-interval breaks. Ramps are stored by name rather than by hex, so one saved style reads correctly in both the light and the dark theme.
Buffer, dissolve, clip and intersection each write a new derived layer instead of overwriting the one you started from. The chain stays visible: style any step, run the next operation on its output, publish whichever layer answers the question.
Build a weighted model out of the layers already in the project: metres to the nearest competitor, how many POIs sit inside a radius, a numeric attribute of the area a point falls in. Every factor carries a weight and a direction, and none of your business logic is buried in the formula.
A grid ranks its cells against each other; a pin rates one place against its layers. Padar tells you which scale you are reading rather than blending the two.
A shared catalog project ships the boundaries most Indonesian analysis starts from: provinsi at both the current 38 (OpenStreetMap) and the 2022-era 34 (OCHA's COD-AB), 522 kabupaten/kota, population joined on, health facilities across every province from OpenStreetMap, and terrain. Every dataset records its source, licence and retrieval date — and anything whose terms are unclear does not ship at all.
Publish a map as a hosted page, or drop it into any site with a single iframe. An embed link carries its own token, so a reader needs no account and sees only the layers you published. The whole studio is an HTTP API underneath, so the same map can be built, refreshed or retired from a script.
Each organization owns its own projects, layers and members. Nothing crosses an org boundary by accident.
Owner, editor, viewer. The role is checked on every write in the API, not merely hidden in the interface.
Org-scoped keys, shown once and revocable at any time, for the pipeline that keeps a layer fresh.
Sign in to a workspace you already have, or create an account and start from the open-data catalog.