Skip to content
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

Thematic Structuring of Collections and Display of Vector Tile URLs in BBOX #81

Open
FabianRechsteiner opened this issue Sep 18, 2024 · 5 comments

Comments

@FabianRechsteiner
Copy link

Description:
Currently, all tables from the PostGIS database are displayed in Collections. I would like to discuss the possibility of thematically structuring these collections. For example:

  • We have various tables in the amtliche_vermessung schema that should be listed under a theme called "Amtliche Vermessung" in BBOX collections.

  • The table solarkataster, on the other hand, should be found under the theme "Energie".

My goal is to use BBOX to provide an API through which all geographic data of the city of Winterthur can be accessed. The idea is to have a catalog that displays different themes and datasets, with descriptions, information, and metadata linked to these themes and datasets.

Currently, the collections only display the items. It would also be beneficial to display the URL for Vector Tiles if available. Additionally, some collections might be combined into a single tileset, and it would be useful to show these as well.

I’m interested in how other users handle the organization of large datasets and if there are suggestions for effectively structuring and presenting a large number of data sources. Are there best practices or features that could help achieve this?

@pka
Copy link
Contributor

pka commented Sep 19, 2024

Maybe STAC Catalogs could be a way for grouping topics? (see also #61, @kdesjard ?)

@kdesjard
Copy link
Contributor

Indeed, I have a fork that I've been meaning to get packaged for upstream.

You can see here how we are using it:

https://radiantearth.github.io/stac-browser/#/external/www.eodms-sgdot.nrcan-rncan.gc.ca/ogc/catalog.json

@pka
Copy link
Contributor

pka commented Nov 25, 2024

Indeed, I have a fork that I've been meaning to get packaged for upstream.

You can see here how we are using it:

https://radiantearth.github.io/stac-browser/#/external/www.eodms-sgdot.nrcan-rncan.gc.ca/ogc/catalog.json

We're very interested in your Stac implementation! I found two branches:

Are you fine with merging them into upstream bbox? Are there dependencies between them?

@pka
Copy link
Contributor

pka commented Dec 2, 2024

@kdesjard: Are you fine with merging the mentionend branches or could you submit them as PRs?

@kdesjard
Copy link
Contributor

kdesjard commented Dec 2, 2024

Sorry, missed your previous message. I need to work on some small fixes for link hierarchy and then I'll have to rebase and create PR's. I'll try to get this done within the year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants