Parse not working for POINT with space(s) after first parenthesis and/or space(s) before last parenthesis
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 281
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Parsing fails for WKT POINTS that have spaces directly after the open parenthesis and/or directly before the closing parenthesis. I haven't tested this issue on other types of geometry.
> POINT ( -68.1712366598 -16.5122344611 4124.6247727228 )
```
var parse = require('wellknown'),
geometry = parse('POINT ( -68.1712366598 -16.5122344611 )');
console.log(geometry);// geometry will be null
````
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 parser entry point used by require('wellknown') and reproduce the issue with the POINT examples containing spaces inside both parentheses. Confirm that those inputs parse successfully and that existing geometry parsing behavior remains unchanged; the payload does not name a specific source file or test.
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
- Clearly specified
- Newbie friendliness
- 42/100