Re: [Tagging] RFC Reception_desk Mk2
On Thu, May 21, 2015 at 12:34 AM, pmailkeey . pmailk...@googlemail.com wrote: 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. I believe we should simply map the reality. So a reception should be called a reception, and an entrance (independent from its appropriateness)—an entrance. If a company decides to move the reception from one entrance to another, does it mean we should erase the previous entrance? My university has the reception at the back entrance, the main entrance being used for official delegations only (that don't need reception) and for students and staff who have badges. And they are 10 minutes walk from each other, so it's important to know. 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. OSM is a database database of things on the planet, not an information centre for general public. There are restricted roads, and they are still mapped. So should by the entrances that are not for public access. Cheers, Kotya ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] RFC Reception_desk Mk2
On 21 May 2015 at 10:41, Kotya Karapetyan kotya.li...@gmail.com wrote: On Thu, May 21, 2015 at 12:34 AM, pmailkeey . pmailk...@googlemail.com wrote: 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. I believe we should simply map the reality. So a reception should be called a reception, and an entrance (independent from its appropriateness)—an entrance. If a company decides to move the reception from one entrance to another, does it mean we should erase the previous entrance? I'm quite happy for all the information to be on the map when all the information is on the map. If the full detail is not there then we need to ensure the more important data is on first - so we don't end up with a staff entrance marked on before the public entrance. My university has the reception at the back entrance, the main entrance being used for official delegations only (that don't need reception) and for students and staff who have badges. And they are 10 minutes walk from each other, so it's important to know. 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. OSM is a database database of things on the planet, not an information centre for general public. There are restricted roads, and they are still mapped. So should by the entrances that are not for public access. I wonder if OSM has generated any legal clauses yet ? So the heating engineer has to sign an agreement not to put the layout of the boilerhouse on OSM before they're allowed to carry out the work ! -- 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 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
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] 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
[Tagging] RFC Reception_desk Mk2
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 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 suggestedextended tag for camp sites http://wiki.openstreetmap.org/wiki/Proposed_features/Extend_camp_site%7C, 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
