search

geosolutions-it / inspire-issues

This repository works as an aggregator for GeoServer known issues with respect to INSPIRE compliance and support.
https://waffle.io/geosolutions-it/inspire-issues
0 stars 0 forks source link

FeatureTypes/layers always published in all service types #16

Open nmco opened 5 years ago

nmco commented 5 years ago

Due to performance reasons it makes sense to publish the WMS layers and WFS featureTypes for the same INSPIRE feature types using different data sources: It should be possible to publish the complex feature data for the INSPIRE data via a WFS endpoint using AppSchema data source, and a WMS layer corresponding to the same feature type using a direct PostGIS data source, or even a shapefile. Currently each layer is automatically visible both as a WFS feature type and a WMS layer, so this is not possible.

Workaround The data provider has to use different Geoserver instances for WMS and WFS to map their data source differently.

nmco commented 5 years ago

Ilkka Rinne 16.3.2017: The proposed ""Isolated workspaces"" feature would provide a workaround. Data providers could create separate workspaces with only WMS enabled in one and only WFS enabled in the other, with different data source configurations for the identically named layers. Iurie Maxim 24.04.2017: This isolated workspaces seems actualy to be multiple Geoserver instances. Actualy Geoserver is installed several times on the same machine (the war file is uncompressed in the Tomcat twice, once for WMS and once for WFS. For 10 datasets a data provider will have 20 Geoserver Instances that will consume a significant amount of RAM that will need to be provided to Java. We already performed some tests. Implementations are not possible without specialised people or step by step guidelines.