bsed / ala

Automatically exported from code.google.com/p/ala
0 stars 0 forks source link

Funny behaviour with http://spatial.ala.org.au/alaspatial/ws/sitesbyspecies #768

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
If I ask for sitesbyspecies in 110E-165E range: 

(In R) sites_by_species("genus:Eucalyptus",wkt="POLYGON((110 -45,165 -45,165 
-10,110 -10,110 -45))",gridsize=1)

(Equivalent direct call) 
http://spatial.ala.org.au/alaspatial/ws/sitesbyspecies?speciesq=genus:Eucalyptus
&qname=data&area=POLYGON((110%20-45,165%20-45,165%20-10,110%20-10,110%20-45))&bs
=http://biocache.ala.org.au/ws/&movingaveragesize=1&gridsize=1&sitesbyspecies=1

then I get records that extend to about 146E.

If I trim down the WKT on the request:

sites_by_species("genus:Eucalyptus",wkt="POLYGON((140 -45,165 -45,165 -10,140 
-10,140 -45))",gridsize=1)

then I get records extending to about 159E

It's not a problem in R - I've checked the actual data files coming back from 
the service directly.

What's going on? I guess there's a lot of Eucalypt records ... is the 500k 
record limit being hit behind the scenes perhaps?

Original issue reported on code.google.com by antarcti...@gmail.com on 2 Oct 2014 at 6:05

GoogleCodeExporter commented 9 years ago
Closing. We no longer use this issue tracker.

Issue raised here: 
https://github.com/AtlasOfLivingAustralia/analysis-service/issues/1

Original comment by moyesyside on 2 Oct 2014 at 6:12