- MAPUBLISHER GOOGLE BASE LAYER UPDATE
- MAPUBLISHER GOOGLE BASE LAYER FULL
- MAPUBLISHER GOOGLE BASE LAYER CODE
MAPUBLISHER GOOGLE BASE LAYER 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.
![mapublisher google base layer mapublisher google base layer](https://cdn.shopify.com/s/files/1/0014/0981/0497/products/IMG_1061-2_7a3b83ed-cd11-417b-9d47-756758f7e870.jpg)
MAPUBLISHER GOOGLE BASE LAYER CODE
Timestamp columns in database and server-side code have been updated for these for app setups and user generated content. 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.
![mapublisher google base layer mapublisher google base layer](https://cdn.shopify.com/s/files/1/0276/8407/7642/products/4279fcfd-570d-4670-8e5c-83ce2bcbbd16_700x700.jpg)
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.
![mapublisher google base layer mapublisher google base layer](https://cdn.shopify.com/s/files/1/0901/0064/products/AztecDiamondEcom176copy_b4f1b44c-e885-4dec-a38d-139544ba6d95_800x.jpg)
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 GOOGLE BASE LAYER FULL
Fixed 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.