Overview

The older OSM shapefile examples in the sibling workspace are a useful reminder that themed shapefiles remain common as an interchange format. The web map, however, usually wants something else:

• normalized fields
• simpler geometry
• consistent layer naming
• a format that performs well in the browser

Why it matters

• Raw shapefiles carry desktop-era constraints into web workflows.
• Browser maps do not need every field and every vertex.
• Publishing without schema cleanup leads to brittle layer logic.

When to use

Use this pattern when:

• receiving shapefile deliveries from consultants or public sources
• preparing web maps from desktop GIS archives
• publishing recurring layers into a static or low-complexity site

Inputs

• shapefile components or zipped shapefiles
• target layer list
• desired field schema
• simplification thresholds by layer family
• output target such as GeoJSON, PMTiles, or vector tiles

Workflow and method

1. Unpack Confirm .shp, .dbf, .shx, and projection metadata are present.
2. Inspect Review CRS, geometry type, field names, and record counts.
3. Normalize Rename fields, drop dead weight, and standardize types.
4. Simplify Reduce geometry complexity where cartographically safe.
5. Split Separate layers by use or zoom strategy.
6. Package Export web-ready GeoJSON or vector tiles.

Recommended logic

Suggested CLI layout

scripts/
  publishing/
    inspect_shapefile.js
    normalize_schema.js
    simplify_geometry.js
    build_tiles.js
data/
  incoming/
  staged/
  web/

QA checks

• Verify CRS before conversion.
• Compare bounding boxes before and after simplification.
• Confirm IDs survive into the publish layer.
• Inspect the output at multiple zoom levels in a browser map.

Outputs

Typical outputs:

• normalized GeoJSON
• vector tile package or equivalent publish artifact
• lightweight metadata note describing schema and simplification choices

Limitations

Some shapefiles are structurally messy enough that a quick pipeline will not save them. Broken geometries, weak CRS metadata, and overloaded attribute tables often require a dedicated cleaning pass before web packaging is safe.

Related pages