Putting appart this 'man' vs 'human' debate...This reminds me a thinking I regularly have in minds: OSM shall have a way to tell all (registered) data users that "starting from /mm/dd following major change in the database will be applied following vote xxx from OSM community. Please see
then why not using addr:interpolation=no to state that the hyphen in addr:housenumber does not define a range ? I think everyone would be happy and it will not break current tagging schema. QA tools would raise a warning if there is an hyphen and no addr:interpolation tag. Default rule might be
I totally agree. Soren and all others members don't disserve such comment. OSM is a project where everyone can submit its point of view and ask for voting. Even if some think they own the truth.Having said that I think the main topic has not been adressed. For me contact is a namespace. I would
Oups, wrong key, 32 use of landuse=mixed, sorry. LeTopographeFou
And what about something like:Landuse=mixed (0 use in taginfo)Landuse:orchard=yesLanduse:meadow=yes I would prefer that compared to secondary_landuse as it is
Look at this recent page:https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dsatellite_dishNote that this tag is 'in use' and has few usage. You can make/revive a proposal in order to approve it (together with man_made=communication(s)_dish?)
For me, if none of those tags would already exist, I would say that toll is an infrastructure and shall be put where the toll is (booths, gates, automatic systems...) whereas fee is an attribute which denote that this amenity/road/ferry is not free to use.But as of today both are used, so I
Oups sorry, it was not your discussion on plateau/mesa, I mixed those
discussions, my bad...
Whatever I still think summarizing a proposal would help for all those major
geological features :)
LeTopographeFou
Message original
De: letopographe...@gmail.com
Envoyé: 19 avril
Warin,
Now you start having some main feedbacks (see plateau/mesa/...), may I suggest
you write a global proposal for missing geological features? In fact it is what
you are doing in the mailing list but without formalism. But too many emails
with too many threads to be able to follow and
The signage should make the tag, not the opposite. I think it is one of the main rule here. Otherwise there will always be interpretations and personnal feelings.Access=adherents is a non-sens. You don't have to be a customer to enter a shop (you may become one, but only after you entered), same
Hi,
Personnaly I already use amenity=* for the whole plot/complex when it's clear
it is not limited to a building. This apply to schools, hospitals and places of
worship (not exhaustive list) in my way of tagging. I believe this is how
schools and hospitals are suggested to be mapped and see
I disagree with the fact that making things even more complex (with adding an "all_lane" ) will help to solve when there is already a well known use of lane schema. Imagine cases where bicycles lanes are between two same direction lanes (it sometimes happens with a turn right lane. There the
In absolute yes but be carefull: Some editors (like StreetComplete since some
weeks or iD) might push one or the other schema without the user knowing which
one is used in the background and sometimes without rationale why this one and
not the other one on editor side (they implement ONE, they
Agree on the purpose of Wikidata but many OSM features (such as buildings) does not have a Wikidata item (only major buildings have one, usually landmarks).I would rather say that as soon as an OSM item has a Wikidata attribute then a QA tool may suggest to move some other attributes in Wikidata
Hi Emanuel,
I would first consider to put them under its Wikidata page (if any) with
property P166. Personally I would not take time to enter awards on OSM but
would link the OSM item to a Wikidata item and fill the Wikidata item with this
kind of property.
Moreover looking on Taginfo I can't
Hi,Wiki suggests amenity=recycling + recycling:drugs=yes/nohttps://wiki.openstreetmap.org/wiki/Tag:amenity%3DrecyclingIf we choose to put it under 'waste' (instead of recycling) then I suggest to copy the recycling namespace schema and use waste:drugs= yes/no (or something similar) instead of
Personnaly I don't think I would map umbrella organisations... I would put
operator and operator:wikidata and let Wikidata update partnerships between
associations. It is not a property of the kindergarten, it is a property of the
operator.
LeTopographeFou
Message original
De:
I don't see as many issues in your exemple... If École or Musée is part of the name, I don't see why we shall invent a truncated name. It's not because the type is part of the name that we shall remove it.Let's take a more famous example: 'Arc de Triomphe' is the name of a landmark in Paris but
Hi Leif,I would rather consider the ability to store a "GTFS API link" (or something similar) in transport relations. As soon as its stops are well referenced, then an app will have everything it needs with nearly no need from users to update them (and ability to automatically detect missing or
Hi,
Your intent is to simplify but I don't understand how replacing one tag by
three or more with different syntaxes key/value according to the type of
transportation and their introduction in OSM can make things easier.
I share your view when you say that two schemas is too much to maintain
I'm not aware of other toll systems but official country references are tagged
using the prefix ref:XX where XX is the country code. Note that HU represent
the country and hu the language (see ISO codes). So your prefix would be ref:HU.
LeTopographeFou
Message original
De:
Hi John,
Based on what you said I would tag this area as a farmyard (because it produces
things) inside a probably bigger (because of parking, buildings...) regular
theme park which contains everything else (visitor center, toilets, parking,
shop...).
LeTopographeFou
Message original
De:
RoadsguyOn Thu, Mar 30, 2017 at 9:05 AM, Topographe Fou <letopographe...@gmail.com> wrote: In your case I would probably also consider to add something like colour=green/yellow/... on the
In your case I would probably also consider to add something like colour=green/yellow/... on the detour relation.LeTopographeFou
It's a different topic: speed, height... Mainly apply to a way whereas stops
mainly (always ?) apply to a node.
Speeds can still be tagged on the way and the sign put appart from the road,
mainly for rendering purpose because the way it applies to is already tagged
with the consequence (the
Hi,
I put stops, give ways and traffic light where the car has to stop/yield which
can be far from the position of the sign (for instance in the US where the
light is after the junction, thus may not be crossed if you turn). Also on
narrow junction you may have the lights at the junction but
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
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
For your interest and according to Taginfo:
access:lanes > 4269 use
access:lanes:both_ways > 726 use
access:lanes:both_ways=no > 695 use (+ 24 use of value "no|no" )
Used mainly in central North America and Germany.
Yours,
LeTopographeFou
Message original
De: letopographe...@gmail.com
Marc, it looks like you propose to tag it as a lane which can be used to turn
which is not what Roadsguy wants to do (if I get it right...).
If the central line can't be used but exists I would put
lanes:both_ways=1
access:lanes:both_ways=no
LeTopographeFou
Message original
De:
Hi,One interest to do it may be to reduce the volume of the database by improving compression, improve indexing of the values, simplify queries by reducing the need for a request to handle variations of case in a value, simplify statistics by reducing post-analysis... for me there is an added
Hi,I know that some consider the wiki as a not-trustable thing but when I read the dedicated page there is a third POV which makes more sense for me and which may explain why you add an extra area tag.http://wiki.openstreetmap.org/wiki/Tag:railway%3DstationTo summarize quickly: It says that
32 matches
Mail list logo
