[Tagging] How to solve the problem with relation overload?
imagic.osm at gmail.com
Tue Dec 4 10:26:09 GMT 2012
2012/12/4 Ilpo Järvinen <ilpo.jarvinen at helsinki.fi>:
> On Tue, 4 Dec 2012, Martin Vonwald wrote:
>> 2012/12/4 Erik Johansson <erjohan at gmail.com>:
>> > But then maybe the "no-right-turn" relation is too complicated as well.
>> The problem is not really the complexity of those relations, but the
>> fact that they create some kind of extreme long "relation-way". The
>> probability of two (or more) people working at the same time on a
>> 200km "relation-way" is much higher than on a 200m ordinary way and
>> therefore the conflict probability is much higher with those
> If so, it must be mainly problem with the tools handling the relation
> conflicts. If two people edit a route relation in clearly different
> places, merging the results should be automatic (similar to what e.g.,
> git does while merging code in a single file that gets edited from two
> different, non-conflicting places).
I fully agree with you. But that means changing the API (to be more
precise: the backend of it) and that's nothing that will happen until
next week ;-) Some kind of automatic conflict resolution within the
editors can only improve this situation slightly, because the editor
can't handle the resolution as an atomic action (as the API can) and
therefore while the editor is resolving the conflict and uploading
again, another change to the relation might already have happened and
the conflict-resolution-conflict-cycle begins again.
More information about the Tagging