Thanks for the update of the wiki. I added one of my photos.
Best regards,
Martin
2013/2/26 Alberto albertoferra...@fastwebnet.it:
To Martin Vonwald.
I've added field_shelter here [1].
Can you upload a picture for it? I haven't one and I don't want to upload a
copyrighted picture.
[1]
2013/2/26 Janko Mihelić jan...@gmail.com:
Hi,
I made a wikidata tag proposal, here is the link:
http://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata
I think connecting our data with wikidatas data would give us a big
potential. It's as easy as giving our entities a wikidata=Qxxx
On Wed, Feb 27, 2013 at 11:56 AM, Martin Koppenhoefer
http://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata
I like the idea to use URIs for operators,
Tag operator:wikidata=Q38076 much better than operator=McDonalds ?!
Are you all so disconnected from real contributors ?
Pieren
I added a wikidata tag to our main church:
http://www.openstreetmap.org/browse/changeset/15183730
What is the (intended) effect?
Will it be possible to visualise it somewhere?
Jo
2013/2/26 Janko Mihelić jan...@gmail.com
Hi,
I made a wikidata tag proposal, here is the link:
2013/2/27 Steve Bennett stevag...@gmail.com
It's worth menitioning that Wikidata is still very new. How stable are
the IDs? Any policies around them?
Steve
Wikidata is pretty new, but it is already deployed on Hungarian, Hebrew,
Italian, and English Wikipedias. Deployed means that
On Wed, Feb 27, 2013 at 10:07 PM, Pieren pier...@gmail.com wrote:
Tag operator:wikidata=Q38076 much better than operator=McDonalds ?!
Are you all so disconnected from real contributors ?
In addition to, not instead of. operator:wikidata=* is computable.
Martin wrote:
What is the relation
2013/2/27 Martin Koppenhoefer dieterdre...@gmail.com
What is the relation between wikidata and wikipedia? Couldn't one get
the wikidata-reference code by looking up the wikipedia article name?
In this case it would be an unnecessary duplication of information to
also have a wikidata tag.
2013/2/27 Pieren pier...@gmail.com
Tag operator:wikidata=Q38076 much better than operator=McDonalds ?!
Are you all so disconnected from real contributors ?
Real contributors can continue to write operator tags. I'm always for
making it easier for the mapper. But why not help developers once
2013/2/27 Pieren pier...@gmail.com:
Tag operator:wikidata=Q38076 much better than operator=McDonalds ?!
Besides that McD is not the operator, this would be an additional way
to eliminate ambiguity in some cases, of course you could still be
mapping operator=* and it will be sufficient in many
2013/2/27 Janko Mihelić jan...@gmail.com:
2013/2/27 Martin Koppenhoefer dieterdre...@gmail.com
What is the relation between wikidata and wikipedia? Couldn't one get
the wikidata-reference code by looking up the wikipedia article name?
In this case it would be an unnecessary duplication of
Hi Balaitous,
I think trying to classify paths using a type or grade is the
wrong approach. The problem you're trying to solve is a real one:
trying to distinguish important trails from less important ones. So
why not just use that terminology:
importance=5 (most important trails, probably a GR
2013/2/27 Janko Mihelić jan...@gmail.com:
Right now we have 886 McDonald's, 53 McDonalds and 9
McDonald's␣Deutschland␣Inc. I'm not going to mass change them to what I
think they should be, because they all could have their reasons to give them
that operator name. But Wikidata ID should be
Am 27.02.2013 12:28, schrieb Janko Mihelic':
2013/2/27 Pieren pier...@gmail.com mailto:pier...@gmail.com
Tag operator:wikidata=Q38076 much better than
operator=McDonalds ?!
Are you all so disconnected from real contributors ?
Real contributors can continue to write operator
Balaitous wrote
1. Re: Proposition for a classification of path (Balaitous) Also, the
proposed path types would classify any path that ends in a cul-de-sac as the
least-used and least-maintained category, which isn't necessarily the case.
When I say cul-de-sac I refer to paths that go
I'm honestly appalled by some of the criticism here. I think this is a
great proposal and will be very useful once both sides are solid, with
WikiData hosting more and more information and OSM linking lots of objects
to a WikiData node.
As to the McDonalds/McDonalds Deutschland issue, think of a
On 27/02/13 11:37, Martin Koppenhoefer wrote:
2013/2/27 Janko Mihelić jan...@gmail.com:
2013/2/27 Martin Koppenhoefer dieterdre...@gmail.com
What is the relation between wikidata and wikipedia? Couldn't one get
the wikidata-reference code by looking up the wikipedia article name?
In this
On Wed, Feb 27, 2013 at 12:49 PM, Peter Wendorff
wendo...@uni-paderborn.de wrote:
If you keep the original operator, then I don't see the point.
Either the tags operator and operator:wikidata are different and
you have a real problem. Or the tags have the same values/meaning and
it is just
On 27/02/13 12:00, Simone Saviolo wrote:
I'm honestly appalled by some of the criticism here. I think this is a
great proposal and will be very useful once both sides are solid, with
WikiData hosting more and more information and OSM linking lots of
objects to a WikiData node.
For the record,
2013/2/27 Martin Koppenhoefer dieterdre...@gmail.com
Still, why wikidata if
you can use wikipedia?
Imagine a data consumer that wants to list all McDonalds in the World. If
he would try to go by wikipedia tag, he should search for de:McDonald's,
en:McDonalds, hak:Ma̍k-tông-lò Kûng-sṳ̂,
2013/2/27 Pieren pier...@gmail.com
On Wed, Feb 27, 2013 at 12:49 PM, Peter Wendorff
wendo...@uni-paderborn.de wrote:
About McDonalds or McDonald's, define the standard value, call
XAPI/overpass or keepright/osmose to find them and fix the wrong
values with JOSM. It takes 2 minutes and the
Am 27.02.2013 13:01, schrieb Pieren:
On Wed, Feb 27, 2013 at 12:49 PM, Peter Wendorff
wendo...@uni-paderborn.de wrote:
If you keep the original operator, then I don't see the point.
Either the tags operator and operator:wikidata are different and
you have a real problem. Or the tags have the
Adding Q38076 would probably introduce more errors, however if our editors
pulled the data from wikidata to give human readable names to pick from
then our data would become more accurate.
Clifford
On Feb 27, 2013 5:07 AM, Pieren pier...@gmail.com wrote:
On Wed, Feb 27, 2013 at 11:56 AM, Martin
On Wed, Feb 27, 2013 at 1:22 PM, Janko Mihelić jan...@gmail.com wrote:
First, how are you going to force a korean to put operator=McDonald's if he
calls it operator=맥도날드. He is not going to like it.
Second, what if there is a McDonald's in Malawi that has the same name as
the big American
2013/2/27 Pieren pier...@gmail.com
In my turn for questions, what are you doing if the wikidata is
refering to McDonald's but the tag name or operator is telling Burger
King ?
This proposal improves data consistency and relationship between data. Are
we really willing to reject it because
On Wed, Feb 27, 2013 at 1:33 PM, Peter Wendorff
wendo...@uni-paderborn.de wrote:
-1
You would create new bugs for the plumber McDonalds, the taxi company
McDonalds and many more, who are NOT named McDonald's (or vice versa).
I'm talking to amenity=fast_food + operator=McDonalds instead of
On Wed, Feb 27, 2013 at 1:43 PM, Simone Saviolo
simone.savi...@gmail.com wrote:
This proposal improves data consistency and relationship between data. Are
we really willing to reject it because the data we put in may be wrong?
No, Because it duplicates existing tags. Because it might create
2013/2/27 Martin Koppenhoefer dieterdre...@gmail.com
Yes, but the wikidata ID does not help in this case. McDonald's Corp.
is not the same as McDonald's Deutschland Inc., you can find
information about this in the German page, but not in other languages.
As long as wikidata only links to
2013/2/27 Pieren pier...@gmail.com
On Wed, Feb 27, 2013 at 1:43 PM, Simone Saviolo
simone.savi...@gmail.com wrote:
This proposal improves data consistency and relationship between data.
Are
we really willing to reject it because the data we put in may be wrong?
No, Because it duplicates
On Wed, Feb 27, 2013 at 2:06 PM, Simone Saviolo
simone.savi...@gmail.com wrote:
Because it might create inconsistencies.
Does not, as I pointed above. You don't use two tags at the same time for a
single piece of information. At most, you use a second fallback one _in case
the first is not
2013/2/27 Pieren pier...@gmail.com
On Wed, Feb 27, 2013 at 2:06 PM, Simone Saviolo
simone.savi...@gmail.com wrote:
Because it might create inconsistencies.
Does not, as I pointed above. You don't use two tags at the same time
for a
single piece of information. At most, you use a second
On 2013-02-27 12:08, Jo wrote :
I suggested to Waymarked Trail http://hiking.waymarkedtrails.org/en/
and I have mentioned to this list that any free format field like
operator should be explicitly allowed to contain an URL and that the
programs should auto-recognize URLs to make them
You call for editor support for a new external ID that's not controllable.
You want it to be a replacement (well, you agree to keep the old tags,
but your argumentation is that the old tags are not necessary any more
with the existence of Wikidata.
This contains several preconditions you
2013/2/27 Peter Wendorff wendo...@uni-paderborn.de
You call for editor support for a new external ID that's not
controllable.
You want it to be a replacement (well, you agree to keep the old tags, but
your argumentation is that the old tags are not necessary any more with the
existence of
Thank you for your photo. I've also updated the animal page [1] and I reused
your photo.
[1] http://wiki.openstreetmap.org/wiki/Animal
Bye
Alberto
Thanks for the update of the wiki. I added one of my photos.
Best regards,
Martin
___
Tagging
Dana srijeda, 27. veljače 2013., korisnik Peter Wendorff
wendo...@uni-paderborn.de je napisao:
You call for editor support for a new external ID that's not
controllable.
It isn't any less controllable then Wikipedia. But it is more reliable.
2) wikidata will not change the meaning of the
Hi,
You insinuate that I want to remove the other tags characterizing paths.
This is false.
What I propose is a new tag providing a summarized information, such
that no algorithm can do.
Besides, I think we should also tag of the markup, like
markup=yes/no
markup:quality= scale from 1 to 5
Le mardi 26 février 2013 à 15:19 -0500, Richard Welty a écrit :
i think it has the potential to be confusing, in part because tracktype
already exists
for highway=track, and tracktype is entirely about actual physical
characteristics.
i suspect it is a mistake to try to aggregate logical
37 matches
Mail list logo
