Re: [sdw] Communicate good practice for defining geofences in the Best Practices doc (#1268)

Based on the discussion within SDW and elsewhere, what I am hoping for is at least two conventions/standards around geofences.

One really capable as Scott described on the thread and call capable of handling range of use cases and nuanced representations - corridor along a road, dynamic protected airspace, etc,. 

The other would be a more rudimentary representation, easier to define and transmit. I learned at least a couple participants in the Auto WG in practice use polygons, collection of lat/long points from which it is reasonable to calculate whether a given location is inside or out. One of the two participants also uses circles in addition to polygons which only needs one coordinate and a radius. There are open source libraries that do just that. 

In the mail thread I wondered about GIS backed, where it is feasible to lookup if a given location is inside some geographic boundaries (which side of a river, inside or out of a municipality). Depending on where the fence is acted upon, in cloud or on vehicle or device, and its connectivity it may have to have cached data for be able to make that determination. 

Precision certainly matters for many use cases and require more complex definitions but for other cases approximation is more than enough.

-- 
GitHub Notification of comment by tguild
Please view or discuss this issue at https://github.com/w3c/sdw/issues/1268#issuecomment-863511253 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 17 June 2021 19:37:51 UTC