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

WMS doesn't work on some geometry types * gml:MultiSurface #8

Open nmco opened 6 years ago

nmco commented 6 years ago

Description GeoServer cannot provide a WMS from certain complex feature types due to the geometry used Also, seems to crash TomCat when doing GetFeatureInfo but needs to be checked

Workaround Set up simple features and create a WMS for these; may need some rewriting, not sure

nmco commented 6 years ago

Iurie Maxim 21/4/2017: WMS is actualy rendering images very slow based on complex features. so for usability the recommandation is to use always simple features. We used rewriting to produce short URLs for retrieving each feature so they can be used within the WMS to link with WFS (http://inspire.biodiversity.ro/ENV/PADS/psPS/RONPA0022). The problem indicated by Kathi is not a Geoserver problem is a complex feature problem. All existing software have same problem of slow rendering if the features are complex and all have issues with one-to-many relationships. This should not be indicated as Geoserver issue. Actualy I would mention that GML is the real problem and the fact that the geometry in the GML is a text. Compared to a personal geodatabase ir to a shapefile storing the same information a GML is at least 100 times larger (in MB). GML is simmilar to an Oracle or SQL Dump, is a format for data exchange, not for data use. For usability purposes at leaset a compressed GML file similar with KMZ should be developed.