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.
Hi Jason,
We are very sorry for your inconvenience. Please send this data set to verify the issue.
Thanks,
Manoj
Manoj, thanks for your reply. I've attached the dgn and two shapefiles for you to try.
Thanks for your help!
Jason
20180830_BluePrint_Landuse_MC_CCD_Local.zipShapefileAttached.dgnParcels_Federal.zip
Jason Rhodes said:I've attached the dgn and two shapefiles for you to try.
I am not able to simulate the described issue:
Product used for testing:
No other applications / extensions installed and active.
Jason Rhodes said:in Microstation Connect or Descart Connect
Please specify exactly what product versions do you use. There are 12 versions of MicroStation CE avaialble and several Descartes versions as well. They span several years of software development, so to discuss original MicroStation and the current Update 11 is like to discuss completely different products in some areas.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
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 Rhodes said:Please let me know if I can provide anymore information.
Because everything seems work on my computer (and I am not Bentley support ;-), no more information is required by me.
But your idea to check the seed file makes sense, I guess it would be tested again not only with the seed file, but also with the same setting of Windows national settings, because sometimes things like decimal separator, units format etc. are inherited to code from Windows (especially in NET), so it makes sense to check whether there is a dependency or not.
Are you able to migrate to the latest Update 11 and to check the design file again?
Thanks Jan. I haven't updated to 11 yet because of another issue I am currently on with Bentley Tech Support. As soon as I get that resolved, I will try and let you know. It seems to me that that V8i and CE are reading and applying the .prj files differently.
I was finally able to migrate to the latest Update 11, but the problem persisted. I realized that upon opening the file in CE, the message window showed that it was reading some transeed.dgn other than the default transeed.dgn. It was related to a workset that I had set up at some point, even though I was opening the file with no workset. I was able to resolve this by repairing the installation and overwriting the .ucf and .upf files, and starting fresh. Now, when I attach the files in CE, they come in perfectly aligned with the .dgn graphics, but when I open it in V8i, it is shifted. This is apparent not only by the graphics, but in the reference manager, it shows an Offset X, Y, and Z of -178956.971. Setting the values to zero shifts the shapefiles back to the correct location. But then, when save it and open that file in CE, it now shows them shifted again with the inverse Offset X,Y, and Z values of 178956.971. Again, setting the values back to zero shifts them back into place.
So, it seems that there's some difference in the way the two versions read the prj files, or it there's a seed file that manages it, but I cannot find where to specify which transeed.dgn is used to translate the .prj file.