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

More documents

Recommendations

Info

Handling Errors Handling Errors When making requests to the Envinsa REST Interfaces, errors may occur for a variety of reasons. When they do occur, the interfaces return an Error object. Before processing the response from an interface, your client application must first check whether the returned JSON object is an Error object. If it is, your application can examine the contents of the object to determine what type of error occurred, and then call the appropriate error handling code. Error Object An Error object can be identified by its type field, which is set to the String value Error. It has an error field that contains the error details as an object. The object has the following fields: Field Name code message Type String String Description The error code. The error message. The following example illustrates the general form of an Error object: { } "EnvinsaResponse": { "type": "Error", "error": { "code": "8001", "message": "Missing input parameter : point" } } In the above example, the Error object contains an error code of 8001 and an error message of Missing input parameter : point. Error Codes 50 The following table lists the codes and messages for errors that may be generated by the Envinsa REST Interfaces. Note: Errors that are generated by the Envinsa Web Services do not have an error number. MapInfo Spatial Server 1.0
Code 8000 8001 8002 Message Map Tiling Service Guide Service error : message Invalid parameter : message Missing parameter : message Description Appendix B: Errors A general error has occurred. The nature of the error is indicated in the message text. The request URL contained an invalid method parameter value. The request URL did not contain a required method parameter. 51
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 and 46: Common Data Types This appendix des
Page 47 and 48: Name Description in this table. An
Page 49: Errors This appendix describes the
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?