Re: [Tagging] RFC Reception_desk Mk2
On 20 May 2015 at 02:09, Warin 61sundow...@gmail.com wrote: Hi, I have left this for a while. But I don't see it going anywhere in terms of the tag=value. The initial proposal started on 6 February 2015, has been voted on and reformatted to address issues raised. Link to the proposal = https://wiki.openstreetmap.org/wiki/Proposed_Features/amenity%3Dreception_desk One issue that I have not address is when someone wants to have one node with more than one amenity on it. Firstly .. it would be possible to create two nodes and place the different values on the different nodes. That is the solution I use. One node, all tags is the gut feeling I get. Put all the tags on one and if two are the same key with different values, add the values separated by semicolons. If in doubt, create two nodes and use iD to combine them ;) by (shift) selecting both and use the + symbol to combine. Re reception desk - sounds useful but in the meantime I'm making use of the entrance/exit tag to indicate main entrance - where a reception desk would be found. -- Mike. @millomweb https://sites.google.com/site/millomweb/index/introduction - For all your info on Millom and South Copeland via *the area's premier website - * *currently unavailable due to ongoing harassment of me, my family, property pets* TCs https://sites.google.com/site/pmailkeey/e-mail ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] housenumber on node and area
Hi, We know that addr:housenumber http://wiki.openstreetmap.org/wiki/Key:addr=* can be tagged on nodes http://wiki.openstreetmap.org/wiki/Addresses#How_to_map_addresses and that it's very convenient. A problem in tagging the number on a node *instead* of on an area is that someone making a nice copy ( paste) like below (partim) of the nice information found in the left pane of OSM.org will inadvertently miss the number. Does anyone have an objection against the same number being *also* on the node? That is the same number both on a node (once) and on the way/relation *that this node belongs to* (once)? (we already have the other address information routinely duplicated and even triplicated (associatedAddress) for the sake of consumers finding it, so why not the address?) Cheers André. addr:city http://wiki.openstreetmap.org/wiki/Key:addr:city?uselang=en ... addr:housename http://wiki.openstreetmap.org/wiki/Key:addr:housename?uselang=en ... addr:postcode http://wiki.openstreetmap.org/wiki/Key:addr:postcode?uselang=en ... addr:street http://wiki.openstreetmap.org/wiki/Key:addr:street?uselang=en .. amenity http://wiki.openstreetmap.org/wiki/Key:amenity?uselang=en ... building http://wiki.openstreetmap.org/wiki/Key:building?uselang=en yes contact:email http://wiki.openstreetmap.org/wiki/Key:contact:email?uselang=en ... contact:phone http://wiki.openstreetmap.org/wiki/Key:contact:phone?uselang=en ... contact:website http://wiki.openstreetmap.org/wiki/Key:contact:website?uselang=en ... craft http://wiki.openstreetmap.org/wiki/Key:craft?uselang=en ... name http://wiki.openstreetmap.org/wiki/Key:name?uselang=en ... ... ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] RFC Reception_desk Mk2
One node, all tags is the gut feeling I get. Put all the tags on one and if two are the same key with different values, add the values separated by semicolons. If in doubt, create two nodes and use iD to combine them ;) by (shift) selecting both and use the + symbol to combine. +1, but probably will be left up to the mapper, as usual. Re reception desk - sounds useful but in the meantime I'm making use of the entrance/exit tag to indicate main entrance - where a reception desk would be found. For simple situations it works. Sometimes however the reception desk may appear elsewhere (not at the main entrance) as well, and there may be more entrances too. Example: my company campus has 3 main receptions (I am aware of), one main entrance (for the visitors who don't know where to go; however they can go to other receptions too), and dozens of entrances without receptions. A hospital nearby has at least 2 entrances, one being the main one, with a reception at each entrance. That's why this proposal is so valuable. Cheers, Kotya ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - opening hours default PH off
Hi, I disagree here as it's highly dependant of the type of POI. This default might be a correct assumption for shops (in countries where that's the case), but not for - restaurants (as well as fast food, to stay in the OSM nomenclature) - hotels - fuels - swimming pools - casinos - ... Therefore a general assumption IMHO is more often wrong than right. regards Peter Am 30.04.2015 um 15:18 schrieb Robin `ypid` Schneider: Hi everyone As noted by Ein Mapper on [the current weekly task in Germany][1] it would be convenient to have an implicit PH off added to most opening_hours values during evaluation. I had not thought about this before but now that I do I agree more and more that this makes sense and wrote a proposal [2]. Any thoughts about this? [1]: https://blog.openstreetmap.de/blog/2015/04/wochenaufgabe-oeffnungszeiten/#comment-143413 [2]: https://wiki.openstreetmap.org/wiki/Proposed_features/opening_hours_default_PH_off ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] housenumber on node and area
That is the same number both on a node (once) and on the way/relation *that this node belongs to* (once)? Do you mean area when you say way? I think if a building has the address then you should not have a node for just the address. If it's a amenity, craft etc. then it's fine to put the address on that, too. PS: Yay contact: guess that will never end... __ openstreetmap.org/user/AndiG88 wiki.openstreetmap.org/wiki/User:AndiG88 ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] housenumber on node and area
On 20 May 2015 at 14:10, André Pirard a.pirard.pa...@gmail.com wrote: Hi, We know that addr:housenumber http://wiki.openstreetmap.org/wiki/Key:addr=* can be tagged on nodes http://wiki.openstreetmap.org/wiki/Addresses#How_to_map_addresses and that it's very convenient. But wrong. A problem in tagging the number on a node *instead* of on an area is that someone making a nice copy ( paste) like below (partim) of the nice information found in the left pane of OSM.org will inadvertently miss the number. Does anyone have an objection against the same number being *also* on the node? That is the same number both on a node (once) and on the way/relation *that this node belongs to* (once)? (we already have the other address information routinely duplicated and even triplicated (associatedAddress) for the sake of consumers finding it, so why not the address?) Info shouldn't be duplicated or triplicated either. -- Mike. @millomweb https://sites.google.com/site/millomweb/index/introduction - For all your info on Millom and South Copeland via *the area's premier website - * *currently unavailable due to ongoing harassment of me, my family, property pets* TCs https://sites.google.com/site/pmailkeey/e-mail ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] housenumber on node and area
On 21/05/15 09:51, pmailkeey . wrote: On 20 May 2015 at 14:10, André Pirard a.pirard.pa...@gmail.com mailto:a.pirard.pa...@gmail.com wrote: Hi, We know that addr:housenumber http://wiki.openstreetmap.org/wiki/Key:addr=* can be tagged on nodes http://wiki.openstreetmap.org/wiki/Addresses#How_to_map_addresses and that it's very convenient. But wrong. Why? It's all very well that this may be you opinion but the wiki and accepted practice says otherwise. A problem in tagging the number on a node *instead* of on an area is that someone making a nice copy ( paste) like below (partim) of the nice information found in the left pane of OSM.org will inadvertently miss the number. Does anyone have an objection against the same number being *also* on the node? That is the same number both on a node (once) and on the way/relation *that this node belongs to* (once)? (we already have the other address information routinely duplicated and even triplicated (associatedAddress) for the sake of consumers finding it, so why not the address?) Info shouldn't be duplicated or triplicated either. Agree. -- Mike. @millomweb https://sites.google.com/site/millomweb/index/introduction - For all your info on Millom and South Copeland via *the area's premier website - * * * *currently unavailable due to ongoing harassment of me, my family, property pets* * * TCs https://sites.google.com/site/pmailkeey/e-mail ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] RFC Reception_desk Mk2
On 20 May 2015 at 14:42, Kotya Karapetyan kotya.li...@gmail.com wrote: One node, all tags is the gut feeling I get. Put all the tags on one and if two are the same key with different values, add the values separated by semicolons. If in doubt, create two nodes and use iD to combine them ;) by (shift) selecting both and use the + symbol to combine. +1, but probably will be left up to the mapper, as usual. Re reception desk - sounds useful but in the meantime I'm making use of the entrance/exit tag to indicate main entrance - where a reception desk would be found. For simple situations it works. Sometimes however the reception desk may appear elsewhere (not at the main entrance) as well, and there may be more entrances too. Example: my company campus has 3 main receptions (I am aware of), one main entrance (for the visitors who don't know where to go; however they can go to other receptions too), and dozens of entrances without receptions. A hospital nearby has at least 2 entrances, one being the main one, with a reception at each entrance. If they need a map to find the place, the need any reception for newbies. Tag the appropriate entrances with ent/ext tags - all those entrances suitable for newbies. Hospitals tend to have multiple entrances - so tag them appropriately such as A+E(ED) , main, outpatient or even named department. Schools have many entrances too but the general public don't need to know about them all. -- Mike. @millomweb https://sites.google.com/site/millomweb/index/introduction - For all your info on Millom and South Copeland via *the area's premier website - * *currently unavailable due to ongoing harassment of me, my family, property pets* TCs https://sites.google.com/site/pmailkeey/e-mail ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] RFC Reception_desk Mk2
On Wed, 2015-05-20 at 11:09 +1000, Warin wrote: Link to the proposal = https://wiki.openstreetmap.org/wiki/Proposed_Features/amenity% 3Dreception_desk I still see this as a useful thing. David For those not familiar with the proposal. A Reception Desk provides a place where people (visitors, patients, or clients) arrive to be greeted, any information recorded, the relevant person is contacted and the visitor/s, patient/s, or client/s sent on to the relevant person/place. It is particularly useful to know the location of the reception desk when it is located away from the typical place (near a front entry) or where there is only one amongst a number of large buildings. First seen as a suggested extended tag for camp sites, thought to have a wider application to offices, hotels and educational features. I have changed the documentation (many times) hopefully it addresses most issues that have been raised. One issue that I have not address is when someone wants to have one node with more than one amenity on it. This occurs for many key=value situations. Firstly .. it would be possible to create two nodes and place the different values on the different nodes. That is the solution I use. Secondly ... it has been suggested to use a format of a subtag where value2=yes is placed under the key=value1. e.g. amenity=bbq reception_desk=yes I have not seen (nor sought!) documentation for this .. as I don't use it. --- The present proposal format in the upper section shows what the result should look like, while the lower section has the verbose explanation etc. I don't like the title 'Rationale' .. and have appended 'Verbose Explanation' as a simpler, clearer title. I have also added sections on the key, value etc .. as I think that is easier to follow (and I don't get mixed up in my documentation! :-) ). So there it is .. voting soon? Depending on any discussion relevant to the key-value. Discussion of the format etc ... ok .. but not fundamental to the proposal itself, so should not delay voting. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - opening hours default PH off
On May 1, 2015, at 8:58 PM, Martin Koppenhoefer dieterdre...@gmail.com wrote: Am 30.04.2015 um 18:04 schrieb p...@trigpoint.me.uk mailto:p...@trigpoint.me.uk: It really makes more problems than it solves +1 +1 cheers Martin +1 In Japan the public holidays are very very well defined (the calendar holiday days are red on all calendars) - but wether that means the business is closed or not is not something that can be inferred. However, many civic offices and businesses note if they take “holidays” off on their front window. But how to turn that into data parseable by a program might have to be left to the data customer, who hopefully would know the calendar set int he country they’re getting data for. Javbw___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
