or in stead of a full list of =yes
do the same as with vending=product1;product2
with a key like giving=* offering=*
Le 21.02.20 à 13:30, Florimond Berthoux a écrit :
> Hi,
>
> condom=yes
> condom:fee=no
>
> (condom is available here)
> (free condom, yeah!)
>
> As I suggested in the free
Le 20.02.20 à 12:45, Joseph Eisenberg a écrit :
> Can't we have an easy to use top-level feature tag, instead of having
> to add 3 tags like amenity=taxi + motorcar=no + motorcycle=yes to
> define one very common, unique feature?
did we need to have a top-level feature for every "unique"
Hello,
Le 20.02.20 à 07:41, Joseph Eisenberg a écrit :
> I've created a page for Key:dual_carriageway based on existing usage
> in the database:
> https://wiki.openstreetmap.org/wiki/Key:dual_carriageway
how did you proceed? is the tag added by only one contributor to whom
you asked the question
Le 19.02.20 à 04:29, Victor/tuxayo a écrit :
> Coincidentally there was a recent discussion[2] about these signs in the
> french mailing list (talk-fr) which lead to adding the following section
> in the page
> https://wiki.openstreetmap.org/wiki/Tag:man_made=surveillance
I warn that this
On Fri, 7 Feb 2020 at 10:26, Christoph Hormann wrote:
> it would make a lot of sense for OSM-Carto to stop indicating this is valid
> tagging.
it would make more sense to
1) decide what a valid/ideal schema is.
2) decide what a invalid/bad schema is.
3) making sure that the new schema is at
Le 07.02.20 à 13:59, Peter Elderson a écrit :
> intentionally mapped hedge areas. Not leisure/natural/landuse etc.
https://overpass-turbo.eu/s/Qwl exclude it
___
Tagging mailing list
Tagging@openstreetmap.org
Le 06.02.20 à 13:20, Andy Mabbett a écrit :
> We could use relation_type:set
why not using relation type=site that already exist ?
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
the proposals (I'm talking generally, not just about this one) have
often 2 flaws:
- often too big (not this one)
- often rfc too short, even active people still have remarks to make
that the vote is already open, so they are stuck to sink the proposal
(with the risk that its author gets
Le 05.02.20 à 22:08, Christoph Hormann a écrit :
> (either 'invalid', '1d barrier' or '2d barrier'):
Here is my view AND I known that osm consensus is not that :
> closed way, barrier=fence
1d barrier
> closed way, barrier=fence, area=yes
2d barrier
> closed way, barrier=fence,
Le 05.02.20 à 18:41, Andy Townsend a écrit :
> On 05/02/2020 17:24, Christoph Hormann wrote:
> About the "removing tags where they may clash" point
> "if something is mapped as a brewery and also as
> tourist attraction, remove the tourist attraction tags
if osm-carto goal is to trying to give a
Hello,
Some time ago, the proposal of tourism=camp_pitch was approved in order
to respect/return to the initial meaning of camp_site=* (the level of
infrastructure of a tourism=camp_site).
This involved a lot of work in reviewing site by site existing objects
to migrate them to the new scheme.
Le 30.01.20 à 23:51, Warin a écrit :
> comment=local name is used verbally, not on signs as yet.'
unsigned=name or unsigned=yes
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Le 28.01.20 à 13:45, Joseph Eisenberg a écrit :
> I think it would be reasonable to show healthcare=pharmacy,
> healthcare=hospital, healthcare=dentist and healthcare=doctor as
> discouraged and unnecessary in the wiki.
you take 2 tags out of their context, these 2 tags have their logic in
the
Le 27.01.20 à 17:07, Захаренков Алексей a écrit :
> https://www.openstreetmap.org/relation/10629103
> Me and the changeset author could not come to agreement
nobody ca have an agreement with him.
that isn't a country there. if p_v doesn't stop,
ask DWG for a ban
Hello,
some words in the name of some street is not understood by some people.
these are often old notations, sometimes borrowed from another language
but used in the official language to name this street.
street sign have those "one-name-but-in-mixed-language" and only that.
a contributor
I'm using operation_status when I see a such one.
and I'm trying to survey again later to see if it was a temporary
problem or if it's disused:
but to switch to disused: if there's no water on the day of the survey,
I think that's excessive.
Le 20.01.20 à 15:59, European Water Project a écrit :
>
Le 17.01.20 à 02:49, Joseph Eisenberg a écrit :
>>> I'm unsure why Carto ignores such a popular tagging scheme.
>>>
>> Is it actually popular?
>
> The place to request changed to Openstreetmap-carto is
> http://github.com/gravitystorm/openstreetmap-carto/issues
>
> According to taginfo, there
Le 17.01.20 à 12:48, Hauke Stieler a écrit :
> A shop at an airport where travelers generally pay no taxes would be
> tagged with "duty_free=yes" and optionally with "duty_free:refund=no".
>
> I hope this also makes sense to you.
no, sorry.
I don't see the advantage of using 2 keys when only one
Le 17.01.20 à 01:32, Hauke Stieler a écrit :
>> I see 3 levels :
>> the customer doesn't pay the tax duty_free=yes
>> the customer pay the tax but the shop help for a refund
>> the customer pay the tax and the shop doesn't help a refund duty_free=no
>
> Exactly, this is the basic idea for the
Le 17.01.20 à 09:58, Marc Gemis a écrit :
> abandoned:military=bunker
> + building=bunker
that look fine for me.
> Not sure about the ruins:building
I have never yet seen a building=bunker in ruins because of the mass
of concrete used, but if structurally one of them is a ruin and not
a bunker
Le 17.01.20 à 09:36, Lionel Giard a écrit :
> What do you think about this?
keep simple.
if a parking space is only for disabled ppl with access restriction,
why not using capacity=* on it ?
it's not wrong but useless to use namespace capacity:disable=*
in this case.
especially since
Le 17.01.20 à 00:51, Hauke Stieler a écrit :
>> about : duty_free:refund=yes
>> is it an intermediate level between duty_free=yes and duty_free=no ?
>> if yes, wouldn't it be better to use duty_free=limited ?
> I wouldn't say "duty_free:refund=yes" is something in between
> "duty_free=yes" and
about : duty_free:refund=yes
is it an intermediate level between duty_free=yes and duty_free=no ?
if yes, wouldn't it be better to use duty_free=limited ?
about "global_blue" and the following : what is that ?
maybe add a link.
Le 16.01.20 à 21:28, Hauke Stieler a écrit :
> Hi,
>
> just a
, Dave F via Tagging a écrit :
> Well. Done. You.
On 16/01/2020 12:01, marc marc wrote:> you want me to believe that every
time an object has gone,
Le 16.01.20 à 14:26, Dave F via Tagging a écrit :
> It's not gone. We're talking about buildings
I have put back above the line to whic
Le 16.01.20 à 12:53, Dave F via Tagging a écrit :
> On 16/01/2020 11:34, marc marc wrote:
>> I'm also using was: because I don't care
>
> Well. Done. You.
you want me to believe that every time an object has gone,
you make an enquiry to find out how it disappeared ?
I did this a
I'm also using was: because I don't care and often don't known if a poi
is destroyed, dismantled, demolished, moved, the only thing I can see is
that it's gone.
f.e. a room whose store type has changed doesn't fit my description of
disused:
Le 16.01.20 à 12:16, Dave F via Tagging a écrit :
>
Le 16.01.20 à 02:52, Joseph Eisenberg a écrit :
> The simple "seasonal=yes/no" is at least clear, though with natural
> features "intermittent=yes/no" is more common and has a similar
> meaning.
I see a big difference between the two:
an intermittent water point provides water today but not
Le 15.01.20 à 16:15, Jmapb via Tagging a écrit :
> On 1/15/2020 12:55 AM, European Water Project wrote:
>> Would it be appropriate to use the tag "seasonal" for a water fountain
>> (whether tagged as "amenity=drinking_water" or "amenity = fountain and
>> drinking_water = yes" )?
>
> Don't forget
Le 15.01.20 à 06:55, European Water Project a écrit :
> Would it be appropriate to use the tag "seasonal" for a water fountain
yes I think so.
I'm going to check/survey the nearby fountains: some are closed
in winter but don't have a precise opening/closing date.
Of course this tag is a bad idea, which duplicates existing information
in osm and is therefore a source of conflict when one of the 2 data is
capitalized and not the other one.
if not, what next ?
distance_from_bus_stop ?
distance_from_tram_stop train station pub supermarket postoffice town
Le 15.01.20 à 12:49, Mateusz Konieczny a écrit :
> Anyone with opinion on that topic is welcomed to comment in this
> discussion on the OSM Wiki.
I'm very unhappy with that.
some tools use wiki and not data items (for ex taginfo)
doing that destroy usefull information.
in fact I'm unhappy with
Le 15.01.20 à 05:15, Warin a écrit :
> On 15/1/20 6:32 am, marc marc wrote:
>> Le 14.01.20 à 19:34, Markus a écrit :
>>> If i understand it correctly, building=* values describe how the
>>> building looks, not how it is used. For example, a church that is now
>
Le 14.01.20 à 19:34, Markus a écrit :
> If i understand it correctly, building=* values describe how the
> building looks, not how it is used. For example, a church that is now
> used as a pub still remains a building=church.
I fully agree with that.
note that building:use may record the current
Le 14.01.20 à 18:33, António Madeira via Tagging a écrit :
> https://wiki.openstreetmap.org/wiki/Proposed_features/olive_oil_mill
> What can I do to revive this proposal and implement this tag?
for small changes :
check taginfo if another tag/value exist with the same meaning.
check if the most
> free_water:container =
bring_your_own is very explicit.
but "provided" or "establishment" is ambiguous.
from my experience, drinking a free glass of water in a cafe is not at
all the same as receiving a container filled with water (I have never
encountered this case).
so the choice should be
Le 14.01.20 à 10:00, Martin Koppenhoefer a écrit :
> if you have to buy something in order to get "free" water,
> it isn't free, is it? It's included.
you're right, I often make that remark in everyday life.
but in osm terminology, how would you inform the private and free
swimming pool for
Le 11.01.20 à 21:05, Florimond Berthoux a écrit :
> What do you think ?
avoid the word "type" in a key as it as no additional meaning.
type can be everything (type of operator, difficulty, use, length, ...)
___
Tagging mailing list
Le 11.01.20 à 06:21, Joseph Eisenberg a écrit :
> The tag route=inline_skates
> Are there actually signed, verifiable inline skate routes?
yes
> Should a rare tag like this be in Map Features?
listing all the rare cases on maps feature is like turning it into
a wiki search engine or a taginfo
Le 06.01.20 à 08:47, Florian Lohoff a écrit :
> If you have HUGE Buildings i use a node with an address.
it's amazing the difference in usage.
I find that addr nodes are very problematic for hudge buildings like
shopping malls or train stations. the localisation of the node forces
the routing to
why it isn't a paving_stones ? the max height ?
I ask myself how and how many mappers 'll see a diff.
Le 08.01.20 à 22:36, Mateusz Konieczny a écrit :
> Is following picture
> https://commons.wikimedia.org/wiki/File:Paving_being_laid_arp.jpg
> depicting construction of surface=paving_stones?
>
>
Le 08.01.20 à 05:10, Marc Gemis a écrit :
> On Tue, Jan 7, 2020 at 10:30 PM marc marc wrote:
>>
>> Le 06.01.20 à 04:19, Jarek Piórkowski a écrit :
>>> Comments most welcome!
>>
>> keep it simple !
>> advanced stop box only use a cycleway=asl without relat
Le 06.01.20 à 03:24, John Willis via Tagging a écrit :
> parking=tourism
> parking=disabled
> parking=loading_dock
> parking=taxi
> parking=waiting_lot
that conflit with the current meaning :
https://wiki.openstreetmap.org/wiki/Key:parking
parking=surface/underground/roof top would have looked
Le 07.01.20 à 20:21, joost schouppe a écrit :
> function=recreational/practical
usage=tourism/transport ?
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Le 06.01.20 à 04:19, Jarek Piórkowski a écrit :
> Comments most welcome!
keep it simple !
advanced stop box only use a cycleway=asl without relation
https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dasl
a single node is not enought ?
___
Tagging
Le 07.01.20 à 20:58, Richard Welty a écrit :
> a profound lack of interest
> https://wiki.openstreetmap.org/wiki/Talk:Relations/Proposed/Circuit
maybe it's due to the funny url for a propal
moving it at the right place may help
___
Tagging mailing list
Le 07.01.20 à 13:40, Jeroen Hoek a écrit :
> using the exsiting ISO3166-1:alpha2
all those ISO3166-1* key doesn't have a wiki page.
if the key is fine (I find it ugly as a top level key),
it could be a good idea to write a small sheet about them.
___
Le 06.01.20 à 04:48, Paul Johnson a écrit :
> Domestic refuse metals like metal packaging from consumer products
> (think like, food and beverage cans), something that you can typically
> drop off at your average grocery store parking lot recycling center. As
> opposed to scrap metal, which is
Le 06.01.20 à 01:28, Tomek a écrit :
> W dniu 20-01-06 o 00:24, marc marc pisze:
>> are you planning a mechanical edit ?
> NE, mi volas redakti ĉiun punkton aparte.
editing one by one, doesn't solve the the mechanical issue,
mechanical isn't about the size of the changeset,
it's about
Le 05.01.20 à 23:25, Tomek a écrit :
> I plan to remove the "name" and "wikipedia" tags from places
> that are not associated with a specific nation or language:
> Please support (vote) my proposal or write a reason why not.
are you planning a mechanical edit ?
if yes, you misunderstood
Hello,
https://josm.openstreetmap.de/ticket/18152
https://wiki.openstreetmap.org/wiki/Tag:amenity%3Drecycling
the wiki describe recycling:metal as "ll sorts of metal – possible
duplicate of more frequently used recycling:scrap_metal; see below."
the wiki doesn't describe recycling:scrap_metal
Le 29.12.19 à 21:50, bkil a écrit :
> fee=no @ register with an Italian phone number
it seems to indicate that it's fee=yes if you don't register,
which doesn't seem to fit with what you're saying.
I prefer :
internet_access:fee=customers (you need to be a customer of it... some
use access for
Le 29.12.19 à 22:23, bkil a écrit :
> What do you think about these?
if the value is an abbreviation, then it's a short_name (but brand
doesn't have a short_brand key, in this case it's normal to put the
abbreviation in uppercase in brand=*)
if the value is not an abbreviation, I will use the
Hello,
boith tags look fine, except the unneeded use of a namespace
duty_free= (already exist 6 time)
tax_refund=
Regards,
Marc
Le 23.12.19 à 21:25, Hauke Stieler a écrit :
> Hi all,
>
> so I think of creating/establishing two new tags:
>
> shop:duty_free=
> -> Shops in airports where nobody
. 2019 om 15:31 heeft marc marc het volgende geschreven:
>>
>> I always thought that routrip=yes was an alternative when there is no
>> start and end point to enter in from=* to=* key.
>> Otherwise circular routes with a known start/en
I always thought that routrip=yes was an alternative when there is no
start and end point to enter in from=* to=* key.
Otherwise circular routes with a known start/end point can enter
as from=A via=B to=A.
___
Tagging mailing list
Le 20.12.19 à 15:47, Cascafico Giovanni a écrit :
>
>
> Il mer 18 dic 2019, 16:48 Tom Pfeifer ha scritto:
>
>
> The 'box' would contain a full access point and not just the
> antenna, thus I'd prefer not to tag the
> antenna alone.
>
>
> So how to tag the whole hardware?
> Shall
Le 18.12.19 à 17:24, Philip Barnes a écrit :
> On Wednesday, 18 December 2019, marc marc wrote:
>> Le 18.12.19 à 16:58, Robert Skedgell a écrit :
>>> I think creating shop=vegan_cheese might be excessively specialised.
>>> https://www.openstreetmap.org/node/6776593885
Le 18.12.19 à 16:58, Robert Skedgell a écrit :
> I think creating shop=vegan_cheese might be excessively specialised.
> https://www.openstreetmap.org/node/6776593885
ho yes, please don't create a new shop=* only to describe that
the shop had a limited number of products.
you may add
On Thu, 28 Nov 2019 at 17:58, Jan Michel wrote:
> the purpose of the berm - e.g. berm = noise_barrier
usage=* may fit the need
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Le 27.11.19 à 22:35, s8evq a écrit :
> 1) Add a node approximately in the middle of the forest with the name tag
> together with place=locality
> 3) Draw a new way around the outline of the forest and put the name tag on
> that. The problem with this approach is that you need an additional main
Le 27.11.19 à 17:42, Martin Koppenhoefer a écrit :
>> On 27. Nov 2019, at 17:36, marc marc wrote:
>>
>> I don't see a physical séparator between the road and the sidewalk
>> so it's controversial to separate these different lanes into several ways
>
> afaik the hi
Le 27.11.19 à 16:11, Volker Schmidt a écrit :
> I do have a topological problem with the mapping of a junction of two
> roads one of which has parallel cycle lanesa and sidewalks
> Both are correctly mapped: the sidewalk as a separate highwy=footway
I don't see a physical séparator between the
Le 24.11.19 à 21:51, Kevin Kenny a écrit :
> the damaged roads are still signed with the route numbers
ref on way + relation for the real (= in use) route
___
Tagging mailing list
Tagging@openstreetmap.org
Le 24.11.19 à 04:32, John Willis via Tagging a écrit :
> Levees have construction projects that can be years in length (building
> a new sluice gate, enlarging the levee), and the route is detoured
> around this construction.
if the itinerary is modified for years, I would modify the main
Le 21.11.19 à 22:51, François Lacombe a écrit :
> Those two boxes will be hard to describe on the same node, although they
> can be located on the same pole.
> Should we recommend to put as many nodes as required around the pole or
> choose another option?
the easiest way to use the data is to
Le 19.11.19 à 13:22, A A a écrit :
> What do you think about the possibility of standardizing the use of
> a url in "departures_board" or "passenger_information_display" tags to
> be able to report arrival times in real time at a stop or train / subway
> / bus station?
yes.
Le 11.11.19 à 23:13, Herbert Allmeier a écrit :
> Country tags: There is no worldwide toll system.
the same apply for parking : no the same-for-all-parking exist
but we still avoid using a country code to said that all parking in this
country use somethink specific to this country.
the same
Le 11.11.19 à 15:44, Joseph Eisenberg a écrit :
> decide which tags under `emergency=` should be treated as polygons
> when mapped as closed ways
is this information not already present on the wiki pages? for example
https://wiki.openstreetmap.org/wiki/Tag%3Aemergency%3Dambulance_station
Le 08.11.19 à 16:16, Mateusz Konieczny a écrit :
> 7 Nov 2019, 14:39 by marc_marc_...@hotmail.com:
>> Le 07.11.19 à 14:01, Andy Townsend a écrit :
>>> you won't see a unique sign that identifies "you can't cycle here"
>> an good pratice rule is "don't map the legislation", isn't
Le 07.11.19 à 14:01, Andy Townsend a écrit :
> you won't see a unique sign that identifies "you can't cycle here"
an good pratice rule is "don't map the legislation", isn't it ??
no sign ? thus no tag on the way
at most a default value in the wiki or on the boundary.
Hello,
Le 06.11.19 à 19:55, Mark Wagner a écrit :
> There are places like federal Wilderness Areas in the United States
> where possession of a bicycle is forbidden
can you share the a picture of this traffic sign ?
Regards,
Marc
___
Tagging mailing
Le 28.10.19 à 09:44, Mateusz Konieczny a écrit :
> "sign having a hospital icon and no name can simply be tagged
> type=destination_sign + amenity=hospital"
> https://wiki.openstreetmap.org/wiki/Relation:destination_sign
Yes it's horrible
the next line said destination:symbol=hospital
it's
Le 25.10.19 à 20:29, John Willis via Tagging a écrit :
>
>> On Oct 25, 2019, at 10:53 AM, Joseph Eisenberg
>> wrote:
>>
>> The value should have something that suggests that it will be flooded.
>> I would think of "flood_mitigation" as something like a levee or dyke
>> which prevents flooding,
Hello,
Le 24.10.19 à 21:12, Clifford Snow a écrit :
> [1] https://wiki.openstreetmap.org/wiki/Proposed_features/access_aisle
highway=footway is sometime (counry-specific) restricted to way
with a traffic sign like the current one in its wiki page
Le 23.10.19 à 11:35, Florian Lohoff a écrit :
> You need to eliminate the node and replace it with a circular road
a junction=roundabout is also allowed as a node
https://taginfo.openstreetmap.org/tags/junction=roundabout
so it's a bad rational to deprecate mini_roundabout
Le 20.10.19 à 20:01, Valor Naram via Tagging a écrit :
> https://wiki.openstreetmap.org/wiki/Discussions/tagging/contact:phone_or_phone
is it a good idea and valid to open a vote with a url different from the
conventions made for proposals? it makes it much less readable for the
community
Le 07.10.19 à 23:07, Martin Koppenhoefer a écrit :
> let’s bury the contact: - prefix
in this case, be logical and also propose to bury the prefix addr:
on the contrary, I believe that having a namespace to group the keys
concerning the addr and another namespace to group the keys concerning
Le 18.09.19 à 01:02, Paul Allen a écrit :
> Those machines are generally available for use only by people
> staying on the site (they could accept anyone, but usually do not). How
> are you going
> to tag that? We don't have access=campers
access=private private=campers
Le 12.09.19 à 13:52, Frederik Ramm a écrit :
> A supermarket chain can introduce paper bags today, discontinue them
> next week, and re-introduce plastic bags next month.
in theory yes.
in practice logistics chains probably change less quickly
than the urbanization of agricultural land.
if we
they have to use one-use only bags
> for hygienic reasons.
>
>
> On 12/09/2019 12:29, marc marc wrote:
>> Hello,
>>
>> Le 12.09.19 à 12:20, Antoine Jaury via Tagging a écrit :
>>> https://wiki.openstreetmap.org/wiki/Proposed_features/reusable_
Hello,
Le 12.09.19 à 12:20, Antoine Jaury via Tagging a écrit :
> https://wiki.openstreetmap.org/wiki/Proposed_features/reusable_packaging
> Definition: Describes a shop accepting reusable containers from their
> customers and/or proposing some
it'sn't the same as
Le 09.09.19 à 16:18, Mateusz Konieczny a écrit :
>
>
>
> 9 Sep 2019, 15:14 by pella.s...@gmail.com:
>
> Imho: the real problem, why we have multiple objects for
> "name:*" tags? ( admin_centre, label, relation, ... )
>
> Label is an attempt to manually
> specify optimal place
Le 06.09.19 à 12:17, Martin Koppenhoefer a écrit :
> placement(?)=soil / street
location seems better and already exist
https://wiki.openstreetmap.org/wiki/Key%3Alocation
___
Tagging mailing list
Tagging@openstreetmap.org
Hello,
does both have the same meaning ?
I thought that sculter was a typo in french (the word is "sculteur"
in french) but usage in french-speaking countries is very low,
so that's not the explanation.
Regards,
Marc
___
Tagging mailing list
Le 28.08.19 à 11:19, Joseph Eisenberg a écrit :
> New description is 'An office for a consulting firm,
> providing expert professional advice to other companies."
at least a tag to specify the activity should be provided,
because with the current description, an accounting, IT security,
Le 26.08.19 à 12:57, Warin a écrit :
> Is there a requirement to go in to all of these wiki pages and explain
> why the demotion of one over the other simply due to frequency of use
> without consideration of other factors?
I ask myself "what would we do if the other tag didn't exist ?"
would
Le 26.08.19 à 00:18, Joseph Eisenberg a écrit :
> What should we do with a page like Tag:landcover=dunes? I already
> tried adding a mention that natural=dune was more common and mentioned
> on the Talk page that "dune" is a landform, not a landcover
the first sentence on the wiki is enought to
Le 25.08.19 à 17:42, Colin Smale a écrit :
> Your model (using only phone=*) only allows an object to have a single
> phone number.
not true.
phone=number1;number2
ex https://www.openstreetmap.org/node/26861282
18219 discint value for a total of 19694 count
> one for general enquiries, one for
Le 25.08.19 à 16:55, Martin Koppenhoefer a écrit :
> What about deprecating the contact: prefix, at least for phone?
not "AT LEAST FOR" that's the main issue !
having some contact with contact: prefix and some other without
is a very bad idea.
we need to switch all contact to key with contact:
Le 24.08.19 à 18:04, Valor Naram a écrit :
> why we have two tags for one purpose sometimes?
many (almost all bad) reasons can explain it :
- one key exist, a new schema is born with a new tag for the same
feature/meaning, but the new schema never got a proposal or the proposal
never go into
Le 21.08.19 à 09:58, Markus a écrit :
> Otherwise, we need a new relation (maybe type=stop_position?) to
> connect the stop position to the waiting area
imho that's why stop_area relation exist
___
Tagging mailing list
Tagging@openstreetmap.org
Le 19.08.19 à 15:28, Joseph Eisenberg a écrit :
>>> The tag livestock=*
>>> used 132 times
>>
>> 16% of landuse=farmyard have a animal=* tag.
>
> I think you misread taginfo.
you're right.
> If we remove the animal=yes tags
in stead of a replay, can you explain
why those valid datas need to be
Le 19.08.19 à 13:34, Paul Allen a écrit :
> On Mon, 19 Aug 2019 at 12:16, Warin wrote:
>I like property tags that can be used anywhere appropriate.
>
> The authors of at least one editor disagree with you there.
> Unless all of the possible
> values are applicable to all objects for which
Le 19.08.19 à 12:17, Joseph Eisenberg a écrit :
> The tag animal=* has been 2137 times
> animal=yes (unhelpful!)
I wonder why it's useless.
if the contributor does not know if they are cows or calves,
this allows him to enter "there are farm animals there" and any
application can easily target
Le 15.08.19 à 19:40, Martin Koppenhoefer a écrit :
> why would you not do it for roundabouts?
when we split a building in several parts, we keep one building=*
and use several building:part
for roundabouts, the tag is the same. for the whole roundabouts and for
part of it.
So spliting one
Le 15.08.19 à 16:28, Martin Koppenhoefer a écrit :
>> On 15. Aug 2019, at 15:54, marc marc wrote:
>>
>> - keep booking=* for the few booking.com urls that currently exist
>
> IMHO we should not reserve tags named with a common word like „booking“ for a
> commerci
Le 15.08.19 à 15:26, Dave F via Tagging a écrit :
> How about using booking?
> https://wiki.openstreetmap.org/wiki/Key%3Abooking
we talk a few days ago to :
- move value used as in reservation=* into this tag to avoid
duplicate tag with the same meaning
- keep booking=* for the few booking.com
Le 14.08.19 à 02:00, Warin a écrit :
> On 14/08/19 00:20, Martin Koppenhoefer wrote:
>>> On 13. Aug 2019, at 16:02, Paul Allen wrote:
>>>
>>> Which diverged into this thread. We've come full circle.
>> you have to repeat and explain the outcome of older discussions
>> to bring those on board
Le 10.08.19 à 07:24, Warin a écrit :
> the key produce=* could be used to detail what was sold
a shop produce nothing. better to use vending=*
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
resend with 2 corrected errors (in caps)
Le 09.08.19 à 15:46, marc marc a écrit :
> Le 09.08.19 à 15:32, Joseph Eisenberg a écrit :
>> I'm trying to figure out what this means
>
> it mean the contributeur doesn't understand changeset TAG
> or understand it but find it more conv
1 - 100 of 581 matches
Mail list logo
