Re: [thredds] Retrieve THREDDS metada from the NetCDF file

Ah, okay -- I didn't realize you wanted specifically THREDDS metadata.   To
enable search across multiple THREDDS catalogs (as well as other OGC and
community services) ,  we've be avoiding the direct use of THREDDS metadata
in favor of the ncISO metadata, which we then harvest using GI-CAT or
GeoPortal Server.    An application can query GI-CAT or Geoportal Server
using OpenSearch or CSW, and then process the DAP data URLS matching the
query constraints.
Is this similar to what you are trying to do?

Rich: Yes is what I am trying to do. But, I think the THREDDS metadata
displayed helps to know about the dataset without examine it with the
services (ISO, opendap,...). So, maybe you could retrieve the THREEDS
metadata from the ISO service. It's a suggestion.

Feature collections know how to add these 3 metadata elements
automaticallly, because they understand "what the data is", eg how to
extract that info.  You have to add this manually for plain ole datasets. i
think that for the TDS, the future is all about feature collections.

John: Ok. I undertand feature collections will include the observation data
and automatically add the 3 metadata elements, Is that correct?

Thanks a lot!

El 8 de marzo de 2012 16:22, John Caron <caron@xxxxxxxxxxxxxxxx> escribió:

>  On 3/8/2012 6:56 AM, Kristian Sebastián wrote:
>
> Hi Rich,
>
>  Actually, our Thredds thredds.socib.es have the ncISO services enable.
> So, I think the ncISO doesn't add  "Time coverage", "Geospatial coverage"
> and "variables" metadata (link to the dataset example
> http://thredds.socib.es/thredds/catalog/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/catalog.html?dataset=mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc
> ):
>
>>  Catalog
>> http://thredds.socib.es/thredds/catalog/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/catalog.html
>>  Dataset:
>> L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc
>>
>>    - *Data size: *1.298 Mbytes
>>    - *Data type: *STATION
>>    - *ID: *
>>    
>> mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc
>>
>> Access:
>>
>>    1. *OPENDAP:*
>>    
>> /thredds/dodsC/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc<http://thredds.socib.es/thredds/dodsC/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc.html>
>>    2. *HTTPServer:*
>>    
>> /thredds/fileServer/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc<http://thredds.socib.es/thredds/fileServer/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>    3. *NCML:*
>>    
>> /thredds/ncml/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc<http://thredds.socib.es/thredds/ncml/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>    4. *UDDC:*
>>    
>> /thredds/uddc/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc<http://thredds.socib.es/thredds/uddc/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>    5. *ISO:*
>>    
>> /thredds/iso/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc<http://thredds.socib.es/thredds/iso/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>
>> Dates:
>>
>>    - 2012-03-08 13:20:02Z *(modified)*
>>
>> Properties:
>>
>>    - viewer = "
>>    http://www.socib.es/jwebchart/webncdump/?file={url},webncdump";
>>    - viewer2 = "http://www.socib.es/jwebchart/?file={url},jwebchart";
>>
>> Viewers:
>>
>>    - NetCDF-Java ToolsUI 
>> (webstart)<http://thredds.socib.es/thredds/view/ToolsUI.jnlp?catalog=http://thredds.socib.es/thredds/catalog/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/catalog.xml&dataset=mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>    - 
>> webncdump<http://www.socib.es/jwebchart/webncdump/?file=http://thredds.socib.es/thredds/dodsC/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>    - 
>> jwebchart<http://www.socib.es/jwebchart/?file=http://thredds.socib.es/thredds/dodsC/mooring/oceanographic_buoy/buoy_bahiadepalma-ime_buoy001/L1/dep0003_buoy-bahiadepalma_ime-buoy001_L1_latest.nc>
>>
>>
>  But, we have configured a Forecast Model Run (
> http://thredds.socib.es/thredds/catalog/operational_models/oceanographical/hydrodynamics/model_run_aggregation/wmed/catalog.html?dataset=operational_models/oceanographical/hydrodynamics/model_run_aggregation/wmed/wmed_best.ncd)
> Collection following the Feature Collection 
> Tutorial<http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/tutorial/FeatureCollectionsTutorial.html>.
> As you can see, the  "TimeCoverage", "GeospatialCoverage" and "Variables"
> metadata is displayed.
>
>> Variables:
>>
>>    - *Vocabulary* [CF-1.0]:
>>       - *dens* = *potential density* = sea_water_potential_density (kg
>>       m-3)
>>       - *salt* = *salinity* = sea_water_salinity
>>       - *temp* = *potential temperature* =
>>       sea_water_potential_temperature (Celsius)
>>       - *u* = *u-momentum component* = eastward_sea_water_velocity
>>       (meter second-1)
>>       - *ubar* = *vertically integrated u-momentum component* =
>>       barotropic_eastward_sea_water_velocity (meter second-1)
>>       - *v* = *v-momentum component* = northward_sea_water_velocity
>>       (meter second-1)
>>       - *vbar* = *vertically integrated v-momentum component* =
>>       barotropic_northward_sea_water_velocity (meter second-1)
>>       - *zeta* = *free-surface* = sea_surface_height_above_sea_level
>>       (meter)
>>
>> GeospatialCoverage:
>>
>>    - *Longitude: *-5.8 to 9.2 degrees_east
>>    - *Latitude: *34.9 to 44.70621220623353 degrees_north
>>
>> TimeCoverage:
>>
>>    - *Start: *2012-03-06 00:00:00Z
>>    - *End: *2012-03-10 00:00:00Z
>>    - *Duration: *4.0 days
>>
>>  So, I don't know why the metadata is displayed in the feature
> collections and not in the other datasets.
>
>
>  Hi Kristian:
>
> Feature collections know how to add these 3 metadata elements
> automaticallly, because they understand "what the data is", eg how to
> extract that info.  You have to add this manually for plain ole datasets. i
> think that for the TDS, the future is all about feature collections.
>
> John
>
>
> _______________________________________________
> thredds mailing list
> thredds@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
> http://www.unidata.ucar.edu/mailing_lists/
>



-- 

Kristian Sebastian Blalid
SOS Division: Data Center Technical
Tel: 971439860 - Fax: 971439979
E-mail: kristian.sebastian@xxxxxxxx <sonia.gomara@xxxxxxxx> /
kristian.sebastian@xxxxxx <sonia.gomara@xxxxxx>

PNG image