Reading your GeoJSON
mapverter accepts a FeatureCollection, a single Feature or a bare geometry, saved as .geojson or .json. Coordinates are read as WGS 84 longitude and latitude. Older files with a crs member, such as urn:ogc:def:crs:EPSG::5186, are read in that coordinate system instead when it is one mapverter knows. A Feature id is kept as an id attribute.
Fitting properties into a DBF table
- Property names longer than 10 bytes are shortened, and duplicates get
_1,_2endings.field_names.csvin the ZIP maps each shortened name to the original. - Objects and arrays are written as JSON text. Text longer than 254 bytes is cut, and the report counts how many values were affected.
- Properties whose values are all numbers become numeric fields.
- simplestyle properties such as
strokeandfillare not stored, and the report counts the features that had them.
Geometry rules
- When the data mixes points, lines and polygons, each type gets its own Shapefile in the ZIP.
- A GeometryCollection is split into one feature per geometry type, each with the same attributes.
- Features with a null geometry are left out, and Z values are removed. Both are reported.
- The Shapefile starts in the source coordinate system. You can switch the target to WGS 84 or Web Mercator (EPSG:3857), or open a coordinate system page that presets another one, and the ZIP gets a .prj for the system you use.