On 25/3/20 10:30 pm, Martin Koppenhoefer wrote:
Am Mi., 25. März 2020 um 10:27 Uhr schrieb Frederik Ramm
mailto:frede...@remote.org>>:
In my opinion, a name:xx tag should only be added if you can
demonstrate
that people natively speaking the living language xx are actually
using
On 26/3/20 2:05 pm, Warin wrote:
Some tags used at present are;
alt_nameAyers Rock
alt_name:cs Ayersova skála
alt_name:en Ayers Rock
nameUluṟu
That's odd. The big red rock in the middle of Australia is called
Uluru / Ayers Rock
https://www.ntlis.nt.gov.au/placenames/view.
Hi Joseph,
Would segregation of data via a namespace tagging solution, as an
alternative to using place=refugee_site, address these concerns regarding
fuzzy "place" boundaries and the lack of observability (ie source based
descriptive data)?
Best regards,
Stuart
On Thu, Mar 26, 2020, 00:40 Jos
Am Mi., 25. März 2020 um 15:23 Uhr schrieb Joseph Eisenberg <
joseph.eisenb...@gmail.com>:
> > "if the name is otherwise regarded correct by mainstream media or a
> language authority."
>
> In that case, please add it to wikidata with a reference, but it would
> not be appropriate for Openstreetma
Some tags have been approved which allow for adding such details under the
barrier:-tag, e.g. https://wiki.openstreetmap.org/wiki/Key:barrier:personnel
This is the original proposal:
https://wiki.openstreetmap.org/w/index.php?oldid=840159#Combinations_.2F_Subtags
Unfortunately, the other addition
Names in OSM map is to show the world reader what each objects are.
Unlike Wikipedia and Wikidata, OSM map everything on the ground.
Let assume the world's common language is now priparaish, and English is
now only spoken by a small insignificant African tribe, and is also the
only language in the
I was blissfully unaware of the issues involved in creating a bilingual map
(dual labeled in the local language and in my language) until I actually tried
to create one.
Most objects in OSM do not have name: tags for non-local languages and it
is unreasonable to expect that every named village,
sent from a phone
> On 26. Mar 2020, at 23:54, Tod Fitch wrote:
>
> 2. Create a scheme where a default language can be set on boundaries as has
> been suggested by Joseph Eisenberg [4]. This has the advantage that
> relatively few objects need to be tagged, for example it might be possible
Note that there were several rejected proposals before mine, including
these two by Sommerluk:
https://wiki.openstreetmap.org/wiki/Proposed_features/Language_information_for_name
(name:language=*)
https://wiki.openstreetmap.org/wiki/Proposed_features/Language_information
(language:*=*)
And note
Hi all,
The line_management=* proposal vote will be open starting on next Monday.
https://wiki.openstreetmap.org/wiki/Proposed_features/Lines_management
Clarifications and improvements have been made as follow :
* Focus on power only and remove telecom usecase. Proposed terminology is
generic eno
The explanation of line_management=branch is not very clear:
"==Loops are actual branches==
Former undocumented key {{Tag|branch:type}} had a value for
connections between several power lines coming from the same
direction: ''loop''.
"It is proposed to consider them as branches due to
[http://osm
On 27/03/2020 00.51, Martin
Koppenhoefer wrote:
sent from a phone
On 26. Mar 2020, at 23:54, Tod Fitch wrote:
2. Create a scheme where a default language can be set on boundaries as has been suggested by Joseph Eisenberg [4]. This has the advant
12 matches
Mail list logo
