knoflook/cctv-010
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: explain working-data

Browse Source
This commit is contained in:
knoflook 2025-02-24 00:35:08 +01:00
parent 91a7ca23fe
commit b60093cddb
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -12,5 +12,4 @@ this is a WIP, the current structure of repo is as follows:
- `query-header` and `query-footer` - don't worry about it too much, this is used by `scripts/03-build-query-for-district` which includes the header and footer in every file it generates. You'll need to play with this if you choose to run these scripts for a different city, because that's where Rotterdam is coded in.
- `scripts/` - the heart of this repo. A set of bash scripts using some basic unix utils and the Overpass API to parse the source data and return jsons that can be converted into geojson. They should be ran in order, starting from `01-sed-to-single-line`, till `05-show-missing-streets`. Each of them will take data from the previous one and output to `working-data/its-own-number` so you can inspect the data at every step of the process.
- `geojson-files/` - QGIS, which I use to assemble the maps accepts data in geojson format. This is where those files should land. Think of it as the output directory of this program. This is not populate by any script. You have to run `for i in working-data/04/*; do osmtogeojson "$i" > "geojson-files/$(basename $i)"; done` from the root dir of this repo to get those files, and `osmtogeojson` is a node.js program that you obtain by running `npm install osmtogeojson`
- `working-data` - this is where each script outputs its data. Ideally you don't need to look into here, except for debugging. one interesting place is `working-data/05` which contains all the places that were requested from the overpass api but didn't return for one reason or another.