This section describes major features that are new or changed since the previous release of MapViewer that was included in Oracle Fusion Middleware Release 11.1.1. This section groups the new features into "MapViewer Core" and "Oracle Maps" subsections.
This section describes features related to MapViewer generally, including the Map Builder Tool.
If you have an existing MapViewer Release 11g installation, and if you want to use its MapViewer configuration on Oracle Fusion Middleware Release 12.1.3, see Section 1.5, "Upgrading MapViewer".
Support is added for LRS themes. An LRS theme is a special kind of MapViewer theme useful for visualizing features defined using the linear referencing system (LRS) of Oracle Spatial and Graph. Two tables are needed by an LRS theme: one (the LRS table) has an LRS geometry column, and the other (the join table) has one or two measure columns.
For more information, see Section 2.3.11, "LRS (Linear Referencing System) Themes".
A web map tile service (WMTS) server has been added into MapViewer. Now tile layers defined in the USER_SDO_CACHED_MAPS metadata view can be retrieved through WMTS requests. This server is Open Geospatial Consortium WMTS 1.0.0 compliant.
For information about how to configure this server in MapViewer, see Section 1.6.2.13, "Customizing WMTS GetCapabilities Responses".
See also Appendix F, "OGC WMTS Support in MapViewer" for information about the WMTS service for MapViewer, WMTS Operations, and preparing the WMTS service for MapViewer.
The <rendering> element can have multiple <style> elements defined. You can also assign scale ranges for each <style> element. For more information, see Section 2.3.1.5, "Using Multiple Rendering Styles with Scale Ranges".
A web version of the Map Builder utility can be accessed using the MapViewer web console (top-right corner link), as explained in Section 7.3, "Map Builder Web Version".
The MapViewer JSP library, announced as deprecated in the previous release, is now desupported and is not included in this document.
Instead, you are encouraged to use the MapViewer Java API, which is more comprehensive and up to date. Moreover, if you prefer to use tags, consider using the GeoMap tags in the JDeveloper Application Development Framework (ADF).
The MapViewer PL/SQL API, announced as deprecated in the previous release, is now desupported and is not included in this document.
Instead, you are encouraged to either (A) use one of the other supported MapViewer APIs, or (B) use Oracle Application Express (APEX) with the MapViewer JavaScript API.
This section describes features for Oracle Maps, which is documented in Chapter 6.
The map cache auto-update feature periodically updates cached map tiles when they become "dirty." A cached map tile becomes dirty when data in base tables is changed by an update, insert, or delete operation, because such changes may affect the shape, annotation, or choice of rendering style for the already cached map tiles.
For information about map cache auto-update, see Section 6.3, "Map Cache Auto-Update".