Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`estimate-area` returns 0 km2 for certain files

Open
#161 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
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

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.

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

Dominant language
Python
Stars
141
Forks
27
PR merge metrics
No merged PRs in 30d

Getting set up

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/tilesets-cli

All issues in mapbox/tilesets-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.