`estimate-area` returns 0 km2 for certain files
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
tilesets estimate-area command returns "km2": "0" for certain geojson files. It seems that it might be related to the amount of nodes in a given Polygon, are there any limitations regarding polygons with many nodes?
Here's one of the files for which estimate-area returns 0 km2
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 issue by running tilesets estimate-area with the GeoJSON file linked in the report. Then locate the estimate-area command and trace how polygon node counts and area results are handled. Done means identifying why the result is "km2": "0" and either correcting the behavior or documenting the confirmed limitation.
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
- Needs clarification
- Newbie friendliness
- 35/100