Am Sonntag 05 Oktober 2008 13:01:48 schrieb Richard Fairhurst:
Marc Schütz wrote:
Several of the ways in this area
http://www.openstreetmap.org/?
lat=49.89487lon=10.88733zoom=17layers=0B00FTFTTT
have been modified with Potlatch so that they contain the same node
twice in a
row. Is
Marc Schütz wrote:
Several of the ways in this area
http://www.openstreetmap.org/?
lat=49.89487lon=10.88733zoom=17layers=0B00FTFTTT
have been modified with Potlatch so that they contain the same node
twice in a
row. Is this a known bug? Should the API be changed to reject such
ways?
Rogier Wolff wrote:
Number one has the disadvantage of allowing the database to grow
bigger than it needs to be.
Heh. Of course, we have an elephant in the room there - one which,
mercifully, 0.6 will address. I committed a change last night (not
deployed yet) so that amf_controller
Several of the ways in this area
http://www.openstreetmap.org/?lat=49.89487lon=10.88733zoom=17layers=0B00FTFTTT
have been modified with Potlatch so that they contain the same node twice in a
row. Is this a known bug? Should the API be changed to reject such ways?
Regards, Marc
On Sun, Oct 5, 2008 at 1:02 PM, Richard Fairhurst [EMAIL PROTECTED] wrote:
Rogier Wolff wrote:
Number one has the disadvantage of allowing the database to grow
bigger than it needs to be.
Heh. Of course, we have an elephant in the room there - one which,
mercifully, 0.6 will address. I
Matt Amos wrote:
just out of interest, i did a quick check on a recent UK extract: 65%
of all tags are created_by and that 87% of created_by tags are JOSM.
'taint a simple comparison, though: Potlatch doesn't set created_by
on nodes at all, but does set created_by on way updates. JOSM sets
On 05/10/2008 17:00, Matt Amos wrote:
On Sun, Oct 5, 2008 at 1:02 PM, Richard Fairhurst [EMAIL PROTECTED] wrote:
Rogier Wolff wrote:
Number one has the disadvantage of allowing the database to grow
bigger than it needs to be.
Heh. Of course, we have an elephant in the room there - one which,
2008/10/5 David Earl [EMAIL PROTECTED]:
And this underestimates it because Potlatch replaces any created_by's on
objects originally created by JOSM, but JOSM doesn't replace Potlatch's
created_by's.
The underestimation is probably worse than that as JOSM stoped
creating created_by's at all a
David Earl wrote:
And this underestimates it because Potlatch replaces any
created_by's on objects originally created by JOSM, but JOSM
doesn't replace Potlatch's created_by's.
Which is _really_ annoying for debugging purposes. ;)
But anyway, you are, as an unwise man once said,
Am Sonntag, den 05.10.2008, 17:10 +0100 schrieb Richard Fairhurst:
I did a few bits of SQL footling around recently on a UK planet and
it would _roughly_ suggest that more UK edits at present are done
with Potlatch than JOSM. I suspect the reverse is true in Germany!
See also
Hi,
this thread is really valuable for me as someone who writes an
osm editor. With respect to overwriting the created_by entry,
i was just copying potlatchs behaviour. So: What's the preferred
behaviour? Overwriting imho doesn't make much sense. But since
osm2go is in an early development change
i was just copying potlatchs behaviour. So: What's the preferred
behaviour?
Merkaartor systematically overwrite the created_by when doing changes on
the server (after having followed a similar thread).
If this tag has any value, it is, IMHO, to be able to identify editors
having
The idea is to move the created_by tag to the changeset for the
API0.6, thus reducing the amount of data stored considerably. It
would also mean that any changeset could only be used for one editor.
Shaun
On 5 Oct 2008, at 21:34, Till Harbaum / Lists wrote:
Hi,
this thread is really
On Sun, Oct 5, 2008 at 2:12 AM, Matt Amos [EMAIL PROTECTED] wrote:
On Sat, Oct 4, 2008 at 9:36 AM, Florian Lohoff [EMAIL PROTECTED] wrote:
To get the ROMA database in sync again i replaced the notes by
broken-utf8 - As notes typically get not rendered thats not a problem
for me though.
On Sat, 4 Oct 2008, Henry Loenwind wrote:
BTW: SVN holds 11 patches, now.
I applied some stuff and also #1622.
Thought I'm not yet happy with it.
a) Please save keyboard configuration only if it differs from the defaults
to allow later changes.
b) Don't save automatic changes. These should
Dear plugin authors,
when you'll recompile your pligins against the latest JOSM you'll get a
number of deprecated warnings. You might be tempted to change your code
to use the new API, and usually I would ask you to do so. However, I
just noticed that I forgot to include a way to revoke the
16 matches
Mail list logo
