W3C home > Mailing lists > Public > public-poiwg@w3.org > May 2011

Fwd: ISSUE-16 (handling-multiple-locations): How do you represent multiple locations for a POI in an AR app?

From: Thomas Wrobel <darkflame@gmail.com>
Date: Thu, 12 May 2011 12:13:55 +0200
Message-ID: <BANLkTimQfQmn=1O7qc5t0N4u4w0UGtcooQ@mail.gmail.com>
To: public-poiwg@w3.org
I dont see any reason to have anything else but a single "point" really.
If your positioning a 3d model you would already have a pivot point in
the model you can move, so any other position spec seems redundant.

To be honest, I'm not keen on any POI having more then one location
specified. Id tend to say that a different location is a different
POI. For example, the "entrance of parking lot POI" is a POI in itself
to me, rather then a specific part of the parking lots POI.  (there
is, after all, many sorts of location navigation types...do we need
seperate fields for pedestrian and car enterances? what about bikes or
even airplanes? Helicopter landing pads on a hospital?)
Seems to rapidly add complexity to the spec compared to just having
each feature a seperate POI.

That said, one option is for AR apps to just interpret multiple
locations as a "OR", putting the data at both.
Anyone using a POI to position a 3d model via a data link to it should
know enought to not have "overlapping" positions.

On 11 May 2011 22:41, Points of Interest Working Group Issue Tracker
<sysbot+tracker@w3.org> wrote:
> ISSUE-16 (handling-multiple-locations): How do you represent multiple locations for a POI in an AR app?
> http://www.w3.org/2010/POI/track/issues/16
> Raised by: Matt Womer
> On product:
> From: roBman@mob-labs.com
> Date: Tue May 03 06:13:46 2011
> Archived: http://lists.w3.org/Archives/Public/public-poiwg/2011May/0003.html
> [[
> <pois>
>        <poi id="StataCenter" xml:lang="en-US" >
>                <location id="location1">
>                ...
>                        <point latitude="42.360890561289295" longitude="-71.09139204025269"/>
>                        <point id="mainpoint" latitude="27.174799" longitude="78.042111" altitude="10m"/>
>                        <center latitude="27.174799" longitude="78.042111" radius="10m"/>
>                ...
>                </location>
>                ...
>        </poi>
>        ...
> </pois>
> How would you go about representing this POI in an AR app?  No clear
> direction on which of these to use.  If the first one is a typo/mistake
> then I'm still not clear on the separation between point and center.
> ]]
Received on Thursday, 12 May 2011 10:14:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:29 UTC