Until now, I am confused as to how to handle multiple ways referring to the same road but are separated by a bridge. In several places, I have seen so much of these ways as separate entries when searching the name of a major highway or road, many of which are because of the bridges:

Multiple ways referring to the same road

I tried merging some of those ways before but it could not be merged because of the bridges in between. Should they really be separate entries despite referring to a single road or is there a solution to merge them despite the bridge in between?

asked 20 Dec '17, 11:49

JAT86's gravatar image

JAT86
1117813
accept rate: 0%


Roads are split like this because different sections have different tags (which might not be bridges - and many tag differences won't be visible on e.g. openstreetmap.org). That's perfectly normal - data consumers such as routers will merge together as needed.

permanent link

answered 20 Dec '17, 11:54

SomeoneElse's gravatar image

SomeoneElse ♦
32.0k63330748
accept rate: 15%

2

Ok, but will this not present a problem for GIS users, especially since these separate entries have different ID numbers? The ways would appear as separate entries when filtering for a way using the road name.

(20 Dec '17, 12:07) JAT86
1

He is right though, that it can be quite confusing, when doing searches with Nominatim.

(20 Dec '17, 12:10) Hjart
3

@JAT86 Yes, but it's part of the processing that GIS users will have to do in order to work with OSM data. Another thing that they'll have to get used to is that there are no hardcoded "layers" (though people have created shapefiles based on OSM data to make things easier for GIS users).

(20 Dec '17, 12:27) SomeoneElse ♦
3

It will probably cause problems for people used to other conventions, but due to how OSM's data model works, it's kinda unavoidable. The OSM data model would not have problems that other conventions would have.

(20 Dec '17, 12:41) rorym
5

OpenStreetMap's data model is not optimised for particular third-party users. It's expected that you will post-process the data into whatever format and layout you need.

(20 Dec '17, 13:13) Richard ♦

We do use relations for waterways (like rivers), so this sounds like a good idea for multiple segments of roads too.

There will be also similar problems, especially with continuity - waterway going through the (named) lake is similar to a road going trough the named roundabout or square.

(28 Dec '17, 09:19) kocio
showing 5 of 6 show 1 more comments
-1

Impossible. Ways must be continuous in order to be merged.

permanent link

answered 29 Dec '17, 04:36

Wetitpig0's gravatar image

Wetitpig0
292151827
accept rate: 10%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×139
×58
×9
×4

question asked: 20 Dec '17, 11:49

question was seen: 912 times

last updated: 29 Dec '17, 04:36

powered by OSQA