geokokos
Joined: 24/03/2016 14:30:25
Messages: 4
Offline
|
Hello,
For a research project, we use search queries similar to this one:
[url]
<a href="http://api.geonames.org/searchJSON?west=-26.0156&maxRows=30&fuzzy=0.8&north=19.4328&username=<USERNAME>&q=engelberg&south=-51.0985&east=84.375&featureCode=HLLS&featureCode=HLL&featureCode=HLLS&featureCode=GAP&featureCode=PK&featureCode=MT&featureCode=PK&featureCode=RK&featureCode=PASS&featureCode=RDGE&featureCode=MTS&featureCode=RDGE&featureCode=RKS&orderby=relevance" target="_blank" rel="nofollow">http://api.geonames.org/searchJSON?west=-26.0156&maxRows=30&fuzzy=0.8&north=19.4328&username=<USERNAME>&q=engelberg&south=-51.0985&east=84.375&featureCode=HLLS&featureCode=HLL&featureCode=HLLS&featureCode=GAP&featureCode=PK&featureCode=MT&featureCode=PK&featureCode=RK&featureCode=PASS&featureCode=RDGE&featureCode=MTS&featureCode=RDGE&featureCode=RKS&orderby=relevance</a>
[/url]
We set a timeout of 5 seconds. Most of these requests do not succeed in this time (timeout). Is there a way for us to structure this query differently to make the server process the query more efficiently (e.g. adjusting the order of query parameters, reducing the number of maxRows, reducing the number of featureCodes,...)?
Thank you for your help.
|