Reverse GeoCoder:FAQ - Revision history

Admin at 16:09, 2 August 2022

2022-08-02T16:09:14Z

← Older revision		Revision as of 16:09, 2 August 2022
Line 1:		Line 1:
	[[Reverse GeoCoder\|← Reverse GeoCoder]]		[[Reverse GeoCoder\|← Reverse GeoCoder]]
	{{CustomTOC}}		{{CustomTOC}}
	==Service Returns ~~SE01~~==		==Service Returns GE54==
	;Why Is the service returning ~~SE01~~?		;Why Is the service returning GE54?

	As with most most web services, a request can fail for any number of reasons internal to the service and not due to user configuration. For reverse Geo, this may simply be that the service could not perform all the searches and computations necessary to determine the nearest location to the input before the service timed out. Depending on the use case, decreasing the <code>max distance</code> search radius may actually be the best workaround.		As with most most web services, a request can fail for any number of reasons internal to the service and not due to user configuration. For reverse Geo, this may simply be that the service could not perform all the searches and computations necessary to determine the nearest location to the input before the service timed out. Depending on the use case, decreasing the <code>max distance</code> search radius may actually be the best workaround.

Admin at 15:43, 12 May 2022

2022-05-12T15:43:48Z

← Older revision		Revision as of 15:43, 12 May 2022
Line 1:		Line 1:
	[[Reverse GeoCoder\|← Reverse GeoCoder]]		[[Reverse GeoCoder\|← Reverse GeoCoder]]
	{{CustomTOC}}		{{CustomTOC}}
			==Service Returns SE01==
			;Why Is the service returning SE01?

			As with most most web services, a request can fail for any number of reasons internal to the service and not due to user configuration. For reverse Geo, this may simply be that the service could not perform all the searches and computations necessary to determine the nearest location to the input before the service timed out. Depending on the use case, decreasing the <code>max distance</code> search radius may actually be the best workaround.


	==Maximum Records Per Request==		==Maximum Records Per Request==
	;What's the maximum number of records that the user can get per request?		;What's the maximum number of records that the user can get per request?

Admin at 00:22, 19 April 2022

2022-04-19T00:22:19Z

← Older revision		Revision as of 00:22, 19 April 2022
Line 41:		Line 41:
	==Service Throughput==		==Service Throughput==
	;What is the expected throughput?		;What is the expected throughput?

	~~The expected throughput is approximately 1,500,000 records per hour.~~

	:{\| class="alternate01"		:{\| class="alternate01"

Admin at 00:21, 30 March 2022

2022-03-30T00:21:26Z

@@ Line 31: / Line 31: @@
 The Distance returned (in miles) between the input and the output point will serve as an indicator of accuracy. A distance of zero means an exact match was returned.
 [[Category:Reverse GeoCoder]]
 [[Category:FAQ]]

Admin: Admin moved page Reverse GeoCoder Web Service:FAQ to Reverse GeoCoder:FAQ

2015-03-10T23:11:15Z

Admin moved page Reverse GeoCoder Web Service:FAQ to Reverse GeoCoder:FAQ

← Older revision	Revision as of 23:11, 10 March 2015
(No difference)

Admin at 23:11, 10 March 2015

2015-03-10T23:11:04Z

← Older revision		Revision as of 23:11, 10 March 2015
Line 1:		Line 1:
	[[Reverse GeoCoder ~~Web Service~~\|← Reverse GeoCoder ~~Web Service~~]]		[[Reverse GeoCoder\|← Reverse GeoCoder]]
	{{CustomTOC}}		{{CustomTOC}}
	==Maximum Records Per Request==		==Maximum Records Per Request==
Line 33:		Line 33:


	[[Category:Reverse GeoCoder ~~Web Service~~]]		[[Category:Reverse GeoCoder]]
	[[Category:FAQ]]		[[Category:FAQ]]

Admin: Created page with "← Reverse GeoCoder Web Service {{CustomTOC}} ==Maximum Records Per Request== ;What's the maximum number of records that the user can get ..."

2014-10-31T20:44:37Z

Created page with "← Reverse GeoCoder Web Service {{CustomTOC}} ==Maximum Records Per Request== ;What's the maximum number of records that the user can get ..."

New page

[[Reverse GeoCoder Web Service|← Reverse GeoCoder Web Service]]
{{CustomTOC}}
==Maximum Records Per Request==
;What's the maximum number of records that the user can get per request?

The Maximum number of records returned by the service is 100. Setting a higher number (Or no number at all) in the request MaxRecords field will not change this limit.

==Maximum Distance==
;What's the maximum distance allowed?

The Maximum is 10 miles regardless whether the user specifies a higher number in the MaxDistance field, or doesn't specify anything at all.

==Mandatory Fields==
;What fields are mandatory in the request?

The mandatory fields are CustomerID, Latitude and Longitude.
MaxRecords and MaxDistance are optional. If They are not specified, the default value for MaxRecords is 100 records, and for MaxDistance it's 10 miles.

==Supported Lat/Long Formats==
;What Lat/Long formats does the service accept?

The service accepts only the decimal representation of the Lat and Long.
Formats such as: <br>116°14'28.86"W or -116 14 28.86 will not be accepted. East/West, Minutes/Seconds formats will have to be converted by the user prior calling the service.

==Percentage of Accuracy==
;Is there a percentage to the accuracy of the results returned?

The Distance returned (in miles) between the input and the output point will serve as an indicator of accuracy. A distance of zero means an exact match was returned.

[[Category:Reverse GeoCoder Web Service]]
[[Category:FAQ]]