Sensor Parameter

[archinform]

Hello,

I have some questions to the new (required) sensor parameter in v3:
- Why the parameter is necessary? Are there any extra functions in the
Maps API, if a sensor is available? With the navigator.geolocation
(new W3C API) or Google Gears it is already possible to get the user's
position, so why the Maps API require this?
- Isn't it possible to extend the Maps API to do the checking for a
sensor? Now the website (server) have to decide, if the user have a
sensor or not. This is really bad, because it means, that websites
have to provide separate versions for sensor enhanced devices and
sensorless ones.

Sascha

[pamela (Google Employee)]

Hi Sascha-

We detail the sensor here:
http://code.google.com/apis/maps/documentation/v3/#SpecifyingSensor

It's required because we must report usage of sensors to our data providers.

The Maps API doesn't provide sensing itself, but you're welcome to use
it in combination with AJAX ClientLocation, Gears, Safari Geolocation,
etc.

Since you'll be writing the code that uses those sensing technologies,
then it should be possible for you to confidently pass in the value of
the sensor parameter.

You're welcome to file a feature request for more built-in sensing in
the Maps API, if that's what you're looking for.

- pamela

[archinform]

Hi Pamela,
thanks for the detailed answer.
If I understand You right, it means that the sensor parameter doesn't
have any software functionality. It is just for statistics.
Does Google have to pay more for delivering sensor enhanced web
application ;) ?

Sascha

[pamela (Google Employee)]

Yes, it's for statistics. ;)

- pamela

[bratliff]

On Jul 2, 9:18 am, "pamela (Google Employee)" <pamela...@gmail.com>
wrote:

> Yes, it's for statistics. ;)
>
> - pamela

Unless an application is designed for just one audience, it ought to
be determined at run time for the active browser rather than hard
coded into the URL.