# Projection doesn`t work correctly.

Sergey Louks shared this problem 5 years ago
Solved

1) I add first point of the route (long click, pick location dialog, Points, "first point")

2) then I should place cursor on the "first point"

3) then I choose projection (pick location dialog, projection) and enter distance 10000m and bearing 61.82454

4) Check bearing between "first point" and "projection point" - it matches bearing that I entered. It works!

But If I:

1) I add first point of the route (long click, pick location dialog, Points, "first point")

2) place cursor somewhere else

3) then I choose projection (pick location dialog, projection) and enter distance 10000m and bearing 61.82454

4) Check bearing between "first point" and "projection point" - it doesn`t match bearing that I entered. For example 62.458!

If In Projection Dialog I choose different "Location" (not "Map Center", for example point -> "first point"), enter distance 10000 m, bearing 61.82454 then "projection point" matches "first point".

0

Hello Sergey,

in moment you display "projection dialog", you may see text "map center" in coordinate panel. This mean, that locus took current map center as first point for projection. his mean, that when if you in step 2, moved map center from point to different location, Locus took this different location as first point for projection

So if I understand correctly what you wrote, then there is no problem in Locus. If you want to use a projection function, you have to

1. move map center to first point and then start projection, or

2. start projection and choose first point in this projection dialog

0

Hi, Menion. It was helpful, but what should I do with the bug? I add first point, then long click on add button, choose projection, then choose from dialog "pick location" "points" or "coordinates" , then enter distance and bearing. If I choose "points" and pick for example point "A", then projection doesn`t start from point "A" it will place second point to point "A".

0

ah, I firstly do not saw issue. by your second post, I finally see where`s a problem.

Hmm it`s quite complicated because you call twice in row window with grid of possible location sources, and Locus second call attach to first, so if you on second call choose point A, it`s attached to first call (so attached to track as next point)

Anyway, problem should be fixed now. So check it please in next version, but seems that it finally works correctly

0

Thanks for help!