Page 1 of 1

SurvCE Localization Problem

PostPosted: Thu Jun 02, 2005 5:47 am
by John \"Da Ringer\"
Hi Guys,

There is a problem with the localization routine in SurvCE 1.21 and 1.50.

If I set my base unit and do a rover localization on 4 or more existing
points located with a total station, everything works fine.

The problem occurs when I move the base unit to a point that has been
located with RTK.

I wish you would post how to perform a localization on an existing point
number(s) by "read from GPS" that will allow the user to move the base unit
in the future to another point and stay calibrated.

Thanks

John Roberson

Re: SurvCE Localization Problem

PostPosted: Fri Jun 03, 2005 9:12 pm
by Barkley Hensley
John "Da Ringer" wrote:
Hi Guys,
How To: Move RTK base.


If you have a localization completed on a site, the points in that
localization and any other RTK stored points can be used later as a
different base location.

When you set the base up the second time (on a different point), do not
do "Read From GPS". That would grab a new Lat/Lon for that point. We
want to use the Lat/Lon for that new base position that is relative to
the localization file and all the previous work.

Use the "From Known Position" tab, "Previously Surveyed Point". Select
the point number. The program will go back to the rw5 file to find the
Lat/Lon record for that point and set the base there.

Now your new base is still relative to the previous base setup.

Do not mix 1.21 localization files with 1.50. The *.dat files are formatted






There is a problem with the localization routine in SurvCE 1.21 and 1.50.

If I set my base unit and do a rover localization on 4 or more existing
points located with a total station, everything works fine.

The problem occurs when I move the base unit to a point that has been
located with RTK.

I wish you would post how to perform a localization on an existing point
number(s) by "read from GPS" that will allow the user to move the base unit
in the future to another point and stay calibrated.

Thanks

John Roberson


Re: SurvCE Localization Problem

PostPosted: Fri Jun 03, 2005 9:53 pm
by John \"Da Ringer\"
Hi Mr Hensley (Barkley)

A few months ago I think I tried it that way. It didn't work for me at that
time.

In a few days I will try it again and let you know what happens.

Do I need to have a "geoid" file loaded for my area?

Thanks for the reply.

John Roberson


"Barkley Hensley" <bhensley@carlsonsw.com> wrote in message
news:d7q2rh$i40$1@update.carlsonsw.com...
John "Da Ringer" wrote:
Hi Guys,
How To: Move RTK base.

If you have a localization completed on a site, the points in that
localization and any other RTK stored points can be used later as a
different base location.

When you set the base up the second time (on a different point), do not do
"Read From GPS". That would grab a new Lat/Lon for that point. We want
to use the Lat/Lon for that new base position that is relative to the
localization file and all the previous work.

Use the "From Known Position" tab, "Previously Surveyed Point". Select
the point number. The program will go back to the rw5 file to find the
Lat/Lon record for that point and set the base there.

Now your new base is still relative to the previous base setup.

Do not mix 1.21 localization files with 1.50. The *.dat files are
formatted







There is a problem with the localization routine in SurvCE 1.21 and 1.50.

If I set my base unit and do a rover localization on 4 or more existing
points located with a total station, everything works fine.

The problem occurs when I move the base unit to a point that has been
located with RTK.

I wish you would post how to perform a localization on an existing point
number(s) by "read from GPS" that will allow the user to move the base
unit in the future to another point and stay calibrated.

Thanks

John Roberson

Re: SurvCE Localization Problem

PostPosted: Fri Jun 03, 2005 11:06 pm
by Barkley Hensley
John, i don't think it would hurt a thing. Depends upon the scope of
the job i would suppose but I would recommend using a geiod.



John "Da Ringer" wrote:

Hi Mr Hensley (Barkley)

A few months ago I think I tried it that way. It didn't work for me at that
time.

In a few days I will try it again and let you know what happens.

Do I need to have a "geoid" file loaded for my area?

Thanks for the reply.

John Roberson


"Barkley Hensley" <bhensley@carlsonsw.com> wrote in message
news:d7q2rh$i40$1@update.carlsonsw.com...

John "Da Ringer" wrote:

Hi Guys,

How To: Move RTK base.

If you have a localization completed on a site, the points in that
localization and any other RTK stored points can be used later as a
different base location.

When you set the base up the second time (on a different point), do not do
"Read From GPS". That would grab a new Lat/Lon for that point. We want
to use the Lat/Lon for that new base position that is relative to the
localization file and all the previous work.

Use the "From Known Position" tab, "Previously Surveyed Point". Select
the point number. The program will go back to the rw5 file to find the
Lat/Lon record for that point and set the base there.

Now your new base is still relative to the previous base setup.

Do not mix 1.21 localization files with 1.50. The *.dat files are
formatted









There is a problem with the localization routine in SurvCE 1.21 and 1.50.

If I set my base unit and do a rover localization on 4 or more existing
points located with a total station, everything works fine.

The problem occurs when I move the base unit to a point that has been
located with RTK.

I wish you would post how to perform a localization on an existing point
number(s) by "read from GPS" that will allow the user to move the base
unit in the future to another point and stay calibrated.

Thanks

John Roberson



Re: SurvCE Localization Problem

PostPosted: Tue Sep 12, 2006 9:29 pm
by elconejocl
have you try using Initialize to Know Point?








##-----------------------------------------------##
Article posted with CarlsonSWNewGroups
http://CarlsonSWNewGroups.sourceforge.net
Share your knowledge in... carlson.survce
##-----------------------------------------------##