Closed benquan closed 6 years ago
Changes ready
@ebidel @benquan Do we need a separate property for this, while we can access it via the position
object property?
<geo-location
watch-pos
high-accuracy
position="{{position}}">
</geo-location>
<p>Accuracy: [[position.coords.accuracy]]</p>
If yes, I can create a pull request that adds separate properties for all position
object properties such as accuracy, altitude, altitude accuracy, heading, speed, timestamp. :wink:
@FluorescentHallucinogen that's a good point. I exposed lat/long b/c those are the most common but you can get accuracy through position
.
I don't think we need properties for all the sub properties :)
@ebidel On the other hand, the separate properties are more easy to use. As you can see, not all users know / understand that accuracy, altitude, altitude accuracy, heading, speed, timestamp, etc. are hidden behind the position
object.
Every property does come at a cost (observers, listeners, etc.) I think examples and docs help with showing what's possible.
@ebidel Could this pull request be closed?
Closing since position
already gives you this info. Appreciate the PR @benquan!
I have a added the accuracy property to be pulled to the project.