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

More documents

Recommendations

Info

Global Configuration Parameters 10 Parameter MinIdle MaxIdle MaxTotal ExhaustedAction Type integer integer integer string Required no no no no Description hausted. The default setting for this parameter is 8. The minimum number of idle offscreen bitmaps (per tile dimension) that should always be available. If this parameter is set to a positive number and TimeBetweenEvictionRunsMills is greater than zero, each time the idle object eviction thread runs, it will try to create enough idle instances so that there will be this number of idle instances available under each key. The default setting for this parameter is 0. The maximum number of offscreen bitmap that can sit idle in the pool (per tile dimension) at any time. When negative, there is no limit to the number of objects that may be idle per key. The default setting for this parameter is 8. The global limit on the number of objects that can be in circulation (active or idle) within the combined set of pools. When non-positive, there is no limit to the total number of objects in circulation. When MaxTotal is exceeded, all keyed pools are exhausted. When MaxTotal is set to a positive value and an offscreen bitmap is requested when at the limit with no idle instances available, an attempt is made to create room by clearing the oldest fifteen percent (15%) of the elements from the keyed pools. The default setting for this parameter is -1 (no limit). The behavior when the pool of offscreen bitmaps is exhausted. The options are fail, grow, or block. Fail will throw an exception when an offscreen bitmap is requested when the pool is exhausted. Grow, the default, will create a new offscreen bitmap and return it, making MaxActive meaningless. Block will stop the process until a new or idle object is available. Optionally, one may configure the pool to examine and possibly evict objects as they sit idle in the pool and to ensure that a minimum number of idle objects is maintained for each key. This is performed by an idle object eviction thread, which runs asynchronously. Caution should be used when configuring this optional feature. Eviction runs require an exclusive synchronization lock on the pool. If they run too frequently or incur excessive latency when creating, destroying or validating object instances, performance issues MapInfo Spatial Server 1.0
Parameter MinEvictableIdle- TimeMills TimeBetweenEvictionRunsMills Type integer integer Required no no Description Uploading and Accessing Resources in the Repository may result. The idle object eviction thread may be configured using the MinEvictableIdleTime- Mills and TimeBetweenEvictionRunsMills parameters. The minimum amount of time that an offscreen bitmap may sit idle in the pool before it is eligible for eviction due to idle time. When non-positive, no object will be dropped from the pool due to idle time alone. This parameter has no effect unless TimeBetweenEvictionRunsMillis is greater than zero. The default setting for this parameter is 30 minutes. How long the eviction thread should sleep before examining idle offscreen bitmaps. When non-positive, no eviction thread will be launched. The default setting for this parameter is -1 (i.e., by default, idle object eviction is disabled). Named resource files are stored in the repository. These files are located at http://localhost:8080/RepositoryService/repository/default/ under a particular folder. For example: • NamedLayers • NamedMaps • NamedStyles • NamedTables • NamedTiles You can access these files using two methods: the NamedResource service or manually using a WebDAV compliant tool. This section describes the manual method. For more information on using the NamedResource service, see the NamedResource Service SOAP Reference. To access resources manually, you must use a WebDAV protocol tool to access the JCR repository. There are many tools available to upload and access resources in the repository using the WebDAV. We have provided two examples: Using WebFolders to Access the Repository Resources To add or modify a resource, you must copy the resource to or from the repository using a WebDAV tool. Using WebFolders is an easy way to access the repository and the resources contained in the repository. Note: WebFolders is for Windows machines only. To access the repository, you must be on the same machine where MapInfo Spatial Server and the repository are installed. To configure a WebFolder: Map Tiling Service Guide Chapter 2: Managing Map Tiling Resources and Configuration 11
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 and 8: Managing Map Tiling Resources and C
Page 9: Parameter MimeList MapResolution Ma
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?