QGIS General Inquiry and Overlap In Models

[HadiAram]

Good morning,

I recently started working with the QGIS connector and had some questions regarding a few things we found.

The model took hours to send at times. Is there a limit to how large the data being sent from QGIS is?

Is there a version for Speckle connector that works for QGIS version 3.40? When I tried to open Speckle with it, the 2.20 connector showed an error that it only works from version 3.34 up to 3.38 and downgrading the connector version did not work.

In relation to the overlap, I tried two versions of sending a model in QGIS, one sending it in parts and then adding the models to each other and the other sending it as a whole. The first time I viewed the model by adding it, there was an issue in overlapping where one of the models hid the others but the second time it worked perfectly. What could be causing this issue?

One last thing, there are sometimes visual glitches when viewing the model, with what seems like colors mixing and the image not showing fully. Is this common when there is a lot of dense data being sent?

Thank you for your support.

[JoostGevaert]

@HadiAram

Is there a version for Speckle connector that works for QGIS version 3.40?

Nope, see this thread and reply from @Kateryna:

QGIS Speckle connector not working due to patch version mismatch

QGIS has changed the Python version, so unfortunately latest version of Speckle plugin only works with 3.34.6 onwards. I would recommend to always use the latest LTR for QGIS (currently 3.34.12)

I experienced this as well

@HadiAram

One last thing, there are sometimes visual glitches when viewing the model, with what seems like colors mixing and the image not showing fully. Is this common when there is a lot of dense data being sent?

I ended up sending seperate layers to separate branches in my Speckle project, and then control how stuff is displayed by federating models in the Speckle viewer. Here is a public Speckle project with lots of Ground Investigation data that I sent to Speckle from QGIS:

[jonathon]

@JoostGevaert

Nope, see this thread and reply from @Kateryna:

QGIS has changed the Python version, so unfortunately latest version of Speckle plugin only works with 3.34.6 onwards. I would recommend to always use the latest LTR for QGIS (currently 3.34.12)

But we are working on it right now. 3.40 for Mac is the last hurdle.

[HadiAram]

I ended up sending seperate layers to separate branches in my Speckle project, and then control how stuff is displayed by federating models in the Speckle viewer.

What exactly did you mean by federating models in the Speckle viewer? I know that one time I got the overlap and another time I didn’t, so I want to know how to make sure it is consistent.
@JoostGevaert

As for the connector for 3.40, that is good to know. Thank you.

[jonathon]

@HadiAram

What exactly did you mean by federating models in the Speckle viewer?

What @JoostGevaert is referring to is that you can send separate QGIS layers to separate Speckle models and then recombine them in the Speckle viewer online and also as a URL address:

This embedded viewer shows five models uploaded and then federated/aggregated/overlaid.

This can be useful for reducing the load on Publish and, at times, allowing for more focused sharing with others.

[HadiAram]

This was partly my issue in that the overlap wasn’t correct and the different layers obscured each other with the bottom layer appearing on top. I will check if this issue persists. Thank you.

[HadiAram]

I have tried again and found that at certain angles, the model works well while at other angles, it shows something like this.

I added the different branches of the project to each other and this was the result at this angle. When I rotate the model, I get the following result.

Is this normal with more data heavy models?

[jonathon]

It is difficult to tell from static images, but in general, I’d speculate it has less to do with the data size and more to do with the coplanarity of elements. If you share the URL with me its easier to see what the effect you might be describing.