I'm attempting to bring a .3mx file into ORD so that I may convert it into a TIN file. I'll explain my steps as well as where the error with georeferencing begins, along with some screen shots.
1) Create a .3mx file, with the Production set to export using my local State Plane system: NAD 83 / North Carolina (ftUS) (EPSG:2264) as its SRS.
2) In ORD, I set my Geographic Coordinate System to match my CC Production export SRS: NAD 83 / North Carolina (ftUS) (EPSG:2264)
3) "Attach Mesh" --> Select my file --> Make sure "Attach and Apply Geographic Coordinate System" is checked --> "OK"
4) I am prompted with a warning message that my Mesh is displayed in a different Coordinate System and that existing geometry will be effected.
Any ideas on why ORD is not reading the GCS of my .3mx correctly?
In addition to this error, when I look at my .3mx file in the Reality Mesh Attachments menu, my GeoCS is set to none. Have I not set my Coordinate System already by choosing to "Attach and Apply Geographic Coordinate System"?
Thanks in advance.
-jake
I have the same problem... where is the answer?
The only workaround I have found is to bring the mesh in as a reference. The following workflow has been working well for me:
1) Create your file
2) Change your Coordinate System to your desired format. When prompted, select "Change Storage Units in the model from "..." to "..." to match the GCS" **Once this is set, do NOT change the GCS**
3) Attach your mesh as a reference. Orientation:Coincident- World.
If you're trying to produce a TIN File:
4) Search for Ground Extraction tool. Set output as Terrain and select your mesh to begin the conversion. Takes a little while for the conversion but if I remember correctly there should be a progress bar somewhere on your screen or in the ribbon.
Let me know if this works for you or if you have any issues. It seems to be a rather chintzy workaround, but it has been working ok as far as I can tell so I'll be using this until I learn a better way.
Unfortunately it didn't work
At what point in the workflow are you running into issues?
3mx always goes to the origin... attaching