Lat·Lng vs the alternatives

We're not the only way to convert geospatial files — and for some teams, a free tool or an enterprise ETL suite is the right call. Here's an honest read of where each option wins and loses, so you can make the decision that fits your stack.

CapabilityLat·Lng (Browser + REST API, Free / €49/mo / Custom)Mapshaper (Browser-only, Free, OSS)MyGeodata (Web app + REST API, Free trial / €30–500+/mo)FME (Desktop + Server, From ~$1,500/yr/seat)ogr2ogr (CLI, Free, OSS)
Read GeoJSON / KML / Shapefile / GPX / CSVYesYesYesYesYes
Read TopoJSONYesYesYesYesNo
Read GeoParquetYesNoNoYesYes
Read FlatGeobufYesNoNoPartialYes
Write Shapefile (with .prj)YesNoYesYesYes
Write GeoParquetYesNoNoYesYes
Drag-and-drop in browser, no installYesYesYesNoNo
REST APIYesNoYesPartialNo
Typed SDKs (Node + Python)YesNoNoNoNo
Scheduled workflows (cron / S3 / webhooks)YesNoYesYesNo
Batch convert 100s of filesYesPartialYesYesYes
RFC 7946 GeoJSON validation on outputYesPartialNoPartialNo
Auto-detect CRS from .prj / filenameYesNoYesYesNo
Reproject between any of 8,112 EPSG codesYesNoYesYesYes
Files never leave the browser by defaultYesYesNoNoYes
Signed DPA availableYesNoPartialYesNo
EU data residencyYesYesNoYesYes
SAML / OIDC SSOYesNoNoYesNo
Free tier good for one-off conversionsYesYesPartialNoYes
Predictable monthly pricingYesYesYesNoYes

Pick by use case

Where Lat·Lng fits

Teams pick us when they need browser-side privacy for ad-hoc conversions, a real REST API and typed SDKs for pipeline integration, and a signed DPA + SSO for procurement. If you only need to convert a KML once or twice a year, mapshaper is great. If you have a $50K/year ETL budget and a graphical-workflow team, FME is fine. We sit in the middle.

See pricing · Talk to sales