Blind spots for oceanJSON service?

jlmt — GMT

Hi, Have just discovered geonames, it looks like some of the JSON services could be very useful for a project I have coming up. I'm at the stage of trying out a few of the URIs, but I'm running into what seem to be blind spots on the map. For example, lat= 0.0, lng = 0.0, is a location at sea in the South Atlantic Ocean, but the following URL: http://ws.geonames.org/oceanJSON?formatted=true&lat=0&lng=0&style=full returns only: Code:

{"status": { "message": "we are afraid we could not find an ocean for latitude and longitude :0.0,0.0", "value": 15}}

I get similar results for 30, -30, which should be in the middle of the North Atlantic: http://ws.geonames.org/oceanJSON?formatted=true&lat=30&lng=-30&style=full Code:

{"status": { "message": "we are afraid we could not find an ocean for latitude and longitude :30.0,-30.0", "value": 15}}

Am I misinterpreting something here? I'd assumed I should be able to give any at-sea coordinate and get back the name of the ocean in which it falls. Cheers

Re:Blind spots for oceanJSON service?

marc — GMT

you are right there was a problem with input parameters exactly on the border between two oceans and it did not return any one of the two. Marc

Re:Blind spots for oceanJSON service?

jlmt — GMT

Marc, thanks, works great now!

Latest posts for the topic "Blind spots for oceanJSON service?"

Blind spots for oceanJSON service?

Re:Blind spots for oceanJSON service?

Re:Blind spots for oceanJSON service?