Hello,
Is there a way to connect a linear feature from one field book to a linear feature in another field book?
For example, if I have a gap between the end of a linear feature in Field Book "C" and the beginning of a linear feature in Field Book "D", is there a way to connect these 2 linear features?
I cannot seem to add the beginning point of a linear feature in Field Book "D" to the end of a linear feature in Field Book "C".
Is there a setting that I need to change to allow the 2 field books to interact with each other?
Thank you.
-Cliff
There are plenty of legitimate reasons for having multiple field books. Enhanced control of building terrain models is one example. Example: It makes sense (to me at least) that I would have a different field book for bridge deck. Thus I can easily exclude the bridge deck from terrain model. Yet, I still need to connect the roadway edges of pavement to a point on the bridge.
Unfortunately, you will find various inefficiencies baked in when you try to avail yourself of the power of field books. One example is the inability to join linear features as you wish to do here. In my example above, my choices are to put the bridge deck into the same field book as everything else, make duplicate points merely so I can join my EOP to the bridge, or leave a gap in the EOP.
Because of said inefficiencies then most people use only a single field book.
My 2 cents: your expectations are reasonable and intuitive. Perhaps some day the oversights will be corrected.
Robert Garrett Senior Consultant
www.envisioncad.com
Robert, my 'single fieldbook' statement was really directed toward combining any field files where interconnectivity is required. Since fieldbooks have never talked to each other (InRoads and now ORD), my workflow has always been to use a single fieldbook. Your example of a Bridge deck is unique and can warrant a separate fieldbook, sure, but generally speaking, in my opinion, a single fieldbook is the way to go in most cases.
Thank you for your comments, gentlemen. You both have verified my question.
Zen Dude is right on the money about single field book workflows. I always combine field books when creating final deliverables and merged survey submittals. The issues seem to go away when the project is handled by a single field book.
As a warning I would not use the Export - Import Field book routines from the ribbon in any sort of merge workflow. It has subtle issues that seem to accumulate into big trouble the more the tool gets used.
Take care,
Cliff