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

More documents

Recommendations

Info

Accessing and Modifying the Configuration File Accessing and Modifying the Configuration File The named Map Tiling Service configuration file MapTilingConfigurationis 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/Map- TilingConfiguration To configure the Map Tiling Service, perform the following: 1. You must be located on the local machine hosting MapInfo Spatial Server and the repository. 2. Use a standard WebDAV protocol tool to access the repository (e.g., Windows WebFolders, DAVExplorer, etc.) and copy the configuration file from the repository to a directory on your local machine. The Map Tiling Service configuration file is located at http://localhost:8080/RepositoryService/repository/default/Configuration/MapTilingConfiguration For examples of using standard WebDAV tools, see Accessing the Repository using WebDAV 3. Make changes to the local MapTilingConfiguration file. For parameter descriptions for the configuration file, see Global Configuration Parameters on page 8. 4. Upload the modified configuration file back to the same location (and name) in the repository using your WebDAV tool. 5. Use the MapInfo Spatial Server JMX Console to invoke the new configuration for the service. For instruction on how to reload the configuration using the JMX Console, see Reload the Service Configuration using JMX Console on page 13 Global Configuration Parameters 8 The Map Tiling Service configuration consists of a set of global parameters that define how tiles are generated. These parameters are used if optional parameters defined in the named tiles are not specified. If a named tile has defined these parameters, then the parameters in the global configuration will be overwritten. The following are global configuration paramters: Parameter RepositoryURL ExpirationDate Type string string Required yes no Description The URL defines the location of your local repository where resource are stored that are accessed by the Map Tiling service. This URL should point to the Repository Service rmi, for example: http://localhost:8080/RepositoryService/rmi Note: In most instances, this URL should not be changed. The date on which the client should delete the map tile from the cache, and request a new copy from the server. The ExpirationDate value must be specified as a W3C formatted date string (for example, 2013-12-31). MapInfo Spatial Server 1.0
Parameter MimeList MapResolution MapRendering RenderLabels PadFactor Type string integer string boolean integer Required no no no no no Description Note: The ExpirationDate parameter has effect only when using external caching software such as Squid or Apache. The available types of tiles generated by the tile server for named tiles when the MimeList is not specified. The resolution of the tile images in dots per inch (the number of individual dots that can be placed within the span of one linear inch). The minimum dpi you can define is 72, anything less would render a poor quality image. If a value less than 72 is defined, the service will throw an exception. The rendering quality (anti-alias) of the tile images generated. You can specify either Speed or Quality. If MapRendering is not specified in either the global configuration or in a named tile, the default rendering quality is Speed. Tells the service not to render LabelLayers when generating a tile. The value is case-insensitive. If RenderLabels is not specified in either the global configuration or in a named tile, the default is 'true'. Used to prevent the clipping of labels when a label crosses a tile boundary. The PadFactor controls the amount of space is rendered around the requested tile with 0 meaning no padding, 1 meaning padding of 1 tile around the requested tile and so on. If PadFactor is not specified in either the global configuration or in a named tile, the default is 1.0. Internally, the Map Tiling service draws tiles to an offscreen bitmap (OSBM) (e.g., BufferedImage). To help speed up rendering of tiles by reducing garbage collection pauses, pools of offscreen bitmaps may be used to avoid constantly creating new ones. The OSBMPooling configuration controls how the offscreen bitmaps are created in memory. Note: If the OSBM pooling section of the configuration is removed, then pooling will not be enabled. The following are OSBM configuration paramters: Parameter MaxActive Map Tiling Service Guide Type integer Chapter 2: Managing Map Tiling Resources and Configuration Required no Description Controls the maximum number of offscreen bitmaps (per tile dimension) that can be allocated by the pool (checked out to client threads, or idle in the pool) at one time. When non-positive, there is no limit to the number of objects per key. When this value is reached, the keyed pool is said to be ex- 9
Page 1 and 2: MapInfo Spatial Server Version 1.0
Page 3 and 4: Contents Chapter 1: Introduction...
Page 5 and 6: Introduction The Map Tiling Service
Page 7: Managing Map Tiling Resources and C
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?