Skip to content

opening hours that differ in e.g. summer are not displayed in resurvey #6175

@mnalis

Description

@mnalis

(Opening a new issue as suggested in #6164 (comment))

How to Reproduce

  • open a node which has a more complex opening_hours which are due to resurvey (as e.g. node 1990156785 with valid opening_hours of Mo-Su 06:00-22:00; Jun-Sep Mo-Su 06:00-24:00; PH off). Note that having default opening_hours which are overriden in summer (as in that example) is common practice at least in summer-tourism-bound countries like Croatia (and is signed as such on the doors: having a regular opening hours sign, and then an additional sign with "override" for summer / holidays).
  • see that resurvey quest kicks-in
  • however, clicking on the quest user is presented with zeroed-out (empty) opening_hours. That is both annoying to the user (who has to engage in complex task of filling-in data from scratch) and damaging to existing data (which was likely more precise and versatile then what user will enter via SC on such resurvey).
small_Screen_Recording_20250318_051855_StreetComplete.mp4

Expected Behavior
From more preferred at the top to less preferred at the bottom:

  • ideally, I would expect the SC to parse those opening_hours, and present it for editing to user in SC-compatible format (e.g. as Oct-May Mo-Su 06:00-22:00; Jun-Sep Mo-Su 06:00-24:00; PH off in this case). That way, user could detect and correct any inaccuracies in existing UI, while the data would remain preserved.
  • if that is too complex, I would expect that SC would skip resurvey on such opening_hours that are too complex for it to handle. (i.e. do not needlessly zero-out valid existing data and ask user to re-enter it from scratch)
  • or, at the very least, to warn the user that it is about to nuke existing valid opening_hours if the user proceeds with updating them.

Versions affected
SC 60.3, Android 14

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions