Re: [idvusers] Issues opening NetCDF trajectory file in IDV and ToolsUI

Hi,

The attached NetCDF file is a valid "Track file" Data type. The IDV can
open it and  display the parameters (platform speed, temperature...). What
modifications have I do?
I must rename the latitude, longitude and altitude coordinates variables.
The original name was "LAT", "LON" and "ALT",
now "latitude, "longitude" and "altitude".
Maybe, the NetCDF library looks for the coordinate variable from the
variable name, not the standard name. It should look for the standar
name... no?


El 6 de marzo de 2012 09:38, Kristian Sebastián <ksebastian@xxxxxxxx>escribió:

> Hi Yuan Ho,
>
> We have also glider trajectories and we can open them with the IDV as
> "Track file" data type. But if I open the surface drifter NetCDF file as
> track file the IDV throws the exception attached in the TrackFileError
> image. That's why testing the "Trajectory Sounding files" Data type is see
> the time issue. I can't change the time units to seconds since 1980-01-06
> 00:00:00, so more testing is needed!.
>
> Thanks a lot!
>
> 2012/3/6 Yuan Ho <yuanho@xxxxxxxxxxxxxxxx>
>
>> On 3/5/2012 2:13 AM, Kristian Sebastián wrote:
>>
>>> Hi,
>>>
>>> We save the surface drifter data in NetCDF format and CF-1.6 ( like the
>>> "dep0002_idrifter003_scb-**idrifter003_L1_2012-02_depth.**nc" attached
>>> file).
>>> When we try to display it through the IDV some issue :
>>>
>>>    - The "Data Source type" selected to open the NetCDF file is
>>> "Trajectory
>>>
>>>    Sounding Files" no "Track files" (throws a BadDataexpception). Is the
>>> data
>>>    type correct?
>>>
>>
>> Trajectory sounding Files is designed for the COMSIC dataset, if you want
>> to use this type, you need to modify unit of time of your dataset to
>> seconds since 1980-01-06 00:00:00, and the values too.
>>
>>
>>
>> Yuan
>>
>>>    - We can display the trajectory and the parameters like temperature,
>>>
>>>    platform speed ... but the displayed time in IDV is wrong
>>> "3645241-01-9"
>>>    (view MapViewSurfaceDrifterWrongTime image)
>>>    - The axis Z is defined with the ALT (standard_name = altitude)
>>>
>>>    variable, but if the axis Z with the DEPTH (standard_name = depth)
>>>    variable, only the bounding box is displayed in the "Map View" (view
>>>    MapViewSurfaceDrifterOnlyBound**ingBox image)
>>>
>>> I have also tried to open the file with the ToolsUI-4.2.18 but I can't
>>> open
>>> it as "Trajetory" in the "FeatureType" (view FailedTodFindDataTypeFactory
>>> image).
>>> The coordinate system seems to be ok, I have checked it opening the file
>>> with the tab "CoordSys".
>>> As "PointFeature"-"TRAJECTORY" is possible to open it and display all the
>>> dataset values (view PointFeatureTRAJECTORY image). The time values seems
>>> to be ok, I don't why in the IDV the time value is wrong. An "unknown"
>>> point is displayed in the map.
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>> ______________________________**_________________
>>> idvusers mailing list
>>> idvusers@xxxxxxxxxxxxxxxx
>>> For list information, to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/**mailing_lists/<http://www.unidata.ucar.edu/mailing_lists/>
>>>
>>
>> ______________________________**_________________
>> idvusers mailing list
>> idvusers@xxxxxxxxxxxxxxxx
>> For list information, to unsubscribe, visit: http://www.unidata.ucar.edu/
>> **mailing_lists/ <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>
>
>
>


-- 

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

Attachment: dep0002_idrifter003_scb-idrifter003_L1_2012-02_depth.nc
Description: Cdf file