Re: Geofencing Proposals

Regarding geofencing, you may find this document relevant:  "Requirements on a location based API”
http://www.scf.io/en/documents/092_-_Requirements_on_a_location_based_API.php

The document lists some geofencing service requirements and surveys existing APIs.  Web APIs need to be cast in different technology than for Small Cells, but the geofencing functions are similar.  And there is need to have accurate handling of location across technologies.

Regards,
George


On Aug 29, 2014, at 4:10 PM, Mandyam, Giridhar <mandyam@quicinc.com> wrote:

> TPAC is coming up, and we should spend part of our time there discussing geofencing.  In order for group participants to be prepared, I’d like to invite  any interested persons to put their geofencing proposals to the list before September 12.
>  
> The Blink/Chrome team posted a proposal  http://lists.w3.org/Archives/Public/public-geolocation/2014Jul/0027.html.
>  
> Also, Qualcomm put forward a proposal during the breakout sessions at last year’s TPAC:  http://gmandyam.github.io/enhanced-geolocation/.  {Note:  please ignore Sec. 8 as it deals with indoor location extensions that are currently not in scope}
>  
> Look forward to seeing more proposals.
>  
> -Giri

George Percivall
gpercivall@opengeospatial.org
http://www.linkedin.com/in/gpercivall
@Percivall on Twitter
+1-301-560-6439
http://www.opengeospatial.org/
OGC -- Making Location Count