0:00:06.259,0:00:08.379
Hello. So, good afternoon.
0:00:08.379,0:00:11.919
Welcome to the OpenStreetMap[br]and Wikidata workshop.
0:00:11.919,0:00:13.479
My name is Eugene.
0:00:13.479,0:00:16.849
And together with Edward,[br]we'll be talking about OpenStreetMap
0:00:16.849,0:00:20.069
and how it can work together[br]with Wikidata.
0:00:20.118,0:00:21.718
So, just a show of hands.
0:00:21.718,0:00:24.638
Who here has an OpenStreetMap account?
0:00:26.538,0:00:30.638
Okay, some. So, probably[br]this is not new to you.
0:00:30.638,0:00:33.838
But for those who are not familiar[br]with OpenStreetMap,
0:00:33.838,0:00:37.348
I'll give an introduction[br]to OpenStreetMap and its data model.
0:00:37.348,0:00:39.478
So, basically, what is OpenStreetMap?
0:00:39.478,0:00:42.688
It is basically a crowdsourced project[br]to map the whole world.
0:00:43.579,0:00:46.608
And the usual way we introduce[br]OpenStreetMap to people
0:00:46.608,0:00:50.636
is like OpenStreetMap[br]is like Wikipedia for maps.
0:00:51.692,0:00:55.097
But actually, a more accurate way[br]to introduce OpenStreetMap
0:00:55.097,0:00:57.897
is that it is like Wikidata[br]for geographical data.
0:00:58.260,0:01:01.711
But that presupposes that the audience[br]already knows or is familiar
0:01:01.711,0:01:03.695
with what Wikidata is.
0:01:04.347,0:01:07.596
And why do we say[br]that OpenStreetMap is like Wikidata?
0:01:08.083,0:01:11.690
And that's because both[br]have quite a lot of things in common,
0:01:11.690,0:01:14.731
both being crowdsourced[br]and open data projects.
0:01:16.071,0:01:18.136
So, you know Wikidata--
0:01:18.136,0:01:20.938
it has items, statements,[br]properties, et cetera.
0:01:21.250,0:01:26.690
In the same way, OpenStreetMap[br]has things like nodes, ways, relations,
0:01:26.690,0:01:30.570
that have members and roles,[br]and these have tags
0:01:30.570,0:01:33.450
that are composed of keys and values.
0:01:34.230,0:01:40.236
So, as more detail, nodes, ways,[br]and relations model the geometry
0:01:40.236,0:01:42.380
and topology of objects.
0:01:42.971,0:01:46.950
And then, we have tags,[br]which are actually key value strings
0:01:46.950,0:01:51.040
that describe the actual things[br]that those objects represent.
0:01:51.920,0:01:57.760
So, to give an example,[br]here's the Wikidata item for Berlin.
0:01:57.790,0:02:02.530
So, we can have property[br]like population, 3 million something,
0:02:03.069,0:02:05.695
with a qualifier, point in time,[br]and references.
0:02:06.243,0:02:09.782
And they have counterparts[br]in OpenStreetMap.
0:02:09.782,0:02:13.136
So, for example, the Berlin relation[br]in OpenStreetMap
0:02:13.136,0:02:17.162
has the tag population is equal[br]to 3.4 million something,
0:02:17.662,0:02:23.662
and it has another tag, source:population[br]equals this URL and that date.
0:02:24.382,0:02:26.522
So, unlike in Wikidata,
0:02:26.522,0:02:29.762
wherein you can have qualifiers[br]and references for your statements,
0:02:29.762,0:02:32.412
in OpenStreetMap, the tag is quite flat.
0:02:32.912,0:02:36.452
There's no secondary levels of tags.
0:02:36.521,0:02:37.821
Everything is flat.
0:02:37.821,0:02:40.881
And that's why we have to put[br]what you call secondary tags.
0:02:40.912,0:02:43.732
So, for example here, source:population
0:02:43.732,0:02:46.963
to indicate that the population tag[br]has this source.
0:02:48.583,0:02:52.108
Another thing is that OpenStreetMap's tags[br]are not strictly controlled.
0:02:52.108,0:02:55.532
Unlike with Wikidata, wherein you have[br]to have approval process
0:02:55.532,0:02:57.583
before properties are created,
0:02:57.583,0:02:59.431
here, OpenStreetMap mappers
0:02:59.431,0:03:02.792
can invent and add[br]any tags that they like.
0:03:02.792,0:03:05.587
However, there is a tagging[br]proposal process
0:03:05.587,0:03:07.858
in order to propose common tags
0:03:07.858,0:03:11.391
that will be used by mappers[br]all over the world.
0:03:14.107,0:03:17.770
Okay, data modeling discussions[br]on the Wikidata:Project chat page
0:03:17.770,0:03:19.899
are actually quite similar[br]to the discussions
0:03:19.899,0:03:22.039
in OpenStreetMap's tagging mailing list.
0:03:22.659,0:03:26.709
For example, here's an example[br]of discussion on the project tag,
0:03:27.759,0:03:30.599
how do we model a building[br]that has changed its use?
0:03:30.599,0:03:33.393
In OpenStreetMap,[br]we have similar discussions.
0:03:33.393,0:03:35.819
How do we tag these sorts of buildings?
0:03:37.734,0:03:40.833
So, I've given an introduction[br]of what OpenStreetMap is.
0:03:40.833,0:03:45.293
I'd love to discuss it more,[br]but we don't have enough time.
0:03:45.429,0:03:48.772
So, we'll go into how do we link
0:03:48.772,0:03:51.392
between OpenStreetMap[br]and Wikidata together.
0:03:51.392,0:03:54.612
I don't have to explain[br]why linking is a good thing.
0:03:54.671,0:03:58.332
We're all Wikidatans, and we know[br]that linking data is a good thing.
0:03:59.052,0:04:03.012
So, how do we actually link[br]Wikidata with OpenStreetMap?
0:04:03.601,0:04:06.202
So, from Wikidata to OpenStreetMap,
0:04:06.681,0:04:10.721
Wikidata items on places can link[br]to OpenStreetMap relations
0:04:10.721,0:04:14.842
using the OSM relation ID,[br]or the P402 property.
0:04:15.442,0:04:17.612
So, the question is: why only relations?
0:04:18.133,0:04:20.861
That's because OSM IDs are not stable.
0:04:21.521,0:04:26.272
For example, you can change nodes[br]to represent a different object.
0:04:26.942,0:04:28.700
Ways can be split
0:04:29.760,0:04:34.550
to add new information about those ways.
0:04:35.410,0:04:42.326
However, relatively, relations[br]in OpenStreetMap are relatively stable.
0:04:42.860,0:04:47.349
At least for major relations,[br]such as administrative boundaries,
0:04:47.349,0:04:50.410
or highway routes,[br]or public transportation routes.
0:04:51.171,0:04:54.839
That way, you can link at least the,[br]for example, here,
0:04:55.219,0:04:57.639
Berlin Wikidata data edit item,
0:04:57.639,0:05:00.312
can link to the relation[br]representing the boundary
0:05:00.312,0:05:04.269
in OpenStreetMap via its ID.
0:05:05.260,0:05:09.310
In terms of the ontology,[br]Wikidata items and properties
0:05:09.310,0:05:13.489
for geographical features[br]can link to "equivalent," in quotes,
0:05:13.489,0:05:16.959
OpenStreetMap classes[br]using the OSM tag or key property.
0:05:17.399,0:05:22.759
For example, the lighthouse item[br]in Wikidata has the value
0:05:22.838,0:05:27.029
for OpenStreetMap tag or key[br]Tag:man_made=lighthouse.
0:05:27.279,0:05:32.369
That means that lighthouses are equivalent[br]to objects that are tagged
0:05:32.369,0:05:35.459
in OpenStreetMap[br]with man-made lighthouse.
0:05:37.379,0:05:41.489
Going in the other direction,[br]OpenStreetMap objects can link
0:05:41.489,0:05:44.859
to corresponding Wikipedia articles[br]and Wikidata items
0:05:44.859,0:05:48.340
using the Wikipedia[br]and Wikidata tags, respectively.
0:05:48.818,0:05:50.039
So, here's an example.
0:05:50.039,0:05:52.498
The OpenStreetMap relation for Berlin.
0:05:52.498,0:05:54.838
We have the Wikidata tag, Q64,
0:05:55.379,0:06:00.128
and the Wikipedia article[br]linking to the German article for Berlin.
0:06:02.158,0:06:04.678
There are also several Wikidata[br]secondary tags,
0:06:04.678,0:06:09.001
such as for example, brand:wikidata,[br]architect:wikidata, artist:wikidata,
0:06:09.001,0:06:11.196
or name:etymology:wikidata.
0:06:11.196,0:06:14.418
We use this in order to exactly specify
0:06:15.468,0:06:17.840
what we are referring to.
0:06:18.334,0:06:21.135
For example, on the top part here,[br]we have the example.
0:06:21.746,0:06:24.059
There's an artwork in OpenStreetMap
0:06:24.059,0:06:27.427
that was created[br]by the artist named Herakut,
0:06:27.876,0:06:29.215
but who is that?
0:06:29.215,0:06:32.669
So, in order to specify exactly,[br]we use artist:wikidata,
0:06:32.669,0:06:34.380
and that Q ID number.
0:06:34.383,0:06:39.530
So that you can be exactly sure[br]which Herakut artist it really is.
0:06:40.090,0:06:43.850
This is also useful, for example,[br]if you're tagging, for example,
0:06:46.090,0:06:48.700
objects in OpenStreetMap[br]that are in a different language.
0:06:48.700,0:06:52.856
For example, in Japan, you might have[br]a fast-food restaurant
0:06:52.856,0:06:56.437
called Makudonarudo,[br]which is actually McDonald's.
0:06:56.437,0:06:59.483
So, you can tag that using[br]the brand:wikidata tag
0:07:00.183,0:07:03.343
pointing to the McDonald's[br]item in Wikidata.
0:07:06.059,0:07:11.399
So, in terms of ontology,[br]we define and describe the tags
0:07:11.399,0:07:14.809
in OpenStreetMap[br]on the OpenStreetMap Wiki,
0:07:14.809,0:07:20.309
and we can add links to corresponding[br]Wikipedia articles and Wikidata items
0:07:20.729,0:07:25.688
so that we can sort of explain[br]the correspondences and relations
0:07:25.688,0:07:29.780
between these tags and items in Wikidata.
0:07:32.692,0:07:38.532
Okay, so how do OpenStreetMap[br]and Wikimedia use each other's data?
0:07:39.827,0:07:42.181
So, first, we have the interactive maps.
0:07:42.181,0:07:44.744
So, OpenStreetMap data powers
0:07:44.744,0:07:48.475
the Wikimedia Foundation's[br]Kartotherian map tile service,
0:07:48.475,0:07:51.242
which is used by the Kartographer[br]MediaWiki extension.
0:07:51.607,0:07:54.241
So, basically, any time you see[br]an interactive map
0:07:54.241,0:07:58.213
or almost any interactive map[br]on any Wikimedia project,
0:07:58.213,0:08:01.816
that is usually powered[br]by the Kartotherian map tile service.
0:08:02.263,0:08:07.004
For example, here's the interactive map[br]for Berlin in the English Wikivoyage.
0:08:07.695,0:08:11.583
So, the base map there is all coming[br]from OpenStreetMap.
0:08:13.446,0:08:16.811
So, another thing that[br]the Kartographer extension can do
0:08:16.811,0:08:20.332
is it can pull and overlay geometry[br]from OpenStreetMap.
0:08:20.778,0:08:25.799
So, here's the infobox on Commons[br]for the Berlin category.
0:08:26.324,0:08:30.953
And the map there, you can see[br]an outline for Berlin, there.
0:08:31.397,0:08:33.873
That outline comes from OpenStreetMap.
0:08:35.659,0:08:40.528
In 2008, the foundation released[br]localized map tiles for Kartotherian,
0:08:40.528,0:08:45.191
and this leveraged the multilingual[br]name tags in OpenStreetMap,
0:08:45.191,0:08:49.370
so that you can view those maps[br]that you see on Wikimedia projects
0:08:49.370,0:08:51.279
in the user's language.
0:08:53.067,0:08:56.229
Then, how do we use Wikidata[br]in OpenStreetMap?
0:08:56.594,0:08:59.270
For example, when tagging brands,
0:08:59.336,0:09:02.216
for example, in shops[br]and restaurants or banks,
0:09:02.986,0:09:07.726
OpenStreetMap's Name Suggestion Index[br]uses Wikidata to provide brand identity
0:09:07.726,0:09:09.326
and improved tagging.
0:09:09.326,0:09:13.306
So, for example, if you tag[br]an object in OpenStreetMap
0:09:13.306,0:09:18.456
with brand Wikidata pointing[br]to the McDonald's item in Wikidata,
0:09:19.886,0:09:22.937
the name field is now automatically locked
0:09:22.937,0:09:26.598
so that users cannot just change that[br]to, for example, Burger King.
0:09:27.567,0:09:32.523
And then, you can edit or also pull icons,
0:09:34.063,0:09:35.763
the McDonald's icon there
0:09:35.763,0:09:41.962
that is taken from the Facebook[br]item property
0:09:41.962,0:09:43.782
in Wikidata.
0:09:44.361,0:09:45.811
So, yeah.
0:09:45.811,0:09:50.111
So, that, at least, when users are tagging[br]these shops in OpenStreetMap,
0:09:50.111,0:09:52.751
they can be sure[br]that they're doing it correctly.
0:09:54.822,0:09:59.311
Okay, so Sophox is a SPARQL endpoint[br]for OpenStreetMap data.
0:09:59.771,0:10:04.081
So, this service can use RDF federation[br]to also query linked Wikidata items.
0:10:04.721,0:10:09.251
So, actually, in OpenStreetMap,[br]we usually use other query services,
0:10:09.251,0:10:11.041
such as Overpass.
0:10:11.421,0:10:16.771
But if you want to also query[br]using Wikidata items,
0:10:17.311,0:10:21.511
we have the Sophox endpoint[br]that you can use.
0:10:23.711,0:10:27.101
And for geocoding,[br]if you're not familiar with geocoding,
0:10:27.101,0:10:32.291
basically, that's the technology[br]wherein given an address,
0:10:32.831,0:10:37.097
you are returned geocoordinates.
0:10:37.825,0:10:42.900
So, we have what we call Nominatim,[br]which is the usual service
0:10:42.900,0:10:45.417
in OpenStreetMap for doing geocoding.
0:10:45.417,0:10:50.008
And previously, it already uses[br]Wikipedia tags in OpenStreetMap.
0:10:50.534,0:10:55.316
But this year, we added[br]Google Summer of Code project code
0:10:55.316,0:10:59.289
to integrate using Wikidata tags[br]in Nominatim,
0:10:59.289,0:11:02.855
so that search results[br]can become more relevant for users
0:11:02.855,0:11:05.084
who are doing the searches.
0:11:06.583,0:11:12.306
And for localization, Mapbox and MapTiler,[br]which are third-party companies
0:11:12.306,0:11:15.622
that extensively use OpenStreetMap,
0:11:15.622,0:11:18.787
they use Wikidata to power[br]their localized map products.
0:11:19.111,0:11:23.854
So, basically, if there[br]are missing name tags in OpenStreetMap,
0:11:23.854,0:11:29.937
and if that object is linked to Wikidata,[br]they can pull the labels from Wikidata,
0:11:29.937,0:11:35.217
and use that to show multilingual labels,[br]if that is missing in OpenStreetMap.
0:11:35.705,0:11:39.675
The reason for that is because[br]we have a philosophy in OpenStreetMap
0:11:39.675,0:11:45.603
that we do not try to add too many tags,[br]especially if that can be automated.
0:11:45.656,0:11:48.296
For example,[br]for automatic transliterations,
0:11:48.857,0:11:52.973
if that can be automated, we don't need[br]to add that to OpenStreetMap.
0:11:52.973,0:11:56.156
But in Wikidata, that's no problem.
0:11:56.156,0:12:01.184
So, you can do that by doing this linking[br]between OpenStreetMap and Wikidata.
0:12:01.184,0:12:06.616
You don't have to do[br]that transliteration on your own.
0:12:06.625,0:12:08.855
You can just pull it from Wikidata.
0:12:10.315,0:12:15.805
And also, the OpenStreetMap Wiki[br]has the Wikibase extension installed.
0:12:16.565,0:12:22.085
So, the idea here is that we want[br]the tag information or the description
0:12:22.085,0:12:27.025
or the description of the tags,[br]that we use in OpenStreetMap
0:12:27.025,0:12:28.905
to be machine-readable.
0:12:28.905,0:12:32.705
Hopefully, this will be used[br]by software and editors
0:12:32.705,0:12:38.096
that use OpenStreetMap data to better see
0:12:38.096,0:12:41.475
how objects are described[br]in OpenStreetMap.
0:12:41.995,0:12:43.995
Currently, this is not used as much,
0:12:43.995,0:12:48.935
but hopefully, as the tagging information[br]becomes more complete and better,
0:12:48.935,0:12:52.215
this can be used[br]by OpenStreetMap software,
0:12:52.215,0:12:54.755
thanks to the Wikibase installation.
0:12:56.195,0:12:58.635
Okay, some copyright and IP issues.
0:13:00.395,0:13:03.805
Wikidata can't import coordinates[br]from OpenStreetMap.
0:13:03.805,0:13:06.975
The reason for that is because[br]OpenStreetMap is licensed
0:13:06.975,0:13:09.675
under the Open Database License.
0:13:12.195,0:13:14.875
And also, we have conflicting doctrines.
0:13:14.875,0:13:19.118
Here in the European Union[br]and the United Kingdom,
0:13:19.215,0:13:20.974
we have database rights.
0:13:22.214,0:13:26.944
Whereas, in the US, we have the idea[br]that facts are not copyrightable.
0:13:27.364,0:13:32.034
So, we cannot just--[br]even though you cannot say--
0:13:32.034,0:13:35.954
you cannot copyright the fact[br]that this restaurant or this bank
0:13:35.954,0:13:39.804
or this place is at this location,
0:13:39.804,0:13:45.264
doing that as an import[br]or as a batch job
0:13:45.403,0:13:47.953
is not allowed
0:13:47.953,0:13:51.883
because OpenStreetMap[br]is protected by database rights
0:13:52.843,0:13:56.134
being hosted in the United Kingdom.
0:13:57.883,0:14:03.723
Conversely, OpenStreetMap[br]will not import geodata from Wikidata,
0:14:03.723,0:14:07.863
despite the CC0 license,[br]because of data provenance issues.
0:14:09.563,0:14:15.033
If you're not familiar[br]with how geocoordinates are added
0:14:15.033,0:14:19.723
into Wikipedia articles,[br]usually users just go to Google Maps,
0:14:20.353,0:14:24.173
search, and then copy the coordinates[br]that show up in the results,
0:14:24.173,0:14:26.983
and place that[br]into the Wikipedia articles.
0:14:27.883,0:14:31.353
In OpenStreetMap, we, as much as possible,
0:14:31.353,0:14:34.895
avoid copying data[br]from third-party sources
0:14:34.895,0:14:37.984
that are proprietary, such as,[br]for example, Google Maps.
0:14:38.613,0:14:43.493
And because of that, we will never,[br]in OpenStreetMap, never import data
0:14:43.493,0:14:46.823
from Wikipedia and also Wikidata,
0:14:46.823,0:14:51.333
because most coordinates in Wikidata[br]have been imported from Wikipedia.
0:14:52.173,0:14:54.603
So, it's an established principle[br]on OpenStreetMap
0:14:54.603,0:14:57.033
that we don't import from Wikipedia.
0:14:58.443,0:15:01.667
Okay, I'll just then[br]turn it over to Edward.
0:15:02.803,0:15:06.153
(Edward) I'm going to talk[br]about the process for adding links
0:15:06.153,0:15:08.293
from OpenStreetMap to Wikidata.
0:15:08.412,0:15:12.942
So, I've written a tool[br]for automating this process.
0:15:13.772,0:15:15.752
Like, it's user-assisted editing.
0:15:15.752,0:15:18.072
So, it's not a fully automated tool.
0:15:18.072,0:15:20.072
It's available. Anyone can use it.
0:15:20.142,0:15:21.992
There's the address.
0:15:22.452,0:15:29.200
So, when I run the tool on Berlin,[br]it finds 2,800 matches.
0:15:30.080,0:15:31.685
So, these are Wikidata items
0:15:31.685,0:15:36.604
where it thinks it has found[br]the same OpenStreetMap objects.
0:15:37.868,0:15:40.904
So, the matcher is using this criteria.
0:15:40.904,0:15:43.194
It looks for things[br]that are the same entity type.
0:15:43.194,0:15:44.556
They've got the same coordinates,
0:15:44.556,0:15:48.209
and then either they've got the same name,[br]street address, or identifier.
0:15:48.981,0:15:52.750
So, with the name, it's doing lots[br]of kind of normalization,
0:15:52.750,0:15:57.537
like lower casing, removing spaces,[br]all kinds of bits and pieces
0:15:57.537,0:15:59.847
to try and match up[br]slightly different ways
0:15:59.847,0:16:01.386
that you could write a name.
0:16:01.386,0:16:03.695
And I'm looking at names[br]from different sources,
0:16:03.695,0:16:05.361
like the labels, and the aliases,
0:16:05.361,0:16:08.563
but also the site links,[br]the article titles,
0:16:08.563,0:16:13.710
and I pull anything in bold[br]from the Wikipedia article,
0:16:13.710,0:16:15.934
so lots of sources for names.
0:16:16.504,0:16:18.589
These are the identifiers[br]that I'm matching on.
0:16:18.589,0:16:21.671
So, we've got lots[br]of identifiers in Wikidata.
0:16:21.671,0:16:24.629
OpenStreetMap has identifiers, as well.
0:16:24.629,0:16:27.468
So, I've got a mapping[br]between the name of the tag
0:16:27.468,0:16:31.833
for the identifier in OpenStreetMap,[br]and the property in Wikidata,
0:16:31.833,0:16:34.472
and I look for things[br]that have the same identifier.
0:16:34.706,0:16:38.850
So, my first version of this,[br]I tried to completely automate it,
0:16:38.850,0:16:41.760
and the OpenStreetMap community[br]was not impressed.
0:16:41.760,0:16:44.860
So, better to have[br]a semi-automated process,
0:16:44.860,0:16:49.110
so people put in a place name,[br]and then they see a list of matches,
0:16:49.110,0:16:51.500
and they go through[br]and they check the matches,
0:16:51.500,0:16:53.731
and when they're happy, they hit save.
0:16:54.371,0:16:57.080
And the OpenStreetMap community[br]is much happier with that.
0:16:57.080,0:17:00.770
It does make mistakes, the software,[br]it tries very carefully,
0:17:00.770,0:17:03.470
but there are errors in there.
0:17:03.470,0:17:05.510
So you have to have[br]someone checking them.
0:17:06.725,0:17:09.150
I've got a question of like,[br]when I designed this,
0:17:09.150,0:17:11.150
I felt like there should be[br]a one-to-one mapping
0:17:11.150,0:17:13.880
between things[br]in OpenStreetMap and Wikidata,
0:17:13.880,0:17:15.370
and it doesn't really work.
0:17:15.370,0:17:20.651
Like for my example, tunnels[br]often get represented as two objects
0:17:20.651,0:17:22.750
in OpenStreetMap--[br]one for each tunnel bore,
0:17:22.750,0:17:25.951
or each road, lane within the tunnel--
0:17:25.951,0:17:29.990
whereas in Wikidata they tend[br]to be represented as a single item,
0:17:30.550,0:17:34.150
so I need to change my software[br]to take account of this.
0:17:36.030,0:17:38.820
And I have difficulties with tram stops.
0:17:38.974,0:17:43.174
So one item in Wikidata for a tram stop,
0:17:43.174,0:17:46.506
but in OpenStreetMap, it's represented
0:17:46.573,0:17:50.093
as a relation with nodes
0:17:50.093,0:17:53.023
where the tram stops[br]on either side of the road.
0:17:53.023,0:17:57.852
But I'm using a piece of software[br]called osm2pgsql
0:17:57.852,0:18:00.602
to do the OpenStreetMap side of things.
0:18:00.602,0:18:03.112
And it doesn't really support[br]these relations.
0:18:03.112,0:18:05.772
So, I'm struggling with tram stops.
0:18:06.653,0:18:08.133
And so, people are using this tool.
0:18:08.133,0:18:11.612
There's almost 10,000 changesets[br]uploaded to OpenStreetMap.
0:18:11.612,0:18:14.783
Edits on OpenStreetMap[br]are grouped into changesets;
0:18:14.783,0:18:17.602
they're not individual edits[br]like on Wikidata.
0:18:17.602,0:18:20.282
And I've got over 200 users.
0:18:21.062,0:18:25.802
And using this tool, there's been[br]a quarter of a million links added
0:18:25.802,0:18:27.402
to OpenStreetMap.
0:18:27.712,0:18:32.032
But overall, those people are adding[br]Wikidata links by hand,
0:18:32.032,0:18:36.372
or with other tools, and there's now[br]1.4 million OpenStreetMap objects
0:18:36.372,0:18:38.192
with a Wikidata tag.
0:18:40.112,0:18:42.652
Yeah, so that is our presentation.
0:18:43.592,0:18:45.112
Any questions?
0:18:45.112,0:18:46.771
And just while we're taking questions,
0:18:46.771,0:18:50.073
I'll see if I can do[br]a live demo of the tool.
0:18:52.461,0:18:54.272
Any questions?
0:18:59.922,0:19:05.022
(woman) I'm very interested in sort of[br]surpassing this license problem.
0:19:06.127,0:19:12.392
And can you tell me about strategies,[br]that can be already used, such as--
0:19:13.262,0:19:17.035
I understand that there[br]are some contributions that aren't CC0--
0:19:17.035,0:19:21.695
or like the users, or whatever they are--
0:19:21.865,0:19:27.105
that can facilitate the exchange[br]of information between the systems.
0:19:27.718,0:19:30.515
(Edward) It's true that when you sign up[br]to OpenStreetMap,
0:19:30.515,0:19:33.667
you can tick a box saying,[br]"My edits are CC0."
0:19:34.047,0:19:37.277
But the difficulty is that you[br]are often editing something
0:19:37.277,0:19:39.437
that somebody else has edited.
0:19:39.437,0:19:45.797
And so, it's difficult[br]to isolate the CC0 edits.
0:19:47.607,0:19:52.388
(woman) Maybe like-- further question,[br]like what can we do about that?
0:19:52.417,0:19:56.460
Like, can we discuss-- I mean,[br]I think it has been tried,
0:19:56.460,0:19:59.717
but I don't think it's necessarily[br]doomed to fail.
0:20:03.036,0:20:08.232
(Eugene) Well, the best thing we can do[br]is try to link items together
0:20:08.232,0:20:11.027
using Edward's tool and other tools.
0:20:12.217,0:20:18.727
But for the moment, we just try[br]to map these things separately.
0:20:20.065,0:20:21.523
Maybe we can coordinate--
0:20:21.614,0:20:27.504
for example, if the third-party database[br]that we want to import is compatible
0:20:27.536,0:20:32.543
with both Wikidata and OpenStreetMap,[br]you can do a coordinated import to both.
0:20:33.193,0:20:37.633
But otherwise, we really have[br]to respect the license,
0:20:37.633,0:20:42.039
because in order[br]for OpenStreetMap to work,
0:20:42.567,0:20:46.335
it really respects intellectual[br]property and copyright.
0:20:54.909,0:20:58.638
(man) Thank you. Is it possible[br]to change the language of the background
0:20:58.638,0:21:02.085
when you go to the map?
0:21:03.221,0:21:06.182
Because it appears the language[br]of the local place
0:21:06.182,0:21:08.336
that you are looking for.
0:21:09.794,0:21:16.316
(Eugene) So, in OpenStreetMap,[br]basically, we tag the default name
0:21:16.316,0:21:21.219
according to the local language[br]of that place.
0:21:21.625,0:21:24.872
So, for example, if you go to Japan[br]in OpenStreetMap,
0:21:24.872,0:21:26.649
you will see Japanese names.
0:21:28.189,0:21:30.833
You cannot do that using[br]the OpenStreetMap website,
0:21:30.833,0:21:35.465
but there are third-party services[br]or tile services
0:21:35.465,0:21:39.555
that provide multilingual maps.
0:21:40.364,0:21:43.074
As I mentioned, there's Mapbox,[br]there's MapTiler.
0:21:43.074,0:21:46.071
They provide multilingual maps[br]so that you can use that
0:21:46.071,0:21:50.288
instead of the default layer[br]in OpenStreetMap.
0:21:50.896,0:21:56.358
(man) [inaudible]
0:21:56.358,0:22:01.274
or from the OpenStreetMap [inaudible]?
0:22:02.167,0:22:03.748
Yeah, for example--
0:22:03.748,0:22:05.980
(man) [inaudible]
0:22:05.980,0:22:10.605
not actually to this tool,[br]but also [inaudible].
0:22:11.026,0:22:15.304
Well, currently, OpenStreetMap, [br]as a project does not--
0:22:16.564,0:22:19.102
no project to provide this service,
0:22:19.102,0:22:22.699
because the idea[br]is that we provide the data,
0:22:22.699,0:22:26.841
and other people can build on that[br]to provide the services
0:22:26.841,0:22:29.802
that users will be able to use.
0:22:33.410,0:22:38.890
(man 2) Yeah, this is a great project[br]for all to [inaudible] on Wikidata.
0:22:39.458,0:22:45.011
Say, in Wikidata,[br]we have a lot of locations,
0:22:45.501,0:22:48.617
which is already coded and it is CC0.
0:22:49.396,0:22:55.919
So, there are a lot of images,[br]a lot of other things are in Wikidata.
0:22:56.295,0:23:01.216
So, if we integrate[br]this Wikidata Q items to OSM,
0:23:03.698,0:23:06.576
can we pull this,[br]all the other information
0:23:06.576,0:23:10.064
from Wikidata directly to OpenStreetMap,
0:23:10.064,0:23:12.104
any kind of tool, or something like that?
0:23:12.104,0:23:16.133
Or can we add an image[br]which is in Commons?
0:23:16.133,0:23:20.475
Can we add the link of the image[br]in Commons to OpenStreetMap,
0:23:20.475,0:23:23.239
like this Wikidata ID?
0:23:24.138,0:23:25.520
I feel like you don't need to.
0:23:25.520,0:23:29.069
Just leave the data in Wikidata,[br]and access it through the link.
0:23:29.069,0:23:32.428
Like just add the link[br]from OpenStreetMap to Wikidata,
0:23:32.428,0:23:35.428
and then, if you want the images--[br]don't duplicate the data,
0:23:35.428,0:23:38.158
don't have the same thing in both places.
0:23:38.818,0:23:42.198
And like Eugene was saying,[br]it's a bit tricky copying the data.
0:23:42.198,0:23:43.608
It's true that it's CC0,
0:23:43.608,0:23:45.728
but if we just start[br]importing lots of data,
0:23:45.728,0:23:48.459
then OpenStreetMap's going to ask[br]what's the provenance of the data,
0:23:48.459,0:23:50.538
where has all this come from.
0:23:52.589,0:23:55.338
I mean, I don't know if Eugene--[br]if you got anything to add to that.
0:23:55.338,0:23:58.518
(Eugene) Well, OpenStreetMap[br]does have an image tag.
0:23:58.518,0:24:02.217
So, you can add that image tag[br]pointing to a Commons file,
0:24:02.217,0:24:03.551
if you really want to.
0:24:03.551,0:24:07.937
But if you link it to the Wikidata item,[br]you don't need that,
0:24:07.937,0:24:10.577
because the Wikidata item
0:24:10.577,0:24:14.767
would probably have[br]a Commons category statement,
0:24:14.767,0:24:19.182
and that provides you links[br]to several images, as well.
0:24:19.556,0:24:22.843
You don't need to add that[br]in OpenStreetMap.
0:24:23.979,0:24:26.248
Can I just show this quick demo.
0:24:26.248,0:24:28.276
This is the software that I built.
0:24:28.276,0:24:32.173
So, I've looked up[br]Orange County in Indiana.
0:24:32.733,0:24:37.728
You can see, I've already run the software[br]in 2017, and I added 43 elements.
0:24:38.520,0:24:41.074
It guesses the language is English,
0:24:41.074,0:24:45.779
by looking at the number of languages[br]that the Wikidata labels are in.
0:24:46.588,0:24:49.101
And so the software[br]has found five matches,
0:24:49.101,0:24:52.384
and it's got a list of matches[br]with tick boxes.
0:24:52.384,0:24:53.681
There's a map.
0:24:54.004,0:24:58.623
It shows you the first paragraph[br]from the Wikipedia article
0:24:58.623,0:25:00.857
in the currently selected language.
0:25:00.965,0:25:05.105
If I say, show tags, these are the tags[br]from OpenStreetMap,
0:25:05.105,0:25:07.792
so it's matched--the name is the same.
0:25:07.792,0:25:12.058
It says it's found eight name matches,[br]and it's a hotel which matches.
0:25:12.705,0:25:14.245
I can say, show on map.
0:25:14.245,0:25:19.256
And the pin is the location[br]of the Wikidata coordinates,
0:25:19.256,0:25:22.055
and it's matched[br]this hotel building polygon.
0:25:22.625,0:25:24.595
So, I can go through,[br]and you can see some others.
0:25:24.595,0:25:26.035
There's a school.
0:25:26.035,0:25:27.695
It's failed with the airport.
0:25:27.695,0:25:31.095
The airport is represented[br]both as a node and as a way,
0:25:31.095,0:25:33.245
and it can't figure out which one to use,
0:25:33.635,0:25:35.585
so it isn't going to do the airport.
0:25:36.365,0:25:42.085
Here's a historic bank building[br]that it's managed to match.
0:25:42.885,0:25:46.095
There's an old name tag in OpenStreetMap,
0:25:46.095,0:25:49.455
that it's matched the old name,[br]with the name that is in Wikidata.
0:25:50.274,0:25:52.635
And then it's also matched up[br]public library.
0:25:52.635,0:25:55.780
So, if I click on add wikidata tags[br]to OpenStreetMap,
0:25:55.780,0:25:58.058
it gives me a change comment field[br]where I could edit it--
0:25:58.058,0:25:59.628
change comment if I wanted.
0:25:59.628,0:26:01.621
And it shows me the same matches again.
0:26:01.621,0:26:04.389
And I hit save, and it's edited the map,
0:26:04.389,0:26:07.794
and it's added[br]the Wikidata tags to the map.
0:26:10.437,0:26:16.034
(applause)
0:26:19.763,0:26:21.535
([Muhammad]) It's actually not a question.
0:26:21.535,0:26:24.007
But first, thank you for this project.
0:26:25.057,0:26:27.690
My name is [Muhammad Hidjal][br]from Palestine.
0:26:28.083,0:26:31.713
I am a civil engineer,[br]and I do some special statistics.
0:26:32.579,0:26:37.353
A few months ago, a magazine in my country[br]asked me to do some statistics
0:26:37.353,0:26:39.024
on Nobel Prize winners.
0:26:39.524,0:26:42.923
So, for that, I used[br]Wikidata Query Service,
0:26:42.923,0:26:47.113
and ArcGIS program for geographic[br]information system analyzation.
0:26:47.754,0:26:51.653
I extracted the place of birth[br]for all Nobel Prize winners,
0:26:51.653,0:26:55.874
and projected them on the map[br]using ArcGIS program,
0:26:55.874,0:26:58.792
and then they asked me,[br]"How many of them--
0:26:59.124,0:27:03.303
how many of the winners were born[br]in the north part of the world,
0:27:03.303,0:27:06.309
how many of them were born[br]in the south part of the world?"
0:27:06.309,0:27:09.391
The problem here is[br]that ArcGIS program is not free
0:27:09.391,0:27:11.505
and I don't want to use it anymore.
0:27:11.505,0:27:15.317
Can I do these statistics[br]using OpenStreetMap
0:27:15.317,0:27:19.493
after projecting the special[br]information of these?
0:27:21.485,0:27:24.118
Okay, so the problem is[br]that what you're doing--
0:27:24.118,0:27:28.699
what you're trying to do is[br]what we call a geospatial analysis.
0:27:29.309,0:27:32.394
However, OpenStreetMap is a data project.[br]We provide data.
0:27:33.003,0:27:37.018
And what you can do is, for example,[br]take the data from OpenStreetMap,
0:27:37.018,0:27:40.554
take the data from[br]your Nobel Prize place of births,
0:27:40.554,0:27:44.612
and use a tool, like ArcGIS,[br]which is not free,
0:27:44.612,0:27:47.376
but there's an open source tool,[br]called QGIS,
0:27:47.376,0:27:51.067
which you can use to do[br]that spatial analysis that you want.
0:27:51.472,0:27:53.505
So, you can combine, for example,
0:27:53.505,0:27:57.729
the boundaries for northern countries[br]versus southern countries,
0:27:57.729,0:28:03.454
put that in QGIS, then put your data[br]with the Nobel Prize place of births,
0:28:03.859,0:28:07.430
and then do an intersection[br]tool or function.
0:28:08.037,0:28:09.414
So, yeah.
0:28:09.626,0:28:13.086
So, I think we're out of time,[br]and it's lunch now.
0:28:13.175,0:28:14.617
Thanks, everyone.
0:28:14.617,0:28:19.857
(applause)