An a long time Zen subscriber and client asked for Mark's help with this InRoads question:
Hello Mark,
I have a question on how to simply create cogo points within InRoads.
We know how to export various xyz values within various reports (alg/dtm etc).
But often, most often, we are tasked with creating points for the surveyors to stake out to in the field, arbitrary points such as rail switch points/frog points/retarders/ etc. . . . we often do NOT have an associated alignment / or too many alignments which would exclude a roading program (or staking out based on station and offset).
My initial thought and attempts were within the survey data (fwd) files . . . but we struck out.
We want to pick a point, and have a PNEZD (Point Number, Northing, Easting, Elevation, Description) follow in some sort of database that we can export to a csv file to be uploaded into our survey equipment.
Instead we are literally copying and pasting coordinate values from properties into a separate csv file.
- Josh
Here is the Zen Dude's response:
Hi Josh!
Thanks for being a longtime Zen friend.
Yikes!!! Stop the cut / paste madness!!! ; )
As far at the Cogo Point creation goes, I have two thoughts:
- The New Cogo Point tool
- The Horizontal Events tool
Have you tried using either of these tools? Thinking about using the fieldbook would seem intuitive, but I generally stay away from that when it comes to Staking reports.
The Horizontal Events tool works well when you have some geometry, but you don't have to. The Add As Cogo Point will push it right to the Cogo Buffer for reporting.
The New Cogo Point command has the most flexibility to create an arbitrary point where ever you want it ...just use the target / locate buttons with the InRoads Lock set to No Snap for graphic locations, or Point Snap if it's already a point in the DTM or ALG.
The work will be in adding the Description, but if you have some good strong Styles with good names that could possibly work for the Description column.
My first option for the 'database' would be to use the ALG. Depending on the tool, where the data is, user skill and other considerations, I might opt to use the DTM, but that wouldn't be my first choice.
Once the points are stored in the ALG or DTM, reporting is simple.
Does any of this help?
Hi Mark!
I believe it will, I will dive into this once I'm done with all this other stuff;
life is good!!!
Thanks a bunch!
Cool, Josh! . . . let me know if any questions come up when you dive in.
"Life" is the game we're all playing!!! . . . and it's as good as you make it!!
. . . make it great!!
Civilly yours,
-zen
Mark was a great instructor, he presented the material very well. His ability to give each student personal attention I thought was great, because it allowed each student to flow through the class better. 
