Import xml

[654work]

I have an XML file that is off on the location after I import it.  When the surface comes into the file its off approximately 75 ft from the Map Hybrid image.  I’m using US MO East, NAD83 US Survey Foot (tried international too).  Coords on google earth are 38d47'49.12"N, 90d51'17.10"W.  I’ve attached the XML file too.

Civil 3D 2022

WIN 10 Pro

[rl_jackson]

Didn't need the Lat/Long, with the XML, but thanks.

I've played with it in multiple scenarios to do a correction to the data (playing with UNITS, its coming from uSTA). It looks like an IF vs USF shift but the XML is providing "uSta" data. The XML never shifted, just looked good. Maybe @Pointdump has seen this, or has an option.

[Pointdump]

Hi Robert,
The XML file definitely shows US Survey Feet. Looks like it follows Highway Z nicely. Where are you seeing 75' off?
At your point 38d47'49.12"N, 90d51'17.10"W, the difference between US Survey Feet and International Feet would only be 2.59 Feet.(2PPM)
Dave

[ChicagoLooper]

Whats the source of the xml? Do you have (or can you get) the original survey in its original format with its original units? Original meaning there’s no coordinate transformation and no rounding of units. 

[654work]

@Pointdump, it is off near the bridge over Peruque Creek.  That is the main area we are looking at.

[654work]

@rl_jackson, what settings were you using when importing the file IF?

[654work]

@ChicagoLooper, original source was from a Microstation file exported and sent to us.  We attempted to get the original but no luck.

[LucasHicks · Accepted solution]

I've imported the xml into ORD and PowerGeopak.  They come in exactly the same in both programs.  The ORD allows for a Bing background map.  You are correct they are both off like you say.  My guess is whoever exported this from PowerGeopak (assuming they use this or a variant of) had a setting wrong, or coordinate system.  The only way to know is to have the origin dgn file and check it.  I don't think you have done anything incorrect.

[654work]

@LucasHicks, thank you for the information.  I'll pass this along.

[rl_jackson]

The one thing with XML file is that they have coordinates "hard coded" in the file, I don't think any about of adjusting is going to fix the error in your XML, it were the export told it to go. As @LucasHicks says something was bad on the uStation end of things.

[Pointdump]

Robert,
Missouri has tons of LiDAR and DEM elevation data >>>Here<<<.
Dave

[654work]

@Pointdump, thank you for the link.

[Pointdump]

Robert,
I didn't have much luck grabbing LiDAR data from the Missouri site, so I got a point cloud from >>>TNM<<<. In ReCap I filtered Ground Points(2) in one file, then Bridge Deck(17). I used CloudCompare to clip both clouds to your Area of Interest. In Civil 3D I created surfaces from the RCP files, then pasted both surfaces together. Here's a link to the XML file. Import it into a drawing assigned MO83-EF and set UNITS to US Survey Feet. It should land in the right spot.
https://autode.sk/3UuIm7l
Dave

[654work]

@Pointdump, @rl_jackson, @LucasHicks, @ChicagoLooper, found out we were provided the XML with a Modified State Plane coordinates.  We were able to get them to provide the surface along with the topo linework.

Thank you for taking the time to respond to the post.