Reverse GeoCoder:Result Codes: Difference between revisions
No edit summary |
No edit summary |
||
Line 20: | Line 20: | ||
|- | |- | ||
|[[Reverse GeoCoder Web Service:Request Elements|Request Elements]] | |[[Reverse GeoCoder Web Service:Request Elements|Request Elements]] | ||
|- | |- | ||
|[[Reverse GeoCoder Web Service:Example Request|Example Request]] | |[[Reverse GeoCoder Web Service:Example Request|Example Request]] |
Revision as of 23:28, 2 October 2014
← Reverse GeoCoder Web Service Reference
Reverse GeoCoder Web Service Navigation | ||||
---|---|---|---|---|
| ||||
| ||||
| ||||
| ||||
|
Result Code Use
Melissa Data's products use a result code system to indicate data quality; the status and any errors. These result codes are four-character codes (two letters followed by two numbers), delimited by commas. Result code definitions are shared among Melissa Data products.
Example
An example returned result code string:
GS07
Instead of looking at multiple properties and methods to determine status, you can look at the output of the results parameter.
From this output you can determine that the address is:
Code | Short Description | Long Description |
---|---|---|
GS07 | Records Found | The service successfully reverse geocoded the input coordinates and returned addresses. |
Be sure to reference Result Codes for a list of Melissa Data's result codes.
Understanding the Code
To fully understand result codes, you need to know them. Knowing what codes are possible and what they indicate will be key in building an effective application. It is useful to know all the codes, but this does not necessarily mean you will use them all. Just because you have a toolbox, doesn't mean you will also try to use a screwdriver along with a hammer on a nail.