No processing of your file contents takes place on any server. You need no data-processing agreement with gottrix to handle confidential or business documents.
Servers in GermanyGDPR by design
Origin servers at Hetzner in Germany. Since your files never leave your device, their contents are not transmitted at all.
A Shapefile is the classic GIS format from ESRI, actually a set of files (.shp geometry, .dbf attributes, .prj projection and more). This tool reads a Shapefile - easiest as a .zip containing those parts - and converts its points, lines and polygons, together with their attribute table, into a single GeoJSON FeatureCollection.
GeoJSON is the open, web-friendly standard understood by Leaflet, Mapbox, QGIS, PostGIS and most mapping tools. Drop the zipped Shapefile and get a .geojson file you can load directly into a map or a data pipeline, with attributes preserved as feature properties.
Everything runs entirely locally in your browser (no upload, even offline) - your data never leaves your device. Coordinates are passed through as stored; if the Shapefile is not in WGS84 (longitude/latitude), reproject it first, since GeoJSON expects WGS84.
Specifications
Specifications
Input formats
ZIP, SHP
Output format
GEOJSON
Batch processing
No
Processing
Locally in your browser (JavaScript)
File upload
None
In 3 steps
Drop the .zip Shapefile bundle (or a .shp file).
Its geometry and attributes are read in your browser.
Download the GeoJSON (.geojson) file.
Limitations:Reads a Shapefile (best as a .zip bundle with .shp/.dbf/.prj) into a GeoJSON FeatureCollection, with attributes kept as feature properties. Coordinates are passed through; non-WGS84 data should be reprojected first, since GeoJSON assumes WGS84.
FAQ
Is my data uploaded?
No. The conversion runs entirely locally in your browser - even offline. Your data never leaves your device.
Which file do I provide?
Best a .zip containing the Shapefile parts (.shp, .dbf, .prj and more); a single .shp also works but lacks attributes and projection.
Are the attributes kept?
Yes. The attribute table becomes the properties of each GeoJSON feature.
What about the projection?
GeoJSON expects WGS84 (longitude/latitude). Coordinates are passed through unchanged, so reproject a non-WGS84 Shapefile first.