I have a question for all users of this forum, which is the following:
Is there any datum that can project a separate line to me 2 meters of the real line or position according to GPS ?.
Eduardo_01, post: 435230, member: 12858 wrote: I have a question for all users of this forum, which is the following:
Is there any datum that can project a separate line to me 2 meters of the real line or position according to GPS ?.
Difference btwn into. Foot and u.s. foot in your spc?
Sent from my SM-G955U using Tapatalk
Jawja, post: 435231, member: 12766 wrote: Difference btwn into. Foot and u.s. foot in your spc?
Sent from my SM-G955U using Tapatalk
Yes.
Projections are a funny animal, 2 parts per million add up quick when evaluating time signatures issued from space.
BK9196, post: 435237, member: 12217 wrote: Projections are a funny animal, 2 parts per million add up quick when evaluating time signatures issued from space.
I have a question for all users of this forum, which is the following:
Is there any datum that can project a separate line to me 2 meters of the real line or position according to GPS ?.
Eduardo_01, post: 435245, member: 12858 wrote: I have a question for all users of this forum, which is the following:
Is there any datum that can project a separate line to me 2 meters of the real line or position according to GPS ?.
A datum can only project one line at a time. If it projecting where you are, just pull an offset 2 ft to the other line.you cannot run two datum at the same time as far as I know.
Sent from my SM-G955U using Tapatalk
Eduardo_01, post: 435245, member: 12858 wrote: Is there any datum that can project a separate line to me 2 meters of the real line or position according to GPS ?.
I presume that you are asking how you are getting lines that are not landing where you expect them to by 2 meters. Am I right?
There are a few ways this could happen. One, as was already suggested, would be using the wrong foot definition - if you are working in feet. But since you ask about a seperation in meters I presume you are working in meters.
A second way would be to have your base station coordinate change. Possibly by using autonomous positions for the base each time you set up.
A third way - and this would require some doing - is to change the false northing or false easting (or both) in your projection zone definition.
Perhaps you could tell us more about the circumstances. Are you experiencing a change of exactly 2 meters or approximately 2 meters?
Mark Mayer, post: 435249, member: 424 wrote: I presume that you are asking how you are getting lines that are not landing where you expect them to by 2 meters. Am I right?
There are a few ways this could happen. One, as was already suggested, would be using the wrong foot definition - if you are working in feet. But since you ask about a seperation in meters I presume you are working in meters.
A second way would be to have your base station coordinate change. Possibly by using autonomous positions for the base each time you set up.
A third way - and this would require some doing - is to change the false northing or false easting (or both) in your projection zone definition.
Perhaps you could tell us more about the circumstances. Are you experiencing a change of exactly 2 meters or approximately 2 meters?
The problem occurs in the post process, I used locus processor 3 years ago, I currently use GNSS SOLUTIONS.
Mark Mayer, post: 435249, member: 424 wrote: I presume that you are asking how you are getting lines that are not landing where you expect them to by 2 meters. Am I right?
There are a few ways this could happen. One, as was already suggested, would be using the wrong foot definition - if you are working in feet. But since you ask about a seperation in meters I presume you are working in meters.
A second way would be to have your base station coordinate change. Possibly by using autonomous positions for the base each time you set up.
A third way - and this would require some doing - is to change the false northing or false easting (or both) in your projection zone definition.
Perhaps you could tell us more about the circumstances. Are you experiencing a change of exactly 2 meters or approximately 2 meters?
I am not using autonomous positions, my question is:
Because if the same points differs the position, does it have something to do with dates, PDOPs or what happens?
Eduardo_01, post: 435254, member: 12858 wrote: The problem occurs in the post process, I used locus processor 3 years ago, I currently use GNSS SOLUTIONS.
So is it that the bearing and distance between points from the LOCUS processing is the same as the bearing and distance between GNSS SOLUTIONS processed points, only the 2 sets of points are offset from one another?
Mark Mayer, post: 435265, member: 424 wrote: So is it that the bearing and distance between points from the LOCUS processing is the same as the bearing and distance between GNSS SOLUTIONS processed points, only the 2 sets of points are offset from one another?
It is right.
Could be an ellipsoid issue. What projection are you using? Which ellipsoid is correct for that? The difference between GRS80 and the current ITRF ellipsoid is about 2 meters.
Mark Mayer, post: 435271, member: 424 wrote: Could be an ellipsoid issue. What projection are you using? Which ellipsoid is correct for that? The difference between GRS80 and the current ITRF ellipsoid is about 2 meters.
The Locus and GNSS program uses the GRS80, since they have the same semi-major axis and the same inverse.
Eduardo, I do not know the answers to making LOCUS PROCESSOR work today.....
However, I do know that the LOCUS units were made by a company named ASHTECH. Ashtech, was named that, because Javad Ashajee, was the guy that assembled the team, and made them. (Some were sold, with SOKKIA name, but it was the SAME receiver. )
Somebody somewhere, knows what to do.
And, on that note, I suggest you post over on the Javad Forum.
https://support.javad.com/index.php
I can't help you... but those guys are smarter than I am. (Many folks on this forum are smarter than I am!) I suspect you may find a few leftovers, who were involved in the creation of Ashtech Solutions. And, that's as close to the horses mouth as I know.
I still have 2 Locus units....
Nate
Nate The Surveyor, post: 435287, member: 291 wrote: Eduardo, I do not know the answers to making LOCUS PROCESSOR work today.....
However, I do know that the LOCUS units were made by a company named ASHTECH. Ashtech, was named that, because Javad Ashajee, was the guy that assembled the team, and made them. (Some were sold, with SOKKIA name, but it was the SAME receiver. )
Somebody somewhere, knows what to do.And, on that note, I suggest you post over on the Javad Forum.
https://support.javad.com/index.phpI can't help you... but those guys are smarter than I am. (Many folks on this forum are smarter than I am!) I suspect you may find a few leftovers, who were involved in the creation of Ashtech Solutions. And, that's as close to the horses mouth as I know.
I still have 2 Locus units....
Nate
Thank you for your answer
seemed like Mark was troubleshooting this issue just fine
Which program do you use for the post-process?
Nate The Surveyor, post: 435287, member: 291 wrote: Eduardo, I do not know the answers to making LOCUS PROCESSOR work today.....
However, I do know that the LOCUS units were made by a company named ASHTECH. Ashtech, was named that, because Javad Ashajee, was the guy that assembled the team, and made them. (Some were sold, with SOKKIA name, but it was the SAME receiver. )
Somebody somewhere, knows what to do.And, on that note, I suggest you post over on the Javad Forum.
https://support.javad.com/index.phpI can't help you... but those guys are smarter than I am. (Many folks on this forum are smarter than I am!) I suspect you may find a few leftovers, who were involved in the creation of Ashtech Solutions. And, that's as close to the horses mouth as I know.
I still have 2 Locus units....
Nate
Which program do you use for the post-process?
The ITRF which is a product of the International Earth Rotation and Reference System Service does not have its own ellipsoid. Coordinate values are originally published as X,Y,Z Earth-Centered Earth- Fixed. The user applies whatever ellipsoid they want which should be GRS80 which is the international standard. The difference between NAD 83 and ITRF coordinates in the conterminous U.S. is approximately 1.5 m in 3-D.
base9geodesy, post: 435386, member: 7189 wrote: The ITRF which is a product of the International Earth Rotation and Reference System Service does not have its own ellipsoid. Coordinate values are originally published as X,Y,Z Earth-Centered Earth- Fixed. The user applies whatever ellipsoid they want which should be GRS80 which is the international standard. The difference between NAD 83 and ITRF coordinates in the conterminous U.S. is approximately 1.5 m in 3-D.
And in case both programs use the same geoid model?