mapbox / mapbox/mapnik-omnivore
Improve handling of multilayer formats
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 44
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to add FileGDB support and noticing a design limitation: mapnik-omnivore assumes a file has only one projection.
In the case of FileGDB each table is a layer with a potentially unique projection and extent. This means that inside `processOgrDatasource` the `getCenterAndExtent` and `getMinMaxZoom` functions need to operate per layer and not per file.
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 reading processOgrDatasource and the existing getCenterAndExtent and getMinMaxZoom calls. Trace how layers are discovered in a FileGDB and determine how metadata is currently calculated per file. Done means each layer can use its own projection and extent, with the related metadata calculated per layer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100