API & MCP

Everything a person can do on GISela Shapefile to GeoJSON, a program or AI agent can do with the same inputs and get the identical result.

HTTP API

GISela Shapefile to GeoJSON

Reads a zipped ESRI shapefile with GISela’s own parser — points, lines, polygons with holes, multipoints, Z/M records flattened to 2-D — with its attribute table (dBASE, code page from .cpg or the header) and the coordinate system from the .prj file, and writes GeoJSON. Several shapefiles in one ZIP give several files.

Inputs of GISela Shapefile to GeoJSON
FieldTypeDefaultDescription
filefile—Shapefile (ZIP). A ZIP with at least the .shp file; .dbf (attributes), .prj (coordinate system) and .cpg (text encoding) are read when present.
fromtext"auto"Coordinate system of the shapefile. “auto” = from the .prj file. Without a .prj the coordinates are read as WGS 84 unless you give an EPSG code.
toselect (EPSG:4326, EPSG:4258, EPSG:3857, EPSG:3035, EPSG:2056, EPSG:21781, EPSG:27700, EPSG:31466, EPSG:31467, EPSG:31468, EPSG:31469, EPSG:25831, EPSG:25832, EPSG:25833)"EPSG:4326"Write GeoJSON in. RFC 7946 GeoJSON is WGS 84; other systems are written with the older “crs” member.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

{
  "mcpServers": {
    "gisela-shapefile-to-geojson": { "type": "http", "url": "https://giselashapefiletogeojson.usefulweb.site/mcp" }
  }
}