All comparisons
Compare
Google Places tells you the address.Mapbase tells you which locations it belongs to.
You do not have to rip out Google. Pipe the coordinates or place_id through Mapbase and get canonical IDs, INE-aligned hierarchies, and boundaries your product can filter on.
10k credit-weighted ops/mo, 1k/day — no card needed
Google Places
Best-in-class geocoding UX — not a location registry.
- Global address autocomplete UX
- Familiar place_id identifiers
- Street-level geocoding worldwide
- No stable admin hierarchy across PT, ES, IT
- place_id is opaque — not a joinable location registry
- No pre-linked postcodes, LAU regions, or zones
- Boundary polygons require separate tooling
+ Mapbase layer
Canonical registry for PT, ES, IT — complements Google, does not replace it.
- Canonical mb_loc_* IDs that survive source updates
- Point resolve → full administrative hierarchy in one call
- Real boundaries as GeoJSON or polyline
- Works standalone or layered on your existing Google flow