On Fri, 28 Mar 2008, Frederik Ramm wrote:
and you can also limit the
length of these GPS connection lines (draw.rawgps.max-line-length=x,
in metres), for those cases where you get crazy zig-zagging.
I had noticed a while ago that JOSM appeared to handle GPX files
incorrectly (and
On Fri, 28 Mar 2008, Frederik Ramm wrote:
I'll investigate that. However with data retrieved from the server, you don't
even get the trkseg structure, you just get a ton of individual points and
have no chance of finding out whether they belong to the same segment or not!
Ouch - I hadn't
On Fri, 28 Mar 2008, Frederik Ramm wrote:
* It is now possible to have arrows on the lines connecting GPS
points (draw.rawgps.direction=true),
I'm seeing a couple of slightly odd things with the GPS direction arrows:
(screenshot) http://www.nexusuk.org/~steve/josm-gpsarrows.png
They
Hi,
They are pointing the wrong way - the blue motorway loop in the
screen shot is traversed in the anticlockwise direction, but the
arrows on the GPS track are showing it to be clockwise (seems to be
the case for all the GPS tracks, so this isn't just an odd data set).
Are you saying
On Fri, 28 Mar 2008, Frederik Ramm wrote:
Are you saying every single arrow points the wrong way? Because that would be
an easy fix to make ;-)
Yes, seems to be the case :)
This happens when lines of length 0 are drawn. I suspect that those tracks
that suffer from the east arrows have
On Fri, 28 Mar 2008, Steve Hill wrote:
Are you saying every single arrow points the wrong way? Because that would be
an easy fix to make ;-)
Yes, seems to be the case :)
To complicate things more, the direction arrows on data imported from a
local GPX file are the right way around, so this
In message [EMAIL PROTECTED]
David Earl [EMAIL PROTECTED] wrote:
On 28/03/2008 16:50, Raphael Mack wrote:
Am Freitag, 28. März 2008 schrieb Steve Hill:
On Fri, 28 Mar 2008, Steve Hill wrote:
Are you saying every single arrow points the wrong way? Because that
would be an easy
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
On 28/03/2008 17:02, Tom Hughes wrote:
In message [EMAIL PROTECTED]
David Earl [EMAIL PROTECTED] wrote:
On 28/03/2008 16:50, Raphael Mack wrote:
Am Freitag, 28. März 2008 schrieb Steve Hill:
On Fri, 28 Mar 2008, Steve Hill wrote:
Are you saying every single arrow points the wrong
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
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Hughes wrote:
| In message [EMAIL PROTECTED]
| David Earl [EMAIL PROTECTED] wrote:
|
| On 28/03/2008 16:50, Raphael Mack wrote:
| Am Freitag, 28. März 2008 schrieb Steve Hill:
| On Fri, 28 Mar 2008, Steve Hill wrote:
| Are you saying
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
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
Hi,
I should point out that you can't synchronize an audio track to a GPS
track without the exact timing information.
But I'm confused now - if I look at GPS tracks on the third tab of the
OSM home page, what I see is GPX style HTML with exact timestamps and
ordered tracks. So if it
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
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
19 matches
Mail list logo
