Empty polygons in MULTIPOLYGON is supposed to be valid WKT
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 281
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Example:
MULTIPOLYGON((()), ((2.6086630821228027 5.044008255004883, 2.6824445724487305 4.468737602233887, 2.7592148780822754 3.870166778564453, 2.5626981258392334 3.8680214881896973, 2.4898300170898438 4.466637134552002, 2.419797658920288 5.041940689086914, 2.6086630821228027 5.044008255004883)))
Not being treated valid WKT by the parse func
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
Start at the WKT parse function and reproduce the provided MULTIPOLYGON example. Trace how empty polygon members are handled, then verify that this WKT is accepted as valid without breaking existing parsing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100