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

Re: xml representation of TDS dataset contents

Ben Domenico wrote:
Thanks, John,

I'm trying access one variable for all its forecast hours and then perform some arcGIS data analysis operations for each of the forecast hours in order to create an animation in arcMap. I suppose I could ask for all the forecast hours, but then, I'd have to figure out how many forecast hours are in the file once I get it on my local machine.

since you get back a netcdf file, that should be easy enough.

The WCS getCapabilities does not seem to return any information about forecast times. I guess it's time for me to learn the details of WCs describeCoverage.

may be helpful:


Thanks again.

-- Ben

On 10/24/06, *John Caron* <address@hidden <mailto:address@hidden>> wrote:

    Hi Ben:

    If you append "&wantXML" to the showForm URL, you get back the XML
    before its been XSL transformed to HTML, eg:


    unfortunately, the returned XML is an unpublished format, and may
    change in the future. ignore the vertCoord amd missing stuff, and
    you see its a list of the available variables and what forecast
    hours they are available at. The forecast hours do change for some
    models depending on the run time. This is a complication for
    operational models like NCEP.

    the XML returned by WCS is standardized but more complicated, eg:


    we have a new "latest" dataset that should be useful. What problem
    are you trying to solve with knowing the available forecast hours?

    Ben Domenico wrote:
     > Hi,
     > As many of you know, I've been working on scripts to automate the
     > delivery and processing of subsets of datasets from TDS sites.  I've
     > managed to make this work for a few of the model output datasets
     > RUC on motherloade, WRF on lead4).  However, it is clear that the
     > approach I'm using -- basically scraping the HTML of the netCDFserver
     > form for selecting variables, bounding  boxes and forecast times --
     > presents problems because the HTML is very different for different
     > models.  In some cases, it actually seems to change from time to time
     > even for the same model.  Robb has mentioned XML documents that
     > much of the same information in a more systematic and/or consistent
     > format.  I think that would be a better approach.  Maybe the WCS
     > interactions might be a better approach.
     > An example of the difficulties that arise is the fact that different
     > variables have different forecast times and the lists appear in a
     > variety of different ways in the netCDFserver forms for different
     > Please send me whatever suggestions you have for the best way to
     > Thanks.
     > -- Ben
     > PS I realize this is probably not the best time to be distracting you
     > from the training workshop but I thought I'd mention it while it is
     > fresh in my mind.

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.