sci.geo.meteorology (Meteorology) (sci.geo.meteorology) For the discussion of meteorology and related topics.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1   Report Post  
Old March 11th 05, 08:54 AM posted to sci.geo.meteorology
external usenet poster
 
First recorded activity by Weather-Banter: Mar 2005
Posts: 1
Default Hectopascal as proper geographical vertical coordinate


Anybody who has experience with dealing with hPa as vertical coordinate
in GIS or related systems? Or with the WMS / other OCG standards?


We have implemented software for displaying 2D and 3D meteorological
data [1] in accordance with the WMS (Web Mapping Services) protocol [2].



However, the spesifications for WMS 1.1.1 requires that the vertical
coordinate is an EPSG code [3]. (An EPSG code is a unique shorthand code
for a geographical coordinate system or projection - example: the
EPSG:4326 is the WGS84 (World Geodesic Datum))


The hPa vertical coordinate is not deemed worthy of the honor of an EPSG
code (or we haven't found it). This is not really surprisingly: Using a
layer whose height is highly variable as vertical coordinate is probably
quite absurd for most geographers and GIS people.



To me, it seems we have three strategies:

= Ignore the problem. This leaves us with an WMS server that is "not
really WMS".

= Find an EPSG code for hPa vertical coordinate. This probably involves
hunting down a member of some EPSG working committee and use thumb
screews untill the EPSG standard has been revised to suit our needs.

= Circumvent the problem by using another "dimension" than "elevation".
(See [3]). The problem is that not all clients may recognise what we
mean by our server-defined dimension "hPa-elevation" (or whatever we may
care to call it).



Does anyone have any experience of how to deal with this?



References:
[1] Web client for or meteorological WMS server: http://metoc.met.no

[2] WMS is an OCG (Open Geospatial Consortium) standard
http://www.opengeospatial.org/


[3] From the OCG WMS 1.1.1 spesification:

All Dimensions in a Capabilities XML response are server-defined, with
two exceptions. The dimensions named time and elevation are privileged
special cases, predefined as follows:
Dimension name="time" units="ISO8601" /
Dimension name="elevation" units="EPSG:vertical_datum" /
The units "ISO8601" refers to the Time representation specified in Annex
B. The units "EPSG:vertical_datum" refers to elevation units and a
reference used by one of the European Petroleum Survey Group [ref. 13]
vertical datums (use the actual datum number in place of the string
"vertical_datum").
EXAMPLE: Elevation units given as "EPSG:5030" means "meters above the
WGS84 ellipsoid."


Regards, Jan
--
Jan Kristian Jensen
Norwegian Defense Research Institute

Remove the obvious from the email adress to email me.

Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
sources for geographical data fausty sci.geo.meteorology (Meteorology) 1 March 11th 05 11:31 PM
Meteorologists! Stop it! There is no hectopascal. Beable van Polasm sci.geo.meteorology (Meteorology) 74 October 20th 04 02:11 PM
grib files and coordinate location ob3wan sci.geo.meteorology (Meteorology) 1 January 16th 04 01:56 PM
TRANSDAT - Coordinate Transformation Fred sci.geo.meteorology (Meteorology) 0 December 22nd 03 03:10 PM
Odd rainbow-coloured vertical dark band in cloud Julie Brandon uk.sci.weather (UK Weather) 3 August 24th 03 10:51 AM


All times are GMT. The time now is 07:45 PM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 Weather Banter.
The comments are property of their posters.
 

About Us

"It's about Weather"

 

Copyright © 2017