GIS File Converter (SHP, KML, GPX, GeoJSON, DXF)

What this converter does

GIS data moves between different software in different formats. A field crew records GPX, a municipality asks for a Shapefile, someone using Google Earth expects KML, and the design team works in DXF. This tool converts between Shapefile, GeoJSON, TopoJSON, KML/KMZ, GPX, CSV, Excel, WKT, GeoPackage and DXF in any direction. In the same step you can change the coordinate system, drop or rename attribute fields, and convert several files at once into a single zip.

How to use it

1. Choose files or drag them onto the page. For a Shapefile, select the .zip, or the .shp, .dbf, .shx, .prj and .cpg files together. You can also paste GeoJSON, KML, WKT or CSV text.
2. Check the feature count, geometry types, source coordinate system and character encoding in the summary report. If the system could not be read from the file, choose it from the list. For CSV and Excel you can change the X, Y or WKT column.
3. Choose the output format and the target coordinate system.
4. In the field mapping table, untick the fields you do not need and set a new name or type where required.
5. Press "Convert and Download". A single output downloads directly; several outputs come as one zip.

Popular conversions

KML to SHP

Points, paths and polygons drawn in Google Earth are written to separate Shapefile layers by geometry type, and the KML ExtendedData fields become DBF columns. Choose a projected target system and the output is projected straight away. Convert KML to SHP.

SHP to KML

The coordinate system in the .prj file is read and the coordinates are transformed to WGS84; attributes appear in the Google Earth balloon. Convert SHP to KML.

GPX to KML and KML to GPX

GPS tracks and waypoints are kept, and GPX to GPX conversion also carries the track point times. GPX has no polygon type, so KML polygons are written to GPX as tracks. Convert GPX to KML or KML to GPX.

GeoJSON to SHP and Excel to KML

GeoJSON with mixed geometry is split into point, line and polygon layers. Latitude and longitude, or easting and northing columns in an Excel or CSV table are found automatically. GeoJSON to SHP, Excel to KML.

Coordinate systems and character encoding

The source system is read from the .prj file, the GeoJSON crs member or the GeoPackage definition; if none is present, the coordinate range is used. A file with eastings around 500,000 can belong to any Transverse Mercator or UTM zone, and the zone cannot be derived from the file, so you have to choose it. The target list covers WGS84, Web Mercator, WGS84 UTM zones and the systems used in Türkiye (ITRF96/TUREF 3° TM, ED50 TM and UTM); you can also enter any EPSG code or a proj4 definition. ED50 is transformed with the EPSG:1784 (ED50 to WGS 84, Türkiye) parameters, accurate to about 2 metres.

The DBF encoding is taken from the .cpg file first and then from the language driver byte in the DBF header. If neither exists, UTF-8 is used when the content is valid UTF-8, and a local code page otherwise; you can override this under Advanced options. Output can be written in UTF-8 or Windows-1254, and a .cpg file is always included.

Data and method

Files are read, converted and written in your browser; their contents are not sent to any server. Only the library files are downloaded from jsDelivr, and the preview basemap tiles from Esri and OpenStreetMap. Libraries used: proj4 2.9.0, JSZip 3.10.1, PapaParse 5.4.1, shpjs 6.1.0, sql.js 1.14.2 and dxf 5.3.1 (MIT), @tmcw/togeojson 5.8.0 and Leaflet 1.9.4 (BSD-2-Clause), topojson-client 3.1.0, topojson-server 3.0.1 and Lucide (ISC), SheetJS xlsx 0.18.5 (Apache-2.0). The Shapefile, GeoPackage, KML, GPX and DXF writers were written for this tool. GeoPackage output uses the gpkg_spatial_ref_sys, gpkg_contents and gpkg_geometry_columns tables and the standard geometry blob from the OGC specification.

Limitations

• When reading DXF, points, lines, polylines, arcs, circles, ellipses, splines, text and entities inside blocks are converted; hatches, dimensions and 3D surfaces are not. DXF does not carry a coordinate system.
• A Shapefile holds one geometry type per file; field names are limited to 10 characters and text values to 254 bytes.
• Curve geometries and raster tiles in a GeoPackage are not converted.
• File size is limited by browser memory; files with hundreds of thousands of features can take a while.

For organisations

If you need regular, standardised conversion between CAD and GIS or a custom conversion workflow for your team, see the Rodosto Teknoloji website or get in touch.