-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update stac_ipyleaflet to use titiler-pgstac endpoints #131
Comments
@jjfrench if we add the |
@hrodmn I think that would be reasonable, but I also think that this package isn't being used i.e other packages are more popular or stac-ipyleaflet is missing out on key features. I'm unsure about the longevity of this package as we haven't supported development on it for quite awhile now |
@wildintellect thoughts on this? |
I think finding the mosiacjson usage should be easy, pretty sure it's all on the mosaics tab, but should also be easy to swap for titiler-pgstac mosaics instead. The bigger challenge is that dynamic mosaics are not really supported in stac_ipyleafet yet (no gui for it). So the question for the long term roadmap is what's the next evolution of this tool given @jjfrench can you confirm, with this upgrade did we break the existing stac_ipyleaflet version? or will that happen only once we replace the main titiler instance? Thoughts |
@wildintellect, it would only break the current version once we replace/remove the titiler-stac instance - as of right now, titiler-stac is still deployed |
FYI I'm not planning to add such endpoint to titiler-pgstac module but this could be done in a custom app.
I would kinda agrees, if we think stac-ipyleaflet could be use by any stac endpoint then it should at least works with as I said I'm not planning to add this |
@vincentsarago yes I agree that the |
We have an overall goal to make VEDA JupyterHub equivalent to MAAP ADE. If stac_ipyleaflet is a popular feature of MAAP ADE, we should keep maintaining it, also under VEDA, so users who change between the platforms can use the same tool both places. Otherwise, we currently on VEDA do not have a strong use case for further developing stac_ipyleaflet, I would say. Happy to be convinced otherwise. Lonboard has some unique capabilities for interactive vector data exploration that we would like to advertise for on VEDA. Once that advertisement is complete, also there I would say we should not plan for major development on VEDA, unless prominent VEDA users request new features. In short, in terms of user value:
I think where the two differ is that Lonboard is more like a power-ipyleaflet, while stac_ipyleaflet's value comes from the convenient connection to STAC. I guess there are no plans to make Lonboard STAC-aware. |
Not particularly. But there's potential to make an extension to Lonboard to support STAC |
Description
We are working on consolidating the titiler deployments in MAAP to a single instance (titiler-pgstac.maap-project.org) (https://github.com/NASA-IMPACT/active-maap-sprint/issues/945, https://github.com/NASA-IMPACT/active-maap-sprint/issues/988, https://github.com/NASA-IMPACT/active-maap-sprint/issues/471).
I will go through stac-ipyleaflet and figure out which (if any) of the features will require any custom titiler modifications (e.g.
mosaicjson
endpoints) or if we can use new features in titiler-pgstac to replace those custom features.Functions that use titiler-stac.maap-project.org:
Stac.get_tile_url
: will work if we add the/cog
endpointsStac.stac_tile
/collections/{collection_id}/items/{item_id}/{tileMatrixSetId}/tilejson.json
instead of/stac/{TileMatrixSetId}/tilejson.json
/stac
endpoints to the titiler-pgstac tilerStac.get_metadata
: No more/metadata
endpoint... but I can't tell if this function is actually used anywhere. Still need to figure out what is returned by this feature.cc @abarciauskas-bgse @jjfrench
The text was updated successfully, but these errors were encountered: