On Wednesday 08 August 2018, peterkrauss wrote:
>
> > has been an important point of
> > critique of the whole 'adding wikidata IDs to OSM' movement. You
> > can read this up in the previous discussion here and in talk.
>
> Can you send the main links?
No, i can't.
There is a large number of dis
For cities there must be a point associated to the polygon to tell where
the center is (maybe 2 if the city is poly centric, like Budapest maybe ?)
djakk
Le mer. 8 août 2018 à 05:25, Warin <61sundow...@gmail.com> a écrit :
> On 08/08/18 12:52, Bill Ricker wrote:
>
>
>
> On Tue, Aug 7, 2018 at 6
I think that location=underwater is more exact that surface=water. With the
second I expect to walk over the water like Jesus.
Javier
El mié., 8 ago. 2018 a las 1:13, Warin (<61sundow...@gmail.com>) escribió:
> On 08/08/18 09:01, marc marc wrote:
> > Le 08. 08. 18 à 00:26, Warin a écrit :
> >> A
> The centre of a place is a little cultural, a little of frequent use and a
> little from signs.
> In Europe I suspect it is the railway station ..lots of signs pointing there.
> In rural Australia I would go with the post office, though the pub is quite
> popular. :)
In Belgium I would assume
Please see:
https://wiki.openstreetmap.org/wiki/Talk:Multilingual_names#Slash.2C_space.2C_or_spaced_hyphen.3F
where I wrote:
This page (and perhaps actual practice) is inconsistent in suggesting:
* slashes: name=L'Alguer/Alghero (New Zealand, Portugal, Sardinia)
* spaced hyphens: name=Rue d
I also agree with the location tag as it say it is underwater, while the
other method say that the path is made of "water" (as it would be made of
gravel or asphalt in other places).
Note that the tag layer=-1 don't mean anything by itself (if there is no
other data at the same location) as it is
sent from a phone
> On 8. Aug 2018, at 05:24, Warin <61sundow...@gmail.com> wrote:
>
> The centre of a place is a little cultural, a little of frequent use and a
> little from signs.m
I’ve written 2 diary entries about the centres of Rome and Berlin, maybe it is
of interest in this context:
sent from a phone
> On 8. Aug 2018, at 02:12, Warin <61sundow...@gmail.com> wrote:
>
> Humm
>
> highway=path
>
> layer=-1
>
> surface=water
-1 to surface water, because surface is about the surface of the path.
I would also go with location=underwater
cheers,
Martin
sent from a phone
> On 8. Aug 2018, at 14:19, Andy Mabbett wrote:
>
> Greater consistency would surely be advantageous?
I prefer the slash, because hyphens occur in names, while I haven’t yet
encountered a name with slashes
cheers,
Martin
___
T
Osmose generates an error if you use a slash. I don't see consistency as an
advantage. It's a local decision.
If the names use different writing systems (as in the HK example) a space
is sufficient.
Slashes do occur in names, but surely more rarely than embedded hyphens. I
think the spaced hyphen
It's mostly our names did have hyphens, but none had hyphens with spaces
around them. Annoyingly we still get in trouble for those cases where both
sides of the street have different names... They exist, but they are rare
enough not to cause real headaches.
Op wo 8 aug. 2018 om 17:44 schreef Johnp
On Mon, Aug 6, 2018, 03:32 Martin Koppenhoefer
wrote:
Generally properties on the main highway are often a more useful
> representation than dedicated ways, but if you go into details it can be
> better to have a dedicated way (or you will have to split the main highway
> into lots of tiny fragme
Hi peterkrauss,
Am 08.08.2018 um 03:18 schrieb Nelson A. de Oliveira:
> On Tue, Aug 7, 2018 at 9:22 PM, Yuri Astrakhan
> wrote:
>> Nelson, there are several places I have seen in our wiki, e.g. [1], which
>> discourage duplication of information if it can be avoided. name is a
>> special case -
sent from a phone
> On 8. Aug 2018, at 00:35, Yuri Astrakhan wrote:
>
> For this specific case, the railroad stations consumer would probably want a
> single raiway station, not multiples, so they are easier to analyze, easier
> to query by matching it up with wikidata, etc.
For railway s
what about natural=clearing? I don’t see “clearing” as a landcover value that
suits. Landcover is about what is there physically, “clearing” is about the
absence of what was there before.
Cheers,
Martin
sent from a phone
> On 6. Aug 2018, at 02:11, Warin <61sundow...@gmail.com> wrote:
>
> H
sent from a phone
> On 8. Aug 2018, at 02:22, Yuri Astrakhan wrote:
>
> If we duplicated everything, than each part of a railroad station should have
> duplicate web site URL, hours of operation, operator name, and tons of other
> info.
I don’t know what situation you are referring to, and
sent from a phone
> On 8. Aug 2018, at 17:43, Johnparis wrote:
>
> Osmose generates an error if you use a slash.
Osmose could be fixed, I don’t see it has any authority on what is correct or
not, it is just a tool to help you find situations where something might
eventually be suspicious,
I suspect that the different punctuation marks on OSM are a
consequence of different writing habits in the respective regions,
which i recommend to follow.
For example, in English-speaking regions and in Switzerland the slash
without spaces is used (e.g. Biel/Bienne), unless one of the two names
a
> the slash without spaces is used (e.g. Biel/Bienne), unless one of the
two names already has a space, in which case the slash is usually set
with spaces
(e.g. Bielersee / Lac de Bienne).
This I would support. It is generally used and understood like this in
Nederland as well. The remark that if
Other mappers and me are just an absolute minimum, negligible part of
the whole community. Until this is not included in the wiki, it is
hardly known by anyone.
Someone said that this is not a condition for appearance or I
misunderstoodsg?
Szem
2018.08.07. 22:57 keltezéssel, Martin Koppenhoef
ones come before
>> landcover=clearing to discourage it use. The simplest option first - map
>> what is there - as that is the easiest option. If they cannot determine what
>> is there then the next option - map the surrounds. Then the combination of
>> the first two.
(I think I did something wrong and I have been corrected hopefully this is the
correct way to contribute to this list)
I wanted to add my input here as I have done work in several different
countries with several different naming schemes.
It is my interpretation that the goal of this discussio
My understanding was that the discussion is about when both names are
indicated on the name signs and no definite preference is clear. The
method of exactly representing the sign (just copy the string) fails
because usually the names are given as two strings or even as two signs.
Op wo 8 aug. 201
*Daniel McCormick wrote: "I propose that only one language is used for the
name= tag"*
This fails immediately in bilingual countries like Belgium, and also fails
in countries like Morocco, where the predominant language is Arabic, but
the two legal languages are Arabic and Tamazight, while a major
On Wed, 8 Aug 2018 at 20:03, Daniel McCormick wrote:
> I propose that only one language is used for the name= tag. This will help to
> create a standard for naming that will bring clarity and consistency. If
> multiple languages are used in the area, place the most commonly used
> language in t
Wow, thanks Martin - amazing stuff
Thanks
Graeme
On 8 August 2018 at 23:11, Martin Koppenhoefer
wrote:
>
>
> sent from a phone
>
> On 8. Aug 2018, at 05:24, Warin <61sundow...@gmail.com> wrote:
>
> The centre of a place is a little cultural, a little of frequent use and a
> little from signs.m
There are some who would then say that a 'clearing' that is made by man
should not be in the key 'natural' but in the key 'man_made'.
A 'clearing' may not have ever had the surrounding vegetation - an area
of rock for example.
The 'clearing' is about a change in the land cover, not about an
+1
the current proposal of the page seems to me to be a good promise to
improve the current situation while remaining realistic with the fact
that some mapper do not always have all the information or all the
knowledge to make the perfect solution.
in this sense the page is well enough to push g
name must be only one name of course faild with bilingual area.
of course local communities have the rules that apply to this situation
and try to impose a single rule on the world will fail
but Andry's message seems imho a good idea :
having only-one rule that can be used everywhere is better tha
Hi
2018-08-05 21:48 GMT+02:00 Paul Allen :
> Most of them have specific meanings with regard to
> electrical distribution and attachment is the only applicable one I can
> see that doesn't also have an electrical meaning
> (coupling often indicates that it transmits electrical or mechanical
> pow
On 09/08/18 08:47, marc marc wrote:
+1
the current proposal of the page seems to me to be a good promise to
improve the current situation while remaining realistic with the fact
that some mapper do not always have all the information or all the
knowledge to make the perfect solution.
in this sens
W dniu 07.08.2018 o 15:24, Christoph Hormann pisze:
> I think you have not understood the difference between measurement
> tolerance and convergence here.
I'm not sure what do you mean by "convergence", but there's no
measurement tolerance problem, because without accepting area as a base
and wit
On Tue, Aug 7, 2018 at 10:11 PM Graeme Fitzpatrick
wrote:
>
> Yep, Kevin's proposal solves a lot of problems.
>
> Let's try to push it along & get it approved.
I haven't forgotten. I'm just going through a crunch time at work, and
haven't had time to draft the thing formally.
___
> Do you agree to currently tag this as tower:type=suspension and maybe
later according to proposal as line_clamp=suspension? Is there an opposite
of suspension in English?I only find "suspension" in IEC vocabulary
After perusing Electropedia (IEC), I noticed some of the clamp entries
referred to
On Wed, Aug 8, 2018 at 8:11 PM, Kevin Kenny
wrote:
> I haven't forgotten. I'm just going through a crunch time at work, and
> haven't had time to draft the thing formally.
>
As mentioned by Paul earlier in this thread, it looks like you already put
together a pretty solid draft two years ago (as
Andy,
Can you please elaborate a bit on the reason for your question ?
Is it because you want a map with a uniform syntax for multiple names ?
I assume it is not because humans do not understand the meaning of
one of the following forms Biel / Bienne, Biel/Bienne, Biel - Bienne,
Biel (Bienne)
Or
Op do 9 aug. 2018 om 07:18 schreef Marc Gemis :
> Andy,
>
> Can you please elaborate a bit on the reason for your question ?
> Is it because you want a map with a uniform syntax for multiple names ?
> I assume it is not because humans do not understand the meaning of
> one of the following forms
sent from a phone
> On 8. Aug 2018, at 19:42, Szem wrote:
>
> Other mappers and me are just an absolute minimum, negligible part of the
> whole community. Until this is not included in the wiki, it is hardly known
> by anyone.
it is already included in the wiki, there’s the proposal linked
On Thursday 09 August 2018, Daniel Koc4� wrote:
>
> I like real life detailed data, but even in theory it's clear for me
> that while people might want some points, they are just what I've
> said - generalizations. [...]
No, as i have written and explained this is fundamentally wrong. But it
is
sent from a phone
> On 9. Aug 2018, at 07:17, Marc Gemis wrote:
>
> The name field is just a label. If you want to know the exact name in
> a certain language you look at the name:xx field.
the question is about the “name in the local language”.
cheers,
Martin
_
40 matches
Mail list logo
