Hello,
I am from the Survey Department for SHA in MD, when our Field crews send in their collected data, a line feature as (TC ST, TC, TC, TC PC, TC, TC PT, TC) does not work anymore because I have noticed that PC is now a linking code and it starts a new line, I manual edit the previous point with JNC or JPT to connect the line.
Does Anyone have any idea how to get the PC and PT linking codes back to feature codes so they work as usual?
Any Help Greatly Appreciated!!!
Thank You
you can edit the linking codes. please see this video
communities.bentley.com/.../9922.aspx
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Thank You for your answer, but the video does not go into detail about changing the linking codes, not sure if it is because the language he is teaching in? or maybe I asked the question in an awkward description.
I'll try again, when I download a field file into SS3, the linking codes work with ST but not with PC, even when I change from startPC to ArcPC, is there a way to change the numerical value so that it is read as a code feature (secondary linking code) and not an actual primary linking code?
Any help is appreciated
Does that use a TIW file?
If so, which one?
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Answering my own question! Has it come to this?
The other TDS parser appears to come from the GEOPAK side of things - it does not use a TIW file.
So, what does this mean?
Attributes created for InRoads will often get overlooked or assigned to codes that do not exist. It really depends upon the way the Attributes were setup for the Data Collector. We have a choice of 19 attribute "categories" - some are for individual features while others can me used for many features. Our category names end up as the codes on the shots with attributes. InRoads ignored this category name and used the codes from the shot.
So while this allows me to continue testing, using the TIW from InRoads is preferred. Also, InRoads allowed a code that we referred to as Attribute via notes.
This was where the surveyor could add a note to a shot and then, in the note, enter a period as the initial character, followed by an attribute name and then the attribute value. Without a TIW this cannot be done, as far as I know.
I have also tested a NOTEPAD++ regular expression search and replace command which would replace our attribute category with the codes from the shot. This was successful and that's a good thing. And I was able to store it in a macro for reuse.
I wanted to let you know that the Rod Height error when reading TDS files while using the InRoads TDS RAW parse has been fixed in SS3 refresh 08.11.09.674. This refresh is now available for download on our SELECTservices site.
I am in the process of downloading it now. I cannot wait!
Sounds Great, my only problem is my IT guy has to download it, I don't have those privileges at work.
From this and your other post, sounds like things will work, that's good news!!!