Bill Colisch
New Member
DPOS does not seem to be working using the Oregon (US) Network.
It reports that there are no CORS in range.
Thanks for looking into this.
It reports that there are no CORS in range.
Thanks for looking into this.
DPOS in Oregon
- Thread starter Bill Colisch
- Start date
The default network for DPOS is set to "Auto Select" (using J-Field) which can lead to the "No CORS in range" error.
Try changing the setting from "Auto Select" to a specifically use "CORS (US)"...
Try changing the setting from "Auto Select" to a specifically use "CORS (US)"...
Bill Colisch
New Member
John, thank you for your reply. I am submitting my data through the web application. If I select "CORS (US)" it works fine, but that does not include the denser 'CORS' included in the "Oregon US" network.
Mark Wheeler
Active Member
Bill, DPOS only uses the constellation files sent to NGS. That is, if Oregon only sends GPS & Glonas, that is all DPOS has to draw from in creating a solution. Our State network gives RTN for GPS, Glonas, Galileo & Bedio (spelling), yet only sends the data for GPS & Glonass. We have a few prior Cors Stations not included within the State RTN that also send Galileo, therefore if JAVAD selects this Coors for the solution, we also get Galileo. Check on the Orgegon Coors website to see which broadcast data is sent to NGS.
Bill Colisch
New Member
Mark, thank you for your reply.
I will check with the guys at ORGN, but I am unable to get ANY solution if I choose the "Oregon US" network.
I will check with the guys at ORGN, but I am unable to get ANY solution if I choose the "Oregon US" network.
Kevin Dowd
New Member
Do not use the Oregon US network! (Unless things have changed)
I did not realize this until I did a project combining data from Dpos
Oregon network with data from ORGN RTK. There was a consistent shift in
coordinates on the order of 0.5' North and 0.5' feet East.
I reprocessed with Dpos Cors network and everything fit with ORGN.
Unfortunately this discovery was after a years plus of projects using the
Ortegon US network.
I did not realize this until I did a project combining data from Dpos
Oregon network with data from ORGN RTK. There was a consistent shift in
coordinates on the order of 0.5' North and 0.5' feet East.
I reprocessed with Dpos Cors network and everything fit with ORGN.
Unfortunately this discovery was after a years plus of projects using the
Ortegon US network.
Bill Colisch
New Member
Thank you Kevin, hopefully someone a Javad is looking into this.
ORGN has transitioned to NAD 83(2011) epoch 2010.00
From March, 8th, 2013, real-time correctors from the ORGN are referenced to NAD 83(2011) epoch 2010.00, latitude, longitude, and ellipsoid heights.
See - https://www.oregon.gov/odot/ORGN/Pages/Coordinates.aspx
From March, 8th, 2013, real-time correctors from the ORGN are referenced to NAD 83(2011) epoch 2010.00, latitude, longitude, and ellipsoid heights.
See - https://www.oregon.gov/odot/ORGN/Pages/Coordinates.aspx
Bill Colisch
New Member
John, thank you for your reply. When I attempt to use the Oregon (US) Network DPOS reports that there are no CORS in range.
It used to work just fine.
It used to work just fine.
In DPOS, change the setting from "Auto Select" to a specifically use "CORS (US)"...