Geojsonl: zero bytes although source geojson is formatted correctly

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
data

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.

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.

Dominant language
JavaScript
Stars
71
Forks
15
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/mts-data-sync

All issues in mapbox/mts-data-sync

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.