ISSUE-19: How should we represent points?

point-encoding

How should we represent points?

State:
RAISED
Product:
Core FPWD
Raised by:
Raj Singh
Opened on:
2011-05-11
Description:
From: rsingh@opengeospatial.org
Date: Wed May 04 18:22:24 2011
Archived: http://lists.w3.org/Archives/Public/public-poiwg/2011May/0007.html

[[
CHANGE:
<point latitude="42.360890561289295" longitude="-71.09139204025269"/>
TO:
<gml:Point><gml:pos>42.360890561289295 -71.09139204025269</gml:pos></gml:Point>

CHANGE:
<point id="mainpoint" latitude="27.174799" longitude="78.042111" altitude="10m"/>
TO:
<gml:Point id="mainpoint" srsName="urn:ogc:def:crs:EPSG:6.6:4979" srsDimension="3">
<gml:pos>27.174799 78.042111 10</gml:pos>
</gml:Point>

]]
Related Actions Items:
No related actions
Related emails:
  1. Re: 'geo:' URIs (from jens@layar.com on 2011-06-28)
  2. 'geo:' URIs (from alexander.mayrhofer@nic.at on 2011-06-27)
  3. Re: Agenda June 23, 2011 (from ronald@layar.com on 2011-06-23)
  4. Re: Agenda June 23, 2011 (from rsingh@opengeospatial.org on 2011-06-23)
  5. Agenda June 23, 2011 (from ahill@gatech.edu on 2011-06-23)
  6. Re: Agenda 16 June 2011 (from creed@opengeospatial.org on 2011-06-17)
  7. Minutes 16 June 2011 POIWG Teleconference (from mdw@w3.org on 2011-06-16)
  8. Agenda 16 June 2011 (from mdw@w3.org on 2011-06-16)
  9. Agenda June 16, 2011 (from ahill@gatech.edu on 2011-06-15)
  10. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from rsingh@opengeospatial.org on 2011-06-15)
  11. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from darkflame@gmail.com on 2011-06-15)
  12. RE: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from karl.seiler@navteq.com on 2011-06-15)
  13. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from jens@layar.com on 2011-06-15)
  14. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from rsingh@opengeospatial.org on 2011-06-13)
  15. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from darkflame@gmail.com on 2011-06-13)
  16. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from darkflame@gmail.com on 2011-06-12)
  17. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from rsingh@opengeospatial.org on 2011-06-10)
  18. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from jens@layar.com on 2011-06-10)
  19. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from rsingh@opengeospatial.org on 2011-06-08)
  20. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from rsingh@opengeospatial.org on 2011-06-08)
  21. RE: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from karl.seiler@navteq.com on 2011-06-08)
  22. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from ahill@gatech.edu on 2011-06-08)
  23. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from darkflame@gmail.com on 2011-06-08)
  24. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from rsingh@opengeospatial.org on 2011-06-06)
  25. Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from darkflame@gmail.com on 2011-06-06)
  26. can we decide on geography representation this week? (from rsingh@opengeospatial.org on 2011-06-06)
  27. Minutes POI Teleconference 12 May 2011 (from mdw@w3.org on 2011-05-12)
  28. POI Core Strawman: ISSUE-19: How should we represent points? (from mdw@w3.org on 2011-05-11)
  29. ISSUE-19 (point-encoding): How should we represent points? [Core FPWD] (from sysbot+tracker@w3.org on 2011-05-11)

Related notes:

Relevant to ISSUE-36 too.

Matt Womer, 11 May 2011, 23:51:44

in discussion on June 2, we decided to drop namespaces and reference XML schema adopted from other places in the specification narrative -- not through formal XML schema methods. This changes the point syntax to:
<Point id="mainpoint" srsName="urn:ogc:def:crs:EPSG:6.6:4979" srsDimension="3">
<pos>27.174799 78.042111 10</pos>
</Point>

Raj Singh, 6 Jun 2011, 14:53:32

and here is the simplest possible example, with an implied (GPS-style lat/lon) coordinate system, no altitude value (implied srsDimension of 2) and no ID value:
<Point>
<pos>27.174799 78.042111</pos>
</Point>

Raj Singh, 6 Jun 2011, 14:56:21

KML point:
<Point>
<coordinates>-122.084075,37.4220033612141,50</coordinates>
</Point>

Raj Singh, 16 Jun 2011, 14:32:21

Display change log ATOM feed


Alex Hill <ahill@gatech.edu>, Chair, Matt Womer <mdw@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 19.html,v 1.1 2012/09/28 07:11:03 vivien Exp $