2015-03-10 22:41 GMT+01:00 David Bannon dban...@internode.on.net:
On Tue, 2015-03-10 at 09:35 -0700, Bryce Nesbitt wrote:
The wiki has a very low correlation to the rendering.
Does it ? Are you suggesting that there is substantial usage of tags
that don't appear on the wiki ? If so, I'd
2015-03-08 23:08 GMT+01:00 Warin 61sundow...@gmail.com:
The way I search for a relevant tag is to use the wiki, not taginfo. I
suspect many mappers do the same.
I recommend using several sources, my personal priority order is: the wiki,
taginfo, mailing lists.
Using a tag that is not on
2015-03-08 23:08 GMT+01:00 Warin 61sundow...@gmail.com:
The way I search for a relevant tag is to use the wiki, not taginfo. I
suspect many mappers do the same.
Using a tag that is not on the wiki will probably mean it is not rendered.
Many mappers don't use the wiki at all.
The wiki has a
On Tue, 2015-03-10 at 11:38 +0100, Martin Koppenhoefer wrote:
..
Using a tag that is not on the wiki will probably mean it is not
rendered.
rendered where? Many if not even most of the tags that are described
in the wiki are actually not rendered on the OSM-Carto style.
While true
On Tue, 2015-03-10 at 09:35 -0700, Bryce Nesbitt wrote:
The wiki has a very low correlation to the rendering.
Does it ? Are you suggesting that there is substantial usage of tags
that don't appear on the wiki ? If so, I'd suggest we need to fix the
wiki.
Rendering is not the only goal of OSM
On Sat, Mar 7, 2015 at 4:57 PM, Warin 61sundow...@gmail.com wrote:
--
Request For Comments ...
I see this as part of improving the proposal .. not as showing a complete,
fully functional for all possible things, fault free tag. If only
+1
On Sun, Mar 8, 2015, 23:09 Warin 61sundow...@gmail.com wrote:
On 9/03/2015 1:22 AM, Andreas Goss wrote:
Why do you even bother with a proposal when you bascially don't care
about tagging?
I care to get good, if not the best, tags. I try to get ideas for these
from the tagging group.
On 9/03/2015 1:22 AM, Andreas Goss wrote:
Why do you even bother with a proposal when you bascially don't care
about tagging?
I care to get good, if not the best, tags. I try to get ideas for these
from the tagging group. I don't care for arguments on a proposal that
are not directly
Am 08.03.2015 um 00:51 schrieb Andreas Goss andi...@t-online.de:
It should be found because OSM is a geographical database and the
reception, or the multiple receptions
as you asked before, is/are contained in the campus of the facility.
So bascially most of the time you would just tag
Also I believe most of the time you'll be more interested in the entrance,
the reception desk will very likely be close to it.
On our campus, we have a couple of dozens of entrances for employees but
only three of four receptions where a non-employee can enter. So mapping a
reception
You really don't care for the tagging group much, do you?
The way I search for a relevant tag is to use the wiki, not taginfo. I
suspect many mappers do the same. Using a tag that is not on the wiki will
probably mean it is not rendered.. thus I may have wasted my effort. By
waving
Why do you even bother with a proposal when you bascially don't care
about tagging? If you want to tag reception_desks in whatever random way
then just go ahead and do it. Then people will see what you used on
taginfo when looking for reception and at some point you just make a
wiki page with
On 8/03/2015 10:22 AM, Andreas Goss wrote:
And again how would you name it if it was just one of multiple
recpetions desks for one facility. Facility name = operator=*
name=Gate 1? So if the reception has no name then name= stays empty?
Do I use the plant name as operator? Or the company
Well, I think it depends on what kind of visitor you are. For the plant
tour there is probably just one meeting and entrance point. But for
suppliers, constuction workers, people from the same company who don't
work at that plant I don't think it matters.
Then that would be 3 reception desks
You have visitor reception at all gates? Visitor badging and everything?
I assume there is security there letting people in (gate) but are there 3
areas for a person to be badged and wait for their visitee to come down and
pick them up?
3 places to sign up for the tour of the facility? 3
I approve this proposal. Also very useful for big industrial areas. [...]
--Mapper999 (talk) 15:58, 2 March 2015 (UTC)
So how do you tag it on a industrial complex when you have it at let's
say Gate 1, Gate 2 and Gate 3?
I believe it depends on the facility. My company has 3 receptions, and they
are called officially Reception 7, 4 and 8; these are the names
appearing on the phone when I receive a call to collect a visitor. I will
use that as the names.
On Sat, Mar 7, 2015 at 3:57 PM, Andreas Goss
Is it possible to put that in operator or official_name, or is the name assumed
because the point is inside the landuse?
Javbw
Sent from my iPhone
On Mar 8, 2015, at 7:19 AM, Kotya Karapetyan kotya.li...@gmail.com wrote:
On Sat, Mar 7, 2015 at 10:24 PM, Andreas Goss
It should be found because OSM is a geographical database and the
reception, or the multiple receptions
as you asked before, is/are contained in the campus of the facility.
So bascially most of the time you would just tag amenity=reception_desk
without any other tags and that's enough?
Apart
On Sat, Mar 7, 2015 at 10:24 PM, Andreas Goss andi...@t-online.de wrote:
And if I'm a visitor how would for example a OSM based navigation system
figure out to which company or facility they belong?
I think it's a relevant point. I would include the
company/hospital/university etc. name in
What information would the visitor have to select the company/facility?
The name? The address?
If the visitor does not know then they go to the nearest one and ask..
at least the visitor has an indication of where a reception desk is
rather than just a collection of buildings/entrances.
On
Do you 'navigate' to 'drinking water' or simply look for the closest one?
Depends if I said I will meet someone at drinking water spot xyz or I'm
just looking for some water.
most would navigate to an address .. then look on the map for parking,
then look on the map for the closest
And if I'm a visitor how would for example a OSM based navigation system
figure out to which company or facility they belong?
On 3/7/15 22:11 , Kotya Karapetyan wrote:
I believe it depends on the facility. My company has 3 receptions, and
they are called officially Reception 7, 4 and 8; these
Kotya Karapetyan wrote on 2015-03-07 23:19:
On Sat, Mar 7, 2015 at 10:24 PM, Andreas Goss andi...@t-online.de
mailto:andi...@t-online.de wrote:
And if I'm a visitor how would for example a OSM based navigation system
figure out to which company or facility they belong?
It should be
On Sat, Mar 7, 2015 at 11:50 PM, Warin 61sundow...@gmail.com wrote:
Do you 'navigate' to 'drinking water' or simply look for the closest
one?
Most would navigate to an address .. then look on the map for parking,
then look on the map for the closest reception desk ..
I think there is a
On 8/03/2015 10:22 AM, Andreas Goss wrote:
Do you 'navigate' to 'drinking water' or simply look for the closest
one?
Depends if I said I will meet someone at drinking water spot xyz or
I'm just looking for some water.
most would navigate to an address .. then look on the map for parking,
On 8/03/2015 10:51 AM, Andreas Goss wrote:
It should be found because OSM is a geographical database and the
reception, or the multiple receptions
as you asked before, is/are contained in the campus of the facility.
So bascially most of the time you would just tag
amenity=reception_desk
On 8/02/2015 11:11 PM, AYTOUN RALPH wrote:
I have to admit I admire the problem but do not have an answer.
What I would like to suggest that dropping the desk part and just
using reception could make it more conducive to the various
applications being discussed.
It could then be added as a
As
this tag is always going to be used within another entity I think we should
rather look towards something like indoor tagging or other subtags. In
addition using amenity for reception desk would for example prevent you from
placing it on the node of the amenity and use one node for both.
Not
I have to admit I admire the problem but do not have an answer.
What I would like to suggest that dropping the desk part and just using
reception could make it more conducive to the various applications being
discussed.
It could then be added as a subcategory to the area/building such as
Amenity is the best fit for this tag.
I disagree. (Usually that just means I didn't find anything better) As
this tag is always going to be used within another entity I think we
should rather look towards something like indoor tagging or other
subtags. In addition using amenity for reception
Amenity is the best fit for this tag.
I disagree. (Usually that just means I didn't find anything better)
+1
Amenity is very vague in general (), and a lot of things can be
marked as such. So I'd prefer to use it only when it's an obvious
choice or there is nothing better.
What about using
On February 7, 2015 10:41:17 AM CST, Kotya Karapetyan kotya.li...@gmail.com
wrote:
Amenity is the best fit for this tag.
I disagree. (Usually that just means I didn't find anything
better)
+1
Amenity is very vague in general (), and a lot of things can be
marked as such. So I'd
On Sat, 2015-02-07 at 17:41 +0100, Kotya Karapetyan wrote:
...
Amenity is very vague in general (), and a lot of things can be
marked as such. So I'd prefer to use it only when it's an obvious
choice or there is nothing better.
Well, while I agree that Amenity is pretty general, but
On 8/02/2015 3:41 AM, Kotya Karapetyan wrote:
Amenity is the best fit for this tag.
I disagree. (Usually that just means I didn't find anything better)
+1
Amenity is very vague in general (), and a lot of things can be
marked as such. So I'd prefer to use it only when it's an obvious
choice
On 7/02/2015 9:15 PM, Andreas Goss wrote:
Amenity is the best fit for this tag.
I disagree. (Usually that just means I didn't find anything better)
As this tag is always going to be used within another entity
Always is such a large word. What about a hut that is used only for
reception?
Maybe there is a need for something like… a tag for office=* which may cover
the different public or employee facing building types
where the common facilities you would find in each category would be taggable,
so you can tag a point or a building as certain types of facilities.
Reception is used for tourists, but also is common for any large office complex
or even a industrial plant.
People visiting the plant (for work related activities) would go to reception,
check in, and get a visitors badge.
I think there is a difference between a person on vacation and a
On Fri, 2015-02-06 at 13:58 +0100, Janko Mihelić wrote:
Why not tourism=reception_desk? We have tourism=hotel,
tourism=camp_site, tourism=information, it's only logical to use the
same key.
I think the idea of =reception_desk could be applied much more widely
than just tourism. Commercial
On February 6, 2015 4:10:23 PM CST, David Bannon dban...@internode.on.net
wrote:
On Fri, 2015-02-06 at 13:58 +0100, Janko Mihelić wrote:
Why not tourism=reception_desk? We have tourism=hotel,
tourism=camp_site, tourism=information, it's only logical to use the
same key.
I think the
On Fri, 2015-02-06 at 11:16 +, Dan S wrote:
However it occurs to me that it would be useful to have some way of
indicating _what_ it is the reception for.
In a lot of cases, we'd probably see a larger area mapped as something,
be it caravan park, mine, whatever. Then a single node
I think this proposal is very relevant for some larger hotel and
resorts. I've been myself a few times in a situation when I had to
search for the reception over a large area. It can be a trouble if you
simultaneously have to get rid of your car in a parking restricted
area. Same for
Hi,
No big objections from me, sounds useful.
However it occurs to me that it would be useful to have some way of
indicating _what_ it is the reception for. For example, if it was part
of a site relation*, then a role like role=reception would connect
it to the larger entity in a meaningful way.
On February 6, 2015 9:37:20 AM CST, Tobias Knerr o...@tobias-knerr.de wrote:
On 06.02.2015 12:16, Dan S wrote:
However it occurs to me that it would be useful to have some way of
indicating _what_ it is the reception for. For example, if it was
part
of a site relation*, then a role like
On Feb 6, 2015, at 2:18 PM, Paul Johnson ba...@ursamundi.org wrote:
This seems to have a bit of overlap with information to a large extent. Most
have tourism information for the area they're located and vicinity and can
provide a lot of the same stuff as a general tourism information
Why not tourism=reception_desk? We have tourism=hotel, tourism=camp_site,
tourism=information, it's only logical to use the same key.
Janko Mihelić
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
On 06.02.2015 12:16, Dan S wrote:
However it occurs to me that it would be useful to have some way of
indicating _what_ it is the reception for. For example, if it was part
of a site relation*, then a role like role=reception would connect
it to the larger entity in a meaningful way. That
This seems to have a bit of overlap with information to a large extent.
Most have tourism information for the area they're located and vicinity and
can provide a lot of the same stuff as a general tourism information office
would. They just also rent space to park an RV (or even an RV or cabin),
48 matches
Mail list logo
