Should the CoMaps editor automatically update check_date?

General talk
,
1

The CoMaps mobile app has an included editor. There is currently a pull request that would change the behavior of the editor: Every time a POI is edited, the check_date would be updated automatically.

Please read the discussion in the pull request as there are already several arguments in favor and against the suggested behavior. It boils down to the question how likely it is that a CoMaps user would edit POIs that they have not surveyed recently.

I’d be interested in your opinion (here or in the PR discussion).

3 Likes
CoMaps: OSM-related feature updates
2

As an example for easier understanding, if there is a POI with tags:

shop=convenience
name=SomeShop
opening_hours=Mo-Fr 08:00-17:00
check_date:opening_hours=2025-07-01
check_date=2025-12-25

and the CoMaps user clicks Edit and changes opening_hours to be Mo-Sa 08:00-16:00, the suggestion is to also update:

  • check_date:opening_hours=2026-01-21 (i.e. today, because we know the new opening hours was obtained)
  • check_date=2026-01-21 (also today, because we infer that since opening_hours has been updated, the shop also still exists, so the timestamp when the shop existence was checked should also be updated)

But if the user doesn’t edit opening_hours but only e.g. add website=https://someshop.example.com, then the CoMaps would update:

  • check_date=2026-01-21 (today, because we infer that since website has been updated with new data, the shop itself also still exists, so the timestamp when the shop existence was checked should also be updated)
  • but check_date:opening_hours would NOT be updated (i.e. it would be left at its original value), as that information was not verified by that edit.
8 Likes