|
If streets are made of many small pieces, you have to zoom in deep to see the name of the street. This is not ideal for screen or for printing a map. Is it allowed to chain such roads together (provided the rest of the properties are the same)? I would like to 'fix' this for my village. Thanks |
|
Looking at this example in Potlatch 2: http://www.openstreetmap.org/edit#map=19/52.07832/4.67350 it does look like there's some scope for merging. These ways were imported from AND. Here are the full set of tags on these three sections: http://www.openstreetmap.org/browse/way/7420687 http://www.openstreetmap.org/browse/way/7420579 http://www.openstreetmap.org/browse/way/7420684 The left-hand and middle ones differ only in the " The right hand one can't be merged however - it's the member of a bicycle route relation. Further east there's a bridge that also can't be merged into the same way. The second part of this is "even when there do need to be separate ways (such as for the bridge), wouldn't it be nice if rendering software could display only one name for a road if it doesn't change across several sections?" Unfortunately, I don't know of any rendering software that does do that with OSM data - perhaps someone else does? 1
Thanks SomeoneElse! I will be careful not to break these things like bridges and routes (i use these routes for cycling myself) The wiki says about the AND_nosr_r that I may feel free to remove it: http://wiki.openstreetmap.org/wiki/Key:AND_nosr_r
(15 Aug '13, 14:19)
pitdicker
3
Please please do double check relation memberships. Erroneous merges where a relation is involved are one of the two most common mapping errors I encounter.
(15 Aug '13, 20:26)
Richard ♦
To clarify: Due to all the issues it may be an option to just leave the ways splitted. It could be that they would need to be split again in the future (e.g. to add different surface values). Of course newly mapped streets should be created with way segments as long as possible and practical.
(15 Aug '13, 21:27)
aseerel4c26 ♦
|
|
I would say "no" as the answer to this problem (regardless of other factors involved already discussed). It occurs frequently on streets of the brazilian cities, because people's names tend to be very long here (lots of surnames and middle names). The appearance (or "disappearance") of the name of a feature (or of the whole object in some cases) depending on the zoom level is something related to the tile generation server's parameters, and not related to the data per se. If you have your own tile server (or you are allowed to customize parameters on some server that you can use), you can change what shows on each zoom level, and also choose font size, placement, color, etc. Remember that OSM is about the data and not the map, although I consider the map display very important to increase usage/awareness of OSM. |
Could you provide a link to an example? As you mention, the key is "provided the rest of the properties are the same". Depending on what you're looking at to view the data (e.g. an editor) you may not see all the properties.
The browse page will however show all the properties, including relation memberships:
http://www.openstreetmap.org/browse/way/156410284
Any reason to have many small pieces ? You can merge them if they have the same attributs. Otherwise, it is a rendering issue. One could tell you to create a relation but it should not be necessary here.
For example: Biezen, Boskoop, Netherlands http://www.openstreetmap.org/#map=16/52.0776/4.6734