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.
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.
the shape file has a projection defined, how can mstn attach said file correctly without a cgs defined ?
And if one used the same projection for both dgn and shp this would help to remove some variables as the cause of it not working.
More over others have reported that it indeed shifts in CE using the files as supplied, again applying the same cgs that is used in the shp files should make it work correctly and no shift in either versions... so it would seem CE is misreading the prj file interpretation or the way msnt CE is reading where the data in in the dgn...
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me
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.
Hi Jason,
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?
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Lorys,
whether GCS is assigned to master or not is not important in this discussion (despite of it's recommended), because it's about why the same file is displayed correctly in V8i and not in CONNECT Edition.
When there is not GCS used, references are attached 1:1, so there is no shift. When the same file is opened in another version, the result has to be the same and references cannot be shifted.
Moreover, when all all files uses the same GCS, it's not important whether GCS is used or not, so it likely not help in the discussion.
Regards,