Segfault with unknown SRS
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- backend
Research direction
Start in index.js at line 49, where gdal.suggestedWarpOutput is called for the reprojection. Reproduce the case with a TIFF containing an unknown SRS, then verify that the reprojection failure is caught instead of propagating a segmentation fault upstream.
Written by the indexing model from the issue text.
Description
When running wmtiff with a tiff that has an unknown srs, we get a segmentation fault in gdal.suggestedWarpOutput, which isn't caught and leads to some nasty things upstream. I think it would be good to wrap the reprojection process here within a try/catch, which is pretty standard for node-gdal.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
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.
More from mapbox/node-wmtiff
-
Uncaught error: Open
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
mapbox/node-wmtiff#13 ·
All issues in mapbox/node-wmtiff
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·