Denmark Data Corrections

[awisemanapple]

Task Description

This task outlines work to improve OpenStreetMap data in Denmark based on app user feedback. We occasionally receive anonymized user feedback, often related to street names, addresses, road network issues, points of interest and other related features. After we message the talk-dk email list and get 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. We also plan on correcting any road data issues we find while working on this project.

Mapping Guidelines

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

The team will correct the data where we can identify that the feedback is valid, using the imagery and data sources specified below as needed.

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

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

Area of Focus

Throughout the country.

Tools

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

Sources

• Denmark SDFE imagery
• DigitalGlobe Standard/Premium imagery
• Bing imagery
• Mapbox imagery
• ESRI imagery
• 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 needed, the team will tag corrections with review_requested=yes so the local community can double check them.

Error Detection

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

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

Contributors

• Data Team

MapRoulette

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

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

[Hjart]

A long list of aerial imagery sources is listed here. Please note that the danish SDFE imagery is refreshed every year, photographed in the spring and usually released in late november

[Hjart]

I'll personally appreciate it much if you are aware of https://wiki.osmfoundation.org/wiki/Directed_Editing_Policy.

[awisemanapple]

@Hjart thanks for the info on the imagery, that's good to know. We are aware of that, as well as the related https://wiki.openstreetmap.org/wiki/Organized_Editing_Best_Practice

[Hjart]

Good to know, @awisemanapple . It might be worth knowing here too that I (It's practically just me) have been watching the activity in Denmark via mainly https://osm.expandable.dk almost every day for several years as well as practically singlehandedly welcoming and guiding new contributors, catching mistakes etc.

[mikini]

Hi Andrew. Thanks for reaching out to the community. Am a bit surprised that Apple is putting its resources towards improving a common good. That is not the role in which I usually perceive your company to act, to put it mildly. But of course any effort is very welcome if being played by the book.

I see by other issues in this project that a large number of regions are targeted for
your well equipped Data Team's efforts. Do you have any more documentation about the organisation of this? I'm wondering amongst others; how have the regions in focus been chosen? Based on metrics of use in and data quality? Should we expect to see contributions from a large number of members from the team across regions or have individual members been assigned specific regions? The latter would probably improve consistency of changes and effectiveness of communication.

Apart from reiterating hjart's praise of SDFE's imagery (which is the governmental data agency) as the primary source because of its quality and periodicy, I'd also like to stress that we regard the address data in Denmark as "hands off" in manual editing.
This is because all authoritarive address data has been centralized in DAR (Danmarks Adresseregister = database of Denmark's addresses) which is open data and accessible using the AWS/DAWA api. The community have been organising periodic import and updates of DAR into OSM which has been very useful. However, as I see it the current state of the import is inactive after Overpass admins this fall confronted us with some problems of the used tools affecting their service. See more and pointers in this issue on the tool repository where I dug through the undocumented procedure and identified the root and source of the issue. Unfortunately, there has been no consensus about how to proceed since and it seems like few is caring either. I personally have the wish and desire to improve and reactivate the DAWA importer but have not had the time and ressouces to do more, yet.

In hope of a prosperous collaboration,
Mikkel

[Hjart]

I'm not an Apple user myself, but I'm curious too to know what use Apple has from OpenStreetMap in Denmark. Like other danish contributors I'm a bit surprised to learn about Apple's interest in OSM.

Over the years I've been interacting with a few international teams as well as local authorities/companies trying their hand at editing OSM in Denmark, so I sort of have an idea what to expect though and I'm looking forward to it.

[awisemanapple]

Thank you for the feedback and the information about SDFE and DAR. This is very helpful.

The focus of this task is to just address OSM data issues that have been reported directly by local users and verified by our Data Team. Data corrections will only be made by specific individuals on our team who have extensive experience with OSM and the local market. In cases where additional information is needed, we will reach out to the community for further guidance and assistance.

Thank you again for your help.