-
Notifications
You must be signed in to change notification settings - Fork 1
Hints from Alan Rynne to connect Speckle to Cesium #3
Comments
Here's a bit of GraphQL that might help: {
"operationName":"Object",
"variables":{"streamId":"b58e33b830","id":"03ed008756c7c980205bf196db5ee8f0"},
"query": query Object($streamId: String!, $id: String!) {
stream(id: $streamId) {
id
object(id: $id) {
totalChildrenCount
id
speckleType
data
__typename
}
__typename
}
}
} Alternatively: query Object($streamId: String!, $id: String!) {
stream(id: $streamId) {
id
object(id: $id) {
totalChildrenCount
id
speckleType
data
__typename
}
__typename
}
} {
"streamId":"e6fa820fdd",
"id":"03ed008756c7c980205bf196db5ee8f0"
} |
I would look also specifically at SpeckleLoader class … as well as the … and even more importantly the thing that rules all the others, the Viewer itself … … but from there, we're lost: have no idea where we could grab the geometries that we could forward to Cesium. |
I actually manage to create a gltf from the ifc data that we receive from speckle! Key Steps and Hints: Retrieve JSON Data from Speckle: The process begins with fetching JSON data from Speckle, which includes geometry and associated metadata. Iterate through the retrieved objects to identify and store those that have a 'display value'. For objects that contain geometry, decompose the arrays of faces and vertices. Temporarily add the created meshes to a Three.js scene. This step is crucial for visual verification of the geometry. Next Steps: Create an IFC Tree Structure: The next phase involves creating an IFC (Industry Foundation Classes) tree structure. Import the generated glTF into Cesium, a platform for visualizing 3D geospatial data. https://www.loom.com/share/41642ffaa70448c5a71837adb324ca2d?sid=ebb09f89-1938-427e-9f9a-1d566c1b296a |
Goals
@speckle/objectloader
packageIFCDataSource
source code within the ‹cesium-ifc-viewer› componentUseful resources
ObjectLoader
package to read contents of a Stream available from Speckle back-end and use it in either a browser (which we want) or Node.jsLinks
The text was updated successfully, but these errors were encountered: