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
Geocoder Camera Fly To doesn't consider Z position when a terrain provider exists #11898
Comments
Thanks for the suggestion @c3-victor-mao. Would it make sense for your use case to be able to set |
@ggetz thanks for the response! After thinking and discussing with my team, here are our thoughts: No Terrain Provider:
Terrain Provider:
The ability to set What are your thoughts on the proposed behavior? |
Feature
Context
While implementing a Custom Geocoder in Cesium 1.115, we noticed the Geocoder Camera FlyTo would always zoom in very close to the ground. With the normal Camera FlyTo, we are able to specify a
Cartesian3
with a Z position for the camera so that all our objects would be in the camera's final field of view. We wanted the same for the Custom Geocoder but noticed that theGeocoderViewModel.js
code would always place the camera height at the terrain provider elevation plusDEFAULT_HEIGHT
(1000m) without considering theCartesian3
Z-position.Code References
DEFAULT_HEIGHT
to the terrain provider elevation: GeocoderViewModel.js#L359Feature Request
If the terrain provider is removed, then the Z-position is respected. However, is there a way to be able to position the camera at a certain Z-position, even if there is a terrain provider?
Maybe something like this for GeocoderViewModel.js#L356-L362:
Or maybe this can be a flag passed into the Geocoder?
If this is a valid request, then we'd be happy to open a PR for this with your direction :)
The text was updated successfully, but these errors were encountered: