How do I change the point name increment in OpenRoads?

Placing Geometry points in OpenRoads will use a feature definition and that feature definition can have a point prefix.  Other than that I am not sure there is another way.  what you describe above seems related to double or triple coding survey points and importing the point file into survey.

https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/33435/openroads-designer-connect-edition---wiki-articles-and-videos

For example, I have a parcel I want to pick the lot corners (know there is another process for exporting a parcel, but this is a simple example for my question) and I pick the 4 corners beginning with point #5000. Unless I manually key in the next number the next increment is 5000_1, instead of 5001. Where are the settings that tell the next number to be _1? 

Not really. The only ways I know are:

1. Manually change each number as you pick them. That sucks especially when you space of and miss one. Then your number are out of sequence.

2. Set your first point at 500. The next will be 500_1, 500_2,.... After I save the points from the Reporting tool. I change the numbers in Excel and copy that txt file to the collector. 

I am not sure why PowerSurvey has to create the _1 when it could just as easy increment to the next number.

I hope this helps.

Dan 

Hello Dan,

I found the same issue in ss3 thru ORD survey as well. Here is my workflow for bulk renumbers or other edits that need to be done in bulk.

1. Export the data to an excel file. Renumber points using the Excel Fill in series tool.
2. Delete the points from the survey field book. 
3. Re-import points to survey field book.
4. Compress the dgn deleting blank cell headers.

The import / export formatting can be difficult. For instance if the points have attributes or linking codes associated with them you may need to develop a TIW format to get what you need.

Have there been any updates from Bentley on implementing this feature when placing points? This seems like a very simple fix and something that program should do automatically. We are switching to OpenRoads currently and this is going to be a very big headache I am sure. 

Nothing has changed in ORD 10.10. That being said it does matter what type of stake out your doing?

Construction?

Property corners, alignments, search values?

It can all be compiled and exported to CSV or LandXML or compiled and renamed to whatever you want. Then reimported to ORD or a Survey Field book. Learning to create of edit Style Sheets would be helpful.

I'm thinking the naming conventions are built with the underbar _ so you cant overwrite points on data imports. If that is the strategy I think it works great. 

Once the points are brought into the ORD dgn you'll have to annotate them. Annotation is controlled by the feature definition. The annotation workflow is not as well developed for simple tasks like point name and cell. It's a work in progress from what I can tell.

Take care,

Cliff

Nothing has changed in ORD 10.10. That being said it does matter what type of stake out your doing?

Construction?

Property corners, alignments, search values?

It can all be compiled and exported to CSV or LandXML or compiled and renamed to whatever you want. Then reimported to ORD or a Survey Field book. Learning to create of edit Style Sheets would be helpful.

I'm thinking the naming conventions are built with the underbar _ so you cant overwrite points on data imports. If that is the strategy I think it works great. 

Once the points are brought into the ORD dgn you'll have to annotate them. Annotation is controlled by the feature definition. The annotation workflow is not as well developed for simple tasks like point name and cell. It's a work in progress from what I can tell.

Take care,

Cliff