search

bsed / ala

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

Batch intersect failing #766

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Batch intersect seems to be broken

http://spatial.ala.org.au/ws/intersect/batch  

The example in the ALA4R package that previously worked is now throwing an 
error, as is the example on the API page.

The status info seems to go directly from "waiting" (in queue) to "error".

Original issue reported on code.google.com by antarcti...@gmail.com on 18 Aug 2014 at 12:24

GoogleCodeExporter commented 9 years ago 
Update: GET version seems to work 
(http://spatial.ala.org.au/ws/intersect/batch?fids=cl22,cl23,el773&points=-29,13
0,-27,132) POST does not

Checking our POST code now, but it used to work!

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 12:33

GoogleCodeExporter commented 9 years ago 
If it helps, the service is thinks fids and points are not supplied.

Original comment by adam.col...@gmail.com on 18 Aug 2014 at 12:35

GoogleCodeExporter commented 9 years ago 
If that's for the API example, that's because we've noticed that the API 
example does not provide fids or points!

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 12:36

GoogleCodeExporter commented 9 years ago 
Pretty sure it's not the POST code at our end. We've dropped back to the GET 
version as a temporary workaround, for short enough URLs.

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 12:59

GoogleCodeExporter commented 9 years ago 
Odd.  POST is working when I test it.

Original comment by adam.col...@gmail.com on 18 Aug 2014 at 1:00

GoogleCodeExporter commented 9 years ago 
So we are POSTing to http://spatial.ala.org.au/ws/intersect/batch  with a body 
of (e.g.)

fids=cl22,cl23,el773&points=-29,130,-27,132

Is that wrong?

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 1:45

GoogleCodeExporter commented 9 years ago 
Can you try the POST without the content type application/json? Seems to help.

Original comment by adam.col...@gmail.com on 18 Aug 2014 at 2:36

GoogleCodeExporter commented 9 years ago 
OK, POST without setting the Content-Type header seems to work, thanks. I've 
tried our other functions that use POST operations and I think they are all OK 
without this set as well. Should we be safe in leaving the content-type unset 
by default (for all services)?

(We have one remaining problem with POST but I'm pretty sure it's at our end)

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 3:36

GoogleCodeExporter commented 9 years ago 
Should be safe without setting content-type.

Original comment by adam.col...@gmail.com on 18 Aug 2014 at 3:41

GoogleCodeExporter commented 9 years ago 
Goodo, close this issue then

thanks

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 3:52

GoogleCodeExporter commented 9 years ago 
Just for future reference, Content-Type=application/json IS required for the 
BIE bulk names lookup service. (Not a problem for us, we are setting it for 
this service only and not others)

Original comment by antarcti...@gmail.com on 18 Aug 2014 at 5:29

GoogleCodeExporter commented 9 years ago

Original comment by leebel...@gmail.com on 18 Aug 2014 at 5:34