|Oracle® Fusion Middleware User's Guide for Oracle MapViewer
11g Release 1 (11.1.1)
Part Number E10145-07
|PDF · Mobi · ePub|
This section describes major features that are new or changed since the previous release of MapViewer, which was included in Oracle Application Server Release 10.1.3.1. This section groups the new features into "MapViewer Core" and "Oracle Maps" subsections.
In addition, the MapViewer JSP tag library and PL/SQL API are deprecated features. For more information, see the notes at the beginning of Chapter 5, "MapViewer JSP Tag Library" and Chapter 6, "MapViewer PL/SQL API".
This section describes features related to MapViewer generally, including the Map Builder Tool.
MapViewer now supports secure map rendering based on a Web user's identity. Users with different roles or permissions will see different feature sets when viewing the same theme. For more information, see Section 1.8.
Web Feature Service (WFS) features can now be viewed through MapViewer's WFS themes. These themes support the parsing and caching of WFS capabilities, and the use of feature conditions and queries. WFS theme support also works with Oracle Maps; for example, you can display a WFS theme as an interactive feature of interest (FOI) layer. For information about WFS themes, see Section 2.3.7.
The Map Builder tool now supports the creation of WFS themes and Annotation Text-based themes. The base map panel also supports identifying features (and a list of rendered themes) on mouse clicks. For information about Map Builder, see Chapter 9.
MapViewer now supports a default provider and format for applications to supply XML-based nonspatial data for thematic mapping. You can also specify columns from the nonspatial data set to be used in conjunction with an advanced style. For information about thematic mapping using nonspatial external attribute data, see Section 184.108.40.206.
Previously, a feature could be rendered by only one rendering style. You can now use multiple rendering styles when rendering a theme's features. For example, you can shade a polygon with a color style while also plotting a pie chart on top of it, without defining two themes. This is done using stacked styles in a theme's definition. For an example of map request using stacked styles, see Section 3.1.13.
Previously, repetitive street labels or highway shields on linear features were displayed when such features consisted of many small segments. You can now use the Map Builder tool to specify the No Repetitive Labels option in the base map properties, to cause features (such as road segments) with same name to be labeled only once. For information about specific options in Map Builder, see the online help for that tool.
In the context of a base map, you can now assign scale limits to its themes' labels. These scale limits control when a theme's features will display their label texts. For more information and an example, see Section 2.4.1.
Full PDF map output support is provided. If you use
PDF_STREAM as the map format in your XML map request, MapViewer will generate vector PDF maps. For more information, see the explanation of the
format attribute in Section 220.127.116.11.
The TEXT style has been improved to support customizable spacing between letters. It also supports additional (vertical) alignment options when labeling linear features.
MapViewer now supports heat maps, which are two-dimensional color maps of point data sets. Heat map styles are described in Section A.6.8.
MapViewer now supports scalable styles. A scalable style (such as a MARKER or LINE style) uses real-world units such as meter or mile to specify its size and other dimensional attributes; however, at run time MapViewer automatically scales the style so that the features rendered by the style always show the correct size, regardless of the current map display scale. For information about using scalable styles, see Section 2.2.1.
The XML definition of a theme or base map now supports application-specific attribute tags. You can use the Custom Tags option in the theme definition in Map Builder to specify tags and their values, which can be interpreted by your application but are ignored by MapViewer itself.
<list_theme_styles> element enables you to get the names of styles referred to in a predefined theme. This element is described in Section 7.5.
You can now issue a simple URL request to the MapViewer server and get back a sample image of any style that you specified in the URL. This is useful if you want to build a custom map legend. For information about getting a sample image of any style, see Section 2.2.5.
Support is provided for OpenGIS Consortium standard annotation text. Oracle Spatial in Oracle Database Release 11g supports storage of annotation text objects in the database, and MapViewer now supports displaying such annotation texts on a map. For information about annotation text themes, see Section 2.3.9.
A new logging mechanism based on Java logging is provided. You can also use the Oracle Application Server management console to customize how MapViewer logs things at run time.
MapViewer now supports rendering of geospatial data stored in non-Oracle Spatial repositories. This is achieved through a Custom Spatial Data Provider API, where you can implement an Interface that feeds your own (proprietary) spatial data to MapViewer for rendering. Note that you will still need an Oracle Database to manage the mapping metadata, such as styles and themes definitions. For more information, see Section 18.104.22.168.
You can now specify a nondefault row fetch size on a theme, by setting the Fetch Size base map property with the Map Builder tool. MapViewer can use this value when fetching theme features from the database. Specifying an appropriate value can make performance tuning easier in certain situations.
MapViewer uses the SQL array types MV_STRINGLIST, MV_NUMBERLIST, and MV_DATELIST, which support array-type binding variables that might exist in some predefined themes. In some situations, you will need to create these types. For more information, see Section 22.214.171.124.
transparent_nodata attribute can be specified for GeoRaster themes (described in Section 2.3.4). If
true, any GeoRaster NODATA value is to be rendered as transparent. The default value is
Effective with Oracle Spatial GeoRaster for Release 126.96.36.199, GeoRaster objects can be reprojected into a different SRID. For more information, see Section 188.8.131.52.
You can specify the user and password in a predefined WMS map theme for a WMS server that requires authentication for access to the WMS data. For more information, see Section E.3.3.
This section describes features for Oracle Maps, which is documented in Chapter 8.
Applications can now display Google Maps tiles or Microsoft Bing Maps tiles as a built-in map tile layer. Internally, the Oracle Maps client uses the official Google Maps or Bing Maps API to display the map that is directly served by the Google Maps server. For more information, see Section 8.6, "Using Google Maps and Bing Maps". (If you need to overlay your own spatial data on top of the Google Maps or Microsoft Bing Maps tile layer, see also Section 8.7, "Transforming Data to a Spherical Mercator Coordinate System".)
Effective with Oracle Fusion Middleware Release 184.108.40.206, Google Maps API Version 3 and Bing Maps Version 7 are the default APIs used for those technologies by Oracle Maps.
A new Web-based user interfaced has been added to the MapViewer Web administration console for editing map tile layer definitions, as well as previewing and managing map tiles.
MVStyleColor), marker style (
MVStyleMarker), bar chart style (
MVBarChartStyle), pie chart style (
MVPieChartStyle), bucket style (
MVBucketStyle), as well as any MapViewer supported style defined in XML (
The positioning, styling, and sizing of the information window have been improved. Previously, the Oracle Maps client always displayed the information window at a fixed position relative to the specified map location. The Oracle Maps client now can place the information window at the optimal variable position relative to the specified map location. As the result, the map does not to be panned in order to make the information window visible inside the map. In addition, you can specify tabs for the information window.
MVMapView.displayTabbedInfoWindow. The Tabbed info window demo on the Oracle Maps tutorial page shows how to display a tabbed information window.
MVNavigationPanel.setZoomLevelInfoTips and the Navigation Panel demo on the Oracle Maps tutorial page
The Oracle Maps client now displays an animated icon during the loading of a base map or a theme. This is especially useful for providing visual reassurance to users with maps and themes that take a long time to load.
Applications can now customize the appearance of the mouse cursor when the cursor is over different map components, such as map tiles, FOIs, and map decorations.
MVToolBar and the Tool bar demo on the Oracle Maps tutorial page.
Long running tile admin requests that are interrupted due to Fusion Middleware or MapViewer shutdown will be able to resume automatically after MapViewer is restarted. (You do not need to do anything to enable this feature, other than creating the new database view USER_SDO_TILE_ADMIN_TASKS if it does not already exist. For more information, see Section 2.9.)
MVThemeBasedFOI.enbleHightlight and the Highlighting individual features of a theme based FOI layer demo on the Oracle Maps tutorial page.
Many new Oracle Maps tutorials illustrate the new features. To access the MapViewer demos and tutorials, go to: