Feature offset ?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I notice that my area features that I generated to mbtiles has an offset in their positioning when viewed closeup. Is this normal?
tippecanoe -f --no-tile-size-limit --no-simplification-of-shared-nodes --no-tiny-polygon-reduction --no-line-simplification --minimum-zoom=18 --maximum-zoom=18 -o /tippecanoe/Land.mbtiles /tippecanoe/Land.geojson
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 reported offset using the command in the issue with /tippecanoe/Land.geojson and inspect the resulting /tippecanoe/Land.mbtiles at close zoom. Compare the generated feature positions with the source geometry and establish whether the offset is expected or indicates a bug; completion requires a confirmed explanation or a reproducible fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100