EDEKA

488 entries in OSM, not matched in ATP data

563 entries in the ATP data, not matched in OSM

14 potential duplicates in OSM

24 matched entries across a big distance

4736 tag differences

Not matched in OSM
Potential duplicate in OSM
Not matched in ATP data

Entries in OSM, not matched in ATP data

There are many reasons why an object in OSM might not be found in the ATP data:

  • OSM is outdated. The place has closed permanently or changed operators.
  • The place in the ATP data has bad coordinates and is too far away to be matched.
  • The place has newly opened. The ATP data doesn’t have it, yet.
  • It’s a duplicate in OSM.

Please investigate the situation.

  • Look at the OSM object history.
  • Try to find third party information such as newspaper articles or social media posts.

Based on that fix it in the OSM data if possible:

  • If the place has closed permanently, mark it as disused:
  • Add the official website for this individual place
  • Fix all the duplicates first
  • Ignore it and do nothing
  • Leave a note in OSM if investigation on the ground is needed

Entries in the ATP data, not matched in OSM

These are entries on the official website which cannot be matched to an object in OSM. This might happen because of several reasons:

  • A new branch was opened in reality, but has not yet been mapped in OSM.
  • A branch was closed, but is still listed on the website.
  • The object exists in OSM but has a wrong name, or is not tagged with the brand attributes.
  • The coordinates in the ATP data are bad and too far away from the OSM object.

Please investigate the situation.

  • Look at the OSM object history, if it exists.
  • Try to find third party information such as newspaper articles or social media posts.

Based on that fix it in the OSM data if possible:

  • Add it to OSM if it’s not mapped, yet
  • Correct the tagging
  • Add the store-specific website
  • If in doubt ignore it and do nothing
  • Leave a note in OSM if investigation on the ground is needed

Potential duplicates in OSM

Two objects in OSM are potential duplicates if they are too close together. OSM has a rule of One feature, one OSM element. This means that one real-world entity such as a shop should be represented by only one object in OSM.

Please review the OSM objects histories, aerial images, street level images and so on to decide if this really is a duplicate and needs to be fixed in OSM, or if two separate entities of the brand exist close-by. Typical situations are:

  • There’s a way for the building which is also tagged with the POI tags, but there’s an additional node for the POI inside the building.
  • There are simply two nodes for the same thing.
  • There might be nodes at the entrances to the same thing. In this case it’s better to map the outline as way and add nodes with entrance=* at the entrances.

Matched entries across a big distance

These entries are matched based on the website, but there’s a big distance between the OSM and the ATP location.

Often this is caused by bad coordinates in the ATP data, in which case you can ignore this.

Sometimes it happens that the OSM object has the wrong website URL.

If the OSM object points to the generic website, change it to point to the specific website instead.

Tag differences

This section lists tagging differences between OSM and All The Places. If the OSM side is missing the brand, opening hours or website information you can copy and paste it.

If there are other tag differences, please don’t feel compelled to adopt ATP’s tags.