Task Description

This task outlines work to improve map data in Barbados. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM Wiki guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Barbados.

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 Barbados.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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

Task Description

This task outlines work to improve the map data in Brunei. 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.

Improvements that will be addressed include the following:

• Correcting road connectivity and alignment issues and adding missing roads
• Improving road classification consistency according to OSM guidelines
• Correcting coastline and water features
• Adding addresses
• Adding missing buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in Brunei.

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 Brunei.

Community members zulfadli51 and raito also noted some specific areas for improvement, including Temburong district, Raja Isteri Pengiran Anak Saleha Bridge, the new Lebuhraya Jerudong – Tungku (Jerudong – Tungku Highway), Jalan Rakyat Jati Rimba highway, and Lebuhraya Telisai – Lumut (Telisai – Lumut Highway).

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 data validation guidelines such as the OSM Wiki and LearnOSM validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve OSM data in Suriname, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 Suriname.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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

Task Description

This task outlines work to improve OSM data in Belize. We first plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. After that we plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things. We also plan to update and correct major issues or vandalism of roads.

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 OSM guidelines
• Correcting coastline and water features
• Correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 the imagery and data sources specified below for mapping in the country.

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 Belize.

Local user tzsl suggested that there may be some road alignment issues, some missing roundabouts and some roads that are newer than Bing imagery.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve the road network and water features in Réunion.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM Wiki guidelines
• Adding missing roads
• Correcting road alignment issues
• Water and coastline issues
• Other one-off fixes

Mapping Guidelines

The team will use the imagery and data sources specified below for mapping in Réunion.

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.

Highways

The team will follow OSM and local policy, along with any other guidelines as appropriate.

Water

In some cases, the coastline has been mapped using old or low-resolution imagery, meaning that some features are missing or may be inaccurately mapped. We plan to use a variety of imagery sources to help map the coast geometry more accurately.

For inland water, some water features such as rivers or lakes are mapped as lines when they should also be polygons, and others are missing altogether. There are also occasionally issues with relations on water features. We also plan to correct alignment of inland water, rivers, lakes, etc., to improve geometry and adjust coastlines where inland water and coastline meet. All edits will be made using appropriate sources per those listed below.

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.

Area of Focus

Throughout Réunion.

Local OSM user arnaud_mapali confirmed that incorrect alignment and missing new roads and roundabouts were an issue.

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 Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• OpenStreetCam
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve OSM data in Panama, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes.

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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.

We have also messaged the OSM Forum for Panama and the OSM Telegram for Panama to get feedback and suggestions about the project

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

Area of Focus

Throughout Panama.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve OSM data in Ecuador, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM and local guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate. We emailed the talk-ec list for feedback and suggestions as well.

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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 Ecuador.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve OSM Data in Honduras, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes.

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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.

We have also messaged talk-hn to get feedback and suggestions about the project.

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

Area of Focus

Roads throughout Honduras.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Guinea. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global and regional policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and regional 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Guinea.

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

The team will use the imagery and data sources as available including:

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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.

Things you can do

If you'd like to help, here are a few ideas:

• Add missing road names that you know. Here is a tool to identify them
• Fix issues using OSM Inspector
• Let us know in the comments if there are areas with new construction or other issues

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Singapore. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that are intended to be addressed include the following:

• Building Road Intersections via MapRoulette
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Examples of these are provided below.

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Singapore.

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.

The team reached out to editors in Singapore, who confirmed that these were issues they would like help with, and also suggested specific places to look at. Local users confirmed that some roads are not connected, some are incorrectly classified, and in some cases are misaligned. DigitalGlobe imagery and OSM and Strava GPS traces are showing correct alignment.

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

Area of Focus

Throughout Singapore

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

• Maxar/Digital Globe Standard/Premium
• Bing
• Mapbox
• HOT task imagery
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Task Examples

Fixing Geometry and Alignment

Before

After

Before

After

Before

After

Changeset Comments

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

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 the task guidelines including the OSM Wiki and LearnOSM validation guidelines

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Grenada. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM Wiki guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Grenada.

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 Grenada.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Mauritania. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global and regional policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and regional 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Mauritania.

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

The team will use the imagery and data sources as available including:

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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

• Data Team

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

Task Description

This task outlines work to improve map data in Ghana. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that are intended to be addressed include the following:

• HOT Task 3258
• Correcting improper road classification and confirming road classification compliance to the Highway Tag Africa guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Examples of these are provided below.

Mapping Guidelines

The team will follow OSM, regional, and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Ghana.

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.

We have also messaged talk-gh to get feedback and suggestions about the project.

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

Area of Focus

Throughout Ghana.

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

• Digital Globe Standard/Premium
• Bing
• Mapbox
• HOT task imagery
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Task Examples

Here are some examples of the issues the team plans on resolving:

Fixing connectivity

• Finding and fixing overlapping ways, and unconnected junctions.

Examples of Missing connections:

Before

After

Examples of Overlapping Ways:

Before

After

Finding incorrectly classified roads & inconsistent classifications

• Roads with inconsistent classification often switch between multiple highway values along the same stretch of road.

Before

After

Alignment

• Align roads using imagery, Strava and local GPS traces.

Before

After

Changeset Comments

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

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 the task guidelines including the OSM Wiki and LearnOSM validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Nigeria. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that are intended to be addressed include the following:

• Improving road classification consistency following Highway Tag Africa and Nigeria guidelines.
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Examples of these are provided below.

Mapping Guidelines

The team will follow OSM, regional, and local policy, along with any other guidelines as appropriate. We emailed the talk-ng email list for suggestions and feedback as well.

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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below as needed for mapping in Nigeria.

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.

There are a number of small HOT tasks set up by the local community to improve the road network in various states and regions. We will work on them as well, and for the tasks which are 100% marked as done, we will work on validating. They are tasks 1355, 1358, 1370, 1371, 1420, 1421, 1422, 1433, 1438, 1450, 1451, 1454, 1482, 1511, 1725, 2247, 2572, 2636, 2692, 2768, 2861, 2995, 3229, 3326 on the HOT Tasking Manager.

The team will mostly be working on unclassified roads and up.

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

Area of Focus

Throughout Nigeria.

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

• Maxar/Digital Globe Standard/Premium
• Bing
• Mapbox
• HOT task imagery
• ESRI
• Mapillary
• KartaView (formerly OpenStreetCam)
• OpenAerialMap
• Pic4Carto
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Task Examples

Here are some examples of the issues the team plans on resolving:

Fixing connectivity and missing roads

• Finding and fixing overlapping ways, gaps, and unconnected junctions.

Missing connections

Areas with missing roads

Finding inconsistent road classifications

• Roads with inconsistent classification often switch between multiple highway values along the same stretch of road.

Road switching from residential to motorway and back

Small road tagged as secondary, should be unclassified or service

Alignment

• Align roads using imagery, Strava and local GPS traces.

Roads only visible in new Digital Globe imagery

Changeset Comments

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

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 the task guidelines including the OSM Wiki and LearnOSM validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve map data in Burkina Faso. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global and regional policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and regional 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Burkina Faso.

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.

We have also messaged talk-bf to get feedback and suggestions about the project.

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

Area of Focus

Throughout the country.
Local mapper Fofana Bagnoumana Bazo suggested Ouagadougou and Bobo-Dioulasso as places that needed some attention.

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

The team will use the imagery and data sources as available including:

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve map data in Moldova. 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.

Improvements that will be addressed include the following:

• Adding missing roads
• Correcting road connectivity and alignment issues
• Improving road classification consistency according to global and and local policy
• Correcting coastline and water features
• Adding addresses
• Adding missing buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate.

The team will use the imagery and data sources specified below for mapping in Moldova.

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 administrative boundaries, in which case we will adjust both if appropriate.

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.

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

The team will use the imagery and data sources as available including:

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

The team will apply image offsets as needed.

Changeset Comments

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

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.

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

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

Task Description

This task outlines work to improve OSM data in French Guiana, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 French Guiana.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

We have also posted MapRoulette challenges related to the road network: https://maproulette.org/admin/project/41185

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

Task Description

This task outlines work to improve OSM data in Guyana, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 Guyana.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Guinea-Bissau. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global and regional policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and regional 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Guinea-Bissau.

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.

Local user frepps said there are a lot of issues with road classification.

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

The team will use the imagery and data sources as available including:

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in Argentina, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to global and local highway classification guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate. We also emailed the talk-ar email list, OSM Forum for Argentina and the OSM Argentina Telegram for feedback and suggestions.

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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below as needed for mapping in Argentina.

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

The team will use the imagery and data sources as available including:

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

The team will apply image offsets as needed.

Changeset Comments

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

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 the validation guidelines such as the OSM Wiki and LearnOSM validation guidelines.

Things you can do

• We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Benin. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global, regional and local policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM, regional and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Benin.

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 Benin.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve map data in Jamaica. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM and local guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in the country.

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 Jamaica.

Community member lenford suggests that there are ongoing road construction areas to look at in Kingston.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Bermuda. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM Wiki guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Bermuda.

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 Bermuda.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve OSM data in Chile, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to global and local highway classification guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below as needed for mapping in Chile. We emailed the talk-cl list and the OSM Telegram for Chile as well.

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

The team will use the imagery and data sources as available including:

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

The team will apply image offsets as needed.

Changeset Comments

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

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 the validation guidelines such as the OSM Wiki and LearnOSM validation guidelines.

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

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

Task Description

This task outlines work to improve OSM data in Nicaragua, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM and local guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes.

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate. We also emailed the talk-ni list for feedback and suggestions.

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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 Nicaragua

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

(English version below)

Описание задания

В России на некоторых дорожных знаках на автомагистралях отсутствуют определенные атрибуты. Например, направление, номер дороги, номер выхода и другие атрибуты. Это может влиять на маршрутизацию. Для многих мест можно найти изображения уличного уровня от Mapillary или OpenStreetCam, отображающие дорожные знаки. Группа обработки данных в Apple работает над добавлением недостающих атрибутов, исправлением некорректно помеченных знаков, и улучшением геометрии соответствующих узлов в OpenStreetMap.

Рекомендации

Группа будет следовать рекомендациям OSM для пунктов назначения и выходов автомагистралей, а также Российским нормативным актам и другим рекомендациям, где это необходимо.

Для работы со знаками на территории России группа будет использовать изображения и источники данных, указанные ниже.

В неясных случаях группа будет использовать существующие теги и данные, используемые на данной территории. История в JOSM (ctrl-H) позволяет увидеть, какие данные были добавлены, а также комментарии, связанные с каждым изменением. История также может содержать информацию о том, посетил ли картограф данную местность или является экспертом.

Наша команда использует хэштег #adt (для Apple Data Team) для наших правок.

Области фокуса

Дорожные знаки и выходы автомагистралей на территории страны.

Инструменты и источники

Основным инструментом будет JOSM. JOSM выдает предупреждения о корректности дорожных сетей и других потенциальных проблемах, способствуя предотвращению некорректных изменений.

Будут использоваться изображения, предоставляемые Mapillary и OpenStreetCam. В силу неясностей с лицензированием, местный источник Yandex использоваться не будет.
Комментарии к изменениям

Каждое изменение будет сопровождаться комментариями в соответствием в рекомендациями OSM changeset guidelines.

Обнаружение ошибок

Отсутствие ошибок будет подтверждаться с помощью визуального осмотра, а также предупреждений JOSM (JOSM validation warnings) перед сохранением изменений.
В дополнение, группа будет пересматривать совершенную работу в соответствии с такими рекомендациями, как OSM Wiki и LearnOSM.

Разработчики

• Data Team

Чтобы получить больше информации

Свяжитесь с Andrew Wiseman

English Task Description

In Russia, there are some highway signs that are missing attributes: for example, the destination, route number, exit number and others. This can affect routing and directions. In many places, there is street-level imagery from Mapillary and OpenStreetCam that show the signs. The Apple data team is undertaking to add the missing attributes to the signs, correct mislabeled signs and improve the geometry of these junctions on OpenStreetMap. We also posted about this project on OSM Forum for Russia.

Mapping Guidelines

The team will follow OSM destination and exit guidelines, as well as Russia policy, along with any other guidelines as appropriate.

The team will use the imagery and data sources specified below for mapping the signs in Russia.

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

Highway signs and exits throughout the country.

Tools and Sources

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.

For imagery, the team will use Mapillary and OpenStreetCam. Another local source, Yandex, has unclear licensing, so it will not be used.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve the map data in Cambodia. 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.

Improvements that will be addressed include the following:

• Correcting road connectivity and alignment issues and adding missing roads
• Improving road classification consistency according to OSM guidelines
• Correcting coastline and water features
• Adding addresses
• Adding missing buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below as needed for mapping in the country.

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.

We have also messaged theOSM Forum for Cambodia to get feedback and suggestions about the project.

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

Area of Focus

Throughout Cambodia.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve map data in Togo. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global and regional policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and regional 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Togo.

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.

We have also messaged talk-tg to get feedback and suggestions about the project.

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

The team will use the imagery and data sources as available including:

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve the map data in Ukraine. There are some issues with missing roads and highway alignment in Ukraine. In many places, imagery is slightly offset from ground truth. The OSM GPS trace layer in JOSM can show the correct alignment. In addition, we plan to do some edits to other feature types if necessary, such as buildings, water, and land use and other related polygonal features.

Improvements that will be addressed include the following:

• Correcting road connectivity and alignment issues and adding missing roads
• Improving road classification consistency according to global and local highway classification guidelines
• Correcting coastline and water features
• Adding missing buildings and land use as needed
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate. We also posted about this project on the OSM Forum for Ukraine to get feedback and suggestions.

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.

The team will use the imagery and data sources specified below for mapping in Ukraine.

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

The team will use the imagery and data sources as available including:

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

The team will apply image offsets as needed.

Changeset Comments

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

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.

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Guadeloupe. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in the country.

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 Guadeloupe.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in Costa Rica, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM and local guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes.

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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.

We have also messaged talk-cr to get feedback and suggestions about the project.

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

Area of Focus

Throughout Costa Rica.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in Colombia, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM and local guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate. We also emailed the talk-co list for feedback and suggestions.

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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in Colombia.

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 Colombia.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Things you can do

If you'd like to help, here are a few ideas:

• We have posted a number of MapRoulette challenges related to issues with the road network.
• Add missing road names that you know. Here is a tool to identify them
• Fix issues using OSM Inspector -- the tagging and highway views have a lot of road network issues highlighted
• Let us know in the comments if there are areas with new construction or other issues

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve map data in Algeria. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to global, regional and local policy
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM, regional and local policy, along with any other guidelines as appropriate. We also posted on the OSM Forum for Algeria to get feedback and suggestions about this project.

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 administrative boundaries, in which case we will adjust both if appropriate

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 the imagery and data sources specified below for mapping in Algeria.

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

The team will use the imagery and data sources as available including:

• Maxar/Digital Globe Stardard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• KartView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Ferry data

Apple is releasing data on ferry terminal and line information missing from OSM in Algeria. This contribution is made available for use under the OpenStreetMap ODbL license. The data includes ferry terminals with names of ferry lines, whether the ferry is for cars, and the direction of the ferry, if applicable. We will confirm that the ferry exists and the terminal location is correct, and if missing we will add those to OSM and estimate the ferry route. Some of the ferry routes may connect to other countries. The data includes starting and ending points at ferry terminals but not the specific routes between them. When we use the data we will cite it in the OSM changeset source tag.

Changeset Comments

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

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

• Data Team

MapRoulette

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

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.](https://www.openstreetmap.org/user/LessThan3Nodes) (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Hong Kong and Macau. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that are intended to be addressed include the following:

• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Examples of these are provided below.

Mapping Guidelines

Hong Kong was originally digitized using oblique Bing imagery, which made adding geoaccurate data difficult. This was due to the high density of skyscrapers that obscured the road network. Recent imagery layers are much better (DigitalGlobe Standard, Mapbox) and when mixed with Strava show a general data offset across Hong Kong. Our main goal is to use these recent resources to align existing data, with secondary objectives listed above.

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Hong Kong and Macau.

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.

The team reached out to editors in Hong Kong, who confirmed that these were issues they'd like help with, and also suggested specific places to look at. Local users confirmed that many roads and buildings were offset as well because of Bing imagery alignment issues. DigitalGlobe imagery and OSM and Strava GPS traces are showing correct alignment.

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

Area of Focus

Throughout Hong Kong and Macau

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

• Maxar/Digital Globe Standard/Premium
• Bing
• Mapbox
• HOT task imagery
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Task Examples

Fixing Alignment

Fixing Geometry

Before

After

Before

After

Changeset Comments

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

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 the task guidelines including the OSM Wiki and LearnOSM validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in St. Vincent & the Grenadines. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in St. Vincent & the Grenadines.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Martinique. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Martinique.

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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

In collaboration with a few members of the Turkey OpenStreetMap community, we created two checks for OSM data issues, specifically buildings that intersect roads and abbreviated street names that should be spelled out.

Apple’s data team created the two checks using Atlas, a tool we developed that anyone can use to query and find potential issues in OpenStreetMap data.

After making the checks with Atlas we added them to MapRoulette as challenges with Turkish language instructions so local community members can edit them. We emailed the talk-tr email list too.

BuildingRoadIntersectionCheck challenge

For the first challenge, BuildingRoadIntersectionCheck (code here), editors should look at imagery to make sure the buildings and roads align to ground truth and edit as needed to correct the geometry. In some cases, the road may be snapped (attached) to the building, and in some cases there may just be overlap.

To work this challenge, you will need to be familiar with 3 tagging Keys.

• Highway: If one of the intersecting features is not a road/path/trail, then the highway tag needs to be removed to fix the task. (ex. highway=track on a river feature)
• Building: All buildings in flagged in this challenge should be tagged with building=yes. If one of the intersecting features is not in fact a building, then the building tag needs to be removed to fix the task. (ex. a building=yes on a farm field area)
• Covered: Sometimes roads do pass under structures in reality. Examples of this would be the canopy above a gas station or toll booth. In these cases, the section of road beneath the structure needs to be split into its own way and tagged with covered=yes. This will prevent the task from flagging again.

AbbreviatedNameCheck challenge

For the second challenge, AbbreviatedNameCheck (code here), the check found names that have abbreviations such as Cad. (or Cd.), Sok. (or Sk.) and Bul. (Blv.) where they should be expanded to Cadde, Sokak and Bulvar.

See here for more on street abbreviations.

Using MapRoulette

To use MapRoulette, log in with your OpenStreetMap username, then follow these steps.

• Click the URL for the challenge you wish to work on: BuildingRoadIntersectionCheck or AbbreviatedNameCheck
• Click 'Edit' to open the task location in JOSM or iD
• Make the edits or validate according to the task instructions
• Upload edits
• Return to MapRoulette and provide feedback about the task:
  --If you made changes, then confirm that you completed the task and click ‘I fixed it’.
  --If you couldn’t fix the issue or couldn’t see it, then click ‘Too difficult/Couldn’t see’.
  --If issue seems to be fixed already, then click ‘Already fixed’.

Turkish

OpenStreetMap'nin bazı üyeleriyle yaptığımız işbirliği ile, OSM Türkiye haritadaki verilerin kalitesini test etmek için bazı kontrol mekanizmaları oluşturduk. Bunun için yol ve binaların kesişmesi probleminin yanı sıra yol isimlerinde kullanılan kısaltmaları hedef olarak belirlendi.

Apple veri takımı bu problemleri saptamak için Atlas’ı (OpenStreetMap verilerini işlemek için oluşturulan ve paylaşılan açık kaynak kodlu bir program) kullanarak iki kontrol sistematiği oluşturdu.

Kontrol işlemlerinin sonuçları MapRoulette websitesine, kısa sürede iş bölümü yapılarak tamamlanabilecek görevler şeklinde yüklendi. Yüklenen görevlerde İngilizce’nin yanı sıra Türkçe talimatlara da yer verildi.

BuildingRoadIntersectionCheck projesi

BuildingRoadIntersectionCheck (kaynak kod) ile oluşturulan görevlerde, kullanıcılar uydu görüntüsüne bakarak yol ve binayı yeryüzündeki şekillerine göre düzenlemeliler. Bazı durumlarda yol binaya bir ya da daha fazla yerinden yapışmış olabilir. Başka durumlarda ise yol binanın içinden geçiyor olabilir.

Bu görevleri tamamlamak için aşağıdaki 3 etiketi iyi bilmek gerekiyor:

• Highway: Eğer bina ile kesişen çizgi, gerçekte bir yol değilse, bu durumda highway etiketi silinmeli ve bu nesne gerçeğe uygun şekilde etiketlenmelidir. Örneğin, highway=track etiketine sahip bir nehir.
• Building: Görevlerdeki bütün binaların building=yes etiketine sahip olması gerekiyor. Eğer kesişen alan gerçekte birbina değilse, building etiketinin silinmesi gerekir. Örneğin, building=yes etiketi yer alan bir tarım alanı.
• Covered: Bazı durumlarda yollar benzin istasyonu, gişe gibi üstü kapalı alanların içerisinde geçmektedirler. Bu durumlarda yolların kapalı alan içerisinde kalan kısmı geri kalan kısmından ayrılmalı ve bu kısma covered=yes etiketi eklenmelidir.

AbbreviatedNameCheck projesi

AbbreviatedNameCheck (kaynak kod) ile oluşturulan görevler, cadde ve sokak isimlerinde kullanılan kısaltmaları hedef alıyor. Program yol isimlerinde kullanılan Cad., Sok. ya da Bul. gibi kısaltmaları tespit ediyor. Bu kısaltmalar silinerek yerlerine tam kelimenin yazılması gerekiyor.

OSM wiki sayfasında kısaltma kullanımına dair sayfaya göz atarak bu konuda daha fazla bilgi edinebilirsiniz.

MapRoulette kullanımı

• Yukarıda bahsedilen projeler üzerinde çalışıp katkı yapmak için, MapRoulette websitesine OpenStreetMap hesabı ile giriş yapın ve ardından aşağıdaki adımları takip edin:
• Çalışmak istediğin proje için verilen bağlantıya tıkla: BuildingRoadIntersectionCheck ya da AbbreviatedNameCheck
• Karşına çıkan iş üzerinde çalışmak için Edit butonuna tıkladıktan sonra, iD ya da JOSM ile düzenleme yapmak için ilgili butona tıkla. (Edit in iD = iD ile düzenleme yap, Edit in JOSM = JOSM ile düzenleme yap, Edit in new JOSM layer = JOSM’da yeni katman üzerinden düzenleme yap, Nevermind close this = Düzenleme işleminden vazgeç)
• iD ya da JOSM üzerinde verilen talimatlar doğrultusunda gerekli düzenlemeyi yap ve ardından yaptığın değişikliği gözden geçir ve doğruluğundan emin ol. Verilen görev her zaman doğru olmayabilir. Bu durumdan değişiklik yapma.
• Eğer bir düzeltme yaptıysan, değişikleri OpenStreetMap’e yükle.
• MapRoulette sayfasına geri dönerek, yaptığın işlemle alakalı geri bildirimde bulun:
  -- Düzenleme yaptıysan, I fixed it! (Problemi çözdüm) butonuna tıkla.
  -- Düzenleme yapmadıysan, eğer verilen işin çözülmesi zor ise Too difficult/Couldn’t see (Çok zor/Göremedim) butonuna tıkla.
  -- Eğer problem çözülmüş ise, Already fixed butonuna tıkla.

Ayrıca, bu problemi doğru tespit edilmediğini düşünüyorsan, False Positive (Yanlış) butonuna tıklayabilir ve dilersen işin neden yanlış tespit edildiğine dair fikirlerini butonun üzerindeki kutuya yorum olarak yazabilirsin. Aynı zamanda iş üzerinde çalışmak istemiyorsan Skip butonuna basarak bir sonraki işe atlayabilirsin.

Task Description

This task outlines work to improve OSM data in Aruba, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes.

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 Aruba.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

Many Humanitarian OpenStreetMap Team (HOT) Tasks are underway around the world and the Data Team will be working on some of them, mapping the features specified on each tasks' Description and Instructions tabs.

The team will use the HOT Tasking Manager to direct their efforts.

Mapping Guidelines

The team plans on using each task's particular instructions as well as any applicable regional or country specific guidelines such as Highway Tag Africa, if working on a task that involves mapping of roads. We also emailed the talk-africa email list for suggestions and feedback.

The team also plans on using the imagery specified as the correct one to use for that particular task. Often this will be DigitalGlobe, ESRI World or Bing; in some cases Mapbox or other custom imagery available for use in that task. The team will properly note imagery used and include important task information.

The team will apply image offsets if specified in the HOT Tasking Manager or provided by local community members in that region.

Lastly, OpenStreetMap offers a number of QA/QC tools for validating map data. In addition to these, our team will reach out to local community users in order to validate and provide feedback on our work.

Area of Focus

HOT task areas depending on the projects.

Tools

The team will use JOSM for completing these tasks. JOSM has built-in validation warnings for road networks and other possible issues that are important to prevent improper changes.

The team will use the HOT Tasking Manager to find particular tasks to work on.

Sources

The team will use sources as specified in the task. This will generally be one of the following:

• DigitalGlobe
• Bing
• Mapbox
• ESRI World
• Other imagery as specified for certain HOT tasks

Task Instructions

The team will follow the Description and Instructions defined in each specific task. The team will also use the JOSM validation warnings to identify other errors or warnings in the data, and fix as necessary.

Changeset Comments

The team will use the default changeset comments suggested by the HOT Tasking Manager as well as provide additional information that describes what was done in that particular changeset.

Error Detection

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

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

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in Venezuela, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to OSM and local guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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.

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.

The team will use the imagery and data sources specified below for mapping in the country.

We have also messaged talk-ve to get feedback and suggestions about the project.

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

Area of Focus

Throughout Venezuela.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in Curaçao, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 Curaçao.

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 Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• OpenStreetCam
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Trinidad & Tobago. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Improving road classification consistency according to OSM guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in Trinidad & Tobago.

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

Roads throughout the country.
Local user SRASC says there is a lot of highway construction in the southern part of 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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Uruguay based on app user feedback. We occasionally receive anonymous user feedback, often related to street names, addresses, road network issues, points of interest and other related features. After messaging the talk-uy list and getting feedback and suggestions for this project, we plan to correct the data where we can identify that the feedback is valid, using other sources as appropriate listed below.

In addition, we plan to correct other data, such as the road network, coastlines and inland water, and land use -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to global and local highway classification guidelines
• Adding missing roads
• Correcting road alignment issues
• Correcting coastline and water features
• Adding or correcting buildings and land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and Uruguay 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in Uruguay.

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.

Where needed, the team will add review_requested=yes to edits, which was suggested by a the local community.

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

• Maxar/DigitalGlobe Standard/Premium imagery
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• OpenStreetCam
• Pic4Carto
• 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 sources are unclear, the team will tag corrections with review_requested=yes so the local community can double check them, as was suggested on the talk-uy listserve.

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

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve map data in Belarus. We plan to update and correct water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things. We also plan to continue road network improvements.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to local and OSM guidelines
• Improving road classification consistency according to global and local policy
• Adding missing roads
• Correcting and updating water features
• Adding or correcting land use
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate. We also posted on the OSM Forum for Belarus to get feedback and suggestions.

For water features, 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 water features 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.

The team will use the imagery and data sources specified below for mapping in Belarus.

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

The team will use the imagery and data sources as available including:

• Maxar/DigitalGlobe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if available
• Mapillary
• OpenStreetCam
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces
• OpenAerialMap around Minsk (as noted by @Komzpa )

The team will apply image offsets as needed.

Changeset Comments

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

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.

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve map data in Democratic Republic of Congo. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that are intended to be addressed include the following:

• Improving road classification consistency according to OSM, regional and local guidelines
• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to local and OSM guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Examples of these are provided below.

Mapping Guidelines

The team will follow OSM, regional, and local 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 administrative boundaries, in which case we will adjust both if appropriate
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 the imagery and data sources specified below for mapping in DRC.

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 Democratic Republic of the Congo

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

• Maxar/Digital Globe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• HOT task imagery, if any
• Mapillary
• KartaView (formerly OpenStreetCam)
• OpenAerialMap
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Task Examples

Here are some examples of the issues the team plans on resolving:

Fixing connectivity

Finding and fixing overlapping ways, and unconnected junctions.

Examples of Missing connections:

Examples of Overlapping Ways:

Finding "islands" of incorrectly classified roads & inconsistent classifications

“Island” roads are groups of over-classified roads that do not match the classification pattern of surrounding roads or local guidelines. These typically are the result of adding small towns without viewing other data in the surrounding area.

Roads with inconsistent classification often switch between multiple highway values along the same stretch of road.

Adding missing roads

Adding, connecting and aligning missing roads.

Alignment

Align roads using imagery, Strava and local GPS traces.

Before

After

Changeset Comments

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

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 the task guidelines including the OSM Wiki and LearnOSM validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

The Caribbean was hit by a number of disasters recently, with multiple hurricanes in the West Indies. There were a number of humanitarian mapping projects there in response and Apple's data team will be working to clean up the data in collaboration with the Humanitarian OpenStreetMap Team (HOT).

Improvements that will be addressed include the following:

• Correcting road connectivity issues
• Improving road classification consistency according to global highway classification guidelines and local guidelines if available
• Adding missing roads
• Correcting road alignment issues
• Correcting buildings that overlap or are attached to roads
• Correcting duplicate roads
• Topological fixes
• Other one-off fixes

Mapping Guidelines

The team will work with the community in the affected regions and will follow applicable OSM guidelines as appropriate.

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

Team will work to improve data in some of the affected regions throughout the Caribbean.

Tools

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

Sources

The team will use the imagery and data sources as available including:

• DigitalGlobe Standard/Premium
• Bing imagery
• Mapbox imagery
• ESRI imagery
• Imagery from respective HOT projects
• Mapillary
• OpenStreetCam
• Pic4Carto
• Telenav's MissingRoads plugin and ImproveOSM
• Strava and OSM GPS traces

The team will apply image offsets as needed.

Changeset Comments

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

Error Detection

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

Contributors

• Data Team

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in Guatemala, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes.

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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.

We have also messaged OSM Guatemala Telegram to get feedback and suggestions about the project.

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

Area of Focus

Throughout Guatemala.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

How can you help

We have posted a number of MapRoulette challenges related to issues with the road network.

Contributors

• Data Team

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

Task Description

This task outlines work to improve map data in Iran. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to OSM and local guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local policy, along with any other guidelines as appropriate.

The team will use the imagery and data sources specified below as needed for mapping in the country.

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 administrative boundaries, in which case we will adjust both if appropriate.

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.

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.

We have also messaged the OSM Forum for Iran to get feedback and suggestions about the project.

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

Area of Focus

Throughout Iran.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki

Task Description

This task outlines work to improve OSM data in El Salvador, such as the road network, coastlines and inland water, and land use and land cover polygons -- remove duplicates, correct geometry, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Correcting road connectivity issues and network issues such as missing roads and alignment according to OSM guidelines
• Correcting coastline and water features
• Correcting land use polygons where needed, such as removing duplicates, correcting the boundaries, fixing incorrect tags and other issues. These are features like airports, national parks, forests, colleges and universities, and so on
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below for mapping in the country.

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 El Salvador.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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

Task Description

This task outlines work to improve the road network in Pakistan. We plan to work on improving the road network, such as adding missing roads, fixing network issues such as missing connections or crossing roads, and other related issues. We also plan to update and correct coastline and water features as we find them, and correct and improve land use and land cover polygons where needed, such as airports, national parks, forests, colleges and universities, and so on -- remove duplicates, correct the boundaries, fix incorrect tags and other similar things.

Improvements that will be addressed include the following:

• Adding missing roads
• Correcting road connectivity issues
• Improving road classification consistency according to OSM and local guidelines
• Correcting coastline and water features
• Adding or correcting land use polygons
• Other one-off fixes

Mapping Guidelines

The team will follow OSM and local 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 administrative boundaries, in which case we will adjust both if appropriate.

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 the imagery and data sources specified below as needed for mapping in the country.

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 Pakistan.

A local community member suggested looking at Lahore, Gwadar, and the China-Pakistan Economic Corridor.

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

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

The team will apply image offsets as needed.

Changeset Comments

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

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 validation guidelines

Contributors

• Data Team

MapRoulette

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

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. (https://www.openstreetmap.org/user/LessThan3Nodes)
All of our leads can be reached via email.

OSM Wiki