New WFS functionality replacing "transport" webapp #109
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: