Hi,
there have been many plans/concepts in the past that tried to solve
the same problems. I have lost track of the different endeavours and
what they wanted to achieve and why they didn't. I remember a talk by
David Earl about something tagging-related at a SOTM conference years
ago; I remembe
Am 16.03.2017 05:13, schrieb Tod Fitch:
It seems to me that the first and the third definitions should be
split into separate tags with the second definition deprecated.
I agree that this situation is suboptimal. The second meaning has
nothing to do with a direction but with a sense of rotation.
Hi,The second use should not be encouraged IMHO as it is redundant with the direction of the way.Reguarding the third use, you can use either traffic_signals:direction or direction but the first form will explicitly apply to the traffic_signals while the second may apply to different tags of the
Hi,
Am 2017-03-16 um 05:13 schrieb Tod Fitch:
> The “direction” tag [1] has different uses that seem disjoint to me.
> To specify the orientation (compass point or degrees from north) of an object
> (adit or cave entrance, etc.).
> To specify direction (clockwise/counterclockwise) around a round
Hello,
I just want to let you know that I have published the following proposal
https://wiki.openstreetmap.org/wiki/Talk:Wiki#Proposal_for_creating_group_ca
tegories
So if you interested in wiki documentation structure, I would be pleased if
you could read it
and comment/vote on it.
Thank y
>Thoughts?
Unified tag system (iD, JOSM) + suggestions + sharing translations +
unified metadata == imho : one of key problems, but not so easy to
solve.
Some related projects :
#1. Unified Preset Management System ( Google Summer of Code/2017/Project
Ideas )
https://wiki.openstreetmap.or
The road after this point (northwards) is closed in the winter season.
https://www.openstreetmap.org/note/917369#map=17/50.79221/15.32156
But like Petr says, its each year another time. I had the bad luck to
route through this street with maps.me because it is not tagged for
2017, OSRM seems to n
> OSRM seems to not care for the year and does not route there.
OSRM does not route you over barriers, which there is on that way:
https://www.openstreetmap.org/node/73331194#map=18/50.79082/15.32277&layers=D
It has nothing to do with way tags or conditional tags from what I can see.
Also check
On 16.03.2017 15:13, Daniel Hofmann wrote:
>> OSRM seems to not care for the year and does not route there.
>
> OSRM does not route you over barriers, which there is on that way:
>
> https://www.openstreetmap.org/node/73331194#map=18/50.79082/15.32277&layers=D
oh I forgot that I put this one the
What about using an existing solution, Wikibase[1] (of which Wikidata is an
example)? Let's call it OSMdata. Wikibase is great because it allows for
all kinds of structured data, which makes it future-proof. Some examples of
use would be:
We could add links to outside databases, for example Wikida
I believe we still need one user somewhere to update the data each year... I
suggest to have a scheduled bot which detect obsolete conditions value (based
on actual date) and automatically create a note on the map like "Obsolete
conditional access value, please update the feature" .
Otherwise a
On 16.03.2017 19:32, Topographe Fou wrote:
> I believe we still need one user somewhere to update the data each year... I
> suggest to have a scheduled bot which detect obsolete conditions value (based
> on actual date) and automatically create a note on the map like "Obsolete
> conditional acce
Idea:
access:conditional=no @ (winter)
access:conditional=no @ (snow)
note=check availability access during first trimester
...
Salut i mapes
yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
13 matches
Mail list logo
