[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDV #IIB-384472]: topography surface is too tall
- Subject: [IDV #IIB-384472]: topography surface is too tall
- Date: Mon, 30 Sep 2013 14:57:06 -0600
> Geopotential has units of m2/s2.
>
> Yes it is about 1 degree.
> But maybe I wanted the MERRA dataset to have the surface height that
> goes with all the other MERRA datasets fields, on the same grid.
> What do you suggest?
>
I don't think you want to fix this dataset.
> Loading GFS, on another grid and with many fields at incompatible times,
> would be confusing for future users of my MERRA bundles.
>
You can always hide the time of specific display. This is easy.
>
> Is there a fast topographic data server somewhere I should use instead?
> Does it work easily, trying to drape MERRA fields over a different surface
> topography grid?
>
Here is the link:
http://www.ngdc.noaa.gov/mgg/bathymetry/
Yuan
>
> Thanks,
> Brian
>
>
> On Sep 30, 2013, at 1:39 PM, Unidata IDV Support wrote:
>
> >> Full Name: brian mapes
> >> Email Address: address@hidden
> >> Organization: u of miami
> >> Package Version: 4.1 build date:2013-08-02 18:38 UTC
> >> Operating System: Windows 7
> >> Hardware: Java: home: C:\Program Files\IDV_4.1\jre version: 1.6.0_43
> >> j3d:1.5.2 fcs (build4)
> >> Description of problem: Why is the Tibetan Plateau twice as tall as the
> >> ~5000m high Z500 contours here,
> >> even as its color scale shows it should be about 5549 m at the top?
> >>
> >> How can I fix it?
> >>
> >
> > Brian,
> > The value range of the surface geopotential is from 51916 to 103116,
> > and no idea what is its unit. The resolution of the dataset is very low, I
> > think the GFS 0.5 degree dataset is much better if you just want some
> > topography field.
> >
> >
> > Yuan
> >
> >> Do I need to write .ncml to give units to MERRA's surface geopotential
> >> field, and an official formula with metadata units handling, to change
> >> that to meters? (tedious) Or make a new dataset offline and store that on
> >> my RAMADDA?
> >>
> >> Or can I just fix it in IDV somehow, given that this will never change in
> >> time?
> >>
> >> Thanks!
> >> Brian
> >>
> >>
> >>
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: IIB-384472
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> >
>
> Brian Mapes
> address@hidden or address@hidden
>
>
>
>
Ticket Details
===================
Ticket ID: IIB-384472
Department: Support IDV
Priority: Normal
Status: Closed