Setting up translations takes fewer clicks now.
A round of polish on New project after using it every day ourselves.
Publishing now covers the whole project, and a bad publish can be undone.
We ran the spatibase command through a real project from a link code and smoothed every rough edge we hit.
--match-by or language stops the import and names what does exist. Properties that would be dropped are listed.--publish publishes only this run, never other drafts of the type.verify lists them apart and import says they stay hidden until you switch them on.model --preview and import --dry-run with images change nothing and report what would happen.spatibase settings renames a project and adds languages without touching the default. spatibase tools lists what the key can do.spatibase settings --add-locale de
spatibase tools search_draftsOne page now does every pair, instead of a page for each. Open the converter, or see all free tools.
We wanted the shortest way from New project to a map you can put things on, so New project is now a screen with the map right beside it.
Two questions map projects ask all the time now have their own answer in the API.
contains=lng,lat returns the areas that cover the spot. Zones drawn in a field work too, see the delivery area check.nearest=lng,lat lists places closest first with their distance, no radius needed. Ready for a store locator.GET /delivery/v1/projects/{id}/entries?contains=14.42,50.08
GET /delivery/v1/projects/{id}/entries?nearest=14.42,50.08&limit=5You no longer need a whole dataset when you only need your own country.
New project now has From your data, so moving a spreadsheet, map or database over isn’t a project of its own. See create a project.
In Collect on a phone, scrolling the entries list used to grow or shrink the whole sheet.
You can now delete your account under Settings → Profile → Delete account.
If your app keeps its places in a JSON file or a list in the code, your coding agent can move them for you.
spatibase.Show every visitor your places in their language, without a field per language or a copy of every place. How translations work.
?locale=de. Untranslated text falls back to the default, and the response says so.
The top of the Analytics page now tells you something instead of listing counts.
Two small touches so things stay easy to see in light and dark.
The AI agents page has a second path, for building your own map or website on your published content.
Collect on your phone now tells you only what needs you.
The Content model and Media library now look like the API and AI agents pages.
Got a route from a GPS watch or a boundary from a colleague? Drag the file onto Location on the map in the entry.
Edit an entry and the change is saved to its draft on its own.
Fixing one field on 40 entries no longer means opening them one by one.
More in find, edit and export entries.
The map on Entries and everywhere else is calmer.
The New project dialog is wider and starts with a clear choice. See how to create a project.
Every public project has a preview page. Open it from the project menu with Preview data.
Try the demo projects.
Jump to another project and you land on the same section, Analytics to Analytics.
The free converter list just got ten longer. KMZ to Shapefile and KMZ to GPX open a KMZ directly, so you don’t have to unzip it first, and GPX to KMZ packs a track into one small file you can open in Google Earth. We also added CSV to KML, KML to GeoJSON, GeoJSON to KML, GeoJSON to Shapefile, GeoJSON to CSV, GPX to GeoJSON and GPX to CSV.
We picked them after seeing which conversions people kept looking for. Like the other tools, they run in your browser, your file never leaves your computer, and every page has a sample you can try first.
Our first public dataset is out: 9,095 airports from OurAirports, with IATA and ICAO codes, type, elevation, country and region. It’s public domain, served from a public API with no key, filterable (try filter[iata_code]=PRG), and downloadable as CSV or GeoJSON.
The part I like most is Copy into your account. It puts the whole dataset into a new project of yours, already published, with its own API address. From there you can serve it as it is, or add what your app needs, like lounge info, photos or your own descriptions. Signed in already? You’ll find it under New project → Start from a public dataset.
Until now the free tools ended with “download the GeoJSON, then import it”. Now there’s a Save to Spatibase button instead. It opens Spatibase in a new tab and brings the file along, straight from your browser, so nothing is uploaded anywhere until you press Import. If you don’t have an account yet, you sign up first and the file waits for you in the same browser.
You land in a new project with the import already set up, the fields suggested from your file. One more click publishes it, and you get a live GeoJSON address to copy into your site or app. Signed in already? Pick which project it goes to.
Every map library wants its bounding box in a slightly different order, and mixing them up puts your data in the ocean. The new bounding box finder lets you draw a box, use the current map view, search a place, or paste a box you already have in almost any format. It works out the order, and offers a swap when both readings make sense.
Then copy it the way your code expects: west, south, east, north, GeoJSON, WKT, Leaflet, MapLibre, OpenLayers (also in metres), Overpass, ogr2ogr or a Spatibase bbox= query. Boxes that cross the 180° meridian work too, and each format says how it handles them.
Open the bounding box finder | Filter entries by a box with the API
Eight new free tools, one for each pair of formats people kept asking about: KML to shapefile, shapefile to KML, shapefile to GeoJSON, GPX to KML, KML to GPX, KMZ to KML, KML to KMZ and KML to CSV. Drop a file, see it on a map, and download the converted file. Your file never leaves your computer.
We took care of the parts that usually go wrong. Shapefiles in a local grid like UTM are moved to longitude and latitude using their .prj, including older datums that other converters place a hundred metres off. A KML with points, lines and areas becomes a zip with one shapefile layer for each. Every page says what the conversion keeps and what it can’t carry over, such as styles or the time of each GPS point, so nothing gets lost without a note.
Our second free tool. Drop a spreadsheet, an Excel .xlsx, CSV or TSV, and every row with a latitude and longitude shows up on a map. It reads European files too (semicolons, decimal commas like 41,3874), keeps numbers as numbers and postcodes like 08001 as they are, and tells you which rows it couldn’t place and why, so you can fix them in the sheet. Download the result as GeoJSON or KML for Google Earth. It reads columns the same way our import does, so a sheet that works here imports into Spatibase the same way.
Developers get the same engine on its own page, with the few lines of code to do it yourself. And every tool now has a “Download the sample” link next to “Open a sample”, so you can grab the exact file you just saw and try it in your own apps.
When a GeoJSON file won’t load, “invalid” isn’t much help. Paste it or drop the file, and the new validator lists every problem in plain words with its line number: an outline that isn’t closed, coordinates written as text, rings that run the wrong way round, a leftover crs. Most come with a one-click fix, or press Fix all, and the text is checked again after every fix, so what you download is what you see on the map.
It also tells you whether the file will import into Spatibase, using the same rules as the import itself, and which features would be skipped and why. If your points land on the wrong continent, Swap longitude and latitude puts them back. Your file stays in your browser.
Search for a place or click the map, set a distance, and the new radius map draws the area around it. The circles are true on the ground: every point of the edge is that distance from the centre, which is why big circles look stretched toward the poles. Add as many as you need (up to 50), name them, mix kilometres, miles and nautical miles, and drag a centre or the edge to adjust.
The whole map lives in the link, so Copy link is all it takes to share it, and you can download the circles as GeoJSON, KML or CSV. It’s straight-line distance, not travel time.
Someone sends you a shapefile and you just want to know what’s in it. Now you can drop the zip, or the .shp, .dbf and .prj together, and see it on a map with every field in a table below. Click a shape to read its values. Nothing is uploaded, and there’s nothing to install.
For each layer, “About this file” says the shape type, how many features there are, which coordinate system the .prj names and that it was moved to longitude and latitude, the text encoding (so you know why names might look garbled), and each field’s type and size. You can save the data as GeoJSON, CSV or KML.
Our first free tool. Drop a KML or KMZ file on the page and see its places, lines and areas on a map, with a list of every feature and its folder. Download it as GeoJSON or CSV (with latitude, longitude and WKT), copy the GeoJSON, or get the KML out of a KMZ. The file is read in your browser and never leaves your computer, and you don’t need an account. To keep the places in Spatibase, import the GeoJSON into a project.
The Content Delivery API now describes itself. The generic OpenAPI 3.1 document is open without a key. Each project also has its own typed file, /delivery/v1/projects/<id>/openapi.json, that knows your types and fields, so a generated client autocompletes filter[rating][gte] and your field names. Both cover entries, GeoJSON, tiles, files and webhook messages, and import cleanly into Postman and Bruno.
The map your editors work on can now look like the map your visitors see. Each project picks a basemap: Streets, Terrain, Light or Dark (with a Blueprint switch for a quieter look), or your own MapLibre style as a URL or JSON. On desktop, a “Show my location” button centres the map on where you are.
Collect brings Spatibase to the field. Open it in the phone’s browser (or install it from there, no app store), pick a project, and add entries with your GPS position or a tap on the map, photos from the camera and the same fields as on desktop. The entry you’re working on stays on the device if the signal drops. It needs a connection to open; it isn’t a fully offline survey app.
Setting up a content model is faster: the new element dialog groups the field kinds and lets you search them, keeps one draft per kind (a dot shows which are filled in and which need fixing), and creates every ticked one in list order.
Every sign-in email now includes a 6-digit code next to the link. Type it into the sign-in page when the link would open in the wrong place, for example in an installed phone app that keeps its own cookies. The link and the code work once and expire after 15 minutes.
Start a new map from one you already have. Duplicating always copies the content model; you choose whether entries, groups, media files and the published state come along. Members, API keys, the webhook and AI assistant connections are not copied, and you become the copy’s owner.
Teams can now work together properly. Invite people by email as an Owner, Editor or Developer, each with their own permissions. Webhooks are signed, so your site can check that a message really came from Spatibase. And in the entry list you can select many entries and publish, unpublish or delete them in one go.
A blank project is no longer the only way in. Pick the Store locator, Trails & outdoor spots or Events map template and you get a ready content model, sample places and a group, so you can see the editor and the API working in seconds and then replace the samples with your own data.