We are currently trying on the Italian mailing list to get a good tagging
for the ZTL (zona a traffico limitato - limited traffic zone), which do
exist in various Italian cities and are not LEZ (low emmission zones)
because the latter according to the wiki and external definitions are zones
which
sorry, didn't see your email earlier.
On Sat, Nov 08, 2014 at 09:27:03AM +0100, Andreas Goss wrote:
The club page seems to suggest
that club=sport + sport=cycling type tagging should be used for competitive
sports.
Which in my optinion is a bad idea, too. There is really no generel
2014-11-24 13:57 GMT+01:00 Richard Z. ricoz@gmail.com:
According to the approved
http://wiki.openstreetmap.org/wiki/Proposed_features/Club
chess has an own club=chess, as has fishing, automobile, hiking - all
of which can be either leisure type or sport type activities.
I think
On Mon, Nov 24, 2014 at 02:13:07PM +0100, Martin Koppenhoefer wrote:
2014-11-24 13:57 GMT+01:00 Richard Z. ricoz@gmail.com:
According to the approved
http://wiki.openstreetmap.org/wiki/Proposed_features/Club
chess has an own club=chess, as has fishing, automobile, hiking - all
of
Let's look at the entity relations in play here. Surely a club IS an
organisation, not a building. The club MAY USE one or more buildings,
and MAY OWN one or more buildings. A club HAS a contact address, HAS
members, HAS a board etc etc. So following the rules of one object,
one set of tags,
Hi Rainer and thank you.
I didn't spend time yet on the update done on the Pipeline proposal but be
sure I will.
What were the concern against network=* tag ?
If they can be avoided with usage=* (or any common key) I'm ok to join you
to use the same between power transmission and pipelines.
On Mon, Nov 24, 2014 at 02:53:32PM +0100, Colin Smale wrote:
Let's look at the entity relations in play here. Surely a club IS an
organisation, not a building. The club MAY USE one or more buildings,
and MAY OWN one or more buildings. A club HAS a contact address, HAS
members, HAS a board
Okay, so I would place a hint at the corresponding wiki page …
Lukas Sommer
2014-11-23 18:46 GMT+00:00 Zecke z...@saeuferleber.de:
Am 23.11.2014 18:20, schrieb Lukas Sommer:
Would a feature proposal be a good way to get there?
No need to do so. The semi-colon is the accepted way to
Am 24.11.2014 um 20:32 schrieb Lukas Sommer:
Okay, so I would place a hint at the corresponding wiki page …
+1
Do we recommend any order ? youngest to oldest ?
2014-11-23 18:46 GMT+00:00 Zecke z...@saeuferleber.de
mailto:z...@saeuferleber.de:
Am 23.11.2014 18:20, schrieb Lukas Sommer:
On 23.11.2014 19:46, Zecke wrote:
Am 23.11.2014 18:20, schrieb Lukas Sommer:
Would a feature proposal be a good way to get there?
No need to do so. The semi-colon is the accepted way to separate multi
values in cases where there's no other scheme defined.
Hi,
On 11/24/2014 11:51 PM, Tobias Knerr wrote:
The semi-colon is not universally accepted, for good reasons. Contrary
to what you said, it should only be used if it is explicitly defined as
an option for that particular key. To introduce such a convention to an
old and widely used set of
+1
I agree with alt_name=name1;name2
On Mon, Nov 24, 2014 at 1:20 AM, Lukas Sommer sommer...@gmail.com wrote:
Some time ago, there was a discussion on the “talk” mailing list about how
to deal with the situation of more than one alt_name:
Hi,
On 11/25/14 00:35, Frederik Ramm wrote:
There was a discsussion on the talk/imports lists recently (September,
Duh. I should have read Lukas' post before writing ;)
Bye
Frederik
--
Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33
13 matches
Mail list logo
