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

More documents

Recommendations

Info

Request URL Data Types Request URL Data Types 46 The following table lists the common data types for URL parameters to a service method. Although the method parameters (like all URL parameters) are essentially just strings, this table shows how the various types of data must be formatted in the URL of the method call. Note: Name Bounds CoordSys Country Float Integer Language LinearUnit Point Polygon Rectangle String The 'value' portion of a method parameter 'name=value' pair is case sensitive. Description A comma-separated array of four numbers of type Float. A geographical coordinate system. An ISO country code. A floating point number. An integer number. The language used for the service method response. A unit of measure for distance. A point in 2D geometry. A polygon geometry. A rectangle geometry. A string of characters that is not required to be formatted as one of the other data types Format float,float,float,float EPSG format 2 or 3 character ISO country code [sign]integer.integer [sign]integer [ISO language code]_[ISO country code] One of the following values: M, DM, KM, FT, YD, or MI. Example view=-180,-90,180,90 coordsys=EPSG:4269 country=CA radius=6.25 maxCandidates=10 language=en_CA distanceUnit=KM An x and y value pair point=3.57%20-1.89 separated by a space. Both x and y are Float values. In the service request URL, the space separator is encoded as '%20'. An array of Points. Points in the array are separated by a comma character. An array of two Points. The two Points in the array are separated by a comma character. Any string of valid URLencoded characters. polygon=1.23%202.34, 3.45%204.56, ... , 5.67%206.78 rectangle=1.23%202.34, 3.45%204.56 city=New%20York MapInfo Spatial Server 1.0
Name Description in this table. An arbitrary string value. Format Response JSON Data Types Example This section lists the common data types contained in the JSON objects that are returned in the response to a service method request. Note: Note that the data types listed below are distinct from JSON data types. The native JSON data types are Number, String, Boolean, Array, Object, and null. The purpose of this table is to indicate how the various Envinsa data types are formatted in the JSON fields, so you can handle them correctly in your application code. Primitive Types The following table lists the primitive (non-object) data types that may be contained in the JSON response objects. Name CoordSys LinearUnit Country Object Types Description A geographical coordinate system. A unit of measure for distance. An ISO country code. Format EPSG format One of the following values: M, DM, KM, FT, YD, or MI. 2 or 3 character ISO country code Example "coordSys": "EPSG:4269" "distanceUnit": "M" "country": "CAN" This section describes the object data types that may be contained in the JSON response objects. Point A Point object represents a point in the 2D geometry of a geographic coordinate system. Fields A Point object contains the following fields: Field Name x y Map Tiling Service Guide Type Float Float Description The x value of the point. The y value of the point. Appendix A: Common Data Types 47
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 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: Common Data Types This appendix des
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?