Any bad setup of the project in the LS would be caught and corrected when processed through your pre-defined templates in StarNet.It's a good quality control step of post-processing GNSS data.Īttached file extensions were changed from. The benefit of the P line over the C line would be that working your adjustments from geodetic positions can eliminate bad coordinate systems coming in from the field. Ideally if you can output both of these formats P or C records.the only editing to the file in StarNet would be the !!! which is always necessary relating to fixed control for the specific project. (in this example I have !!! in place of the standard errors for StarNet to know this is a fixed position) (this option would just output a Northing Easting Elevation line in the current project projection)Ī correct StarNet Format C record for the attached project with this option checked would output like this: (with this option checked, it would grey out the "P" Record options) output base position as StarNet Coordinate "C" Record Line The second option that would be nice is if we could choose: Pro + 1.0.1.22 ANSYS Discovery Ultimate 2019 R1 Win64 ANSYS SpaceClaim Direct Modeler 2019 R1 Win64 Merrick MARS Production v8.0. (Point) (Lat) (Long) (Ortho) (StdErrLat) (StdErrLong) (StdErrZ) (Desc) MicroSurveySTARNETUltimate9.圆4 Schlumberger DrillbenchCon2016.2.1 Alt.
#MICROSURVEY STARNET UPDAGE HOW TO#
(I don't know how to tell StarNet that just this one line would be an Ellipsoid Height.or that it is in Meters.So these options would bypass a little extra work for that)Ī correct StarNet Format P record line In Lat / Long / Elevation for the attached project with these options checked would output like this: (these would be StarNet preference options.so this way guys could set it up to have it spit out a file for their typical work flow and avoid some editing) output base vertical as orthometric height (default to be Ellipsoid Height) output longitude as positive value (default to be Negative Longitude) output base position as Starnet Lat/Long "P" Record Lineīelow that option we would probably need to also have: There are a few options that would be nice to see in the StarNet Vector output options screen. This is the base position that it's sending over with the vectors.but the format needs tweaked just a little. StarNet was converting Fieldgenius/Topcon data flawlessly while it was failing to properly convert Fieldgenius/ Leica GS15 data. I've attached a recent project and it's output files for you to see what is going on with this.Ĭurrently J-Field's StarNet Vector Output sends out a second line in the file that looks like this:Ĭ 9001 35.200011 -81.070182 177.658507 0.00347173 0.00355785 0.00350412 'BASE
![microsurvey starnet updage microsurvey starnet updage](https://pbs.twimg.com/media/ExvCv23UYAA4YRt.jpg)
#MICROSURVEY STARNET UPDAGE UPDATE#
One more update on the exact format Star*Net accepts here.