Re: ISSUE-19 (point-encoding): How should we represent points? [Core FPWD]

Really not sure about merely having space-separate lat/long/alt co-ordinates.
This means we arnt specifying a name field for them - how well does
this work with none xml formatting like JSON? (co-ordinates will need
to be passed into separate, likely double, variables for use after
all).

We could have space separated as a xml specific optimisation, but I
really think we need specific names defined for lat/long/alt - this
would also remove ambiguity/confusion people sometimes have as to
lat/long or long/lat.

Also, does the point itself need an ID ? (the POI itself is required
to have a unique one, but does each point it might use within it
also?)

~~~~~~
Reviews of anything, by anyone;
www.rateoholic.co.uk
Please try out my new site and give feedback :)



On 11 May 2011 22:44, Points of Interest Working Group Issue Tracker
<sysbot+tracker@w3.org> wrote:
>
> ISSUE-19 (point-encoding): How should we represent points? [Core FPWD]
>
> http://www.w3.org/2010/POI/track/issues/19
>
> Raised by: Matt Womer
> On product: Core FPWD
>
> 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>
>
> ]]
>
>
>
>
>

Received on Monday, 6 June 2011 18:06:25 UTC