Most of our customers do some editing in GMSC and they also have more groups in the legend. When user expands some themes in legend and then enter the editing mode, all themes are collapsed again. This is very frustrating for these users, when there are more groups in legend and they need to expand them again after each editing. Persisting legend state after editing would give more comfort to the users.
For all loaded WMS and WMTS-Layers the user shall be able to select the operation “Get feature info” from the legend entry’s context menu. The operation is only available if the layer supports the request “GetFeatureInfo”.
Once the operation is selected the user can point to a location in the map for which the pixel coordinates are calculated and then used to send a “GetFeatureInfo” request to the WMS/WMTS service.
The service’s response as text/xml is then displayed in a new GMSC internal browser window in a formatted HTML table. If the text/xml format is unavailable it shall be displayed in the text/html format.
A "Show legend graphic" action should be visible for all WMS and WMTS layers at their legend context (right click on the layer).
For all WMS layers that are accessible in the legend, the user shall be able to select the operation “Show legend graphic” from the legend entry’s context menu. The operation should be only available if the service supports the GetLegendGraphic operation for the layer.
The operation triggers a GetLegendGraphic request to the service with the default style and the layer that is used for the legend entry.
The returned legend graphic is then shown in a new GeoMedia® Smart Client's internal browser window.
For all WMTS features that are accessible in the legend, the user shall be able to select the operation “Show legend graphic” from the legend entry’s context menu. The operation is only available if the WMTS layer contains a <LegendURL>-element.
The hyperlink in the <LegendURL>-element is then opened in a new GeoMedia® Smart Client's internal browser window.
For GMSC Public Maps, the Map Views copyright Text is limited to 128 characters only. It would be good to be able to define a Copyright text beyond that limit (at least 255 characters) to be able to enter more specific conditions.
We have a workflow with a data source with quite long attribute names (more than 30 characters). In the process, unsightly effects appear. We think, that the attribute name (property name of element FormField) is capped after a certain length of character.
For example, we have the two attributes FOERDERAGGREGAT_FOERDERSTROMMIN_EINZELN and FOERDERAGGREGAT_FOERDERSTROMMAX_EINZELN. We want to edit these and fill in different values. After saving, both attributes will be filled by FOERDERAGGREGAT_FOERDERSTROMMAX_EINZELN (This value has already been filled into the database, can this be adjusted? Either by canceling the restriction or trigger a validation error.). We found a workaround for ourselves by typing a changed name of the attribute in the FormSettings, do not get the element with persisted = false any longer directly from the data and fill it with a default value
Important customer in France work with GeoMedia Smart Client 2016 and he want to display geographics coordinates in degrees decimals instead degrees-minutes-seconds
GeoMedia® Smart Client 2015 introduced the support of the Windows 8 Location API. With Windows 10 Microsoft dropped this API and replaced it with a new API not compatible to the old standard. In an upcoming release a connect to the new Windows 10 Geolocation API should be implemented.
Based on our community feedback, we want to offer the integration of OpenStreetMap data into our client applications.
Getting a project up and running to provide your end users with the data and workflow they need may consume some time. Getting the right background imagery covering the designated project extend or providing a solid base map can take hours. In the industry, there are a growing numbers of content providers offering you a good foundation of imagery and vector based data sets you can easily integrate into your map composition. As a result we want to extend the number of content provides supported in the product.
Market trends are showing that displays with 4K resolution do have a fast adoption rate.
Today GMSC provides some scaling mechanism for the user interface but items like the map configuration aren’t ready to be used on 4K displays (e.g. some definitions are done in pixel units). We want to implement full support of 4K displays including maps and workflows.
Users shall be able the view the service metadata (capabilities) for OGC services directly in the client. For all WMS, WMTS and WFS features that are accessible in the legend the operation “Show service metadata” from the legend entry’s context menu can be selected, which triggers a GetCapabilities request to the service. The result including all returned information shall be displayed in structured HTML in the GMSC internal browser.