Opensearch.m needs an upgrade to decode data URLs from latest GI-CAT

[GoogleCodeExporter]

The representation of data endpoints is different in ncISO 2.0 than in ncISO 
1.1.  GI-CAT was updated to harvest these URLS, and the OpenSearch response on 
GI-CAT as modified to return these URLS as well.

We now need to modify our opensearch.m file to retrieve these service endpoints 
reliably and easily. 

ncISO 1.1 was introduced with TDS 4.2.6
ncISO 2.0 was introduced with TDS 4.2.8

Here's a sample query:
<http://testbedapps.sura.org/gi-cat/services/opensearch?&si=1&ct=1000&rel=overla
ps&st=watlev&bbox=-90,
27, -87, 
31&loc=&ts=2008-09-01T00:00:00Z&te=2008-10-01T00:00:00Z&outputFormat=application
/atom+xml&enableCrawling=false>

And the links are returned in blocks that look like this:

http://codepad.org/H1aJv4Ct

The old regexp technique won't work, so how best to accomplish our goals?

Is this overkill?
https://beagle.whoi.edu/redmine/projects/ibt/wiki/Accessing_IFCB_data_from_Matla
b

Original issue reported on code.google.com by rsignell on 2 Apr 2012 at 12:42

[GoogleCodeExporter]

I've been playing around with this for a while. Do we think that the 1.1 
profile, should be supported? It wont ever be the real official ISO spec, but 
some servers may never get around to updating to the real specification (2.x). 
The trouble is that I can't tell if the response identifies itself in a clear 
way as one or the other. A user could input, if they knew, but I don't know if 
we can assume that users will know. I'm stumped.

Original comment by crosb...@gmail.com on 20 Apr 2012 at 4:03

[GoogleCodeExporter]

I suggest you ask the GI-CAT developers for their advice (Enrico & co)

Original comment by rsignell on 20 Apr 2012 at 5:00

[GoogleCodeExporter]

Original comment by crosb...@gmail.com on 21 Jun 2012 at 4:16

• Changed state: Started

[GoogleCodeExporter]

Original comment by crosb...@gmail.com on 21 Jan 2013 at 4:50

• Added labels: Priority-Critical, Type-Defect
• Removed labels: Priority-Medium, Type-Enhancement

[GoogleCodeExporter]

Attempted fix here: 
http://code.google.com/p/nctoolbox/source/detail?r=7892a8e0a22f81c524e3bfd5cf1f1
61c46b2e0fa

Please pull the changes and see if this works for your use cases and if it 
continues to work in contrib/gi_cat_demo.m. The geoport GICAT doesn't seem to 
be up, so I can't test with the older style response.

Original comment by crosb...@gmail.com on 21 Jan 2013 at 8:51

• Changed state: Fixed

[GoogleCodeExporter]

Any luck?

Original comment by crosb...@gmail.com on 1 Feb 2013 at 6:49