-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable all layers / see what's not completed on hidden layers #5261
Comments
"The old way" still exists, it's the top of the list choice on the overlay selection list ("Geen" in Dutch, above "Straatverlichting"). Doesn't that work for you? |
I guess additionally the quests for the overlays have been disabled by default, so you would need to enable them again if that is your preferred method of answering. |
Additionally what has been said by @rhhsm (you can just enable all the quests in the settings): In general, I think StreetComplete is not the right choice to "map all the things, at once": It is not very efficient with this app. And I dare say, not very efficient in general. I think EveryDoor is designed to be more like that, at least for POIs. Because, if you wanted to add all the things at once, you could just use Vespucci - but as it turns out, for being on the go, it's all a bit too involved, so less things get done in that app. StreetComplete rather encourages convenient additions on the side, here and there. This goal directly conflicts with wanting to add all the information at once, at least with overlays, which specifically show only one aspect at a time. As I wrote, an overlay that showed all the overlays at once... well, that would be Vespucci or any other editor that just shows and lets you edit everything. |
Okay, but I really don't think it's all that outlandish to work on, say, lighting and path surfaces at the same time. I guess what I'm trying to say is the layer are "too distinct" from one another. I really think it's not that weird to have the option to enable several layers, or maybe just 2 at most, at the same time. And let me be clear: I'm not out to map EVERYTHING, just to map everything StreetComplete offers to map, within my profile of enabled quests. Btw, I don't get the reference to Vespucci; it's all the way on the far end of the spectrum. You can't even compare it StreetComplete, imo. It's like comparing the SATA specification with trying to cat a file in the terminal. |
Right, I absolutely get it. I catch myself switching between overlays often when there are no quests nearby, too. But, showing several overlays at once... I can really not imagine how that could work. The colors for the overlays are completely different, so one will not end up with an understandable coloring. Also, it's one more tap to select which overlay one actually wants to edit after selecting an element. A really nice solution would be an overlay that combines several overlays without making the interface (too) complex. But that's a challenge. We do not even have a desktop editor yet that displays and lets you edit for example the street layout (lanes / width, bus lanes, cycleway, sidewalk, ....more) in a nice UI yet. For mobile, it is even more difficult. In general, I think for visualization on the map of such combined overlays, more advanced (WYSIWYG) visualizations are necessary first which are neither available with the tangram-es library nor (as far as I know) maplibre. ... I guess, when there were no limitations on what could be rendered on the map, there'd be many more opportunities to make the interface and display even better. For example something like a building overlay could display building type via color, height+roof height+roof shape directly on the map itself plus their numerical values labelled on the site when selected. When editing, the map just zooms in to and focuses that particular building while the user gets some slim controls to edit these values in-line. But, well, that's all rather unicorny. |
Yeah, I too unfortunately do not see an easy way to do it...
But if someone sees how such multiple-overlays-at-once UI could be accomplished (with less effort then writing new app from scratch) and would make detailed explanation / mockup screenshots of how it would look like, they could open a GitHub discussion about that; I would certainly be interested in participating. But as it is, I can only see perhaps some very specific very related overlays being extended / merged (e.g. |
Afore we start designing complex UI, let me propose a simple alternative: opt out of the layer functionality. I understand a LOT of work went into developing this, and I don't mean any disrespect. It's just not for me, for my style of mapping. I would much rather be slightly overwhelmed with quests, then run the risk of missing a huge number of them because they are obscured away (to me) on layers that are not currently visible. I understand that there's a valid use case for layers, like "Today I'm going to map all lighting-related quests" or "Today I'm going to map only surface types" or what have you. But as said before, that's not always a luxury one can afford to work with. If you're in a cool area just for a bit, cool enough that you feel passionate about having it mapped & tagged properly on OSM, wouldn't you rather be able to be presented all the things in a single view? I'd be more than happy if this wasn't the default (and it isn't), but a way to see everything that's on layers just like normal quests pointers (like from before layers existed) would be perfectly good for me. I was happy with the app back then, and I imagine many other people were, too. Not everyone, but surely more than a few. (edit: reason I'm living up this issue again, is because I see more layers have got added, and quests pointers get disabled because of them - and I would greatly appreciate if this issue could be reopened, for it is not actually resolved) |
you can do it (almost?) entirely by enabling quests disabled by default for example if you want to keep seeing building quest, you can reenable it |
I read that you prefer Quest-based StreetComplete to Overlay-based StreetComplete - I do too!
But I am not sure I understand you here:
|
For what it matters, I also not a fan of this idea and hope that they can stay disabled-by-default but available. |
Okay, fine. |
Indeed, I am under this impression. Is it not correct? It's hard to tell when quests are being removed, as it doesn't usually stand out. Especially after not having used the app for a while. However, I feel the app should respect custom profiles, and modifications to the default profile, by not retroactively disabling quests in existing installs, but this does seem to be happening. I could be mistaken.
The goal is to see all the things that can be done in a given area. Whatever the means is to get to that goal, is up for grabs. Whether it be showing all quests as pointers on map, showing a layer that combines all other layers, or showing stuff from currently inactive layers somehow. I'm just letting you guys know what my usecase is, and what my personal preference would be to fulfill that usecase. Maybe the title of this issue prematurely contains a suggested solution, which I now realise was wrong of me to do. |
Which quest do you think has been removed? All overlay-related quests still exist.
I recommend checking the changelog, e.g. 57.0 mentions that crossing quest has been split (implying old quest has been removed)
The app can only know that you want a quest enabled/disabled when you actively enable/disable it (then changing the default already has no effect as far as I know).
This is simply impossible. Showing all overlays will clash for usually obvious reasons, and even if it worked the result would be too confusing for the target audience of SC. |
As far as I know, it is indeed not correct. Quest just get disabled in default profile, and you can re-enable them yourself in
I feel the same! But unless I am wrong, SC does already respect custom (i.e. non-Default) profiles (i.e. the ones that you created via
hmmm, well, I think modifications
Thanks @thany, it is much clearer now! What you seem to prefer is using only simpler Many users do (myself included). There is no blockage for you continuing to use only
Thanks for clarification, and no worries! ❤️ There is nothing wrong in suggesting possible solutions (although, of course, such proposed solutions are sometimes unfeasible for various reasons, as it happened to be the case here). It was just confusing to some people as its original wording seemed to imply that you have considered and rejected just using Footnotes
|
So in short, the It does make me wonder how an update deals with modifications made to the |
Use case
Say I want to map all quests in a smallish area. Maybe I'm visiting for just one or two days. I would currently have to remember to switch layers around to see if I haven't missed anything.
Proposed Solution
Add an option to enable all layers, or to somehow point out things on hidden layers that still need to be mapped.
Honestly I prefer the old way, where there weren't any layers to be had, but every quest was just a pin on the map that I can tap to fill out. I guess the majority user base has overruled me regarding this preference.
The text was updated successfully, but these errors were encountered: