locationtech / locationtech/jts
snapRoundingNoder on polygons result in MultiLineString
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.2k
- Forks
- 475
- Avg merge
- 14d 10h
- Merged PRs (30d)
- 1
Description
When using the snapRoundingNoder on the attatched dataset with a precision scale of 10, I get a MultiLineString where the number of decimal places are all reduced to 1, but the number of coordinate pairs go from 2818 in the original polygon data to 5419 in the resulting MultiLineString. This makes the data larger in bytes and more complex to work with. Is this the expected behavior?
Also, why is the result a MultiLineString? I don't see an obvious way to convert this back to polygons as there is no info on what were polygon exteriors and what were holes/interiors.
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 behavior with snapRoundingNoder, the attached snap_problem_area_1144.txt dataset, and a precision scale of 10. Compare the input polygon with the resulting MultiLineString and determine whether the coordinate expansion and loss of polygon ring information are expected; document the explanation or identify the needed fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100