<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16890" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Anselm -</DIV>
<DIV> </DIV>
<DIV>Interesting comment WRT GML. GML is grounded in various ISO TC 211
documents, such as 19107 (spatial schema). GML is an XML grammar for
encoding/modeling geospatial content and is not meant to be a rendering
language. Anyway, GML supports the ability to define multiple CRS (including
local/engineering) and the transforms/conversions associated with them. All GML
CS and CRS elements are based on ISO 19111, spatial referencing by
coordinates.</DIV>
<DIV> </DIV>
<DIV>Regards</DIV>
<DIV><BR>Carl</DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=anselm@gmail.com href="mailto:anselm@gmail.com">Anselm Hook</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=chris@platial.com
href="mailto:chris@platial.com">Chris Goad</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=geojson@lists.geojson.org
href="mailto:geojson@lists.geojson.org">geojson</A> ; <A
title=geowanking@geowanking.org
href="mailto:geowanking@geowanking.org">geowanking@geowanking.org</A> ; <A
title=c.willmes@uni-koeln.de href="mailto:c.willmes@uni-koeln.de">Christian
Willmes</A> ; <A title=georss@lists.eogeo.org
href="mailto:georss@lists.eogeo.org">GeoRSS</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, August 31, 2009 8:47
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [georss] [Geowanking]
[Geojson] simple 3D geocode for AR</DIV>
<DIV><BR></DIV>> Chris Goad writes : <BR>> 3d modeling formalisms
support this (and full GML does too), but GeoRSS, GeoJSON, and KML do
not. This is probably an argument for going to represententations built
for 3d in the first place for AR applications where local coordinates play a
necessary role, but concievably there is a niche for our lightweight geo
standards extended by addition of a transformation node.<BR><BR>I
concur. It's convenient to have an idea of a local coordinate system. I've
always been slightly surprised by how the GML community ignored the work of
the VRML community. Convenience concepts such as transform nodes, multiple
instancing of geometry and behavior nodes make expressing ideas more
succinct.<BR>
<P>
<HR>
<P></P>_______________________________________________<BR>georss mailing
list<BR>georss@lists.eogeo.org<BR>http://lists.eogeo.org/mailman/listinfo/georss<BR></BLOCKQUOTE></BODY></HTML>