On 5/02/2015 12:04 PM, Dave Swarthout wrote:
On Thu, Feb 5, 2015 at 7:10 AM, Warin 61sundow...@gmail.com
mailto:61sundow...@gmail.com wrote:
You mean a one step? Like highway= x ?
To do that I'd think a new supper key waste= at the top level!
And maybe that is what it needs!
Hi!
Is it just me or is currently the whole planet flooded on the main map? At
least at zoom level 1-6. Starting with 7 countries reappear.
regards,
Martin
___
Tagging mailing list
Tagging@openstreetmap.org
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
I think relation street applies to all the way segments of the whole street
with the same name (if in the same municipality), but I didn't check to be
honest.
2015-02-06 19:44 GMT+01:00 Luca Sigfrido Percich luca.perc...@gmail.com:
Many thanks Jo!
Volker also suggests that I should see how
On Fri, Feb 6, 2015 at 6:50 PM, Martin Vonwald imagic@gmail.com wrote:
Is it just me or is currently the whole planet flooded on the main map? At
least at zoom level 1-6. Starting with 7 countries reappear.
It's flooded, yes.
(but tagging isn't the proper place to ask this :-))
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 2015-02-06 21:11, Jo wrote :
I think relation street applies to all the way
segments of the whole street with the same name (if in the same
municipality), but I didn't check to be honest.
Those kinds of relations are made to unsplit
Courtyards use to be mapped as inner members of building multipolygons. We
can also use the multipolygon relation to assign a name to the bullding. If
we want to assign a name to the courtyard, we must assign it to the way. But
then we need some kind of physical tag in addition. Applications won't
On Fri, 2015-02-06 at 19:31 +1100, Warin wrote:
reasoned arg against (eg) amenity=waste_dog_excrement
Yes, Warin, you are probably right, while a more sensible syntax, it
will be resisted as too big a change.
An alternative might be to declare that (eg) waste=waste_dog_excrement
is on
I didn’t know that courtyards have their own name ;-)
In general, it seems a good idea to have a tag (apart from name=*) on
the inner line of the multipolygon. But I would avoid the key place=*
because this key is rather used for bigger features and seems to not
fit well. Maybe there is another
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
imho a courtyard is related to leisure.
why for: because a courtyard matters to people with leisure time and it is
a luxury of sorts.
why against: perhaps a courtyard is a sequestered area/way as it is often
tagger highway designated footpath as an area, an area that is a Very big
way for foot
That's how it was initially done in most places, before we started mapping
those tracks in more detail, which became possible thanks to improved
resolution of the aerial imagery (and in the case of Brussels, thanks to
UrbIS opening the data)
Jo
2015-02-07 4:02 GMT+01:00 James Mast
On Mon, Feb 2, 2015 at 7:53 AM, Janko Mihelić jan...@gmail.com wrote:
But what if hikers still refer to the spot? Like Let's go to the burnt
alpine hut, and then go left. That is a pretty important landmark, even if
there is no sign of the hut any more. Maybe we can tag it as place=locality.
The reason to use separate ways for trams can be seen in the other tram
tracks I mapped:
http://www.openstreetmap.org/#map=18/50.83181/4.33280
You can clearly see that very often the rails don't follow the asphalt
where the cars drive. Cars can make 90 degree turns, the tram rails need to
follow
Nelson A. de Oliveira wrote on 2015-02-06 21:52:
On Fri, Feb 6, 2015 at 6:50 PM, Martin Vonwald imagic@gmail.com wrote:
Is it just me or is currently the whole planet flooded on the main map? At
least at zoom level 1-6. Starting with 7 countries reappear.
It's flooded, yes.
(but tagging
2015-02-06 17:29 GMT+01:00 Luca Sigfrido Percich luca.perc...@gmail.com:
We could also user a lanes modifier:
lanes=3
lanes:backward=2
tram:lanes:backward=yes|no
tram:forward=yes
I think this is the best way to tag this. There's a great map paint style
for seeing roads in towns in JOSM,
Here's how we have done this in the Pittsburgh, PA area where the 'light rail'
line shares the pavement with the normal road lanes. They normally only use
this line during the rush hours unless they have
to close the tunnel @ Station Square and divert the light rail traffic
along this route.
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.
If we're going to have a temperature key - there should be some qualitative
values in human understandable ranges. Yes, they are subjective.
Cool/ cold / frozen / danger-cold
Warm / hot / boiling / danger-hot
Mild (human range comfortable, both hot and cold)
This allows tagging for objects /
1) +1 to drop Kelvins.
2) heated/cooled is a nice idea, but I wouldn't like seeing too many
top level tags.
temperature=heated
temperature=cooled
would be my preferred way to go.
I don't like :hvac too much either, because then what do I do if I
have AC + fireplace + central heating and use all
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
In the USA occasional sections of even Interstate highways are open to
bicycles,
where no equivalent route exists. There's some argument to tag these as
bike paths to avoid the tag soup of lanes,
and ensure the (unusual) situation is perfectly clear.
___
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
Am 06.02.2015 um 14:00 schrieb Bryce Nesbitt:
In the USA occasional sections of even Interstate highways are open to
bicycles,
where no equivalent route exists. There's some argument to tag these as
bike paths to avoid the tag soup of lanes,
and ensure the (unusual) situation is perfectly
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
Ciao,
hai guardato come l'hanno fatto altre città che hanno tram su strada? Mi
vengono in mente:
Strasbourg, Muenchen, Karlsruhe, San Francisco, Basel, ...
Cari saluti
Volker
Padova, Italy
On 6 February 2015 at 17:29, Luca Sigfrido Percich luca.perc...@gmail.com
wrote:
Hi all,
first time
Hi all,
first time I write to the list (after lurking for a while), so I introduce
myself. I am from Milano - Italy, I work for the municipality's agency for
environment and mobility, and we'we been working for the last months to
integrate our road graph with OSM.
Currently in Milano all tram
Ciao Luca,
For an example of a road with many variations in how the tram tracks are
embedded, you can have a look at this stretch I mapped a few months ago:
http://www.openstreetmap.org/#map=16/50.8601/4.3117
To indicate how they belong together, maybe a street or associatedStreet
relation
Many thanks Jo!
Volker also suggests that I should see how things are mapped in other major
cities, and so I'll do.
So you confirm that there isn't an established way of expressing the
tram-in-road relationship?
The use of the street relation has been suggested by a fellow member of the
italian
33 matches
Mail list logo
