Richard, Piotr-
Thank you both very much for yuor quick replies!
So it sounds like some steps I can take to investigate a misbehaving ALG file are:
-Look for bad geometry names, geometry descriptions, point names, or styles and delete them if found.
-You both identifed alignments that looked bad to you. What jumped out about them for you? It appears I can use the horizontal element tools to investigate such alignments and delete/recreate odd-looking elements.
-What other steps might there be? Was there anything else either of you did?
Thanks again very much,
Jeff
I have seen file corruption when dealing with alpha-numeric text (i.e. point / alignment names, styles, descriptions), but it has been quite along time since I have seen these problems. Most of the time it would occur in importing textual data and the string length is too long and the software did not handle it correctly! I am unaware of any issues like this in the latest versions of the software (maybe even as far back as the XM versions)
But I would do any of the following:
Display all of the data in an empty design file and fit the view. If you see graphics that are way out of place, then use the tooltips to identify which alignment those graphics below to. The use Review Horizontal Alignment or Check Integrity to determine what might be wrong! (In this case the 0,0 coordinates popped out)
Create a report and look at the following:
R. W. Bradshaw
Jeff,
I exported your file to LandXML. and checked in notepad++. See attached screen - this is what you and Richard already mentioned - weird characters: ETX (End of Text), EOT (End of Transmission) or BEL (Bell code).
Regards,
Piotr
Looks like Notepad++ in that image.
After Excel, its the next best tool for InRoads users.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration