Mapping Borehole observations using a true 1-D CRS

Comments

2 comments posted
A bit pedantic, perhaps, but

A bit pedantic, perhaps, but I'm sure that CityGML 2 is a GML 3.1.1 application schema, not GML 3.2.

Posted by Peter Parslow (not verified) on Wed, 2013-01-16 08:27
This is very relevant work

This is very relevant work indeed - exciting to see how we gradually break free from the traditional view that there is lat and long, "and nothing else matters". OGC has taken a lead in establishing a CRS universe that can deal with truly multi-dimensional CRSs (and 1-D is a special case, after all). There is a Candidate Best Practice document [1], already resolved by the Web Coverage Service (WCS) group which, due to the nature of their data, is a forerunner in this field. This document establishes rules for identifying CRSs, and even allows to create ad-hoc combinations of existing CRSs. For example, a lat/lon/t CRS for satellite image timeseries might be composed from WGS84 and ISO 88601, which describes temporal CRSs.

Of course, using the coordinate facilities for storing points with a total different meaning - as done in the project reported - is a hack of the tools. But as we have no choice with current tools, given their lack of support beyond lat/lon, this endeavor constitutes an interesting experiment, and hopefully an incentive for GIS developers to boldly go into new dimensions. We are living in exciting times...

This is very relevant work indeed - exciting to see how we gradually break free from the traditional view that there is lat and long, "and nothing else matters". OGC has taken a lead in establishing a CRS universe that can deal with truly multi-dimensional CRSs (and 1-D is a special case, after all). There is a Candidate Best Practice document [1], already resolved by the Web Coverage Service (WCS) group which, due to the nature of their data, is a forerunner in this field. This document establishes rules for identifying CRSs, and even allows to create ad-hoc combinations of existing CRSs. For example, a lat/lon/t CRS for satellite image timeseries might be composed from WGS84 and ISO 8601, which describes temporal CRSs. An open-source implementation handling such CRS identifiers has been completed and is available meantime.

Of course, using the coordinate facilities for storing points with a total different meaning - as done in the project reported - is a hack of the tools. But as we have no choice with current tools, given their lack of support beyond lat/lon, this endeavor constitutes an interesting experiment, and hopefully an incentive for GIS developers to boldly go into new dimensions. We are living in exciting times...

[1] http://www.ogcnetwork.net/system/files/11-135_OGC-NA_Name-Type-Specification-for-CRSs_2012-08-07.pdf

Posted by Peter Baumann (not verified) on Wed, 2012-08-22 08:35