does not check for associatedStreet relation

[skyper]

FixAddress does not check for associatedStreet relation (did not test Street relation).

Please, have the plugin check these relations before adding duplicate data.

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2013-01-04 02:32:00
Last Changed Author: Don-vip
Revision: 5662
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2013-01-04 01:49:12 +0100 (Fri, 04 Jan 2013)
Last Changed Rev: 5662

Identification: JOSM/1.5 (5662 de)
Memory Usage: 158 MB / 643 MB (34 MB allocated, but free)
Java version: 1.6.0_24, Sun Microsystems Inc., OpenJDK 64-Bit Server VM
Operating system: Linux
Dataset consistency test: No problems found

Plugin: FixAddresses (28807)

[OliverW]

It did this check in earlier times, but there was a quite significant protest by the community. Personally I preferred relations due to data integrity reasons, but most people did not share this view and reuquest me to remove this feature under the flag of "user simplicity".

[Don-vip]

Well, things have changed. associatedStreet has become very popular now with 94.000 occurences and cannot be simply ignored :)

[skyper]

Replying to OliverW:

It did this check in earlier times, but there was a quite significant protest by the community. Personally I preferred relations due to data integrity reasons, but most people did not share this view and reuquest me to remove this feature under the flag of "user simplicity".

And now the user does not care and even does not get any information about these relations. Sorry, but this seems to be ignorant and leads to duplicate if not contradicting data.

I wonder, that you got that deeply influenced to remove it completely without any option to turn it on.

Well as time did pass, "associatedStreet" and "Street" relations got more and more popular and I kindly ask you to reimplement the relation support.

Thanks

[OliverW]

You do not need to convince me :)

It was just a frustrating experience and I would like to avoid it a second time. But ok, I can reimplement it. What do you think about the Option to convert a tagged street into a Street with a relation? This could reduce the amount of redundant data dramatically.

[skyper]

Replying to OliverW:

It was just a frustrating experience and I would like to avoid it a second time. But ok, I can reimplement it.

You gonna have some supporter this time, but I do not really know the user of this plugin.
I did already post my opinion above.

What do you think about the Option to convert a tagged street into a Street with a relation? This could reduce the amount of redundant data dramatically.

Wow, this would be 180° turn and would open up the plugin for more users. Right now, I either simply select the relations and look for houses/addresses which are not member (highlighted) or use some filter.

A plugin which checks and makes conversion/inclusion to a relation and fixing possible in one step would be a nice enhancement. Lately there was some code added to core to sort these relations and to guess the right role. Maybe this plugin could use some of it.

[skyper]

Any news or opinions ?

[OliverW]

Nope, sorry

[OliverW]

Could you provide me some coordinates where I can find streets using a relation? Currently I have some time to have a look at it... thanks in advance!

[skyper]

For associatedStreet relations, please, have a look at this ​City. Especially the southern and western neighbourhoods contain a lot. If you are only looking for some use this ​link.

Thanks in advance.

[OliverW]

Relations should now be recognized correctly - please test ([o29969])