[OSM-dev] Duplicated nodes in Potlatch

Rogier Wolff R.E.Wolff at BitWizard.nl
Sun Oct 5 12:56:00 BST 2008

On Sun, Oct 05, 2008 at 01:40:53PM +0200, Marc Schütz wrote:
> 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.89487&lon=10.88733&zoom=17&layers=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?
> >
> > It's not expressly forbidden to have a way comprising 865234
> > occurrences of the same node in succession, though I agree it's not
> > desirable, so strictly it's not a bug.

IMHO, there is one decision to be made: 

- this is allowed, applications/editors are free to not submit
duplicate nodes in succession.

- this is undesirable, applications/editors should be the ones that
filter this out. If the current potlatch didn't filter correctly we'll
have to fix potlatch. However, on first examination potlatch seems ok.

- This is undesirable, applications might not submit them, but if
they do the API code should filter it out anyway.

I'd vote for 3. But then I'm not intimate with the whole system, so 
feel free to ignore me.

Number two has the disadvantage of slowly poisoning the database. 

Number one has the disadvantage of allowing the database to grow
bigger than it needs to be.


** R.E.Wolff at BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

More information about the dev mailing list