[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #RMR-226806]: ncml on TDS server



> Hi Yuan
> 
> They are up on the server:
> 
> http://staging.asascience.com:8989/thredds/test.html
> 
> I have http file transfer available as well as the opendap service so you 
> should be able to download them.
> 
> I have made a simple wrapper for the actual NC file hosted on the server: 
> Simple_ncml_wrapper
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"; 
> location="http://staging.asascience.com:8989/thredds/dodsC/idvtest/ctd.nc"/>
> 
> This does not work, but the actual nc file does.
David,
     I tried this as a local file or remote dods link, both cases worked ok. 
The actual nc file does work faster, and the wrapper ncml file very very slow, 
since you are making 16000 dods requests. If you are wrapping a local file, it 
works the same speed. 
     But, you don't need to dig into this as we are moving into the feature 
type. Here is something you can try, under the featureTypes tab, there is 
pointFeature tab and featurescan tab, you should try to play with all your 
point data here, if you get any 400 error, simply changing http to dods in your 
link.


Yuan
> 
> You can experiment with the three files:
> CTD_nc
> CTD_ncml
> Simple_ncml_wrapper
> 
> David
> 
> 
> 
> -----Original Message-----
> From: Unidata IDV Support [mailto:address@hidden]
> Sent: Friday, August 07, 2009 1:39 PM
> To: David Stuebe
> Subject: [IDV #RMR-226806]: ncml on TDS server
> 
> >
> > Hi Yuan
> >
> > The ctd.nc file is created using the NCML file with netcdf java tools. They 
> > should be two different representations of the exact same data model. That 
> > is why I am concerned that one works and the other does not. The actual 
> > error returned is a server error type 400. This is consistent with the 
> > client (IDV) opening the file but not requesting a specific data type
> 
> David,
> Could you send me the ncml file and the nc file to be wrapped inside this 
> ncml file? Or, you can add them to your TDS server.
> 
> 
> Yuan
> >
> >
> > http://staging.asascience.com:8989/thredds/dodsC/idvtest/ctd.ncml?altitude[0:50:16165]
> >    - returns error 400
> >
> > http://staging.asascience.com:8989/thredds/dodsC/idvtest/ctd.ncml.ascii?altitude[0:1:16165]
> >    - works!
> >
> > I think IDV is not specifying the request correctly for NCML files in the 
> > trajectory reader.
> >
> > I use NCML rappers all the time on other grid datasets etc...
> >
> > David
> >
> > -----Original Message-----
> > From: Unidata IDV Support [mailto:address@hidden]
> > Sent: Friday, August 07, 2009 12:07 PM
> > To: David Stuebe
> > Subject: [IDV #RMR-226806]: ncml on TDS server
> >
> > >
> > > Hi Yuan
> > >
> > > My webmail does not handle replies properly for inline formatting 
> > > >,>>,>>> etc... sorry.
> > >
> > > Thanks for your quick reply. I have had trouble figuring out how to 
> > > properly specify that the File is a trajectory, but I found a method that 
> > > works as an NC file. My concern is that the NC file works while the NCML 
> > > file which I created it from does not when served from TDS?
> > >
> > > I can open the NCML file from TDS using UITools with feature type 
> > > trajectory? see attached. So it seems strange that one works and the 
> > > other does not...
> > >
> > > In any case, can you tell me the correct metadata to repair the issue? I 
> > > have not been able to find a correct example anywhere?
> > >
> > > Thanks
> > >
> > > David
> > David,
> > I can not open your attached file. I tried the new ToolUI on ctd.nc, it is 
> > working ok as a point feature type, but your ncml modification makes it 
> > fail. I think you don't need this ncml. I was not able to open either files 
> > as a feature type trajectory, which is under datatype adapter and 
> > difference from feature type routine, I know it is confusing here. Anyway, 
> > the ctd.nc is ok, you don't need to do anything at this moment since the 
> > feature type is still in the development, your example file may be a test 
> > case for us.
> >
> >
> > Yuan
> > >
> > >
> > > -----Original Message-----
> > > From: Unidata IDV Support [mailto:address@hidden]
> > > Sent: Thu 8/6/2009 4:37 PM
> > > To: David Stuebe
> > > Cc: address@hidden
> > > Subject: [IDV #RMR-226806]: ncml on TDS server
> > >
> > > >
> > > >
> > > > Hey IDV folks
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I am having trouble opening a NCML file on a thredds server.
> > > >
> > > > http://staging.asascience.com:8989/thredds/test.xml
> > > >
> > > >
> > > >
> > > > There are two data sets:
> > > >
> > > > CTD_NC
> > > >
> > > > CTD_ncml
> > > >
> > > >
> > > >
> > > > IDV can:
> > > >
> > > > Open the same ncml locally...
> > > >
> > > > Open the NC file with the same description
> > > >
> > > >
> > > >
> > > > But when I put the ncml through the TDS I get the following?
> > > >
> > > >
> > > Hi David,
> > > The problem is that neither the nc nor ncml file properly define this 
> > > file as a trajectory dataset, so when the IDV opened this file through 
> > > the TDS server, it would try to do it as a typed dataset. Unless you add 
> > > an adapter to the trajectory type dataset to this specific file, you will 
> > > not be able to use a TDS server to serve this file. When you opened both 
> > > nc and ncml file as local file, the IDV just tried it as a netcdf file 
> > > and will not have any problem.
> > >
> > >
> > > Yuan
> > > >
> > > > java.io.IOException: Server returned HTTP response code: 400 for URL:
> > > > http://staging.asascience.com:8989/thredds/dodsC/idvtest/ctd.ncml
> > > >
> > > > at
> > > > sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
> > > > Source)
> > > >
> > > > at
> > > > org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown
> > > > Source)
> > > >
> > > > at
> > > > org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown
> > > > Source)
> > > >
> > > > at
> > > > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> > > >
> > > > at
> > > > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> > > >
> > > > at org.apache.xerces.parsers.XMLParser.parse(Unknown
> > > > Source)
> > > >
> > > > at
> > > > org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> > > >
> > > > at
> > > > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> > > >
> > > > at org.jdom.input.SAXBuilder.build(SAXBuilder.java:489)
> > > >
> > > > at org.jdom.input.SAXBuilder.build(SAXBuilder.java:847)
> > > >
> > > > at
> > > > ucar.nc2.ncml.NcMLReader.readNcML(NcMLReader.java:213)
> > > >
> > > > at
> > > > ucar.nc2.ncml.NcMLReader.readNcML(NcMLReader.java:184)
> > > >
> > > > at
> > > > ucar.nc2.dataset.NetcdfDataset.acquireNcml(NetcdfDataset.java:788)
> > > >
> > > > at
> > > > ucar.nc2.dataset.NetcdfDataset.openOrAcquireFile(NetcdfDataset.java:664)
> > > >
> > > > at
> > > > ucar.nc2.dataset.NetcdfDataset.openDataset(NetcdfDataset.java:434)
> > > >
> > > > at
> > > > ucar.nc2.dataset.NetcdfDataset.acquireDataset(NetcdfDataset.java:514)
> > > >
> > > > at
> > > > ucar.nc2.dataset.NetcdfDataset.acquireDataset(NetcdfDataset.java:491)
> > > >
> > > > at
> > > > ucar.nc2.dt.TypedDatasetFactory.open(TypedDatasetFactory.java:155)
> > > >
> > > > at
> > > > ucar.unidata.data.sounding.CdmTrackAdapter.<init>(CdmTrackAdapter.java:1
> > > > 24)
> > > >
> > > > at
> > > > ucar.unidata.data.sounding.TrackDataSource.doMakeAdapter(TrackDataSource
> > > > .java:533)
> > > >
> > > > at
> > > > ucar.unidata.data.sounding.TrackDataSource.initTrack(TrackDataSource.jav
> > > > a:489)
> > > >
> > > > at
> > > > ucar.unidata.data.sounding.TrackDataSource.getAdapters(TrackDataSource.j
> > > > ava:547)
> > > >
> > > > at
> > > > ucar.unidata.data.sounding.TrackDataSource.initAfter(TrackDataSource.jav
> > > > a:268)
> > > >
> > > > at
> > > > ucar.unidata.data.DataSourceImpl.initAfterCreation(DataSourceImpl.java:7
> > > > 27)
> > > >
> > > > at
> > > > ucar.unidata.data.FilesDataSource.initAfterCreation(FilesDataSource.java
> > > > :270)
> > > >
> > > > at
> > > > ucar.unidata.data.sounding.TrackDataSource.initAfterCreation(TrackDataSo
> > > > urce.java:283)
> > > >
> > > > at
> > > > ucar.unidata.data.DataManager.createDataSource(DataManager.java:1490)
> > > >
> > > > at
> > > > ucar.unidata.idv.IntegratedDataViewer.createDataSource(IntegratedDataVie
> > > > wer.java:1967)
> > > >
> > > > at
> > > > ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataViewe
> > > > r.java:1884)
> > > >
> > > > at
> > > > ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataViewe
> > > > r.java:1818)
> > > >
> > > > at
> > > > ucar.unidata.idv.IntegratedDataViewer.makeDataSource(IntegratedDataViewe
> > > > r.java:1791)
> > > >
> > > > at
> > > > ucar.unidata.idv.chooser.IdvChooser.makeDataSource(IdvChooser.java:907)
> > > >
> > > > at
> > > > ucar.unidata.idv.chooser.ThreddsHandler.processNodes(ThreddsHandler.java
> > > > :745)
> > > >
> > > > at
> > > > ucar.unidata.idv.chooser.ThreddsHandler.doLoad(ThreddsHandler.java:604)
> > > >
> > > > at
> > > > ucar.unidata.idv.chooser.XmlChooser.doLoadInThread(XmlChooser.java:672)
> > > >
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > > Method)
> > > >
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > > > Source)
> > > >
> > > > at
> > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> > > >
> > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > >
> > > > at ucar.unidata.util.Misc$2.run(Misc.java:1033)
> > > >
> > > > at ucar.unidata.util.Misc$3.run(Misc.java:1061)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > This URL does indeed return a error 400 - there should be something on
> > > > the end to get the opendap data I think?
> > > >
> > > > http://staging.asascience.com:8989/thredds/dodsC/idvtest/ctd.ncml
> > > >
> > > >
> > > >
> > > > For instance...
> > > >
> > > > http://staging.asascience.com:8989/thredds/dodsC/idvtest/ctd.ncml?altitu
> > > > de[0:1:16165]
> > > >
> > > >
> > > >
> > > > Hope this helps and feel free to try the server yourself!
> > > >
> > > >
> > > >
> > > > David Stuebe
> > > >
> > > >
> > > >
> > > > Applied Science Associates
> > > >
> > > > 55 Village Square Drive
> > > >
> > > > South Kingstown, RI 02879
> > > >
> > > >
> > > >
> > > > Phone:  401 789 6224
> > > >
> > > > Web:      www.asascience.com
> > > >
> > > > Email:     address@hidden
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: RMR-226806
> > > Department: Support IDV
> > > Priority: Normal
> > > Status: Open
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: RMR-226806
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: RMR-226806
> Department: Support IDV
> Priority: Normal
> Status: Open
> 
> 


Ticket Details
===================
Ticket ID: RMR-226806
Department: Support IDV
Priority: Normal
Status: Open