the example test_linestring.js creates shapefile with null geometry
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 321
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Description
I run the `example/test_linestring.js` in the latest (v3.2.0) repo and it works with no error. But the generated shapefile is not rendered correctly at QGIS because the geometry is NULL, though the properties are properly saved.
I run the script with Node v7.2.1 and open the shapefile with QGIS 2.16.1 in Ubuntu 16.04.
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 by running example/test_linestring.js with the reported Node and QGIS versions, then inspect the generated shapefile and trace why its LineString geometry is null while properties are saved. Done means the example produces a shapefile whose geometry renders correctly in QGIS without losing its properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100