Geojsonl: zero bytes although source geojson is formatted correctly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 71
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
I'm attempting to run the estimate service. However, after I run the config service, I notice that my geojsonl file is zero bytes (leading to the estimate to return $0).
I know that the geojson source file is correctly formatted. I also know that it can successfully be converted into mbtiles via tippecanoe which I did locally to triple check. I tested this out with the actual source geojson file (about 750 MB) and a tiny sample of it (4 KB). Both produce geojsonl files with 0 bytes.
Any advice? I'd be happy to share a data sample if that will help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the 4 KB GeoJSON sample, running the config service and then checking the generated geojsonl file before running estimate. Trace the config service's GeoJSON-to-GeoJSONL path and compare its behavior with the successful tippecanoe conversion; done means the generated geojsonl is populated and estimate no longer returns $0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100