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

Update Helsinki WFS layers #76

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

mhieta
Copy link
Contributor

@mhieta mhieta commented Sep 20, 2024

Replace outdated geoserver.hel.fi layers with layers from kartta.hel.fi and apila.platta-net.hel.fi hosts.
Also update WFS layer names to match correct ones from new sources.

Replace outdated geoserver.hel.fi-layers with layers from kartta.hel.fi
and apila.platta-net.hel.fi hosts.
Copy link

sonarcloud bot commented Sep 20, 2024

@tuomas777
Copy link
Contributor

tuomas777 commented Oct 1, 2024

Related ticket RATYK-36

@tuomas777 tuomas777 requested a review from a team October 1, 2024 06:07
Copy link
Contributor

@danipran danipran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@vikoivun
Copy link
Member

vikoivun commented Nov 5, 2024

Note that api.platta-net.hel.fi won't work outside containers running on Platta. So might be a smidge painful on local development. Of course everything on Apila is only available within Helsinki network anyway, even when disregarding the Platta specific DNS-kludge.

@mhieta
Copy link
Contributor Author

mhieta commented Nov 5, 2024

@vikoivun Those apila.platta-net.hel.fi-layers should be nowadays accessible also from https://kartta.hel.fi/ws/geoserver/helsinki/wfs. But these layers are secured layers and require WFS-authentication, which needs to be implemented first. Also it needs to be specified, where to store credentials for these layers and which application / component should store those (munigeo itself or the application, which uses munigeo).

Since this might take some time to implement, it might be feasible to do it in a separate PR after this one.

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

Successfully merging this pull request may close these issues.

4 participants