open-data icon indicating copy to clipboard operation
open-data copied to clipboard

Morocco | Data Improvements

Open marjanvandekauter-tomtom opened this issue 3 years ago • 2 comments

Project description

Goal

To improve the map quality in Morocco, we propose to make data improvements by sharing challenges, and when appropriate, fixing data errors, and adding or editing certain kinds of geometry.

How to participate

Anyone is welcome to contribute to this project by participating in our MapRoulette challenges. Here is the extended documentation for using MR. Note that sometimes additional instructions are provided within the challenges.

Challenges

Quality check challenges

Click to expand.

Ways with tag highway=* must be connected to the rest of the road network to ensure its continuity, e.g. for route planning. When such a way is not connected to another way with tag highway=*, an error is logged.

The area=yes tag is required for some closed ways when used to define a polygon. For closed ways with other tags, there is an assumption that the way defines an area. In some circumstances, a closed way may define both a closed polyline and an area. When tag area=yes is used, it is expected that one of the necessary accompanying tags is also found.

In general, roads intended for vehicles should be built to maintain proper angles which ensure maneuvers and fluent traffic. Extreme, too sharp angles applied to a way may indicate errors in the road geometry.

The necessary edits will be made to fix cases where the tag on a way indicates that the object is a polygon feature, but the way does not meet the definition of a closed way because it is self-intersecting, or ways in a relation with the same role form a self-intersecting polygon

Simple areas are mapped in OSM by creating a closed way and tagging it as an area object rather than a line. Relations of the type multipolygon are used to represent complex areas with holes inside or consisting of multiple disjoint areas. A multipolygon relation can have any number of ways in the role outer (the outline) and any number of ways in the role inner (the holes), and these must form valid rings to build a multipolygon. When a relation of the type multipolygon consists of only one member, which is a simple area, an error is logged.

Buildings with extremely sharp angles will be identified and corrected if needed.

Features intended to be a polygon should be correctly tagged. When the tag indicates that the object should be a polygon, but the geometry is built out of a NON-closed way, an error is logged.

Identify and fix, if needed, cases where a way with tag highway=* intersects with a building.

Identify and fix, if needed, situations where a water feature intersects with a building.

Identify and fix, if needed, situations where a building intersects with another building at the same layer.

Identify and fix if needed, cases where highway junctions are incorrectly or imprecisely mapped.

Identify and fix cases where highways intersect without a common node.

Check area features of different types (various land use, natural, amenity and leisure features) that are smaller than expected for areas of these types. You may need to correct an area’s tagging, adjust its outline, or merge it with other areas.

Validate and fix objects without tags. Objects without tags are undesirable in OpenStreetMap and should be either fixed by adding missing attributes or removed in case of duplicated or not existing objects.

Identify and fix cases where two or more highways are connected to the same node on a roundabout. 

Geometry challenges

Click to expand.

Data analysis done by TomTom suggests that there should be a road or track here in OSM, but it is missing.

Identify and connect if needed cases where the end of the way with tag highway=* is not connected to the rest of the road network.

Taking Manager

Click to expand.

There are two objectives of this project: Mapping missing roads: Identify and add missing roads along with accurate tags that consist of road types and other attributes. Mapping missing buildings: Locate and add missing buildings that could be residential, commercial, or other structures.

Edits based on User Feedback

We will make improvements to OSM based on user feedback submitted for the TomTom map after comparing and ensuring that it is also valid for OSM.

Here is a list of the types of edits to be made, provided they do not conflict with others’ edits and a local source is available:

  • Highways

    • Adding highways
    • Realigning highways
    • Adding or adjusting bridges, tunnels, layers, or relations
    • Updating lanes
    • Updating traffic signs
  • Addresses

    • Adding or correcting addresses
    • Updating the position of address nodes, usually when an object has multiple addresses
    • Adding or correcting names of ways
  • POIs (Points of Interest)

    • Adding POIs
    • Correcting POI locations
    • Adding or correcting POI information
    • Resolving POI-land use discrepancies
    • Handling POI closures
  • Land Use

    • Adding land use
    • Modifying existing land use extent
    • Adjusting building shape
  • Buildings

    • Adding buildings
    • Updating building type
    • Adjusting building shape
  • Water

    • Adding or realigning rivers, streams, and lakes.

Missing Buildings

Click to expand.

Missing buildings were detected after a spatial comparison with TomTom's map database. The tasks in this challenge focus on physical structures such as residential, commercial, and industrial buildings.

Geographical scope

Data improvements will be made across the whole country.

Announcements

This project was announced in:

TomTom organised editing

We will follow the Organised Editing Guidelines for this project. TomTom will not make any edits until two weeks after the project announcement. Here is our Organised Editing page, including a list of our editors.

How to find TomTom's edits

All edits made by our team have the hashtag #tt or #tomtom.

Sources for editing

  • Esri World Imagery
  • Bing Maps Aerial

For some OSM map edits TomTom editors will use proprietary sources for support. These will typically be in situations where there is not sufficient evidence using the available sources in OSM editors themselves. The proprietary sources will be ground-level imagery and GPS traces, both collected by TomTom's mobile mapping vans. On occasion, we will also use sources collected from a field survey by one of TomTom's sourcing specialists who have visited the location and collected data to support the required map updates.

How to reach out

If you have remarks about a specific edit of ours, please drop a comment in the changeset, and we will do our best to respond thoughtfully. Or, you can also:

https://donate.openstreetmap.org 😄

ghost avatar Feb 13 '23 07:02 ghost

The 'Sources for editing' section updated with the below information-

  1. Removed Maxar Premium Imagery from the list as it's not available anymore in OSM
  2. Added a description of proprietary sources to support editing

kiranahiretomtom avatar Oct 20 '23 07:10 kiranahiretomtom