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

Re: ACTION-33 Map georeference needed?

From: Alex Hill <ahill@gatech.edu>
Date: Wed, 1 Jun 2011 15:45:05 -0400
Cc: "Public POI @ W3C" <public-poiwg@w3.org>
Message-Id: <5EACFDC8-8B1B-4456-A399-D0F43F4DADDA@gatech.edu>
To: "Seiler, Karl" <karl.seiler@navteq.com>
Thanks for looking at that.

On Jun 1, 2011, at 2:47 PM, Seiler, Karl wrote:

> The reference to  civic address [RFC4776] is perfectly good for the use for the POI Spec in my view.
>  
> The reference to the map reference as:
> The optional "map" URL can be used to provide a user of relative
>    location with a visual reference for the location information.  This
>    document does not describe how the recipient uses the map nor how it
>    locates the reference or offset within the map.  Maps can be simple
>    images, vector files, 2-D or 3-D geospatial databases, or any other
>    form of representation understood by both the sender and recipient.
>  
> Does not work for map references ala NAVTEQ, Google Map, TeleAtlas Map, OSM. This works fine for map display / rendering related information.
>  
> We still need a Map Reference URI construct, where the URI potentially returns a map document for:
>         <mapReference>
>                <provider>NAVTEQ</provider>
>                <version>2011.2.1</version>
>                <objectID>123456789</objectID>
>                <objectType>NavPoint</objectType>
>                 <side>L</side>
>          <PFRN>10</PFRN> !Map percent distance from reference node (10%)
>        </mapReference >
>  
>  
>  
>  
> _______________________________
> Karl Seiler
> Director Location Technology & Services
> NAVTEQ - Chicago
> (T)  +312-894-7231
> (M) +312-375-5932
> www.navteq.com
>  
> From: Alex Hill [mailto:ahill@gatech.edu] 
> Sent: Wednesday, June 01, 2011 12:26 PM
> To: Karl Seiler
> Cc: Public POI @ W3C
> Subject: ACTION-33 Map georeference needed?
>  
> Karl,
> Can you take a look at the "Secondary Map Metadata" section in this document and comment on whether this appears to align well with what we have been discussing (i.e what would this stated spec need to add to aid "snapping to a map" as Navteq does)?
> http://tools.ietf.org/html/draft-ietf-geopriv-relative-location-01#page-19
> Alex
>  
> Alex Hill Ph.D.
> Postdoctoral Fellow
> Augmented Environments Laboratory
> Georgia Institute of Technology
> http://www.augmentedenvironments.org/lab
>  
> 
> The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.
> 

Alex Hill Ph.D.
Postdoctoral Fellow
Augmented Environments Laboratory
Georgia Institute of Technology
http://www.augmentedenvironments.org/lab


Received on Wednesday, 1 June 2011 19:45:33 UTC

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