MapInfo Spatial Server Map Tiling Service - Product Documentation ...

More documents

Recommendations

Info

About the Map Tiling Service About the Map Tiling Service The Map Tiling Service dynamically generates subsets of a map on a per-request basis. This subset is called a tile. The tiles generated from the Map Tiling Service can be used individually, or combined to form larger maps, in applications for seamless map interaction. This service provides fast, simple, lightweight map rendering where more complex map rendering can be performed using the Presentation Service. The Map Tiling Service allows the hosting of multiple maps that can be used to generate the tiles. These named maps are located in one or more map repositories. Each map hosted by the Map Tiling Service can have a specific configuration that defines how the map will be used to create tiles. The Map Tiling Service has two interfaces. Both are web based HTTP interfaces, however, one is a REST interface, and the other is a name/value pair interface: • REST - Referred to as the Map Tiling REST interface, this API is a simplified web interface that has methods for getting the name of maps, describing maps, and getting tiles. For details of this REST interface, see Map Tiling REST Interface on page 19 for more information. • Name/Value - Referred to as the Legacy Map Tiling interface, this API provides more complex methods that include the REST methods as well as methods for getting the bounds of maps, level descriptions tile sets, and numerous conversion methods between pixel, tile, and screen coordinates. Note: This is a legacy interface, and should only be used to support PBBI backwards compatable applications. For all new applications, use the REST interface. For details of this interface, see Legacy Map Tiling Interface on page 27 for more information. Supported Data Both vector and raster data can be hosted by the Map Tiling Service. Named Map Modifications 6 The Map Tiling Service is designed to host your maps without modification. However, due to the dynamic nature of tile generation, the Map Tiling Service does make minor modifications to the map after it is loaded into the server. These changes relate to the rendering of labels, and are as follows: • Duplication of labels is not allowed. • Geometry calculation mode is set to STATIC. • Partial labels are allowed. A special category of layers relate to the display of highway shields. To allow the accurate display of highway shield layers the following label properties are set: • Duplication of labels is allowed. • Geometry calculation mode is set to STATIC. • Partial labels are allowed. These modifications are stored in the Map Tiling Service memory and in no way change the source of the maps hosted by the Map Tiling Service stored in the repository. MapInfo Spatial Server 1.0
Managing Map Tiling Resources and Configuration This section describes how to configure and add resources to the Map Tiling Service. The Map Tiling Service is installed and pre-configured with the configuration file (named configuration) located in the repository. The Map Tiling Service uses the standard XML service configuration similar to the other MapInfo Spatial Server services. The named Map Tiling Service configuration file MapTilingConfiguration is located in the Configuration directory under the root repository. For example, a default installation will place the Map Tiling Service configuration file at http://localhost:8080/RepositoryService/repository/default/Configuration/MapTilingConfiguration You can use your standard WebDAV protocol tools (e.g., Windows WebFolders, DAVExplorer, etc.) to copy the configuration file from the repository, and then upload the modified configuration file back. Once uploaded, you must use the MapInfo Spatial Server JMX Console to invoke the new configuration for the service. Note: You must be on the local machine hosting MapInfo Spatial Server to access and make changes to resources in the repository. In this section: • Accessing and Modifying the Configuration File . . . . . . .8 • Adding and Modifying Named Tiles . . . . . . . . . . . . . . . . .14 2
Page 1 and 2: MapInfo Spatial Server Version 1.0
Page 3 and 4: Contents Chapter 1: Introduction...
Page 5: Introduction The Map Tiling Service
Page 9 and 10: Parameter MimeList MapResolution Ma
Page 11 and 12: Parameter MinEvictableIdle- TimeMil
Page 13 and 14: 6. In the Save As dialog box, enter
Page 15 and 16: Parameter MinimumLevel MaximumLevel
Page 17: There is one restriction when defin
Page 20 and 21: What Is the Map Tiling REST Interfa
Page 22 and 23: Tile Tile 22 Returns A MapDescripti
Page 24 and 25: Objects Objects This section descri
Page 27 and 28: Legacy Map Tiling Interface This ch
Page 29 and 30: Example http://localhost:8080/rest/
Page 31 and 32: getTile Description Returns generat
Page 33 and 34: getTileBounds Description Returns t
Page 35 and 36: Parameter level screenX screenY vie
Page 37 and 38: name=/NamedTiles/WorldTile &level=4
Page 39 and 40: Parameters of the screen, regardles
Page 41 and 42: Field Name minLevel coordSys descri
Page 43 and 44: } MapCoordinate "tileDown": 2, "vir
Page 45 and 46: Common Data Types This appendix des
Page 47 and 48: Name Description in this table. An
Page 49 and 50: Errors This appendix describes the
Page 51: Code 8000 8001 8002 Message Map Til
Page 54 and 55: Transforming a Pixel to a Map Coord

MapInfo Spatial Server Map Tiling Service - Product Documentation ...

Create successful ePaper yourself

Delete template?

Save as template?