Surveyors are probably a large portion of the overall population that uses NGS OPUS.?ÿ Most of us are using customary units of feet.?ÿ I really wish OPUS would give us a break by providing the opportunity to use US feet for input and with US feet as an option for output.?ÿ This would save time and reduce errors.?ÿ It would be great to simply cut and paste a coordinate into the field in our office COGO software.?ÿ But maybe they already have this along with an ASCII download for coordinate points.?ÿ If not, Carlson, I bet you could handle this in 5 minutes, and NGS could do it even easier.?ÿ
I only use OPUS for Lat., Long, Ellipsoid height in meters.
If you select OPUS extended data, you will find units in US Feet or Int Feet (depending on state) at the end of the report.
Well in a year we will all be using the international foot any how.
Thanks, Lee.?ÿ?ÿ
I'd like OPUS to save a profile so that I didn't have to reenter my email address and select my receiver model from a list of hundreds every time. I'd also like to see it support Oregon's LDPs.?ÿ
Side note - the extended report gives an elevation estimate on the new datum. Around here there is 3.5 foot difference between '29 and '88. It seems that the new datum will be very nearly exactly equal to '29 hereabouts.?ÿ ?ÿ?ÿ
@norman-oklahoma I agree.
my workaround is type ??trmr? in the box then the first choice is R10.
@jon-collins they aren??t going to make me use International Feet, I??m on a mission from God.
Surveyors are probably a large portion of the overall population that uses NGS OPUS.?ÿ Most of us are using customary units of feet.?ÿ I really wish OPUS would give us a break by providing the opportunity to use US feet for input and with US feet as an option for output.?ÿ This would save time and reduce errors.?ÿ It would be great to simply cut and paste a coordinate into the field in our office COGO software.?ÿ But maybe they already have this along with an ASCII download for coordinate points.?ÿ If not, Carlson, I bet you could handle this in 5 minutes, and NGS could do it even easier.?ÿ
I ask for the XML, edit it (easy), then drop into TBC
@jon-collins Correction. We now have 3 versions of the foot: the U.S. foot, the International foot, and the "foot" (which is the same size as the International foot).
Some poor sucker in a few years will pull a set of SPCS coordinates written in feet and assume (innocently) it is the size of the one newly defined as current by NGS.?ÿ?ÿ?ÿ Oops.
Some poor sucker in a few years will pull a set of SPCS coordinates written in feet and assume (innocently) it is the size of the one newly defined as current by NGS.?ÿ?ÿ?ÿ Oops.
Which is probably why the NGS avoids publishing things in feet as far as it can.?ÿ
Using TBC (if you have trimble) the process is to drag and drop your file to a box, TBC will ask what service you wish to use to process, you will have a chance to edit the HI with a metric value and the correct measure point, it will then ask for your email and if your computer has done it a few times a drop down box will appear with however many email address you use. It only takes a few tens of seconds to send the file.?ÿ
I've only sent these through Trimble, it sounds like it's labor intensive otherwise.
Also there are other processing options, I've noticed that they convert Lat, Long to state plane slightly differently so you will obtain XYZ values that aren't quite the same even though the Lat, Long will be very close. I've also seen that for some reason Trimble's RTX-PP elevations tend to be a bit closer to NAVD88 numbers. The differences between the two processors for the same file are small.?ÿ
I'd like OPUS to save a profile so that I didn't have to reenter my email address and select my receiver model from a list of hundreds every time.
You mean like this?
If you use LSU C4G network you can online post process.?ÿ http://c4gnet.xyz/PluggableWeb/#/ .?ÿ I haven't ran one in awhile so I am not sure of the output format.?ÿ?ÿ
