Linear Traverse not working since 7.0 ???

[MaxRingler]

I was using the linear traverse function back in 2006 with ArcPad 6.0 and it worked perfectly fine with backsight - however, forsight was not working and the angles I entered caused the programm to calculate the points as if they when using forsight.

Today, now in ArcPad 10 I needed the function again, only to find out, that it now seemingly it is not working at all anymore. What is happening?

If I precisely follow the instructions for linear traversing as described in the tutorial, I end up with an error message saying "Reference Point A not set" when I want to enter the second point of my traverse.

Alternatively, when I set a reference point A in the beginning (or if one is set already from other actions) and then start traversing, the first point of the traverse is set propery in respect to "A". However, when I continue by pointing somewhere on the map to set the next point of the traverse, the program prompts me with distance and angle values in respect to "A", not the first point of the traverse. When I change these values, they remain in respect to "A". When I now confirm my entry "OK" the same entry masks pops up AGAIN, now prompting me with set values, that relate to the same point as before, but in respect to the last point of the traverse - however, changing the values now does not change anything and when I commit the values - "OK" again - the point gest set accoding to the first values, and in respect to "A".

So basically, linear traversing is mimicing the behaviour of radial traversing, as all points get set in respect to reference point A, and not in respect to the last entered point of the traverse!

By the way, backsight is still not working, also not for offsetting points, as all points I try to enter via backsigth still end up as if they were entered via foresight.

I have now cross-checked and repeatedly encountered this problem in version 7.0, 7.1, 7.1.1, 8.0, 8.0 SP1, 10.0 and 10.0.2 on three entirely independent machines running either XP SP3 or Win7, using a volume license from my University.

Any suggestions?

Max Ringler
Department of Evolutionary Biology
University of Vienna, Austria

[MarikaVertzonis]

after some thorough research, there are a few separate things going on here:

1) linear and radial traverse works correctly (and as documented in ArcPad Help) when using a laser rangefinder.
2) linear and radial traverse does not work correctly when using pen taps. This procedure is not documented, however should work intuitively. The ArcPad team have now isolated the bug (that the reference point is not automatically set) and will strive to fix it asap.
3) segmented polylines and simply offset polylines work correctly (and as documented in Arcpad Help) when using pen taps.
4) segmented polylines and simply offset polylines do not work correctly when using laser rangfinders. This procedure is not documented, but again, should work. The team have isolated the bug (that two point/vertex forms appear instead of one) and will strive to fix it asap.
5) the comment regarding forsight and backsight i can not resolve. I tested using radial and linear traversing, with a rangefinder (item 1 above), and i can clearly see the difference between using foresight and backsight. Perhaps the ArcPad use of the terminology is different to what you are expecting?
With foresight, you are standing at a known coordinate, such as reference point A, and you are shooting the target, such as the vertex of your feature. With backsight, you are standing at your target, such as the vertex of your feature, and you are shooting back to a known coordinate, such as reference point A. The same feature shape should be created.
Feel free to add more explanation about your issue with foresight and backsight and i will investigate further.

[MaxRingler]

Thanks very much for checking and forwarding!

1) did not try that, as I never worked with a connected rangefinder so far, but always hat to enter distance and bearing from a manual laser rangefinder and a precision compass

2) The procedure ist documented here: http://help.arcgis.com/en/arcpad/10.0/help/index.html#//00s10000010q000000.htm : "With a rangefinder, shoot the next feature from the location of the first feature (foresight). Alternatively, shoot back to the first vertex (target) from the location of the second vertex (backsight). Simply tap the screen if you do not have a rangefinder connected."

3) & 4) never needed these features so far, so I did not check

5) Seems as if I was to quick here - I experienced this problem long ago in 6.0 and 7.0 (probably early 8.0 also?) and assumed, as I could track the linear traversing problem (point 2) back to 7.0, that backsight vs. foresight also still did not work. As for my 6.0 experience: Then, I ended up with  identical points when I entered 90°, 5m in foresight or 90°, 5m in backsight, while 90°, 5m, backsight should have resulted in a point at 180°, 5m, foresight. As of 10.0.2, this obviously works now as expected.

Best

Max

[MaxRingler]

Apparently these issue have not been fixed in version 10.0.3 - as the fixlog states it was more important to display high resolution icons for this erronous function...

"Offset Polyline/Polygon icon is now high resolution on       high resolution devices (CQ00312973)"

...were talking priorities here...