Mx road - Point code problem

Road and Site Design

This is where you can find and contribute to discussions, ideas, and other information about Bentley Road and Site Design products.

Road and Site Design Forum

Mx road - Point code problem

rated by 0 members
This post has 7 Replies |
1 Follower

Posted by Seba80

on Fri, Jul 3 2009 9:34 AM

Yes this is the methiod i used in the first place.

Posted by Seba80

on Fri, Jul 3 2009 9:29 AM

Thanks a lot for your response, and for your time.

Posted by Wolfgang Weh

on Fri, Jul 3 2009 8:09 AM

AsciiImport.pdf

Alternatively you might want to use the ASCII Import Wizard.

See attached screenshots.

Best Regards

Wolfgang

Posted by Mark Marnell

on Fri, Jul 3 2009 7:27 AM

Points.png

Standard MX strings are 3 dimensional - so normally you could not import more dimensions, i.e. only the the X, Y asnd Z values are stored for a point.

However, there is a 4 dimensional string (by default called PSSA) used to store survey stations (control points for a survey) which stored the X, Y, Z, and Survey Station Name. So, for example, a point on this string could be (1000,1000, 25,STN1). Note that the station name is limited to a maximum of 4 characters.

With the example file you posted, I did the following. (i) opened the file in a spreadsheet and removed the first column of numbers - these are not required as MX will number the points when they are put into the model (ii) aded the lines shown below to tell MX how to read the data - note that I am creatinig a survey station string of 4 dimensions.called PSSB (iii) input the file and the string PSSB was stored in the model 'A test case'.

genio,a test case
001,Format(f10.3,1x,f10.3,1x,f7.3,1x,a4)
003,ordr,4=1,1,2,3,4
080,pssb,7=4
533939.680,294540.610,163.860,1
. not showing data here
0,0,0,0
999

The GENIO options above are standard MX options. The 001 option tell tMX how to read the data, in this case, a number of ten colums, then a space, another 10 column number and space, then a 7 column number and space, and then 4 characters (even if the codes are not 4 characters long). The 0,0 at the end shows the end of the string, and 999 shows the end of the GENIO option.

The image shows how this PSSB string is displayed.

Posted by Seba80

on Fri, Jul 3 2009 5:27 AM

I've change the file extension into .txt because .coo extension is not recognizable.

Posted by Seba80

on Fri, Jul 3 2009 5:25 AM

coord.txt

Here is the .coo file.

Posted by Mark Marnell

on Thu, Jul 2 2009 1:49 PM

Can you please post an example of the data in a '.coo' file. I have never heard of this and would like to know what it contains, and then see if I can help.

Thanks.

Posted by Seba80

on Thu, Jul 2 2009 12:58 PM

When i import land data from a .coo file with the ASCi import comand i can't optain the code information of points. If i use the "simple survey" style only the points and the numbers of points are displayed if i use the "points and strings" style only points and level information is displayed. In both cases point codes are not diplayed.

I hope someone has an answer on my question.

Thankx.