Posted Thu, 09 Dec 2021 10:23:04 GMT by Christine C
How can I import the the point cloud with local coordinate system to the Indoor viewer? I add several GCPs which are local coordinate system when processing data and how to place the point cloud and panorama in a right place in Indoor viewer?
Posted Thu, 09 Dec 2021 12:18:37 GMT by Laurin Gottschall
Hi Christine, 

this is Laurin from NavVis. Thank you for your inquiry regarding manual dataset alignment in IVION. Since your dataset is not georeferenced it is necessary to tell IVION where exactly you want the data to be located. For that we have the manual alignment tool. Please find more information on that in our documentation: https://ivion.docs.navvis.com/navvis-ivion-setup/aligning-datasets/aligning-datasets-manually

I hope this helps, let me know if there's any further questions around this process. 

Best, Laurin
Posted Fri, 10 Dec 2021 07:51:01 GMT by Christine C

Hi Laurin,

Thank you for your reply. As you said, even though I use GCPs to process the raw data and I can get the georeferenced point cloud (.las) eventually, the dataset still has no any geoinformation? How can I match the location between the georeferenced point cloud (.las) and panorama exactly? Are the original point of point cloud and of dataset the same? 

Regards, Christine

Posted Fri, 10 Dec 2021 16:47:47 GMT by Christine C
After post processing the raw data which I added the control points when processing data, I eventually have a dataset of which the coordinate system is a local coordinate system and the values of x and y are quite large. So that it is difficult for me to put the dataset in the right place in Indoor Viewer directly. I don't want to move the dataset on my own because it is not accurate enough. 

Looking forward to hearing from you. Thanks in advance.

This is the origin.json in the datasets_web folder I get:
{
    "Pose": {
        "orientation": {
            "w": "0.97370838608903776",
            "x": "-0",
            "y": "-0",
            "z": "0.22779810986898302"
        },
        "position": {
            "x": "821717.20680203079",
            "y": "834279.48791046313",
            "z": "6.2907631238366717"
        }
    }
}

And the GCP information shown as below:
# Hint: X -> Easting, Y -> Northing, Z -> Height

# Further information can also be found in the documentation:
# http://www.navvis.com/docs/mapping/v1.8/en/html/slam_anchor_reference.html#anchor-files

# Explanation of entries:
#  - anchor_name       : unique identifier of the anchor pose, surround with quotes if it contains spaces
#  - pos_x pos_y pos_z : Cartesian position of the anchor (right-handed coordinate system)
#  - yaw_deg           : Yaw Euler angle (degrees) specifying the anchor orientation (not required)
#  - timestamp         : Timestamp corresponding to the given pose (not required)
1.1
"n4" 821668.655000000 834286.524000000 5.394000000 0.000000000
"n5" 821674.280000000 834320.514000000 7.301000000 0.000000000
"n6" 821722.981000000 834310.479000000 7.012000000 0.000000000
"n7" 821717.392000000 834279.802000000 5.380000000 0.000000000

You must be signed in to post in this forum.

Feedback