-
-
Notifications
You must be signed in to change notification settings - Fork 87
focusOnLocation doesn't work in some locations. #35
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
Comments
I've looked a bit more it more into this issue and I think that it's not directly related to the point being 53N. It seems that there are other locations where it happends. |
Thanks for the bug report. I haven't managed to track down the issue in the overlay editor, however if you just use the library to load your overlay and focus on the location using I will look at fixing the overlay editor as soon as possible |
When I modified index.html, and replaced There is an error in the console with the following stacktrace (in Chrome)
I get a different stacktrace in Firefox:
|
You need to call Procedural.init( { container, datasource } );
Procedural.displayLocation({longitude: 21.884765625, latitude: 53.01});
Procedural.addOverlay({
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"color": "white",
"padding": 10,
"name": "Example",
"background": "green",
"icon": "star"
},
"geometry": {
"type": "Point",
"coordinates": [
21.884765625,
53.01
]
}
}
]
}); You can also invoke |
I didn't realise that you need to call I think I've found out why A potential solution seems to be to call |
Describe the bug
In some locations, when using
focusOnLocation
, the camera is placed in correct position, but is facing away from the location.To Reproduce
In the Overlay editor, enter the following geojson:
Expected behavior
Camera should point towards the location. It works for this example:
The only difference between those two examples is the latitude (53.0N vs 53.01N).
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: