Hello everyone,
I am not sure if this is the correct place to share it, but I assume because its 3dtiles related, but please excuse if I made a misplace.
I want to share an idea (maybe not even possible but maybe opens the mind from someone to do something similar) for maybe the 3DTiles 2.0 specification.
Right now, as part of the current 3DTiles specification (https://docs.ogc.org/cs/18-053r2/18-053r2.html), we have the styling language, that later is used in the Cesium3DTilesStyles as for filtering.
We had several use cases, where working with point cloud data, we needed something like, a styling language but with output, lets say sort of a compute language to use in Cesium3dTilesComputes or something like that, that allows us to get the sum(), avg() or some other functions for points under several conditions.
In my head is something like what "defines" from the styling makes, but allowing people to extract that information.
Using the 3dstyles language as a example to try to clarify the idea (this is only an idea), lets imagine we want to get the average height of all points, only using points where height is already more or equal than 100m expressed as a condition, the idea would be something like:
{
“avg” : “${pointHeight}”,
“conditions” : [
[“(${pointHeight} >= 100.0)”]
]
}
I am pretty new still to the 3DTiles so I might be misunderstanding something, but if i understand correctly, now the point cloud data are stored in GPU vertex buffers, so Cesium uses the GPU shader to kind of "iterate" though the points and style them, but all that happens in GPU.
So in that "iteration", the same as to apply color or change the pointSize, could be done in order to extract information. So some simple functions like a sum() or an avg() should theoretically be possible.
Please let me know what you guys think about the idea or if somebody based on this have a similar idea with similar results.
I think it would be really useful for a lot of people to have some king of compute language in the specification, even really basic functions. That would open lots of business opportunities for people that want to use Cesium and 3DTiles in the future.
Much appreciated
Hello everyone,
I am not sure if this is the correct place to share it, but I assume because its 3dtiles related, but please excuse if I made a misplace.
I want to share an idea (maybe not even possible but maybe opens the mind from someone to do something similar) for maybe the 3DTiles 2.0 specification.
Right now, as part of the current 3DTiles specification (https://docs.ogc.org/cs/18-053r2/18-053r2.html), we have the styling language, that later is used in the Cesium3DTilesStyles as for filtering.
We had several use cases, where working with point cloud data, we needed something like, a styling language but with output, lets say sort of a compute language to use in Cesium3dTilesComputes or something like that, that allows us to get the sum(), avg() or some other functions for points under several conditions.
In my head is something like what "defines" from the styling makes, but allowing people to extract that information.
Using the 3dstyles language as a example to try to clarify the idea (this is only an idea), lets imagine we want to get the average height of all points, only using points where height is already more or equal than 100m expressed as a condition, the idea would be something like:
I am pretty new still to the 3DTiles so I might be misunderstanding something, but if i understand correctly, now the point cloud data are stored in GPU vertex buffers, so Cesium uses the GPU shader to kind of "iterate" though the points and style them, but all that happens in GPU.
So in that "iteration", the same as to apply color or change the pointSize, could be done in order to extract information. So some simple functions like a sum() or an avg() should theoretically be possible.
Please let me know what you guys think about the idea or if somebody based on this have a similar idea with similar results.
I think it would be really useful for a lot of people to have some king of compute language in the specification, even really basic functions. That would open lots of business opportunities for people that want to use Cesium and 3DTiles in the future.
Much appreciated