CLI dropping source GeoJSON fields with array or object values
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I'm getting different results when submitting the same GeoJSON source via Studio vs. CLI. Submitting a GeoJSON via CLI drops any field with array or object values. Submitting via Studio converts the array/object field(s) to string but keeps the field in the resulting tileset.
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
Reproduce the same GeoJSON submission through the CLI and Studio, then compare the resulting tileset fields. The fix is complete when CLI submissions retain array- and object-valued source fields consistently with Studio, rather than dropping them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100