I recently installed Survey Pro 5.0 and for the most part like the new look and added features based on the short time I have used it. Until today.
On a typical project we run our traverse, download the raw file, adjust it in Carlson and then upload the adjusted points back to the data collector and overwrite the unadjusted points in the job file. Now when I try to import the adjusted points I get a message "Point XX already exists in the job and it is A point with dependents point." It will not allow you to simply overwrite the point, it give you the options to ignore, rename, or stop importing. The "Dependent" points are my traverse points, points in which we ran a repetition on. I cannot even edit the coordinates in Edit Points.
I'm hoping this is just a setting but cannot find any way to turn it off. Has anyone else ran in to this?
Wes
Not what you asked for, sorry, but instead of trying to overwrite the prior file, maybe just upload to a new file like 11-030 ADJ or something ?
Can you blow away the old file and then re-important the new one?
Not in the same .survey file (Survey Pro no longer creates .job and .raw files). You would have to delete the .survey file, consequently deleting the original raw data. The raw could be spliced together in the office, but that would be a huge PTA for every job. They've added several new "fail-safes" that really prevents manipulation of traverse points.
So whats new in 5.0?
We bought 2 Rangers a while back, used SurveyPro for years, and then put SurvCE on them last year and haven't really looked back.
You mean SurvCE is better?
Thank you.
Survey Pro 5.0 - Data Translation
We've been having the same issue and have experienced a measure of frustration with it. We have been using Survey Pro for over 20 years. Recently on at least 3 different occasions, we have had a block of points just mysteriously get translated without our knowing. We are having a hard time troubleshooting and figuring out what is causing it. Needless to say, we are very concerned by the discovery. If there are any users who have experienced the same problems, please let us know how you resolved it.
Thanks