OvertureMaps / OvertureMaps/schema

[Transportation] OSM junction=roundabout missing access restrictions

Open
#349 2 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

documentation theme - transportation 🛣
Dominant language
Python
Stars
213
Forks
22
Avg merge
3d 3h
Merged PRs (30d)
31

Description

Hi,

I’m encountering a problem with access restrictions for roundabouts. In OSM, roundabouts often don’t have the attribute oneway=yes, which means they are frequently missing access restrictions in OvertureMaps. This causes routing issues, as routes are currently being generated against the intended direction of roundabouts.

Here is an example:

Overture: https://explore.overturemaps.org/#19.31/47.7533986/8.852229/0/16 (ID: 08a1f816532d7fff0474b28f72791a22)
OSM: https://www.openstreetmap.org/way/1032682701

In OSM, roads within a roundabout typically have the tag junction=roundabout. Would it be possible to either include this junction information in the Overture data, or to automatically generate access restrictions based on that tag?
Alternatively, is there currently any way to identify that a segment belongs to a roundabout in Overture?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.