computation of geospatial coverage altitude?

[unidata]

computation of geospatial coverage altitude?

[madry]

Ellyn,

Can you send me one of the original files, or turn on http access for
the Eurostrataform Pasta Experiment? If you send me your NcML/catalog
snippet, I'll see what happens when I put it in a TDS.

Thanks,
Lansing

On 6/17/2013 2:02 PM, Ellyn Montgomery wrote:

Folks-

Not sure if this is a THREDDS issue or not, but please steer me in the
right direction.

For an adcp file with samples between 6 and -0.5 (6 meters deep to
just above the surface), I think I have positive-down in the right
place in my ncml, but the geospatial metadata doesn't seem to pick up
on it.

For my files with multiple depths, I put this in my geospatial
coverage (metadata inherited=true):

6.044800
6.5
meters

Then have this in my depth variable:

but end up with the wrong thing (Altitude should be 6.0488 to -0.5
(positive is DOWN)) in geospatial bounds on the dataset page:
GeospatialCoverage:
Longitude: 13.7566 to 13.7566 degrees_west
Latitude: 43.296902 to 43.296902 degrees_north
Altitude: 6.0448 to 12.5448 meters (positive is up)

for an example see:
http://geoport-dev.whoi.edu/thredds/ts/EUROSTRATAFORM.html?dataset=EUROSTRATAFORM/7011adc-a_2d.nc

Do I need to tell the geospatial bounds metadata that positive is down?

Thanks for any suggestions!
Best, Ellyn

—
Reply to this email directly or view it on GitHub
#25.

[dopplershift]

Closing because there been no response for over 1 year. Feel free to re-open if this is still an issue.