Conversation
|
Please merge this. |
|
hi @mourner - any chance I can get a review on this one? thanks! |
|
Sorry for the late response. I'll need to consider this change more thoroughly because this is technically breaking for the UMD bundle — when you have both default and named exports, the bundle will expose |
|
@mourner would you be open to a version of this that just tacks something like i.e. That's maybe a little weird, but it sidesteps the export issue at least |
|
@mourner @montzkie18 Any update on this? |
|
@mourner Hey! It's been a hot sec. I started looking for this use case and came across this PR. Is this something that you'd still be interested in merging in? Otherwise I can host a fork with the changes. |
|
I would also really like this for my project. My goal is to take a WFS GetFeature response for a given bbox that correlates to a z/x/y tile ID, convert the features to GeoJSON, and finally convert the features to a vector tile. In the meantime, I may have to make use of patch-package. |
|
@neodescis The State of Colorado is currently hosting this version: https://github.com/dfpc-coe/geojson-vt. My hope is that MapLibre will eventually host these changes |
Do you have it published to the npm public repo? If so, I'm not finding it. |
|
We have on boarded a fork of this project to maplibre org now. |
@HarelM that sounds a bit misleading. You have forked the project and will maintain a Maplibre-focused fork, but geojson-vt still remains and will be maintained here. |
|
You are right, sorry, I have updated the message above. |
Exposing new method
geoJSONToTileto generate a specific VT based on passed z/x/y values.This should skip generating parent tiles on all higher zoom levels for the requested tile.
This ports the C++ functionality implemented by @asheemmamoowala in mapbox/geojson-vt-cpp#65