mapbox / mapbox/osm-boundaries
tiny code-modification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
in the last line it has to be:
```js
osmium.apply(reader,location_handler, handler);
```
otherwise i get the following error:
>reader.apply(location_handler, handler);
TypeError: reader.apply is not a function
at Object. (/root/process-boundaries.js:110:8)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:974:3
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 last line of /root/process-boundaries.js, identified at line 110 in the stack trace, and inspect how the reader and osmium objects are used there. Confirm the call matches the issue’s shown form and rerun the process-boundaries example; done means the reader.apply TypeError no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100