Why am I getting random geocoding failures?


so in performing number of geocodes using unstructured queries, i'm getting random failures (missed geocodes, 0 results). take example:

http://dev.virtualearth.net/rest/v1/locations?include=queryparse&query=111%20genesee%20st,%20buffalo%20ny,%2014202&key=<insert key here>

run in browser. you'll answer on first request. hit f5. maybe try few times. doesn't have fast, we're not trying spam service. hit few times. somewhere in first 10 or there failure. you'll 0 results back.

now if have series of addresses, , run each 1 in sequence, you'll miss few. it's bad 10 out of 100 - it's not i'm hitting same address on , on again, because i'm getting failures new address.

why happen? guess maybe sort of load balancing roulette going on , i'm getting bad server , then. makes creating reliable application *really* difficult.

(ps, it's pretty funny "omg no links until verified" freakout includes urls go own service)

this has been answered several times. if getting empty results being rate limited. rate limiting occurs when frequency of request such account exceed free terms of use. rate limiting occurs on trial , basic (non-enterprise) keys when service under lot of load. done prioritize enterprise (licensed/paying customer) requests. if @ header of response see flag there indicates request has been rate limited. documented on page: http://msdn.microsoft.com/en-us/library/ff701703.aspx

http://rbrundritt.wordpress.com



Bing Maps  >  Bing Maps REST, SOAP, Spatial Data Services



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more