[geolocation-api] Pull Request: Update geolocation acquisition algorithm to explicitly define data types and handle cached positions

marcoscaceres has just submitted a new pull request for https://github.com/w3c/geolocation-api:

== Update geolocation acquisition algorithm to explicitly define data types and handle cached positions ==
Enhance the "Acquire a Position" algorithm to include explicit data type definitions and unit specifications for each piece of acquired position data, aligning with the [[WGS84]] coordinate system standards. This update ensures each parameter (latitude, longitude, altitude, etc.) is clearly defined at the point of data acquisition.

Additionally, refine the handling of cached position data within the algorithm. Introduce conditional logic to terminate the algorithm early if a valid cached position is used, preventing unnecessary data acquisition steps. This change improves efficiency and clarity in the geolocation process, ensuring that position data is handled correctly based on its freshness and accuracy requirements.

Key Changes:
- Define explicit data types and units for latitude, longitude, altitude, accuracy, altitude accuracy, speed, and heading.
- Implement conditional checks to skip unnecessary acquisition steps when using cached positions.
- Update parameters passed to the `GeolocationPosition` constructor to include all newly defined data points.

Closes #137

This change is editorial and just contains corrections.


See https://github.com/w3c/geolocation-api/pull/153


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

Received on Monday, 13 May 2024 03:45:50 UTC