[Feature request]: use null in Position class variables to differentiate (un)available values

[georgetian3]

Is there already an issue requesting this feature?

• I have searched the existing issues.

Please select affected platform(s)

• Android
• iOS
• Windows

Use case

According to the comments of geolocator_platform_interface-4.2.2, the altitude, altitudeAccuracy, accuracy, heading, headingAccuracy, speed, speedAccuracy variables may not be available, in which case the value will be 0.

The problem is users cannot differentiate unavailable values from actual readings of 0's for those variables.

Proposal

Make all the above variables nullable, and use null as the value if the variable is unavailable. This is already implemented for the variable floor.

Specific requirements or considerations

No response

Additional information or context

No response

[TimHoogstrate]

Dear @georgetian3,

Thanks for your request. I'll label this as an enhancement and will probably implement something similar during our planned refactor.

Kind regards,