InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

Jacquelyn Pettus — Tue, 06 Nov 2012 20:14:34 GMT

Current Revision posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 11/6/2012 8:14:34 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.

By Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Powerful features implemented in the 2004 Edition of InRoads Survey and PowerSurvey increase productivity and streamline workflows for field data collection and office reduction, with two basic functional enhancements types: Field Operation Tools and Office Reduction Tools.

Field Operation Tools

Field Operation Tools target improvements to field data collection and current workflows used by surveyors and engineers in the field on a daily basis. These tools focus on Cross Section Control Code and Random Control Code functionality.

Cross Section Control Code

The coding scheme for the Cross Section control code enables intelligent feature collection. It does not require, nor is it dependent upon, full-feature coding for every observation as has been considered normal

Figure 1: Control Code dialog box showing new codes
and mandatory in the past. The Cross Section control code is specifically useful considering the time required to observe data using Total Station or RTK GPS systems may be only seconds. Keying in code values can take up to four times as long as it takes to make an observation.

In dense data collection projects, the time required to key in code compels users to collect data in random point mode rather than linear mode to gather the most points possible per day. While this appears workable in the field, the end product (based upon point features versus linear features) is not nearly as efficient or informative relative to creating good digital terrain models (DTMs) and providing optimum planimetrics.

The Cross Section control code enables surveyors to define a consistent series of features to be collected along a linear path. These features provide additional information regarding the linear feature, such as:

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Ideally, users begin with a simplistic ditch or roadway when using the Cross Section command for the first time. After brief experimentation, the user can develop techniques to best meet specific workflow needs.

Random Control Code

There are times during the data collection process when a linear feature, normally treated as a breakline or interior point type, needs to be changed to a random point type. An example of this is a fence line normally used as a breakline feature in DTM creation; however, during the data collection process, elevation breaks could not be located along the fence due to inaccessible field conditions. In such a scenario, the surveyor in the field does not want to eliminate and not use the points already located under the fence. Yet using those points as a breakline would result in an incorrect DTM.

By simply coding any of the points in the fence line chainage with the Random control code, all subsequent points in the specified feature are converted to a random feature type. This field coding option eliminates the need for office personnel to make fieldbook edits to reflect necessary changes in the data.

Office Reduction Tools

Office Reduction Tools address office reduction procedures and improvements ranging from processing speed through more robust editing and filtering tools. Areas of enhancement to Office Reduction functionality include Survey Feature Filter, Chainage Recognition, Point Code Find and Replace Tool with Error Detection, Save to Geometry, Save to Surface, Duplicate Points, Feature Table operational improvements and overall operational improvements.

Survey Feature Filter

The amount of data collected in the field can be quite large. In the office, data reduction can become cumbersome and difficult. The Survey Feature Filter implemented in InRoads Survey and PowerSurvey, 2004 Edition, enables logical query sets to be built and activated/deactivated through a Survey Feature Lock that affects the following commands:

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Figure 2: Survey Feature Filter dialog box showing options
The Survey Feature Filter enables users to use wildcards, determine field statuses, and use numeric ranges to build filters. An example of a filter that simplifies error detection is setting an Exclude Elevation range from 0 through -10. This eliminates the use of all zero through negative elevation points.

Chainage Recognition

The ability to automatically connect points together to form linear and closed features is one of the most important aspects of a survey. With this in mind, it is now possible to locate and manipulate connected survey chains in the survey Fieldbook. The Start control code defines when a survey chain begins.

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Prior to 2004 Edition, InRoads Survey and PowerSurvey coding errors were detected at the time of raw data import. Now users can scan through and edit existing field data after all raw data has been loaded into the Fieldbook. And, the Fieldbook now color codes the erroneous points for easier location of the points.

Save to Geometry

Figure 5: Survey Data to Geometry dialog box showing options
The Save to Geometry command now honors the Feature Filter settings. Save to Surface
The Save to Surface command now honors the Feature Filter settings. In addition, it writes the survey attribute values directly into the surface description for each feature.

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Figure 6: Fieldbook dialog box showing Duplicates
2004 Edition brings significant improvements to the Survey Feature Table Editor interface. After populating the Fieldbook with survey data, the user can now review the survey feature table and recognize only those features that are loaded in the active Fieldbook. Additionally, the user can scan the feature table for other criteria: cells, symbols, attributes, tags, or custom operations.

Overall Operational Improvements

The Survey Options dialog box has been streamlined for ease of use, with Text Point Symbols added as a new planimetric display option. Another major operational improvement deals with the import of large, fixed-point data sets. Processing speed of large data files has seen an enormous improvement within the 2004 Edition.

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

2004 Edition enhancements to InRoads Survey and PowerSurvey enable users to enjoy new functionality that maximizes their civil engineering and survey skills and workflows, yielding greater overall production at reduced costs-making the move to InRoads Survey or PowerSurveyEdition clearly the best move for your organization.

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Tags: Archived Client Server, client server, client server 2004

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

Elisa McGraw — Thu, 12 Aug 2010 20:11:35 GMT

Revision 14 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 8/12/2010 8:11:35 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.

By Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Tags: archived client server, client server, client server 2004

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

Elisa McGraw — Tue, 22 Jun 2010 13:18:27 GMT

Revision 13 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 6/22/2010 1:18:27 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.

By Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Tue, 08 Jun 2010 14:34:51 GMT

Revision 12 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 6/8/2010 2:34:51 PM

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Tue, 08 Jun 2010 14:29:45 GMT

Revision 11 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 6/8/2010 2:29:45 PM

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Figure 5: Survey Data to Geometry dialog box showing options
The Save to Geometry command now honors the Feature Filter settings. Save to Surface
The Save to Surface command now honors the Feature Filter settings. In addition, it writes the survey attribute values directly into the surface description for each feature.

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Tue, 25 Aug 2009 17:24:52 GMT

Revision 10 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 8/25/2009 5:24:52 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.

By and Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Tue, 25 Aug 2009 15:01:28 GMT

Revision 9 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 8/25/2009 3:01:28 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.

By Bentley Technical Support Group, PLS/RPLS, Senior Technical Manager, Civil Engineering, and Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Tue, 11 Aug 2009 21:20:24 GMT

Revision 8 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 8/11/2009 9:20:24 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.

By David Fagerman, PLS/RPLS, Senior Technical Manager, Civil Engineering, and Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Fri, 07 Aug 2009 19:22:11 GMT

Revision 7 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 8/7/2009 7:22:11 PM

This Client Server article is republished in its entirety from 2004 for reference purposes. By David Fagerman, PLS/RPLS, Senior Technical Manager, Civil Engineering, and Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Thu, 30 Jul 2009 15:10:41 GMT

Revision 6 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/30/2009 3:10:41 PM

This Client Server article is republished in its entirety from 2004 for reference purposes.
By David Fagerman, PLS/RPLS, Senior Technical Manager, Civil Engineering, and Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Fri, 24 Jul 2009 18:12:04 GMT

Revision 5 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/24/2009 6:12:04 PM

By David Fagerman, PLS/RPLS, Senior Technical Manager, Civil Engineering, and Patsy Gant, Technical Documentation Coordinator, Civil Engineering Professional Services, Bentley Huntsville Office
28 July 2004

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Thu, 23 Jul 2009 16:47:41 GMT

Revision 4 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/23/2009 4:47:41 PM

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Mon, 20 Jul 2009 18:25:27 GMT

Revision 3 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/20/2009 6:25:27 PM

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

Tags:

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Mon, 20 Jul 2009 17:50:37 GMT

Revision 2 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/20/2009 5:50:37 PM

Field Operation Tools

Cross Section Control Code

Feature name
Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.
After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:
<feature name> <XS# control code> <ST control code>
continue the same for each start of linear feature in the Cross Section set
After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.
Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

Tags:

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Elisa McGraw — Mon, 20 Jul 2009 17:42:44 GMT

Revision 1 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/20/2009 5:42:44 PM

Field Operation Tools

Cross Section Control Code

Figure 1: Control Code dialog box showing new codes
and mandatory in the past. The Cross Section control code is specifically useful considering the time required to observe data using Total Station or RTK GPS systems may be only seconds. Keying in code values can take up to four times as long as it takes to make an observation.

Feature name

Type (breakline, contour, exterior, interior)
Symbology (feature style controlling display)
Triangulation status (include in triangulation or not)
Special attribution (now available in Surface Description)

The Cross Section control code is based on several factors:

The user can identify a typical section and optionally specify key linear features to be carried throughout the length of the section. Examples of typical sections that can use this control code for optimal results are:
A 10-foot wide roadway ditch with 10-key linear features.
A narrow road or rail section with several identifiable features that traverse along an easily recognizable section of roadway.

After identifying the beginning of a section (as described above), the user starts the coding of the features using the following syntax for each of the features to be included in the Cross Section set:

continue the same for each start of linear feature in the Cross Section set

After all linear features in the Cross Section set are identified, all subsequent Cross Section sets belonging to the Cross Section set number are identified with an XS# value. It is important to note that the sequence for using this command must follow all cross sections features in one direction, followed by a direct reversal on the next set of sections. Multiple Cross Section sets can be run simultaneously by differentiating the sets via the set number, such as XS1, XS2, XS3. At anytime during collection of Cross Section data, it is also possible to collect other features simply by identifying them with their own feature code.

Once all features have been coded in the field, all that is needed is to import the raw data file. Prior to importing the raw data file, the feature table must be loaded and contain each of the features used in the Cross Section set. If the feature table has not been loaded, the XS# values will not be honored, and the desired feature creation will not be created. Features in the feature table at the time of data import ensure that the XS# value is recognized for each shot after the set is created and automatically adds the desired feature code to the observations. The remnant XS# will also remain on all points; however, it can be removed or remain using the bulk search and replace command.

Random Control Code

Office Reduction Tools

Survey Feature Filter

Fieldbook Data
View Planimetrics
Survey Data to Surface
Survey Data to Geometry
Writing Survey Data to Graphics
Export Survey Data

Chainage Recognition

Figure 3: Fieldbook dialog box showing Chainage

Figure 4: Fieldbook dialog box showing Point Code Find and Replace

Point Code Find and Replace Tool, with Error Detection

Save to Geometry

Duplicate Points

InRoads Survey and PowerSurvey, 2004 Edition, provide three basic duplicate point types:

Same station, multiple observations to the same point
Different stations, multiple observations to the same point
Different stations, multiple observations to the same point name, but not the actual same point

The corresponding method used to address the above types of duplicates is:

Same station, multiple observations to the same point are mathematically meaned together to find one common coordinate for the point at the station. This becomes obvious when using the Survey to Surface/Geometry commands.
Different stations, multiple observations to the same point indicate a network survey where the same point is used to strengthen the survey system. To address this type of duplicate point, place an ADJ control code on the non-occupied same points. Then generate an adjustment set to compute a least squares solution for the coordinates of the duplicate point. After running adjustments, the duplicate points will change status and reflect a fixed status in the Fieldbook. When using the Survey to Surface/Geometry commands, the single adjusted coordinates for the point are used.
Different stations, multiple observations to the same point name, but not the actual same point has been addressed in the 2004 Edition. It needs to be clear that these types of points are generally accidental and are not intended to be the same point. Adjustments and mathematical meaning have no value on these point types. This is where the Survey > Fieldbook Data > Duplicates Only command is deployed and scans the entire Fieldbook to find this type of duplicate point. Once these points are located, the user is able to make whatever specific edit is desired to correct the misnamed point.

Feature Table Operational Improvement

Overall Operational Improvements

Figure 7: Feature Table dialog box showing options

Figure 8: Survey Options dialog box

Summary

Tags:

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

Field Operation Tools

Cross Section Control Code

Random Control Code

Office Reduction Tools

Survey Feature Filter

Chainage Recognition

Save to Geometry

Duplicate Points

Feature Table Operational Improvement

Overall Operational Improvements

Summary

See Also

Comments or Corrections?

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

Field Operation Tools

Cross Section Control Code

Random Control Code

Office Reduction Tools

Survey Feature Filter

Chainage Recognition

Save to Geometry

Duplicate Points

Feature Table Operational Improvement

Overall Operational Improvements

Summary

See Also

Comments or Corrections?

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows [CS]

Field Operation Tools

Cross Section Control Code

Random Control Code

Office Reduction Tools

Survey Feature Filter

Chainage Recognition

Save to Geometry

Duplicate Points

Feature Table Operational Improvement

Overall Operational Improvements

Summary

See Also

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Field Operation Tools

Cross Section Control Code

Random Control Code

Office Reduction Tools

Survey Feature Filter

Chainage Recognition

Save to Geometry

Duplicate Points

Feature Table Operational Improvement

Overall Operational Improvements

Summary

See Also

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Field Operation Tools

Cross Section Control Code

Random Control Code

Office Reduction Tools

Survey Feature Filter

Chainage Recognition

Save to Geometry

Duplicate Points

Feature Table Operational Improvement

Overall Operational Improvements

Summary

See Also

InRoads Survey And PowerSurvey 2004 Edition New Tools Streamline Workflows

Field Operation Tools

Cross Section Control Code

Random Control Code

Office Reduction Tools

Survey Feature Filter

Chainage Recognition

Save to Geometry

Duplicate Points

Feature Table Operational Improvement

Overall Operational Improvements

Summary