Notifications
Clear all

OPUS and US feet

17 Posts
14 Users
0 Reactions
7 Views
(@bigd1320)
Posts: 61
Registered
Topic starter
 

I submitted a Rapid Static file to OPUS and I did not receive the State Plane coordinates in US feet, only meters. I thought past OPUS computations came in both meters and US feet. Does anyone have a tool or website that will get me from meters to US feet in IA North? I was using the conversion for meter to US feet, but I must be missing something. (1 US ft = 1200/3739m)?ÿ

?ÿ

Thanks,

Dan

 
Posted : 30/01/2021 6:24 am
(@bill93)
Posts: 9834
 

I thought you just needed to multiply meters by the 3.xxxx factor, as the origin and false E and N values apply regardless of the final units.

Take an older OPUS report and check that this works.?ÿ

 
Posted : 30/01/2021 6:44 am
(@peter-ehlert)
Posts: 2951
 

...off point a bit, Recent History:
people were getting very confused with the differences between International Feet and US Survey Feet, they used the Wrong Foot and fubared it all over the place. So the Bureaucrats up above decided to dumb it down "to eliminate confusion".?ÿ This was despite the numerous objections from the Land Surveyor in a dozen or more States are on US Survey Feet for their State Plane Grid Systems.

I understood the decision was to eliminate publishing US Feet and instead just publish Meters (the native vale) and the conversion to International Feet.
I predicted that those same confused people would just jump on the International Foot values and make a royal mess of things.

This new OPUS output with Metric Only is great news! Now it is just math to convert to the preferred/mandated flavor of Feet.

 
Posted : 30/01/2021 7:11 am
(@rover83)
Posts: 2346
Registered
 
Posted by: @peter-ehlert

This new OPUS output with Metric Only is great news!

Agree. I'm 99% sure geodetic computations for all software programs are done natively in meters. Ever bluebooked anything? NGS will reject anything other than meters.

Posted by: @bigd1320

Does anyone have a tool or website that will get me from meters to US feet in IA North? I was using the conversion for meter to US feet, but I must be missing something. (1 US ft = 1200/3739m)

That's the conversion to use (IA is USFt, not IFt, IIRC).

If you really want to hand-enter the geodetic values in an online tool, NCAT's got you covered in the feet conversion.

?ÿ

 
Posted : 30/01/2021 7:36 am
(@brad-ott)
Posts: 6185
Registered
 

3.2808333?

 
Posted : 30/01/2021 7:57 am
(@spmpls)
Posts: 656
Registered
 

As Rover83 said - NCAT.

 
Posted : 30/01/2021 8:07 am
(@oldpacer)
Posts: 656
Registered
 

@peter-ehlert?ÿ ?ÿ'flavor of foot', really?

 
Posted : 30/01/2021 8:42 am
(@mark-mayer)
Posts: 3363
Registered
 

The tool I use is a calculator. For software I might employ Excel.

 
Posted : 30/01/2021 8:43 am
(@bigd1320)
Posts: 61
Registered
Topic starter
 

I found what I was looking for. NCAT results are in meters and US feet. The results match the NRTK 5 epoch shots I took earlier this week. The horizontal was within 0.04'.

?ÿ

Thank for the replies. I enjoy communicating with other surveyors.?ÿ

Dan

 
Posted : 30/01/2021 8:47 am
(@joegeodesist)
Posts: 34
Registered
 

OPUS is unchanged.

For local units, select upload Options > Format > Extended report, and then look waaaaay down near the bottom of the solution. Just as always.

OPUS finds the state-chosen foot (for states which have chosen) from SPCS table.

Now that NGS has NCAT, itƒ??s tempting for OPUS to simply generate ITRF-frame ECEF XYZ plus accuracies at survey epoch, then throw the user into NCAT to dial in their own frames, datums, projected coordinate systems, units, epochs, etc.

The OPUS report format ?ÿis ancient and unchanged, but due for an update, either from the upgrade to the processing engine (2021) or NAD83 replacement (2022). Via what forum can the community suggest which OPUS features to keep and which to add? Send ideas to NGS.opus@noaa.gov and or attend the OPUS User Forum on Tuesday https://www.ngs.noaa.gov/web/science_edu/webinar_series/special-opus-user-forum.shtml

?ÿ

 
Posted : 30/01/2021 8:59 am
(@mathteacher)
Posts: 2081
Registered
 

@bigd1320

You have a transposed digit in your conversion formula. 3739 should be 3937.?ÿ

Actually, it's a double transposition. Back in the early days of my numerical life, we considered people who made double transpositions to be exceptionally talented.?ÿ

Congratulations!!

 
Posted : 30/01/2021 3:55 pm
(@bill93)
Posts: 9834
 
Posted by: @mathteacher

Good eye!?ÿ I should have caught that.

 
Posted : 30/01/2021 4:25 pm
(@mightymoe)
Posts: 9920
Registered
 

I've never paid any attention to the xy from an OPUS report. The lat long is all I care about.?ÿ

 
Posted : 30/01/2021 4:34 pm
not-my-real-name
(@not-my-real-name)
Posts: 1060
Customer
 

@oldpacer

Tasty feet. Yum.

 
Posted : 30/01/2021 5:29 pm
(@john-hamilton)
Posts: 3347
Registered
 

Really? You need a website to convert from meters to US FT?

 
Posted : 31/01/2021 6:05 am
(@john-hamilton)
Posts: 3347
Registered
 

@joegeodesist

Joe: NCAT does NOT support ITRF, which, in my opinion, is a serious mistake. I have been complaining to whoever will listen at NGS that NCAT needs to be able to access the HTDP model. Maybe you can help push for it...?ÿ?ÿ

 
Posted : 31/01/2021 6:09 am
(@dzett12)
Posts: 1
Registered
 

When you originally input your data into OPUS, instead of standard report, select Extended report and at the bottom of the 5 or so page report you get back, you'll see the SP Coordinates in U.S Feet

 
Posted : 01/02/2021 10:08 am