Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Hi, > mh, I guess this cannot be fixed in josm, since the the server returns the > stored gps points in arbitrary order. I would even suggest not to draw any > direction arrows for gps data from the server. But they can't be too arbitrary since drawing lines in between the points would reveal a completely chaotic picture otherwise. I think David Earl is right about sorting by timestamp since this is what's in the API source: points = Tracepoint.find_by_area(min_lat, min_lon, max_lat, max_lon, :offset => offset, :limit => TRACEPOINTS_PER_PAGE, :order => "timestamp DESC" ) ... and the "DESC" nicely explains the observation that all arrows are in the wrong direction! I wonder why it is there. TomH? Bye Frederik ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Frederik Ramm wrote: > ... and the "DESC" nicely explains the observation that all arrows are > in the wrong direction! I wonder why it is there. Because you want the most recent ones first? cheers Richard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Hi, >> ... and the "DESC" nicely explains the observation that all arrows are >> in the wrong direction! I wonder why it is there. > > Because you want the most recent ones first? Does any application *not* read all pages returned? Bye Frederik ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Frederik Ramm wrote: >Sent: 28 March 2008 5:10 PM >To: Raphael Mack >Cc: talk@openstreetmap.org >Subject: Re: [OSM-talk] JOSM update / why does API return GPS points in >descending order? > >Hi, > >> mh, I guess this cannot be fixed in josm, since the the server returns >the >> stored gps points in arbitrary order. I would even suggest not to draw >any >> direction arrows for gps data from the server. > >But they can't be too arbitrary since drawing lines in between the >points would reveal a completely chaotic picture otherwise. I think >David Earl is right about sorting by timestamp since this is what's in >the API source: And since its rare for two people to have the same time period for the same area by chance it generally works (just back to front). But of course that cant be guaranteed, especially if the area is large. Cheers Andy > >points = Tracepoint.find_by_area(min_lat, min_lon, max_lat, max_lon, >:offset => offset, :limit => TRACEPOINTS_PER_PAGE, :order => "timestamp >DESC" ) > >... and the "DESC" nicely explains the observation that all arrows are >in the wrong direction! I wonder why it is there. TomH? > >Bye >Frederik > >___ >talk mailing list >talk@openstreetmap.org >http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Am Freitag, 28. März 2008 schrieb Frederik Ramm: > Hi, > > > mh, I guess this cannot be fixed in josm, since the the server returns > > the stored gps points in arbitrary order. I would even suggest not to > > draw any direction arrows for gps data from the server. > > But they can't be too arbitrary since drawing lines in between the > points would reveal a completely chaotic picture otherwise. I think > David Earl is right about sorting by timestamp since this is what's in > the API source: > > points = Tracepoint.find_by_area(min_lat, min_lon, max_lat, max_lon, > > :offset => offset, :limit => TRACEPOINTS_PER_PAGE, :order => "timestamp > > DESC" ) > > ... and the "DESC" nicely explains the observation that all arrows are > in the wrong direction! I wonder why it is there. TomH? Oh, this sounds nice. I expected, that the timestamps are not even stored in the db, since they are not included in the delivered gpx. Maybe one could implement this, when touching the code to change to ascending order? - This would allow to split the track into track segments which would help to draw arrows only if the time difference is less than some threshold... Rapha ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Frederik Ramm wrote: > Does any application *not* read all pages returned? Well, in Potlatch the "download points in current area" is the primary method of reading tracklogs (as - mercifully - it doesn't have any access to your local file system), so yes, it does return only the most recent n000 points to avoid utterly boggling the server/your browser. That said, it doesn't use the XML API anyway so it's a bit of a moot point. cheers Richard ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
On Fri, Mar 28, 2008 at 05:37:19PM -, Andy Robinson (blackadder) wrote: > And since its rare for two people to have the same time period for the same > area by chance it generally works (just back to front). But of course that > cant be guaranteed, especially if the area is large. Or when there has been a mapping party with multiple groups in the area... cu bart ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
On Fri, Mar 28, 2008 at 12:37 PM, Andy Robinson (blackadder) < [EMAIL PROTECTED]> wrote: > Frederik Ramm wrote: > >Sent: 28 March 2008 5:10 PM > >To: Raphael Mack > >Cc: talk@openstreetmap.org > >Subject: Re: [OSM-talk] JOSM update / why does API return GPS points in > >descending order? > > > >Hi, > > > >> mh, I guess this cannot be fixed in josm, since the the server returns > >the > >> stored gps points in arbitrary order. I would even suggest not to draw > >any > >> direction arrows for gps data from the server. > > > >But they can't be too arbitrary since drawing lines in between the > >points would reveal a completely chaotic picture otherwise. I think > >David Earl is right about sorting by timestamp since this is what's in > >the API source: > > And since its rare for two people to have the same time period for the > same > area by chance it generally works (just back to front). But of course that > cant be guaranteed, especially if the area is large. > > Cheers > > Andy > > On the increasingly likely (as our userbase grows) chance that two or more users upload tracks with overlapping times, would it be possible to do a "group by" user so that the tracks will be logically clustered? I don't know the table schema--I'm not even sure if that table has a "user" column. Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
Hi, > > Does any application *not* read all pages returned? > > Well, in Potlatch the "download points in current area" is the primary > method of reading tracklogs (as - mercifully - it doesn't have any > access to your local file system) "Whoooa! Potlatch has just ruined my personal files!" , so yes, it does return only the most recent n000 points to avoid > utterly boggling the server/your browser. That said, it doesn't use > the XML API anyway so it's a bit of a moot point. Right. I'll change JOSM to draw the arrows the other way for GPS tracks downloaded from the server, but please don't forget to speak up should you ever remove the DESC ordering ;-) Bye Frederik -- Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09" E008°23'33" ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] JOSM update / why does API return GPS points in descending order?
On Fri, Mar 28, 2008 at 5:37 PM, Andy Robinson (blackadder) < [EMAIL PROTECTED]> wrote: > Frederik Ramm wrote: > >Sent: 28 March 2008 5:10 PM > >To: Raphael Mack > >Cc: talk@openstreetmap.org > >Subject: Re: [OSM-talk] JOSM update / why does API return GPS points in > >descending order? > > > >Hi, > > > >> mh, I guess this cannot be fixed in josm, since the the server returns > >the > >> stored gps points in arbitrary order. I would even suggest not to draw > >any > >> direction arrows for gps data from the server. > > > >But they can't be too arbitrary since drawing lines in between the > >points would reveal a completely chaotic picture otherwise. I think > >David Earl is right about sorting by timestamp since this is what's in > >the API source: > > And since its rare for two people to have the same time period for the > same > area by chance it generally works (just back to front). But of course that > cant be guaranteed, especially if the area is large. > It would happen though when there's been a mapping party. > > Cheers > > Andy > > > > >points = Tracepoint.find_by_area(min_lat, min_lon, max_lat, max_lon, > >:offset => offset, :limit => TRACEPOINTS_PER_PAGE, :order => "timestamp > >DESC" ) > > > >... and the "DESC" nicely explains the observation that all arrows are > >in the wrong direction! I wonder why it is there. TomH? > > > >Bye > >Frederik > > > >___ > >talk mailing list > >talk@openstreetmap.org > >http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk > > > ___ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk > ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
