
- #Mapublisher wms url update
- #Mapublisher wms url full
- #Mapublisher wms url code
- #Mapublisher wms url iso
#Mapublisher wms url code
#Mapublisher wms url update
admin functionality, programmatic initialization of layers and scheduled update for layers have been migrated to use the new service.WFS/OGC API will be migrated in future/probably next release.currently WMS and WMTS-layers have been migrated to the new parser/format.Printing vector features with fill pattern is now visually closer to what is shown on the browser.Removed deprecated routes: DeleteFeature, InsertFeature, SaveFeature (replaced by VectorFeatureWriter).You can configure a comma-separated list that you want to enable metadata ids to be used from capabilities: This is not always the case and we added a new config for oskari-ext.properties. When parsing capabilities for layers it is assumed that the metadata url/id referenced in capabilities is a link to the same service that the Oskari instance uses as metadata service (like GeoNetwork or other CSW-compliant service).

Timestamp columns in database and server-side code have been updated for these for app setups and user generated content.
#Mapublisher wms url iso
In short this means using timestamps with time zone in database, java.time package in server code and ISO strings in JSON. For now the decisions for these have been documented in FAQ under "Handling dates and timestamps". Initial steps have been taken to make date handling more consistent on the database and server-side. All current admin tools can query a single editable item separately to get the localized values so this simplifies the code and makes admins use the same code for normal layer operations as other users. Most if not all localizable values are now only returned in the current users language. Layer listing changesĭata providers are now included in the layer list response similar to layer groups. WFS/OGC API Features layers now also have the properties described in DescribeFeatureType included in the capabilities JSON. has methods to query a service for layers including their capabilities per layer, update a single layer capabilities from the service, serialize the capabilities to JSON for oskari_maplayer and deserialize it from oskari_maplayer to get for example WMTS-layer matrix sets for printing. The service-capabilities Maven module now holds the logic for parsing capabilities and all functionalities use it when querying a service for its capabilities data. The oskari_capabilities_cache database table has been dropped and all capabilities data is now stored per layer on oskari_maplayer table capabilities column as JSON.


Map layer capabilities rewriteĪll capabilities parsing have now been fully migrated to the rewritten implementation for all layer types that previously used layer capabilities parsing.

#Mapublisher wms url full
Jetty 9.4.44.v20210927 -> 9.4.48.v20220622įixed an issue with WMTS-layers that define limits on capabilities 2.8.0įor a full list of changes see: My data frontend implementation changedĪ new bundle mydata has been added as (in most cases) drop-in replacement for personaldata.Pass user generated statistical indicators for frontend even when they don't have data (since user can add data for them later).Handle timeseries layer with single time value and no resolution part as normal layer.Enable region mapping for search results in WFS search channels: #883.Handle missing legend url for proxied layer to reduce noise in server logs.Allow admins to override capabilities based max features limit for vector sources with layer attributes.Allow users to include metadata flyout in embedded maps.
