- #MICROSURVEY STARNET DOWNLOAD MANUAL#
- #MICROSURVEY STARNET DOWNLOAD UPGRADE#
- #MICROSURVEY STARNET DOWNLOAD SOFTWARE#
It now creates Direction Set with a DM record for every shot.
#MICROSURVEY STARNET DOWNLOAD UPGRADE#
STAR*Carlson Enhancements Upgrade Tour Movie: n/a Import Resection Observations Average Shots in Multiple Sets (option) Import GPS Descriptions (option) Resections used to be ignored, so you lost some potentially important observation data. Overall robustness has been improved by fixing problems with various odd scenarios that have been reported. The new G4 records are currently only created by the FieldGenius GPS importer, but it is a generic solution that can be manually added to any vector, and in the future we can add this to other GPS import formats as necessary.
This defines the offset direction and distance, resulting in the to point being created in the correctly offset position. The offset is now imported to the new G4 record. GPS Offset measurements, when imported to STAR*NET, used to ignore the offset and create the resulting point at the measured position instead of offsetting it as specified.
These calculations now carry over into the converted STAR*NET data. P:\My Documents\2016\starnet82-features-benefits.docx of 17ġ3 STAR*FieldGenius Enhancements Upgrade Tour Movie: n/a Convert OB (Observation) records from the.raw file to BM (Bearing Measurement) records in the.dat or.gps data file Convert GO (GPS Offset) records from the.raw file to G4 records in the.gps data file New G4 Data Record can be added to any vector group in a STAR*NET data file (not just FieldGenius) Fixed other issues importing FieldGenius GPS data Some users handled point offsets by performing a COGO calculation to create a new point relative to another measured point. It is automatic and intuitive, and STAR*NET now behaves like other modern text editors in this sense.
#MICROSURVEY STARNET DOWNLOAD SOFTWARE#
A data file might be modified outside of STAR*NET in several scenarios, like: - The Edit External button is used to open up the data file in some other text editor - Somebody on another computer is editing the file - A file is updated by re-exporting it from one of the conversion utilities or other survey software The new behavior helps ensure that the editor always displays the expected data. The new refresh is instant and automatic. P:\My Documents\2016\starnet82-features-benefits.docx of 17ġ2 Data File Monitor Data editor will automatically refresh any open data files that are overwritten or appended to by the GPS Import command Data editor will prompt to refresh any open data files that are modified outside of STAR*NET Previously, users had to close and reopen the data file in order to refresh the file this could result in confusion with not seeing the new data, accidentally re-saving the old data and losing the new data, and other similar problems. If the mistake was realized and corrected halfway through the survey, just add a.prism OFF or.prism CLEAR command after the last incorrect observation to stop applying the correction value. Stop, start, and reset the prism correction. This allows you to specify the correct prism offset value and the incorrect prism offset value that was used for the measurements, rather than just a correction value. You can specify two offset values (both in millimeters), and STAR*NET will subtract them (value1-value2), scale the difference to the appropriate unit and add it to the distance values that follow. This will absolutely save users time and money! You can specify one offset value (in millimeters), and STAR*NET will scale it to the appropriate unit and add it to the distance values that follow.
#MICROSURVEY STARNET DOWNLOAD MANUAL#
Previous solution required calculating and handmodifying every incorrect distance value (potentially thousands of manual edits), which is time consuming and very prone to error. PRISM Command Specify an prism offset correction to add to all following distances.prism value.prism value1 value2.prism OFF ON CLEAR Very easy to correct a fairly common field mistake: using a prism with the wrong prism offset setting.
0 kommentar(er)
