GCS missing in 3SM produced in ContextCapture 20 and uploaded to PW ContextShare

Hi, as in the subject, we cannot attach 3SM from PW ContextShare to a dgn in OpenRoads Designer (2021R2) as ORD shows error: "This Reality Mesh needs to be reprojected but no GCS is set" and gets listed in red in Reality Mesh Attachments dialog. The mesh has been produced in ContextCapture 20 (CC) with a GCS plus local geoid vertical datum. The dgn has the same GCS and geoid assigned. Upload to PW ContextShare done from within CC. All looks fine in Reality Data Web Viewer and in iTwin. Other 3SM attached the same way to the same dgn works fine when produced in CC19.

 Has anyone seen similar issues?

Regards

Mariusz

  • Hello Mariusz, 

    Could you please let me know which coordinate system you are using and which geoid ? (EPSG codes)? 

    Are you downloading the 3SM from ContextShare and trying to attach it in ORD or are you streaming the mesh to ORD ? 

    In Update 20 we made some modifications on how the GCS are communicated to the 3SM, to avoid this kind of issues, so I am interrested in knowing more about this specific case. 

    Have you logged a service request already ? 

    Thanks,

    Sylvain

  • Hi Sylvain,

    Thanks for your response.

    Our GCS applied in CC is:

    IRENET95 / Irish Transverse Mercator (EPSG:2157) + Malin Head height (EPSG:5731).

    The geoid entry in vertcs.override.csv is as follows:

    We wanted to attach in ORD from ContextShare which means streaming. This works with older meshes i.e. produced in CC19 with the same GCS. settings).

    We did notice a warning in CC when setting up production at Spatial reference system:

    However, our Block and Reconstruction use the same SRS as above.

    We haven't logged SR yet.

    Regards,

    Mariusz


    OpenRoads Designer 2022 R1

  • The implementation of geoids in Contextcapture is strange approach. It requires full geoid model only to show the model(which covers only small part of it) otherwise alarming errors. Why could not simply embed the part of geoid in 3sm or just use some average offset and to avoid need to have geoid for publishing. The option to be able to use geoids is advantage comparing to other SFM software but disadvantage at the same time as not reasonably implemented.

    What you could try is to export this coordinate system definition in Contextcapture as custom WKT format and then reimport back. This way it won't be in unsupported EPSG:2157+ESPG:5731 but as custom coordinate system. Actually it would be good if could have option to drop geoid on production but keep height offset and avoid need for custom GCS.

  • Hello Marius, 

    Thank you for the feedback. There shouldn't be an issue with the described workflow. As the warnings suggest, there might be a vertical innacuracy because the vertical grid used for ellispoid/geoid separation in iTwin/powerplatform is EGM96. THis sais, this shouldn't prevent you from streaming your mesh in ORD. If possible, could you please add me as a member to your Connect project so I can have access to the 3SM and Web-ready 3SM for analysis ? 

    Thanks,

    Sylvain

  • Hi Sylvain,

    We have done more testing and it turns out that it works properly in OpenBridge Modeler 10.10.20.91 and 10.11.00.310.

    It also works in ORD 10.10.03.02 but not in any newer version of ORD i.e. 10.10.21.04, 10.10.23.15 and 10.11.00.115. However, all versions allow to attach meshes from contextshare originated in CC19.

    Is this a defect?

    Regards,

    Mariusz


    OpenRoads Designer 2022 R1