GeezerVison is showing mapbase.dev — Location search, down to the neighborhood Location search, down to the neighborhood.The full administrative hierarchy behind one API. Classify your inventory, filter search, and build browse pages from day one. 10k credits/mo, 1k/day — no card needed WHY MAPBASE Geography
breaks quietly.Your listings say “Lisboa”, your filters say “Lisbon”, your map says neither. Mapbase classifies everything against one canonical hierarchy you can search, drill, and resolve. 01DATA DRIFT· locations Classify your inventoryTag every listing, store, or asset with one stable ID — countries down to parishes. Stable IDsnot fuzzy names 02YOUR TERRITORIES· zones Your territoriesDelivery areas and sales regions, linked to the official hierarchy once approved. Custom + officialsame registry 1200-203 28013 00184 4050-073 08002 20121 9000-052 46002 80133 03FLAT LISTS· postcodes Postcodes that joinEurostat codes linked to locations — searchable like everything else. Linkedto locations seo-page url/pt/lisboa/… titleLisboa · Mapbase json-ldPlace + Breadcrumb 04PROGRAMMATIC SEO· seo Programmatic SEO pagesBreadcrumbs, meta, and JSON-LD from the same place data. 1 pageper place TWO WAYS INLisboalocations 1200-203postcodes delivery-southzones 05SEARCH Search the registryAutocomplete and browse at every level — district, municipality, parish. One boxevery level resolve.json lat38.7139 lng-9.1394 countryPT regionLisboa parishSanta Maria Maior postcode1200-203 06RESOLVE Resolve any pointCoordinates in; location and zone context out. One callfull hierarchy Search by text. Resolve by coordinate. Same IDs everywhere. A real-estate metasearch classifies its entire inventory with Mapbase — giving users the same district-to-neighborhood search as the market's biggest portals. BUILT TO SHIP, ANY USE CASE Ship product logic,
not geo infrastructure.01 Integrate in hoursTyped SDK, REST, and UI blocks — not a geo project. 02 No fuzzy matchingStable IDs replace fragile string compares. 03 Same stack, every layerOne ID model across search, resolve, and boundaries. 04 Custom zones, enrichedApproved catchments join the same hierarchy. The alternative is a data team Cheaper than building — and far cheaper than maintainingThe data is technically free. Turning it into a linked, queryable, always-current registry is months of engineering up front — and a permanent maintenance tax after. Mapbase starts at €0 with paid plans from €20/mo. Build it yourself Your geo stack, your problem- Ingest and reconcile CAOP, INE, Eurostat, and GISCO releases — each with its own format, projection, and quirks
- Run and tune a PostGIS cluster: spatial indexes, geometry validity, vacuum schedules
- Build a simplification pipeline so boundaries are light enough to ship to browsers
- Link postcodes to administrative hierarchies yourself — none of the sources do it for you
- Re-run everything when sources publish updates, and migrate every ID that changed
- Keep an engineer on call for the geo stack instead of your product
Months to first query — then forever to keep current Use Mapbase Our geo stack, your product- One API key — the registry, boundaries, postcodes, and zones are already built and linked
- Sources ingested, reconciled, and refreshed for you; IDs stay stable across releases
- Boundaries pre-simplified and served as GeoJSON or polyline, ready to render
- Typed SDK, installable UI blocks, and playgrounds — integration is hours, not quarters
- Credit-weighted pricing that scales down to zero
€0 to start · 3,000,000 credits / mo on Scale Search and resolve any location in real time Click to try the live demo Works with your provider Keep Google.
Add meaning.Mapbase isn't a rip-and-replace. Geocoders turn text into a point — Mapbase turns that point into canonical geography. Run it standalone, layer it on your existing provider, or route every source through one client. step 01 Your providerGoogle · Geoapify · yours "Rua Garrett 27" → lat/lng step 02 Mapbase resolvepoints.resolve point → canonical registry step 03 Canonical answerhierarchy + boundary + ID district → municipality → parish step 01 Your provider Google · Geoapify · yours "Rua Garrett 27" → lat/lng step 02 Mapbase resolve points.resolve point → canonical registry step 03 Canonical answer hierarchy + boundary + ID district → municipality → parish StandaloneNo third party required /v1/autocompleteMapbase autocomplete and resolve, end to end. Canonical locations, postcodes, and zones — searched, resolved, and rendered from one API key. /v1/autocompleteTry autocompleteLayered on GooglerecommendedKeep your existing UX /v1/points/resolveKeep Google Places (or Geoapify) for text search. Pipe the selected point through points.resolve and get back what they don't return — the full administrative hierarchy, real boundaries, linked postcodes, and stable mb_ IDs. /v1/points/resolveTry resolvePassthrough, BYO keyOne client, every source /v1/providers/{google,geoapify}/*Call Google and Geoapify through Mapbase's provider routes with your own key — one SDK, one response shape, normalized results. Your key is forwarded per request and never stored. /v1/providers/{google,geoapify}/*Provider routes// 1. Your Google Places flow stays exactly as it is
const place = await googleAutocomplete(query)
// 2. One extra call turns its point into canonical geography
const { data } = await mapbase.points.resolve({
lat: place.lat,
lng: place.lng,
})
data.anchor.id // "mb_loc_01HXYZAB8R" — stable forever
data.hierarchy // district → municipality → parish
Two lines after your existing autocomplete. No migration, no new UX — just answers Google doesn't give you. live 🇵🇹Portugal Distritos, concelhos, freguesias — every place with its own page. mapbase.dev/ptlive 🇪🇸Spain Comunidades, provincias, municipios — browsable and indexable. mapbase.dev/eslive 🇮🇹Italy Regioni, province, comuni — the full hierarchy as landing pages. mapbase.dev/itlive 🇬🇧United Kingdom Nations, regions, counties, councils, and wards — plus towns, parishes, and protected landscapes. mapbase.dev/uklive 🇫🇷France Régions, départements, arrondissements, communes — plus cantons as zones. mapbase.dev/frMore to come. Ready to ship?Keep your geocoder or go all-in — either way, claim a key, hit the API, and be in production before lunch. 10k credits/mo, 1k/day — no card needed |
