Convert GPKG to GEOJSON
Turn GPKG files into GEOJSON. A GeoJSON FeatureCollection in WGS 84 longitude and latitude, as the GeoJSON standard asks, with each feature's attributes as its properties.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop GPKG files on the dialor turn it to pick what to do
Map layers as one GeoJSON file.Every feature lands in a FeatureCollection in WGS 84 longitude and latitude.
What you get
One GeoJSON file holding a FeatureCollection. Each feature keeps its attributes as its properties, so the data behind the map comes along with the shapes.
The coordinates are in WGS 84 longitude and latitude, as the GeoJSON standard asks.
What changes
Coordinates in another system are converted to WGS 84. A GeoPackage in Korea's EPSG:5186, for example, comes out in longitude and latitude.
If a GeoPackage holds several layers, they are joined into one collection. Each feature gets a layer column that names the layer it came from, so you can still tell them apart.
Data with no coordinate system
When the data names no system, it is taken as WGS 84 if its coordinates fit. If they do not fit, the conversion stops with
unsupported_elements.To go the other way, use GEOJSON to GPKG.
GPKG and GEOJSON.What each format is.
The formats
GeoPackage
The OGC GeoPackage, a SQLite database of map layers that QGIS and ArcGIS read and write.
- Extensions
- .gpkg
- MIME type
- application
/geopackage +sqlite3 - Kind
- Text and data
GeoJSON
Points, lines and polygons as JSON, the web's map data format.
- Extensions
- .geojson
- MIME type
- application
/geo +json - Kind
- Text and data
In your code.The same GPKG to GEOJSON conversion through the API, for your app or your agent.
$ cv convert report.gpkg report.geojson$ cv convert report.gpkg report.geojsonQuestions.What people ask about GPKG to GEOJSON.
Only if they are not already in WGS 84. Coordinates in another system, such as EPSG:5186, are converted to WGS 84 longitude and latitude.
The layers are joined into one FeatureCollection. A layer column on each feature names the layer it came from.
Yes. Each feature's attributes become its properties in the GeoJSON.
The file names no coordinate system, and its coordinates do not fit WGS 84. The conversion stops instead of guessing.