Opened 15 years ago
Last modified 4 years ago
#4132 new enhancement
'Shift+g' to switch from all GPS traces to just mine
Reported by: | liotier | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core shortcuts | Version: | latest |
Keywords: | gpx, gps, UI, user interface, keyboard shortcut, layer, display | Cc: |
Description (last modified by )
In Potlatch, 'Shift+g' shows only your traces and 'g' show all the
traces (http://wiki.openstreetmap.org/wiki/Potlatch/Keyboard_shortcuts).
But the same shortcuts don't work in JOSM. Wouldn't it be nice ?
In areas which contain many GPS traces, that layer can be an horrible mess - especially where many of the traces are low-quality. Finding which one is the carefully captured data that you trust for tracing that new street is very difficult. Potlatch's 'Shift+g' makes it easy. Let's have that in JOSM too !
This thread contains the discussion of that feature on talk@… : http://old.nabble.com/Seeing-only-my-traces-in-JOSM---td26479018.html
Attachments (0)
Change History (3)
follow-up: 2 comment:1 by , 15 years ago
Priority: | normal → minor |
---|
comment:2 by , 15 years ago
Replying to stoecker:
I don't think we can implement this. The API does not allow to access that data.
Isn't trace metadata what we need for this wishlist item ?
http://wiki.openstreetmap.org/wiki/API_v0.6#Downloading_Trace_Metadata
Example "details" response:
<?xml version="1.0" encoding="UTF-8"?>
<osm version="0.6" generator="OpenStreetMap server">
<gpx_file id="38698"
name="rathfarnham_churchtown_nutgrove.gpx" lat="53.285644054" lon="-6.238367558"
user="robfitz" public="true" pending="false"
timestamp="2007-09-13T23:28:41+01:00"/>
</osm>
We do have the user name in the GPS track detail metadata. Is there anything else that is needed and that I might not be aware of ?
comment:3 by , 4 years ago
Component: | Core → Core shortcuts |
---|---|
Description: | modified (diff) |
I don't think we can implement this. The API does not allow to access that data. Neverthelesse leaving the report open. Maybe API changes somewhen.
Storing and loading the tracks locally is suggested solution for now.