Hello all,
I work for a land surveying firm in Oklahoma City, OK, and we just recently purchased InRoads from Bentley with the intent of reducing the survey data that we collect out in the field. We have our own "system" or "way" of collecting survey data that does not jive with the DOT .XIN file, and I need a way to get our points/lines to show up in InRoads correctly. I don't mind putting in the work by adding every single file so long as I know that I will be able to load up what our guys shoot out in the field in InRoads.
I would like to build our own individualized .XIN file from scratch, but thus far, nothing I have read nor nay of the support people I talk to have been able to get me past this dilemma.
Please let me know what I need to do.
Thanks,
Jonathan Nazari
Kevin,
When I do the three things you mention, several things happen. When I import the data after making those additions to the Style Manager, I get yellow exclamation points everywhere. When I hover one of the exclamation points, I get this message:
Additionally, as you can see, none of the points have lines connecting to them. I think that I need to add he styles to the Feature Definitions as well, but I think that I am missing something somewhere somehow.
Thanks for the help. I eagerly await your reply.
Bearing Tree Land Surveying
(405) 605-1081
After your XIN is ready, you will need to link the Survey Feature Definitions to the XIN. Check out Chapter 9 in this document: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/transitioning-to-bentley-civil-survey-document
Chapter 6 also mentions the CIVIL_SURVEY_STYLEFILE workspace variable that can be set in the workspace to point to the XIN.
Correct, there are three options in the Survey Settings for connecting the points with linework: By Field Codes will require the linking codes, By Consecutive Field Code just connects them in order until another code is encountered, and Connect All Matching Field Codes connects all matching codes.
Here is link to an example using the different linking codes: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/16136.point-coding-example
For Alpha Codes with a numeric suffix, the program automatically treats these as separate codes, so you will only store the Alpha Code in the XIN. For example, you will only have an "EP" code in the XIN for an edge of pavement, but you can shoot the left and right edges of pavement as EP1 and EP2. The program will connect the EP1s separately from the EP2s.