[Poland] Reviewing osmlint-osmium and osmlint data issues

[sonyahilchik]

Background

As part of on-going work to improve the quality of OpenStreetMap data, we use internal Mapbox data validation jobs that search OSM data for errors for detecting issues related to road network data in Poland. In total, we are going to review issues in 9 categories.

Our plan is to review all detected issues and fix it in OpenStreetMap. There's a link to the OSM Wiki page.

Timeframe

We are going to start review on March 2022.

Tools

We will use existing OpenStreetMap editing tools, we will use #hashtag for the project #mapbox_linters_poland

Editor: iD or JOSM Satellite Imagery: Geoportal 2: Orthophotomap, Bing, Maxar, Esri Street Level Imagery: Mapillary, Other open sources if available

Contact Person

We welcome feedback, suggestions, and insights from local mappers. If you have questions about this work, or a specific edit by our team, please reach out to Natallia (natallia.zhouner@mapbox.com). Also you can leave a comment in a changesets.

Linter Output for Poland

As soon as we process issues, we'll update this page with json files, which will contain exact items we're going to review.

@Zetkun @abrohood @shvrm @lukasmartinelli @vladaboitsik

[matkoniecz]

Hello, welcome in Poland. Help with mapping is always welcome!

Satellite Imagery: Bing, Maxar, Esri

Edits in Poland using such aerial images are a mistake. Geoportal.gov.pl imagery is strictly superior, edits using Bing, Maxar, Esri are very unlikely to be a good idea.

EDIT: in some rare cases other aerial may be useful, local mapper mentioned that close to German border Maxar may be latest. Outdated imagery may be also useful to deciding whether something was demolished or is just poorly visible.

(mirrored from PL forum)

[matkoniecz]

Are you aware that in many places in Poland mapping data is more up to date than aerial imagery? In case of conflict between OSM data and imagery, please check history of objects and presence of note/description tags (which will be likely in Polish).

(mirrored from PL forum)

[matkoniecz]

In total, we are going to review issues in 9 categories.

Please, be specific and link full dataset of this issues in format accessible to a average mapper (display on the map, not just raw CSV/json file). Geojson uploaded to GitHub repository is likely sufficient if objects are clearly annotated. Or use one of services directly provided by Mapbox company.

(mirrored from PL forum)

[matkoniecz]

https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/resolve_linting_issues_in_Poland

using the hashtag #mbx_linters_poland

Please use #mapbox_linters_poland clearly identifying company.

(mirrored from PL forum)

[sonyahilchik]

Hi @matkoniecz ! Thank you for info about images and history, we'll get it into account. We'll share the json files, which can be opened by open source geojson.io where you can see all detections we'll get. We already changed the hashtag for clear identifying company. We always welcome feedback and suggestions!

[sonyahilchik]

Here are json files by categories, you can watch them through geojson.io Issue	Data
Crossing Highways	PL_crossinghighways.zip
Island Highways	PL_islandhighways.zip
Impossible Angle	PL_impossibleangles.zip
Impossible Oneways	PL_impossibleoneways.zip
Missing Type Restriction	PL_tr-missing_type_restriction_tr.zip
Missing Role	PL_tr-missing_role_tr.zip
Excessive Roles	PL_tr-excessive_role_tr.zip
Invalid Role	PL_tr-invalid_role_tr.zip

[matkoniecz]

Please, be specific and link full dataset of this issues in format accessible to a average mapper (display on the map, not just raw CSV/json file). Geojson uploaded to GitHub repository is likely sufficient if objects are clearly annotated. Or use one of services directly provided by Mapbox company.

In the current form average mapper cannot review it and therefore it is not possible to be really reviewed. So, this is inherently insufficient to be considered as a reviewed by Polish community.

[sonyahilchik]

@matkoniecz you can use geojson.io for looking through the issues by this way: 1) unzip archieve with json files which contains issues 2) open json file in geojson.io by 'open -> file'. by this way you will see all detections from category on a map

3) by zooming in you can watch all detections in details and use coordinates in the link of the site for moving to the osm. example:

[wzbartczak]

I am very glad that you have published this data here. However, I would like to point out that you contacted the Polish community on the forum and until today you have not responded to its comments. Remember that the forum is the most appropriate place for discussion.

[sonyahilchik]

@wzbartczak Hi! Thanks for your comment, we just now answered on the forum comments. We always welcome feedback and suggestions!