mga 2020 v55 and Esri shape files dont transform to correct location

Question

I have received ESRI shape file data even though they named everything mga55 the prj file reveals that the esri dat set is in fact gda94z55 
 No problem I open and created a dgn in v8i ss10 ( 8.11.09.919) set the GSS to MGA94z55 then used the remanager to ref attach the SHP file I then checked it landed in the right place with my airphoto and double checked via Bing maps ( I have bing key for v8i ) so it doesn land in right spot. so I merged the ref to keep it in the dgn. 
 ok I need this to be in MGA2020Z55 
 So in Connect edition I made a new file set the GCS to MGA2020Z55 and ref attached the original shape file and told mstn xref to reproject the ref esrishape file turned on Bing and it is not in the right place by alot...(5147467.960m north) so I ref attached my V8i dgn and told msnt to reproject it and wow the v8i file that was GDA94z55 lands in the right place or as close as I can work out from BING Maps as I have no coordinate listings to verify with. 
 So it seems that CE 13 10.13.0048 doesnt know what to do with the esri gda94z55 shp file .. but it does reproject the dgn 
 Can somebody else take a look at this please and check if its my work flow or just CE13 or is the GO particular to my seed files that zip contains my esri data set and my two dgns 
 
 shapefile.zip

Andrew Bell · Accepted Answer

Hi Lorys 
 Good to speak with you regarding this issue with referencing your shape (shp) files in MicroStation CONNECT Edition (Update 13). As we confirmed that it is not reproducible in Update 16 I suggest you organize an upgrade with your IT but I am still going to check in Update 13. I will also have a look whether someone may have raised this issue in a previous Defect.

Andrew Bell · Answer

Hi Lorys 
 I have just tested this same operation in a new VM installation of MicroStation CONNECT Edition (Update 13) and cannot replicate what you are explaining is your original issue with the location of this shape file. It appears to be placing it at the correct location the same as I see in Update 16. There may be something else in your workspace that is affecting this so it might be worth trying with the default or No Workspace option.

Lorys · Answer

after much investigation we have traced the culprit down..it was in VicRoads workspace configurations both CE and V8i both use or are pointing to a vicroads 3d seed file as the file for transeed use .. this file has the old false origin as the Global origin from the old days when we had a limited design plane and could not fit our local state in the design file ... however if we edit this file that is being used as the Transeed in our vicroads workspace configuration to have a GO=0,0 then its all works perfect again with attaching Esri shape files and datum transforms.. also checked with GDay calculator and Bing maps ....works great now...both CE and V8I ss10.... 
 So good tip for Victorians in Australia who use the VicRoads interface and configuration files with their default seed files provided need to be amended...If no VicRoads seed files used and use the out of the box Bentley trans seed file it too works perfectly as the go for the Bentley seed files has the GO=0,0...

Lorys · Answer

yes your right Andrew... there appears to be something from third party addon in configs settings interfering with correct operation of using shp files .. was able to do it properly in open roads designer with no workspace settings or 3rd party software addons configs being used ... once created and imported as dgn polygon it opens in CE update 16 in correct location as reprojected 2020z55 from a 94z55 shape file source data..

mga 2020 v55 and Esri shape files dont transform to correct location

Top Replies