-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
in map display access restrictions - fully restricted ways and barriers like fences and walls #199
Comments
It seems that currently Cinnabar from https://mapzen.com/products/maps/ is the currently used basemap. And it would mean that https://mapzen.com/documentation/tangram/tutorials/editing-basemaps/ is potentially useful. |
Makes sense
Am 8. Mai 2017 08:44:49 MESZ schrieb Mateusz Konieczny <[email protected]>:
…One may end not reaching quest because chosen route is blocked by
access restriction/barriers like fences.
It is a bit irritating to end in such situation and discover that
obstacle was mapped in OSM.
Would it be considered preferable to use map style that marks roads
unavailable for foot travel and marks barrier=fence/wall, and
potentially also other obstacles that make reaching to the destination
impossible?
from #198 I understand that iff somebody forks current map style or
makes new one from scratch it may be potentially used so I want to
check whatever such canges would be considered as desirable
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#199
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
|
https://github.com/westnordost/StreetComplete/blob/604f6b02f797f8aafedeb0649d29da514501ab08/app/src/main/assets/cinnabar-style-7.0.0.yaml is location of the currently used style. https://github.com/tangrams/cinnabar-style is repository of this style with showcase at http://tangrams.github.io/cinnabar-style/. I am a bit confused by relation of code in these locations, StreetComplete is using version 7.0.0 while https://github.com/tangrams/cinnabar-style/commits/gh-pages has only version 0.12. Is it a correct guess that if one would use the same formatting of version number then street complete would be using v0.7 and current would be v0.12? |
In addition I opened issue at tangrams/cinnabar-style#26 ("show major barriers like barrier=fence or barrier=wall") to check whatever PR that adds showing wall/fences would be welcomed upstream |
See https://github.com/tangrams/cinnabar-style/releases Though, in danger to repeat myself: If there will be a custom style for street complete, it should start from a basic template, not one of these "house styles". |
What you mean by "house styles"? Focusing too much on buildings? Developed as showcase by company? Or something else? |
Updating cinnabar style will add fences - see tangrams/cinnabar-style@7d905d4 |
|
Developed as showcase by the company |
For now I opened also tangrams/cinnabar-style#32 |
fixes part of streetcomplete#199
fixes part of streetcomplete#199
fixes part of streetcomplete#199
One may end not reaching quest because chosen route is blocked by access restriction/barriers like fences.
It is a bit irritating to end in such situation and discover that obstacle was mapped in OSM.
Would it be considered preferable to use map style that marks roads unavailable for foot travel and marks barrier=fence/wall, and potentially also other obstacles that make reaching to the destination impossible?
from #198 I understand that iff somebody forks current map style or makes new one from scratch it may be potentially used so I want to check whatever such canges would be considered as desirable
The text was updated successfully, but these errors were encountered: