lgoltz
lgoltz
Currently the HTML output of a GFI response contains the same GML ID for each feature. Example: https://geoportal.saarland.de/gdi-sl/inspirewms_Verwaltungseinheiten_ALKIS?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&BBOX=302444.6399650537641719,5356659.78744656965136528,388315.51130642730277032,5586443.87835079990327358&CRS=EPSG:25832&WIDTH=324&HEIGHT=867&LAYERS=AU.AdministrativeUnit&STYLES=&FORMAT=image/png&QUERY_LAYERS=AU.AdministrativeUnit&INFO_FORMAT=text/html&I=152&J=412&FEATURE_COUNT=10 GML: https://geoportal.saarland.de/gdi-sl/inspirewms_Verwaltungseinheiten_ALKIS?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&BBOX=302444.6399650537641719,5356659.78744656965136528,388315.51130642730277032,5586443.87835079990327358&CRS=EPSG:25832&WIDTH=324&HEIGHT=867&LAYERS=AU.AdministrativeUnit&STYLES=&FORMAT=image/png&QUERY_LAYERS=AU.AdministrativeUnit&INFO_FORMAT=text/xml&I=152&J=412&FEATURE_COUNT=10 This PR fixed the html.gfi to ensures the correct GML...
Currently all properties of a features are fetched from database. This behaviour sometimes introduces some overhead and performance loss. see: http://osgeo-org.1560.x6.nabble.com/Rendering-takes-too-long-between-deegree2-and-deegree3-td5144950.html
Currently a GetFeature request with a PropertyName like `app:contact/app:Contact/app:email` is ignored and the following statement is logged: ``` Only simple qualified element names are allowed for PropertyName projections. Ignoring 'app:contact/app:Contact/app:email'...
**Setup** * PostgreSQL * SQLFeatureStore * simple FeatureLayer configuration: ``` tn_w_atkis tn-w:WaterwayLink TN.WaterTransportNetwork.WaterwayLink TN.WaterTransportNetwork.WaterwayLink ``` During startup of the workspace an error occurred: ``` [10:35:16] ERROR: [DefaultWorkspace] Unable to build...
Editing resources in subfolders like "services/test/test.xml" results in a NullPointerException: * Edit resource via deegree console * Save resources (without changes) `Fehler "null"` is shown in the console. A FileNotFoundException...
For group layers a legend graphic should be configurable. The legend graphic can be referenced as local file or remote URL.
If a legend graphic from the RemoteWMS is unusable the legend graphic for the RemoteWMS layer should be configurable in the deegree workspace configuration. **Example:** A RemoteWMS provides the layer...