Enable lighting-related quests during daylight; at least optionally

[pigsonthewing]

Please revert the change which made several lighting-related quests only show during hours of darkness; or at least make it possible for a user to override that change in their settings.

It is often possible to tell that, for example, a path through a park or countryside is not it, by the complete absence of lighting posts or other infrastructure. Likewise simple bus stops with no lamp.

Similarly, in built up areas the presence of maintained lighting posts, even in daylight, shows that the way is lit.

[westnordost]

It will not be reverted.

For many ways, especially those ways that are near or alongside streets that are lit, it is not possible to say with certainty whether the street lighting reaches to these well. Because quests in StreetComplete should be easily answerable, they are now only shown after sundown.

Likewise simple bus stops with no lamp.

There may be a street lantern right at it or near it. To judge whether the bus stop is thus lit can only be ascertained with certainty when the lights are actually on.

[pigsonthewing]

It will not be reverted.

Then, as requested, please make it user-configurable.

For many ways, especially those ways that are near or alongside streets that are lit, it is not possible to say with certainty whether the street lighting reaches to these well.

And for many ways it is possible to see that there is no street lighting anywhere in the vicinity.

Likewise simple bus stops with no lamp.

There may be a street lantern right at it or near it. To judge whether the bus stop is thus lit can only be ascertained with certainty when the lights are actually on.

I referred to cases where there is no lamp. The lights cannot be on if they do not exist.

[mnalis]

I acknowledge that both variants (always showing a lit, and only showing it during the night) have their own disadvantages. And I understand that for average StreetComplete user the new behaviour is likely better in majority of cases.

But I still miss the ability to mark forest paths (with no infrastructure anywhere) as unlit. Anyway, I'd also prefer if it was "only show during night" by default, but the users had the option to override it in the menu. But I also do understand the need (for StreetComplete especially!) to keep UI as simple as possible.

For reference, see original discussion in #1285

[davidpnewton]

So you want people to hang round in dark forests after dark do you? Alternatively you want people to tag things that they are not physically near at the time of tagging.

Since you seem determined to keep the unwarranted removal of functionality which turning the lit quests off during the day entails, then one of those two general points must be true. One conflicts with app user safety. The other conflicts with the philosophy stated for the app.

My own solution? Tag according to streetlight placement seen during the day whilst I am nowhere near the location in question. So that's in line with your possible want two: encouraging people to tag things they are not physically near at the time of tagging.

Aren't the results of silly removals of functionality great!

[mnalis]

I must say @davidpnewton does have a point, this does seem to promote non-onsite mapping and/or discourages outside-the-town lit status mapping.

Is there some solution that might work?

• add a preference to choose if such limiting of quest (perhaps global preference, or per-quest settings like in @Helium314 fork? maybe only show if "expert mode" checkbox is on - "StreetComplete for experienced mappers" #3003 / Expert Mode: Allow to edit tags directly #471 so no extra complexity would be shown for "simple" default users) . That is more work, but would fix several other issues too (and changes made in expert mode could have extra tag in changeset to differentiate them)
• modify lit quest so it asks for lit status always if the highway=path or highway=track with surface != asphalt (or other paved surfaces - indicating the path is probably not in the city).
  Alternatively use day/night filter for it only if highway =~ motorway|trunk|primary|secondary|tertiary|residential
• modify lit quest so it is always asked, but user can only answer yes if it is nighttime (that would remove false positives, while still allowing users to answer quest for forest paths without infrastructure)
• have two lit quests, one always shown, and one only on night, so users can enable what they want in their preset (with night-only quest being the one selected by default)
• make a separate lit quests for urban areas (only active during night) and separate lit quest for unpaved forest paths (available always)
• or at least do not add source=survey to changeset tags if user is more than 300m from GPS location (or GPS location is unknown). That wouldn't discourage offsite mapping, but would at least (in a reasonable way) drop the pretense that SC is being used only for on-site mapping. (also related: Ability to use satellite images #3137 (comment), Do not incorrectly add "source=survey" tag to changesets #298)
  Alternatively: never add source=survey on lit quest changesets
• if the intention was indeed "to make collecting data more efficient, not to prevent an incorrect data", perhaps enabling lit quests always, but putting them at the bottom of priority list would be sufficent replacement (as users will answer them only when there is nothing else to do)
• revert lit quest to be asked always
• something else?

[matkoniecz]

So you want people to hang round in dark forests after dark do you?

If you live in unsafe area and that is dangerous in your area or for you, please do not do this. As reminder, on the first opening app asks to not do dangerous stuff just to map.

So that's in line with your possible want two: encouraging people to tag things they are not physically near at the time of tagging.

No. Note that if you start doing this app will ask you to do doing this.

Aren't the results of silly removals of functionality great!

This quest was quite confusing in day time, in multiple cases people were entering wrong data

then one of those two general points must be true

This misses several possibilities. Also, if I would not be on mobile I would insert image of xkcd with spacebar heating.

[mnalis]

This one https://xkcd.com/1172/ ? xkcd reference is always nice, but I do not think that users wanting to map "no lights in forest paths via SC" is really such a horrible idea. (actually, user having to change the system clock to workaround it seems like much worse workflow idea to me.)

[Helium314]

So you want people to hang round in dark forests after dark do you?

I suspect whatever dark forest you mean might be tagged quite unusual if StreetComplete asks whether the ways there are lit.

[mnalis]

I suspect whatever dark forest you mean might be tagged quite unusual if StreetComplete asks whether the ways there are lit.

@Helium314 what do you mean? I can easily see highway=track+surface=compacted (or highway=path) going through natural=wood (or landuse=forest) area and being marked with lit=yes or lit=no. What is so unusual about it?

[Strubbl]

I really do not like that the lit question is only shown during night. And i cannot change this, in my opinion stupid, default behavior of the app? I am thinking how to work around this during day or i am not going to answer this question at all anymore.

For many places answering questions only during night or day would mean visiting the same place multiple times. Often i do not have the chance to do so. And often i do not want to do that during night. There are reasons.

There may be a street lantern right at it or near it. To judge whether the bus stop is thus lit can only be ascertained with certainty when the lights are actually on.

How shall i measure the luminous intensity? And what is the treshold value to put a lit=yes or lit=no?

edit:
so far i decided to put a lit=yes or no based on the existence of street lamps. So if the street next to the bus stop has street lights, the question whether the bus stop is lit, is answered with yes. What special cases else are we going to try to map here?

[westnordost]

Hm so you think that limiting the quest to only after sundown was wrong altogether and should be reverted?

We can talk about that, but please first take the time to read through #1285 (and linked) where it was discussed.

[Strubbl]

Hm so you think that limiting the quest to only after sundown was wrong altogether and should be reverted?

From my point of view, yes, we could save these lines of code. But that is only my preference. There is always somebody who has arguments for or against that behavior of the app. It would be nice, if the user can decide here. And of course the current state (v34.1) can be the default state.

So i read the other thread. I am answering here.

The argument with creating a profile for day/night was already mentioned and i second this. This solution is far better than some automagic. @mnalis comment in #1285 (comment) has a lot of good arguments.

There was an argument:

In some cases check during the night is necessary to check whatever cycleway/footway next to the road is also lit

This is a special case. If i cannot reliably answer the lit quest, i can decide by myself to not answer it and let somebody (maybe myself) check it during night. Yes, sometimes this means i have to skip a lot of lit quests.

My intention was to make collecting data more efficient, not to prevent an incorrect data.

It is not efficient in the case, that i can reliably answer this quest during day where i am sure ways are lit/not lit and keep the quest open for ways i am not sure. Those i can efficiently survey during night, because the obvious ones are answered already.

[peternewman]

I've just realised, don't we need to disable the speed quest during the daytime too now (or at least for residential roads)? In the UK at least it asks (and tags) if the road is lit in some circumstances as that affects the speed limit. If we're saying we can't be trusted to tag it directly in the daytime, that should be the case for indirect tagging too.

FWIW like @mnalis I've had many paths through woods and fields where I'm asked if they're lit, and sometimes one major one has lamp posts and other minor ones don't, so I can't now answer those quests sensibly, and I'm unlikely to be in most of those areas in the dark. I'm also encountering areas that are lit during the daytime (i.e. 24/7) which I can't tag as such, I still don't understand how someone at night will know that status (or be expected to remember both), so they're probably getting miss-tagged (although part of that is down to a tagging scheme that includes two states you can't observe at the same time in the same tag, rather than say lit:daytime=yes, lit:nighttime=yes).

[arrival-spring]

I've just realised, don't we need to disable the speed quest during the daytime too now (or at least for residential roads)? In the UK at least it asks (and tags) if the road is lit in some circumstances as that affects the speed limit. If we're saying we can't be trusted to tag it directly in the daytime, that should be the case for indirect tagging too.

I believe that the speed limit is affected by the presence (or not) of street lighting, and not whether or not the lighting is in use (although it almost always will be).

Perhaps the followup question could be reworded and it only adds lit=noand not lit=yes even if there are street lights.

[westnordost]

I am thinking about completely reverting this feature. Via the feedback function from within the app, I now got several requests to remove that feature again. I can also follow the arguments that whether anywhere are lanterns or not is visible during day as well.

After all, everyone can now with quest profiles create a day and a night-profile.

[matkoniecz]

Main problem is that in showing SC to other people there were multiple cases where people made opposite mistake - they failed to notice existing lanterns.

Variants included:

• steps lit by high lantern quite far away
• light that was positioned at low level (placed about 40cm or 1m from ground)
• footway lit by street lights quite far away

And general confusion "how I am supposed to know which version is correct"?

Would it be maybe solvable by adding one more quest (disabled by default) that would ask about lit status also during day?

[mnalis]

Having two quests lit (night only) and lit (always ask) with just the first one enabled by default would work for me, @matkoniecz. From cleanliness point of view, it does look like the kludge, however.

Perhaps per-quest configure button (like in @Helium314 fork) would look cleaner (and could also be used for other problematic quests in the future)? (those two were my favourites, although I did suggest few other workarounds around most glaring issues at #3248 (comment))

Failing that, @westnordost idea of falling back to previous always-show-lit-quest behaviour does look like the lesser of two evils.

[smichel17]

From cleanliness point of view, it does look like the kludge, however

From my point of view, it looks a little like subquests

[matkoniecz]

Perhaps per-quest configure button

That is going to be way more complex to implement and maintain (at least I think so)

[mnalis]

Perhaps per-quest configure button
That is going to be way more complex to implement and maintain (at least I think so)

Perhaps, but (to my untrained eye) current proof-of-concept implementation does not look that bad - see for example Helium314@e256a94 or Helium314@a60a389.

(Of course only the few quests that do require possible configuration get that configure icon, as can be seen in that fork)

[Helium314]

a) I know someone who really dislikes adding more settings and made that very clear
b) The way these settings are implemented in my fork mixes android-specific stuff into the quest code. This will not be accepted in SC, and fixing/adjusting this will likely be more work.
c) My fork has the option of disabling the daytime filter (affects all quests that use it) instead of using the per-quest settings, Helium314@965a942

[timothywashere]

I think for main roads the quest should be allowed in the day time, since the local authority has an obligation to repair any that are faulty and you can easily see in the daytime.
For bus stops and footpaths that run alongside roads, it should be disabled in the day time because it's too tempting to guess from the location of streetlights and may be incorrect.
For informal paths, paths through forests, it should be possible to say no, but trying to say yes would result in a warning asking them to make sure the path is lit at night and not just that there are lamps present.

[smichel17]

As a compromise, what if answering the Lit quest during the daytime shows a confirmation dialog?

It would work similar to answering a quest too far from your current location, where after the first time you'd have the option to turn it off for that session. That way, it's possible to answer the Lit quest during the daytime, but maybe annoying enough that you'll reconsider whether it's a good idea :P

Extra bonus: it advertises that the quest exists. I normally map during the daytime, and I'd completely forgotten about the lit quest until I took a screenshot a few minutes ago.

One downside to this approach: we'd need to turn the priority of the Lit quest down below any others that operate on the same nodes, because we wouldn't want to force people to answer (or hide) Lit during the day just to get to the other quests that they can answer. Ideally we'd give the quest a different priority depending on the time of day (probably implemented as two quests, as discussed above).

[westnordost]

It is an interesting idea. I thought about this but reached to the conclusion that this is not a good solution.

The reason why the lit quest has issues during daytime is because for some/many ways, it is really difficult to answer if a particular segment of way can be considered lit. So, during daytime, sometimes the "🐿️ Easy answer" rule does not apply.

Adding a confirmation dialog does not solve this problem, instead it just makes contributing this information during daytime more pesky for all lit quests, even those for which a clear and easy answer is possible.

[westnordost]

Alright, so I reverted the disablement of certain quests during daytime. When it was implemented, we had

• no quest presets. So, no possibility to e.g. create a "night jog" preset. This changed.
• quests were ordered by "importance" rather than how easy and quick they can be solved. So, I think it was a problem that a lit quest one wasn't able to answer blocked other quests. Now, I moved the lit quests down in the default quest order so everything else is asked first.

I played with the idea to default-disable the quest with an explanation message like "Sometimes it is hard to ascertain during daytime whether a particular section of path is lit. Consider to only enable this quest when the lights are on."
However, I don't remember the lit quests to be that problematic. It is an option for the future though, in case the lit quest turns out to be still somewhat problematic in this way.

[westnordost]

Alternative would have been, by the way, that "show quest only during nighttime" setting would only have the effect that during day, the quest is considered as "disabled by default". So the user can in the settings enable this quest type manually. So during night, the quest would be enabled and during day, the user can manually enable it after acknowledging an explanation message.

But this is somewhat of a incomprehensible magic behavior. Then rather unconditionally disable the quest by default, see my last post.

[RubenKelevra]

Well, I can see both sides. I guess we just need a more specific quest which does use an additional tag.

Sometimes said street lights are extremely bright and sometimes areas are barely lit between two street lamps.

This cannot be surveyed at day time.

If we add an additional quest for the quality of the illumination, a user might spot the very dark spots and answer them with either very poorly lit or unlit.

There's the tag "lit:perceived" which offers exactly this.

[mnalis]

@RubenKelevra yes, lit:perceived quest, if implemented, would be a great candidate for (likely disabled-by-default as not to overload regular SC users?) night-only quest (and it could be used to override answer from lit all-day quest if needed, thus alleviating outlined potential problems with precision of "daytime mappers of lit quest").

Judging by it's wiki it looks only mildly subjective, and has about 1800 uses so far, so perhaps it might be an option.

[RubenKelevra]

@RubenKelevra yes, lit:perceived quest, if implemented, would be a great candidate for (likely disabled-by-default as not to overload regular SC users?) night-only quest (and it could be used to override answer from lit all-day quest if needed, thus alleviating outlined potential problems with precision of "daytime mappers of lit quest").

I don't think we overload regular users. Never heard that complaint from anyone... its more a disappointment when someone cannot solve something, like 'oh I can't even possibly see the roof of that building clearly' and then proceeds to wander around with a long neck awkwardly around the house 😂

So I usually disable those building quests for new users. Especially the house type quest is kind of confusing.

So as long as the quest is solvable 99% of the time by easy observation without any explanation from me, it's well designed IMHO. This would be the case for a perceived lit one - nice graphics presupposed. But @westnordost never failed to deliver on that :)

Judging by it's wiki it looks only mildly subjective, and has about 1800 uses so far, so perhaps it might be an option.

Well, I think it's pretty good actually. Except that colorless tag.

It is oddly placed in a tag which only covers the amount of light. A fixture might spend very poor amounts of yellow light, or a huge amount. This tag is completely misplaced IMHO since you cannot tag both.

It assumes that yellow light is always perfect, which is not the case.

I think this should maybe moved to some other subtag, like "lit:type" or something like that.

This tag was proposed but never made it through quality control:

https://wiki.openstreetmap.org/wiki/Proposed_features/Key:lit:type

---

tldr: just create a perception tag quest (but exclude the colorless value).

[smichel17]

Especially the house type quest is kind of confusing.

Perhaps you could create a new discussion around how to improve it? Building type is currently necessary in order to unlock the address quest.

[mnalis]

• @RubenKelevra As for the lit:perceived, due to some amount of overlap, it might even be preferred to merge it into lit quest, in a way that during the day quest is asked as before (just basic answers yes/no/...), but during the night extra answers appear (for filling in lit:perceived data) so more detailed answers can be provided. (Perhaps extra detailed answers should also be shown during the day, but grayed-out/disabled, for giving users indication they could be answering more here).

  I'm not too keen about proposed lit:type (nor even more ultra-detailed https://wiki.openstreetmap.org/wiki/Proposed_features/Key:light_source with its sets of tags). lit:perceived would add just enough information IMHO, even if it does not distinguish between all possible lighting types - that non-detailedness is IMHO what makes it easily solvable. Especially since all artificial lightning is sub-ideal (ie. having much worse CRI than during daylight), making a fuss about cold-white LED vs. halogen vs. xenon is hopeless. I'd even separate llt:perceived=colorless into Other answers instead of being offered in main choice picker.

• As for the mentioned house type quest, also note that it was suggested that House Address quest should be solvable even without solving type of the building first, if it's priority was changed (or building type quest disabled). It was being considered, but is currently waiting for more input/experience and/or implementation of Layers - see Give priority to address (housenumber) quest #2464 (comment) and below.

[RubenKelevra]

• @RubenKelevra As for the lit:perceived, due to some amount of overlap, it might even be preferred to merge it into lit quest, in a way that during the day quest is asked as before (just basic answers yes/no/...), but during the night extra answers appear (for filling in lit:perceived data) so more detailed answers can be provided. (Perhaps extra detailed answers should also be shown during the day, but grayed-out/disabled, for giving users indication they could be answering more here).

Well, I would keep them separate.

• "Are there street lamps?"

• "How (well) lit is this way at night?"

And if the answers are for example 'yes' and 'none/minimal' we could show a popup asking if the lights are broken or not existing for example.

I'm not too keen about proposed lit:type (nor even more ultra-detailed https://wiki.openstreetmap.org/wiki/Proposed_features/Key:light_source with its sets of tags). lit:perceived would add just enough information IMHO, even if it does not distinguish between all possible lighting types - that non-detailedness is IMHO what makes it easily solvable. Especially since all artificial lightning is sub-ideal (ie. having much worse CRI than during daylight), making a fuss about cold-white LED vs. halogen vs. xenon is hopeless. I'd even separate llt:perceived=colorless into Other answers instead of being offered in main choice picker.

Colorless just doesn't fit well and is barely even used. I would avoid implementing it and move on. 🤷‍♂️

Maybe even start a discussion on the wiki page to see if others think the same (for example the author(s)) or users who used the tag before.

• As for the mentioned house type quest, also note that it was suggested that House Address quest should be solvable even without solving type of the building first, if it's priority was changed (or building type quest disabled). It was being considered, but is currently waiting for more input/experience and/or implementation of Layers - see Give priority to address (housenumber) quest #2464 (comment) and below.

Well it feels just too tedious to decide between detached house, house, apartment etc.

I feel we need just need to put in a value instead, which flags the building as inhabited: residential. Everything else is quite difficult to observe sometimes.

Additionally it would be nice to have the information about additional uses of the building, like retail or a amenity etc in the floor level.

So maybe make it multiple choice, like "people are living there" and it has a shop in it and make building=residential; retail out of it or something like that.

This would open the possibility to create quests for missing shop nodes for example, since we now have the information that there should be a shop in a building.

[smichel17]

@RubenKelevra I like the direction of your ideas, but can you please post them in a new discussion or issue?

This conversation is going to get lost here, in a closed issue about the lit quest.

[matkoniecz]

Well, I would keep them separate.

"Are there street lamps?"

"How (well) lit is this way at night?"

Note that we would need an established or accepted tagging for that.

This would open the possibility to create quests for missing shop nodes for example, since we now have the information that there should be a shop in a building.

building=retail may not house shop anymore (repurposed, abandoned, under reconstruction)...

See #3398

[RubenKelevra]

Well, I would keep them separate.
"Are there street lamps?"
"How (well) lit is this way at night?"

Note that we would need an established or accepted tagging for that.

We have. Street lamps along the street are lit=yes, while how well the way is lit at night is lit:perceived=*.

This would open the possibility to create quests for missing shop nodes for example, since we now have the information that there should be a shop in a building.

building=retail may not house shop anymore (repurposed, abandoned, under reconstruction)...

True, but that would still be worth a shop node IMHO, with either shop=vacant or disused:shop=yes.

[westnordost]

1800 usages worldwide, no proposal, status unspecified is hardly established tagging, not even with a lot of goodwill.
Plus, if this was a proposal, I doubt it would be accepted.

[RubenKelevra]

@westnordost is there an alternative?

[westnordost]

I don't think so.

[Bubu]

I just wanted to share a slightly different opinion here, which I don't think has been mentioned before:

I quite liked these quests being only being enabled at night, it gave you something new to do at different times of the day and in that made StreetComplete being played as a game, instead of being used as a tool to fill OSM, more engaging. (Which means I got quite a few people to play that have had no interaction with openstreetmap mapping whatsoever before. "Let's go back to this area at night, to discover new quests" really works quite well for the discovery and adventure aspect of it :))

Just wanted to throw this in here. This doesn't mean that reverting this isn't the right call to make for now.

[TurnrDev]

Hi, long time no speak. I wrote the day/night stuff, and whilst it's sad to see it gone, I agree that it's just not needed now we have quest presets. I do think there should be better tagging of lit:perceived=* but someone needs to write up a proposal for that first. Dibs not me. Keep up the good work @westnordost and @matkoniecz