-
Notifications
You must be signed in to change notification settings - Fork 771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why Geometry/Point created in Geolocate? #122
Comments
We could add a |
yes, i did think of suggesting that. But I'm wondering why the Point is created at all. Alternatively, as a LonLat is being created, why not return that? |
To make it easier to add the location to a vector layer, but I agree this is of little value. |
I'm also thinking it would be useful to have a bindZoom option, so people could set the zoomlevel bind should use. I would imagine in most cases, a zoom level of 0 is not what people would want. |
I've decided the simplest way to get what I want is not to use the OL control. Creating my own code for this is pretty straightforward. So I will close the issue. |
Why is "locationupdated" in Control/Geolocate/geolocate() creating and returning a Geometry/Point? Surely all that's needed is the position as provided by navigator.geolocation.
I would like to create a simple page using a marker to mark current position, and to cut bandwidth to the minimum by using only the essential classes. Having this in there just adds unnecessary classes to my build.
The text was updated successfully, but these errors were encountered: