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

New WFS functionality replacing "transport" webapp #109

Open
ZakarFin opened this issue May 14, 2019 · 2 comments

Comments

Projects
None yet
1 participant
@ZakarFin
Copy link
Member

commented May 14, 2019

We have been working on a replacement for the "transport" webapp that has handled most of the WFS-related integrations on Oskari for some time now. The replacement improves on transport by making the features available as vector data on the browser allowing client side styling and things like hovering on features while also including initial support for WFS 3 APIs. It also simplifies the logic how features are loaded to the browser by using the action route logic in Oskari as a replacement for websocket used by transport and benefits from tiling and thereby caching abilities. This will also remove the requirement we currently have for running the transport webapp on a Jetty-server.

As we are finalizing the implementation I'm proposing that:

  • in 1.52 the initial version of the new backend is included and instructions are provided how to configure the replacement in Oskari instances for testing purposes
  • in 1.53 we will provide a migration script that is run automatically on update that will migrate users to use the new backend. We will provide a toggle where you can opt-out of the feature by having a configuration in oskari-ext.properties
  • in 1.54 we will migrate any remaining instances to use the new backend and remove transport from the Oskari package.
@ZakarFin

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

"Native" WFS 2.0 support will not be included in the new WFS-system initially. 3.0 has it's own client and requests to other versions will fallback to 1.1.0.

@ZakarFin ZakarFin added approved roadmap and removed Proposal labels Jun 11, 2019

@ZakarFin ZakarFin changed the title OIP: New WFS functionality replacing "transport" webapp New WFS functionality replacing "transport" webapp Jun 11, 2019

@ZakarFin

This comment has been minimized.

Copy link
Member Author

commented Jun 11, 2019

Approved in 11.6. PSC meeting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.