-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Cesium Troubles #371
Comments
Not directly addressing your misalignment issue, however, I've just updated all the cesium loaders, and updated the ion_asset <- 96188
tile_data <- paste0("https://assets.ion.cesium.com/",ion_asset,"/tileset.json")
mapdeck(
style = mapdeck_style("dark")
, location = c(144.95, -37.82)
, zoom = 14
, pitch = 60
) %>%
add_cesium(
data = tile_data
, ion_token = ion_token
) ion_asset <- 43978
tile_data <- paste0("https://assets.ion.cesium.com/",ion_asset,"/tileset.json")
mapdeck(
style = mapdeck_style("dark")
, location = c(144.95, -37.82)
, zoom = 14
, pitch = 60
) %>%
add_cesium(
data = tile_data
, ion_token = ion_token
) |
The point cloud now works! The building layer is still not great. Here's a video showing the issues. You can see some buildings are under the base map and all the others are floating above it at varying heights across the map. The cesium layer doesn't seem to work with all the assets either, I am trying to get 3D terrain into my map (Asset ID - 1). It is in my assets list on my cesium account but doesn't show up when I try to load it. Do you have any suggestions on bringing in 3D terrain? Thank you for your quick responses! |
full disclosure: I've never used this layer other than to build the examples as a 'proof-of-concept', so my knowledge is very limited. Under the hood {mapdeck} is designed to implement all the deck.gl examples. I can't see any native deck.gl examples that use DetailsIn the Cesium ion page, the code it gives for showing the pointcloud is
and for the terrain it's
And they are both using different "loaders" ( Which explains why Given there are Losts of different types of loaders, updating this Way ForwardI'm not sure. In all the various terrain discussions I've seen there's no mention / examples of using the But for now I'm not sure I can help much (with the usual excuse of "work-gets-in-the-way-of-opensource-projects") |
@Zekiye-VAP this may be relevant for you - r-spatial/discuss#29 (comment) |
Will keep looking into fixing the projections of the buildings for the cesium layer. I have switched over to using the add_terrain function for 3D terrain which is looking great however I am having issues with clear_terrain() and it seems like there is not a clear_cesium() function implemented yet. Is it possible to get these working? Thank you for all your help!! |
Deck.gl has recently added a terrain extension to allow 2D layers to generate across the 3D surface. Would is this something that could be integrated into mapdeck? https://deck.gl/docs/api-reference/extensions/terrain-extension |
Been trying to get the add_cesium function to work but have come across a few obstacles.
First, I was not able to get the example running and figured out an alternate method of calling the tile data using the tileset.json URL from this api call; https://api.cesium.com/v1/assets/{ion_asset}/endpoint (however this only seems to work for the Cesium OSM Buildings tileset).
I am trying to add the Cesium Open Street Map Buildings layer to my map and using the below chunk, I managed to get the buildings rendered HOWEVER it seems the projections do not match and many buildings are misaligned. Seems cesium only supports web mercator and WGS84, not EPSG:4326 which mapdeck renders in. (CesiumGS/cesium#3877) Wondering if you encountered this issue with the original example?
Not really sure what to do to get this layer working and would appreciate any solutions.
The text was updated successfully, but these errors were encountered: