I have a shapefile attached to a .dgn that comes in aligned perfectly when opened in V8i, but when I open the same file in Microstation Connect or Descart Connect, it's shifted way off to the northeast. I have tried detaching in Connect and reattaching, but it still comes in shifted. When I open it again in V8i, it comes in correctly. I have tried with and without a geographic coordinate system defined in the DGN.
Hello Jan,
Thanks for your reply. After reading your response, I thought maybe the issue was related to the seed file. So I created a new dgn in Microstation Connect with the Microstation default 3D Imperial Design seed. I attached as reference the dgn I sent to you and the two shapefiles. The two shapefiles are shifted to the northeast from the referenced dgn. See screenshot below.
Then I open the same file in Microstation V8i SS3, the shapefiles appear aligned correctly with the dgn. See screenshot below.
Then I open the same file in Descartes Connect Update 3 and they are shifted again to the northeast.
Applications used:
Microstation V8i SS3 V08.11.09.655
Microstation Connect Update 10 V10.10.0023
Descartes Connect UPdate 3 V10.03.0018
Thanks for your help. Please let me know if I can provide anymore information.
Jason
Hi Manoj,
Please see reply to Jan above. Thanks for your help, and please let me know if I can provide any more information.
Was curious, so I tried this. DGN with georeference, referenced shape file in the same part of the world. File came in with a scale of 3.28xxx, closed file reopened, now it's 1:1, and correct. Sometimes when I attached the shapefile, it might show 1:1 in error. Try checking/forcing your shapefile to 1:1, see if it doesn't align. Or simply attach, close, re-open.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Thanks for trying. For me the references come in at 1:1 every time in both V8i and CE. In V8i the shapefiles align with the dgn and in CE they're shifted to the northeast, with or without projection defined in the dgn.
That's what my CEr11 did the first time, shapefile was way up NE, subsequent tries and/or exit re-open seemed to fix it. Inconsistent, frustrating to diagnose.