Map of Boutcham in GeoJSON-Seq format
A map built from OpenStreetMap data, ready to download
Customize the map
Open this place's area in the constructor and adjust everything to your needs
Open in constructor →Map passport
What this map contains by default
This is how the map is built as-is — every setting can be changed in the constructor.
About GeoJSON-Seq
Map of Boutcham in GeoJSON-Seq: 13 km of roads — in the WGS 84 coordinate system, units are meters.
Which layers are in the file
This file for the selected area contains:
- Roads
Geometry by layer
- Roads — lines (LineString) with OpenStreetMap tags
What the file carries
The GeoJSON-Seq file for Boutcham: the whole map comes as a single file, the file is plain text and opens in any editor, all features lie in one collection, and the source layer name stays in the _layer field, OpenStreetMap tags are kept as feature attributes.
File size
The expected size of the GeoJSON-Seq file for Boutcham is about 1.3 MB; the exact size depends on the chosen layers and area.
Coordinate systems
WGS 84 (EPSG:4326), selectable in the wizard
Units
Meters (projected in the chosen coordinate system)
| Category | GIS |
| File extension | .geojsonl |
| Tier | Open Beta |
How to use GeoJSON-Seq for Boutcham
- jq — jq -c 'select(.properties._layer=="roads")' map.geojsonl > roads.geojsonl filters out the layer you need without loading the file into memory.
- Tippecanoe — tippecanoe -o map.mbtiles map.geojsonl builds vector tiles: the line-based format is its native input.
- QGIS and ogr2ogr — GDAL reads GeoJSONSeq out of the box: ogr2ogr -f GPKG out.gpkg map.geojsonl.
Programs that open GeoJSON-Seq
FAQ: GeoJSON-Seq for Boutcham
How is GeoJSON-Seq different from GeoJSON?
In GeoJSON-Seq each line is a separate feature. You can read line by line without loading the whole file.
Where is GeoJSON-Seq used?
In streaming systems, Kafka, Spark, and for processing via jq/ndjson.
How is .geojsonl different from .ndjson and .geojsons?
In essence, not at all: these are different extensions for the same thing — one feature per line. We hand out .geojsonl, and if you need to, the file can simply be renamed.
How do I tell which layer a feature came from?
Every feature has a _layer property with the name of its source layer: roads, buildings, water and so on. It takes the export apart in a single jq command or a GeoPandas filter.
Can such a file be opened straight in a browser map?
Not directly: Leaflet and Mapbox expect a single FeatureCollection object. Assemble it from the lines on the client or at project build time — or take ordinary GeoJSON.
