Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Sometimes when the device is pulling coordinates with the GeoPositionAccuracy set to High and the MovementThreshold set to 0, the GeoCoordinate that is captured is further away and not inline with the other coordinates. How can I prevent that or remove that GeoCoordinate from my collection of GeoCoordinates? You'll notice that in the imge below right above the second light grey 'e' and to the right on the route 11 symbol, you'll see a little jog out. The same thing under the first little grey 'e'.

enter image description here

share|improve this question

Set the MovementThreshold to a higher value:

The minimum distance that must be travelled between successive PositionChanged events.

See Documentation

share|improve this answer
Even if I set the MovementThreshold to 20, it still picks up the last known GPS location at somepoint in the PositionChanged event. That would/should fix the other jog outs, but since this is a navigation-like app, I have it set to 0 to get better results (or so I choose). The only thing I can think of is invalidating coordinates based on speed and distance that was traveled. If it's not close, I shouldn't add that coordinate. Thoughts? – Jason N. Gaylord Jun 22 '11 at 4:38
See the following for similar gripes:… – Jason N. Gaylord Jun 22 '11 at 4:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.