GeoJSON, Shapefile, DXF, GML, KML and CSV formats.
Every dataset ships in seven formats from one set of polygons — GeoJSON for web maps, ESRI Shapefile (.shp) for desktop GIS, DXF for CAD, GML, KML and CSV. Nothing is approximated except the DXF, which is projected to metres and simplified to about 45 m so it behaves in AutoCAD. Everything else is the full source geometry.
.geojsonRFC 7946, the reference version of the data.
.shpWith .shx, .dbf, .prj and .cpg — UTF-8 attributes intact.
.svgOne group per division, keyed by its code; names in a hideable layer.
.dxfR12 ASCII, projected to metres, simplified to ~45 m.
.gmlOGC GML 3.2, lat/lon axis order.
.kmlStyled for a readable default view.
.csvUTF-8 with BOM, so Excel shows Chinese correctly.
Fields on every feature
Each format carries the same attributes. The shapefile's DBF uses the same names, shortened only where the ten-character field limit forces it.
| Formats | GeoJSON · SHP · SVG · DXF · GML · KML · CSV, one zip |
|---|---|
| Coordinate system | WGS 84 · EPSG:4326 · decimal degrees |
| Geometry | MultiPolygon — one feature per division |
| Codes | 6-digit GB/T 2260, e.g. 440300 |
| Names | name_en and name_zh on every feature |
| Hierarchy | province_code → city_code → code |
| Extras | parts, center_lon, center_lat, bbox |
| Licence | Commercial use, one organisation, no attribution required |
| Delivery | Instant download; links re-issued whenever you open them |
| Data current to |
About the DXF
CAD does not want degrees: a line weight in millimetres against a coordinate in degrees is meaningless, and offsets snap to a grid no one can use. The DXF is therefore written in metres, projected with Lambert Conformal Conic, standard parallels 25° and 47°, central meridian 105°, on WGS 84. The proj string is:
+proj=lcc +lat_1=25 +lat_2=47 +lat_0=35 +lon_0=105 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs
Geometry is simplified with Douglas–Peucker at roughly 45 m. That is invisible at print scale and keeps a national county file openable. If you need CAD output at full resolution, convert from the shapefile or GeoJSON with your own projection instead.
About the GML
GML 3.2, and the coordinates are written latitude first, longitude second. That is the axis order EPSG:4326 actually defines, and writing longitude first under that srsName is the classic reason a GML file opens rotated in GeoServer. GDAL, PostGIS and ArcGIS read this ordering correctly.
A feature, as delivered
{ "type": "Feature",
"id": "440300",
"properties": {
"code": "440300",
"level": "city",
"name_en": "Shenzhen City",
"name_zh": "深圳市",
"province_code": "440000",
"province_en": "Guangdong Province",
"province_zh": "广东省",
"parts": 1,
"center_lon": 114.06,
"center_lat": 22.55,
"bbox": [113.75, 22.39, 114.63, 22.87]
},
"geometry": { "type": "MultiPolygon", "coordinates": [ ... ] }
}