Re: Vehicle Location Information

It was my understanding, and Paul, please correct me if I'm wrong,
that we felt there should be changes to the geolocation API, that
those changes should be proposed to that group.  We want to avoid
duplicate APIs.  As far as accuracy goes, an OEM can implement the
geolocation API with much more accuracy in the vehicle because they
have more data available (gyro, rotation angle of the wheel, etc).
That however is not an API problem.  It's an implementation problem.

So there are two questions that need to be solved:

1 - Is the geolocation API good enough for vehicles?  If not, we need
to work with that group to fix it.
2 - Can implementers of the geolocation API take advantage of vehicle
data to improve accuracy?  I think the answer is "yes".

On Tue, May 6, 2014 at 7:37 AM,  <ta-hirabayashi@kddi-ri.jp> wrote:
> Hi, Paul-san and Kevron-san
>
> While I do not notice it, a definition of the vehicle location
> information disappears in
> first draft spec.
>
> In the last f2f meeting, Urata-san pointed out the generic geolocation
> information (GPS-based)
> is not accurate enough. With gyro, vehicle speed, rotation angle of the
> wheel and so on, most
> of car navigation diveces have higher accuracy (within 1 or 2 meters
> errors in any roads of
> Japan) than conventional devices such as a smartphone and tablet.
>
> In the case where the OS and the device which web apps are running on
> support generic
> geolocation APIs, it becomes difficult for us to acquire the accurate
> positioning data easily
> if vehicle location information should be not available as it is.
>
> In short, we thought that geolocation information and vehicle location
> information are distinct
> APIs in accuracy.
>
> Can you restore the definition of vehicle location information in spec?
>
> T.Hirabayashi/KDDI
>
>
>

Received on Tuesday, 6 May 2014 15:26:36 UTC