JtsGeometry.unwrapDateline creates an invalid polygon in some cases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with JtsGeometry initialization and the unwrapDateline path, using the WKT polygon in the issue to reproduce the conversion. Done means the example remains a valid polygon after initialization and does not collapse all -180 longitudes to 180.
Written by the indexing model from the issue text.
Description
Start with this Geometry:
POLYGON ((-180 -24.5271348, -180 0.9447814, 180 0.9447814, 180 -24.5271348, -180 -24.5271348))
Pass it to a JtsGeometry, and when unwrapDateline is called during initialization, it modifies to the following:
POLYGON ((180 -24.5271348, 180 0.9447814, 180 0.9447814, 180 -24.5271348, 180 -24.5271348))
That's not a valid polygon; note that all the -180 longitudes are now 180, so all of those points are on a straight line.
- Dominant language
- Java
- Stars
- 962
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from locationtech/spatial4j
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
locationtech/spatial4j#233 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
locationtech/spatial4j#232 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
locationtech/spatial4j#231 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
locationtech/spatial4j#230 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
locationtech/spatial4j#227 · 2 comments ·
All issues in locationtech/spatial4j
Similar issues
-
dependencies priority high
Difficulty 1/5 Under an hour Newbie friendliness 88/100
martin-francois/symphony-trello#865 ·
Maintainers usually reply within 1 day
-
🐞 bug 🔎 detector good first issue hacktoberfest java
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
owasp-noir/noir#2853 ·
Maintainers usually reply within 1 day
-
good first issue kernel
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
JackFurton/who-would-build-a-kernel-in-java#81 ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
LawnchairLauncher/lawnchair#7360 · 1 comment ·
Maintainers usually reply within 1 day
-
Temporal transforms put pre-epoch timestamps at `.999999` into the previous unitPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/iceberg#18371 · 1 comment ·
Maintainers usually reply within 1 day