Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

P2's GPS traces (from server) display is affected by new API treatment of unordered traces #5501

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: aseerel4c26
[Submitted to the original trac issue database at 4.04pm, Thursday, 25th October 2018]

If I remember correctly (cannot test, since I have no Flash player anymore) P2 displays all GPS traces as lines. Hence, it is likely affected, as JOSM is, by the API trackpoints api call code change which closed openstreetmap/openstreetmap-website#2046 .

@openstreetmap-trac
Copy link
Author

Author: SomeoneElse
[Added to the original trac issue at 6.20pm, Thursday, 8th November 2018]

If I click "edit" against one of my existing traces it works as before. I I load one of my tracks within P2 it works as before.

Loading all GPS traces gives the attached effect (not working as before)

@openstreetmap-trac
Copy link
Author

Author: Richard
[Added to the original trac issue at 9.21am, Friday, 9th November 2018]

Do you have a sample lat/long where this behaviour is exhibited?

@openstreetmap-trac
Copy link
Author

Author: SomeoneElse
[Added to the original trac issue at 9.28am, Friday, 9th November 2018]

That screenshot is of around https://www.openstreetmap.org/#map=18/53.17388/-1.41611 .

@openstreetmap-trac
Copy link
Author

Author: Richard
[Added to the original trac issue at 12.25pm, Friday, 9th November 2018]

Addressed in systemed/potlatch2@550aab4

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant