Dear CSPRO user Community,
I just finished working on a survey which involves taking GPS Coordinates repeatedly. I realized that I could make the unique identifier fields persistent. The GPS coordinates could also be included in the Unique Identifier variable set. But GPS coordinates have decimals whilst a variable in the unique identifier section can't be assigned decimal number. So, I decided to pull the GPS coordinates out the unique identifier section.
Now, I want the previous values in the identifier section plus the GPS coordinate reading to remain there until I change the persistence to record new values. So in effect I want the previously taken GPS coordinate to remain for new cases until I want a new reading to be taken.
I need urgent help as I want to role this survey in the next couple of days.
Thanks, in advance.
It is the GPS of the Pole, I want to make persistent. Or alternatively the previous reading to remain until I decided to change it.
How to Copy the the previous GPS reading if it is not Persistent .
-
lmoriba
- Posts: 56
- Joined: June 10th, 2018, 6:21 pm
How to Copy the the previous GPS reading if it is not Persistent .
You do not have the required permissions to view the files attached to this post.
-
aaronw
- Posts: 571
- Joined: June 9th, 2016, 9:38 am
- Location: Washington, DC
Re: How to Copy the the previous GPS reading if it is not Persistent .
The easiest approach and one that would work without a menu is to make use of savesetting and loadsetting. When you take a GPS reading, store the values locally using savesetting. Then in the next case you can access them through loadcase.
savesetting: https://www.csprousers.org/help/CSPro/s ... ction.html
loadsetting: https://www.csprousers.org/help/CSPro/l ... ction.html
savesetting: https://www.csprousers.org/help/CSPro/s ... ction.html
loadsetting: https://www.csprousers.org/help/CSPro/l ... ction.html
-
lmoriba
- Posts: 56
- Joined: June 10th, 2018, 6:21 pm
Re: How to Copy the the previous GPS reading if it is not Persistent .
Thanks
the issue is now resolved.