MapFactor Forum

I have tested the build in google search. really nice, it works. "Internetsuche" in German version.
But some OSM Users making the house numbers in OSM, and some house numbers in OSM are better than Google data, because some Google house numbers are wrong and some google POIs are wrong. For example know google not the difference between Kirchweg and Kirchstraße and moved a POI from the Kirchstraße to the Kirchweg in DE 09212.
When no mobile internet available, it should with the osm data only work.

Thats great. I have tested it in Limbach-Oberfrohna with the new germany_east_osm. Thats a new feature, i know that it was not possible. I am very happy about.

The Boundary-Problem seems solved in Limbach-Oberfrohna, but someone added a questionable boundary again. I will see what happens with this strange Post code boundary by the next update, because the postcode-area of Limbach-Oberfrohna is now twice, one is redundant.

I guess, the streetnames should be a relation, because mapfactor list every single part of a longer street. In the new map import the full street was on top, that´s really better than before.

Hi lagiraudiere,
can you give me an example (way/relation ID)? There is unfinished conversion script for interpolated houses (mainly in Argentina), but what you mean is maybe something different?
thanks
   Martin

...and as far as I know "associatedstreet" is still proposed in OSM-Wiki.

http://wiki.openstreetmap.org/wiki/Relation:associatedStreet

@blubb in the page http://wiki.openstreetmap.org/wiki/Key:addr
you can read in the addr:street key entry : "The belonging to a street can alternatively be represented by a associatedStreet relation"

@mdx
"streetRelation" has nothing to do with "interpolated houses"
You can set an "interpolated houses" when you don't want to create every addresses in the street.
The streetRelation allows you to attach the address to the street. Then, you can correct the name once for every street-segments and every addresses since the name used is the relation name.

the relation :
http://www.openstreetmap.org/browse/relation/3075617

Country : France
Town : Oullins
here is a map where you can see the affected nodes :
http://tools.geofabrik.de/osmi/?view=addresses&lon=4.80512&lat=45.71387&zoom=16&overlays=no_addr_street

NB : the addresses are imported from the cadastre (land register) of the city

@lagiraudiere
"you can read in the addr:street key entry : "The belonging to a street
can alternatively be represented by a associatedStreet relation"

Yes, that's right but I mean: There is no information that addr:street and addr:housenumber is "the old style" and outdated.
If this is "the old style" then there is much work to do.

@hurdygurdyman
http://wiki.openstreetmap.org/wiki/Relation:associatedStreet
where do you see "Status:Proposed" or "draft" ?!

@lagiraudiere
I tried to find out Informations about a proposal for "associatedStreet" and couldn't find any. So I have no idea, how this scheme has been accepted "officially" in OSM.
But anyway: it exists and is in use. And so we got that unlucky situation of two solutions for one problem, which is a sad situation for using and interpreting the OSM-database.
So MapFactor has to decide how to handle that. Further discussions about the usage of
"associatedStreet" or "addr:street" should been conduced toward success in OSM-forums etc.

@mdx
yes : the only difference seems to be the value of the type tag. However the "street" relation support the "address" role for its members  while "associatedStreet" doesn't.

Thank you, Martin.