Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Improvements in Syria #155

Open
awisemanapple opened this issue Nov 18, 2019 · 0 comments
Open

Data Improvements in Syria #155

awisemanapple opened this issue Nov 18, 2019 · 0 comments

Comments

@awisemanapple
Copy link
Collaborator

awisemanapple commented Nov 18, 2019

Task Description

This task outlines work to improve map data in Syria. We plan to focus on improvements to the road network first, and later we may do some edits to other feature types if necessary, such as buildings, addresses, water, and land use and other related polygonal features. We will message the local community and get feedback and suggestions for this project.

We plan to do some improvements such as the following:

  • Correcting road connectivity issues and network issues such as missing roads and alignment according to local and OSM guidelines
  • Correcting coastline and water features
  • Adding addresses
  • Adding missing buildings and land use
  • Other one-off fixes

Mapping Guidelines

For roads, the team will follow OSM and local highway policy, along with any other guidelines as appropriate.

For water and coastlines, the team will follow OSM coastline guidelines, waterways policy such as water and natural=water and local policy along with any other policy as appropriate.

Some coastlines are connected to lower level subnational administrative boundaries. In that case we will adjust the boundary with the coastline. These are not country boundaries, but things like place, district and county.

Where we see them, we will remove the source=PGS tag, which was from an earlier coastline import that needs to be cleaned up. We received a message on the India coastlines project requesting this, and it is commonly done in other coastline improvement edits.

The team will use imagery and data sources below as needed. When in doubt, the team will use the existing tags and data which are used locally. The history in JOSM (ctrl-H) identifies what previous mappers added and their notes and/or explanations regarding changes made. This history can also show if a previous mapper has visited that area or has expert knowledge or sources.

Our team uses the hashtag #adt (for Apple Data Team) for our edits.

Area of Focus

Throughout the country

Tools

The team will use JOSM for completing the task. JOSM has validation warnings for road networks and other possible issues that are important to prevent improper changes.

Sources

  • DigitalGlobe/Maxar Standard and Premium imagery
  • Bing imagery
  • Mapbox imagery
  • ESRI imagery
  • Mapillary
  • OpenStreetCam
  • Pic4Carto
  • HOT Task Imagery, if available
  • Telenav's MissingRoads plugin and ImproveOSM
  • Strava and OSM GPS traces
  • OpenAerialMap

The team will apply image offsets as needed.

Changeset Comments

The team will provide changeset comments that are in compliance with OSM changeset guidelines.

Where needed, the team will tag corrections with review_requested=yes so the local community can double check them.

Error Detection

The team will check for errors visually and using JOSM validation warnings prior to committing the changeset.

In addition, the team will review its work in accordance with validation guidelines such as the OSM Wiki and LearnOSM.

Contributors

MapRoulette

We have also posted MapRoulette challenges related to the road network: https://maproulette.org/browse/projects/41146

For more information

Our community lead is Teddy Ahlvin and our editing leads are Jon Westlake and Erica Olson.
To get in touch with Teddy, you can email or contact him via OSM.

All of our leads can be reached via email.

OSM Wiki

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant