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.

Sign up for GitHub

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

Jump to bottom

Alternative implementation of get_oe_layer based on mercator Features API #4

Open

maarten-vermeyen opened this issue Mar 8, 2024 · 0 comments

Labels

question

Milestone

Contributor

maarten-vermeyen commented Mar 8, 2024

Should we switch tot the Mercator OGC Features API services to download OE layers:

Benefits:

consistent layer naming with GDI services
smaller download size, when using geojson with transfer zip compression
less to download if you require a specific service
better overall performance?

Downsides:

multiple requests needed (at least for designation objects and architectural heritage layer). Mercator supports up to 40.000 returned items, so 3 request for a layer should be the maximum.
results still cacheable?

maarten-vermeyen added the question label

maarten-vermeyen added this to the 0.1.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment