Skip to content
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

csv-geo-au points incorrectly located in 3D Terrain view #2454

Open
tobybellwood opened this issue Mar 30, 2017 · 4 comments
Open

csv-geo-au points incorrectly located in 3D Terrain view #2454

tobybellwood opened this issue Mar 30, 2017 · 4 comments

Comments

@tobybellwood
Copy link
Contributor

Using csv data from https://www.data.act.gov.au/api/views/nuki-h32w/rows.csv?accessType=DOWNLOAD

Looking at http://staging.nationalmap.nicta.com.au/#share=s-85BZLceJMeKfhTkzazIXV41tRag

and paying attention to the crashes on the corner of Eastern Valley Way and College St for reference - they appear correct in 2D and 3D Smooth, but are misplaced in 3D terrain
image

image

Any ideas why?

@meh9
Copy link
Contributor

meh9 commented Mar 30, 2017

This is because points are always placed on the ellipsoid (i.e. sea level), so when terrain is turned on they suffer from parallax.

See #702

Looks like the Cesium feature to fix this is still open: CesiumGS/cesium#2172

But maybe we can solve this at least for points using some hack, @kring?

@geoffrowland
Copy link
Contributor

Looking forward to visualising vector data on terrain, too ;-)

@kring
Copy link
Member

kring commented Feb 8, 2018

It's possible to fix this by sampling the terrain under every point and adjusting its height accordingly. We have to be careful this doesn't lead to very long load times for some CSVs.

@kring
Copy link
Member

kring commented Feb 8, 2018

Cesium does have support now for points / billboard on terrain, so we may be able to just enable it (but again be careful of the costs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants