 Good afternoon, Wikimania. This session continues with presentations in the Wikimapathon series. From today, we have had a full day of activities. First on the stage will be Dennis Raylin-Chen and Eugene Alvin Willer. They are going to talk about learning about the OpenData project OpenStreetMap, how it relates to various Wikimedia projects, how to contribute to it, how to link it with Wikidata. Yes, Wikidata. Dennis is a Taiwanese OpenStreetMap mapper and Wikidata contributor user Superplex, one of the hosts of OpenStreetMap's Wikidata monthly meetup in Taipei. Recently speaking in Taiwan is Hockian at conferences, also the board of directors of Wikimedia Taiwan. Eugene Alvin Willer from Wikimap's user group has been contributing to Wikimedia since 2002 and to OpenStreetMap since 2007. He is an advocate for open knowledge and OpenData projects and wants to seek further collaboration between the Wikimedia and OpenStreetMap projects. Eugene is also a member of the Wikimedia user group and has served on the board of OpenStreetMap Foundation from 2020 to 2022. Please, the stage is yours. OK. Hello, everybody. Do we have your lunch? Already me, Dennis, and Eugene will talk about these sections. OpenStreetMap and Wikimedia, all summed together. OK. Does anyone have no idea what is OpenStreetMap? Can you raise your hand? Oh, there's one person who has no idea what it is. OK, I think he's joking about it. So I'll just keep going on. OK. The first time I have been to a Wikimedia, I have an OpenStreetMap-related subject. It's in 2012, the Wikimedia in Washington, DC, that the person has shared about OpenStreetMap. They also have an OpenStreetMap mapping party that time. OK. And personally, I'm very involved in both OpenStreetMap and Wikidata. I have mapping so many map features like highways, waterways, and cross-link. If they have Wikidata, I will link those Wikidata QID added on OpenStreetMap. We usually will describe OpenStreetMap as the largest crowdsourced project to map the whole world. And on this slide, you can see a part of the city Singapore that includes the islands and also Singapore city center. And I think the airport is not in this screenshot. So it's a part of the Singapore area. But personally, I will describe OpenStreetMap as a geographical database that not only a map tile, not only an online map like Google, but also is a geodatabase that has the possibility to link to other database, third-party database. For example, the main topic today, Wikidata, also Wikipedia, also other like the geonames. We can input the geonames ID on OpenStreetMap. OK, this is the other map title that prove that OpenStreetMap not only is a web map, but also a geodatabase that can render what you need. This is the cycling map that focus on the outside activities like bike route, or bike stop, or bike rental station, this kind of stuff. And also, we did parks and green area highlight on this map. For Wikipedia guys, you might describe OpenStreetMap as, OpenStreetMap is like Wikipedia for maps, but there are some slightly different parts. Like OpenStreetMap won't allow anonymous editing, but on Wikipedia, Wikidata, it is possible to find anonymous editing. You don't need a reserve for account to edit on Wikipedia projects. The more accurate way of introducing OpenStreetMap is OpenStreetMap is like Wikidata for geographical data. We already mentioned that OpenStreetMap is a geodatabase. Wikidata, of course, I think you have all had the idea of what Wikidata is. It is a database that is machine readable database. Sorry. OK, this one is another map title is more focused on the public transportations. The red line on the map is the bus stop. No, bus route in the Singapore central area. And the black line represents subway or train lines. OK, here we go to the history part that when did OpenStreetMap establish? It established in 2004. That is in the United Kingdom. There's a bunch of guys riding bicycle to recording those bike routes or bike tracks or highways around the Cambridge or in London. Now it is overseen just like Wikidata Foundation overseen various Wikidata projects. OpenStreetMap is overseen by OpenStreetMap Foundation. And this foundation is registered in England and Wales. OK, here we go into the might be quite hard to imagine data structure of OpenStreetMap. OK, let's go inside how do we produce data. All I say, Wikidata have quite a lot of comments. Both community-driven, both being crowd sources. And of course, it is all powered by open source software. And itself, both these projects are open data projects. Well, we might be, I think, everyone in this hall is familiar with Wikidata. Wikidata has items, statements, properties, values, qualifications, reference, label, and description. And the label and description part can be in Chinese or English or other language exists in the world. And OpenStreetMap also has this kind of data structure. It is called, they have node, ways, relation. Relation is quite a complicated concept that you just remember that they have members and each member has rules. And on the nodes, ways, relation, they have the key value tags for this object to represent what they present in the world. For example, if you want to map part, we will use the key value, lesser equals part. Here is the data model that node contains the geographic location. Ways are a bunch of nodes that it might be closed ways, represent a program, open ways that might represent reverse highways. Yeah. Okay, here's OpenStreetMap Wikidata comparison. And use the example of Suntech Singapore that is where are we right now that for representations about Wikidata use statement. So for Suntech Singapore Wikidata, we will have a statement official website or date or official opening and also the coordinate location that can be added on Wikidata. For OpenStreetMap, we not only can add those official website, data opening or coordinate location, of course, we also can add the address. Suntech Singapore. But OpenStreetMap has an advantage that is also key value pair is not that strictly controlled compared to Wikidata. User can invent and add any tags they like. There is a tagging proposal, however, it is quite similar like Wikidata. Okay, here we go is the community process. It might be quite political actually, both on Wikidata and OpenStreetMap. On Wikidata, we have the project chat that we discussed if we need new properties. On OpenStreetMap, we use the tagging marines to discuss what this kind of, what type of these stuff should be tagged on OpenStreetMap. Okay, here we go is the linking OSM with that part. That is, we can add an OSM relation ID, way ID, or no ID on the Wikidata items. This is the size we'll show you. P40402, it's also relation ID, way ID. P10689, and the no ID is P11693. And if you look into any items on Wikidata that contain geographical features, it's usually you can add not only geocoordinates, but also relation ID, way ID, or no ID. Okay, and also that we can, as an ontological way of thinking, we can also have Wikidata items properties for geographical future, can link to equivalent OSM classes using the OSM tag or key. P1282 properties, that is, for example, we have an item that is called Wikidata lighthouses. We can add its correspondent OSM tag or key, tag, column, manmade, equal lighthouses to represent the equally stuff on the OSM tagging system. And for other properties, it's quite interesting, it's also OSM numeric user ID that will link Wikidata people to their OSM correspondent ID. Yeah, and also we have OSM name suggestion index to linking those brand changes using Wikidata QID on the Wikidata to tagging using OSM secondary tag to add it on OpenShredMap. It will be very convenient if you add the name suggestion index on OpenShredMap, then you can simply query using overpass query, this kind of stuff to do over, yeah. And we also can add Wikimedia tags on OpenShredMap objects. For example, the downtown core of Singapore, we can add the correspondent Wikipedia articles is in English, downtown core to the English Wikipedia articles and QID on the OpenShredMap correspondent items. And here we go as a secondary tag, powered by Wikidata and it is discussed for use on OpenShredMap that we can add it, this kind of stuff. Brand column Wikidata is part of the name suggestion index. Architecture column Wikidata is very convenient to know who designed this building. And the artist, column Wikidata, you can state which artists that had make this artwork, public artwork. And then column entomology, column Wikidata that you can make a statement that what is the name orange of this street or other stuff. Right now, before we check it several days ago, there are almost three million objects and all I said were Wikidata tags. And almost two million objects on OpenShredMap had the secondary OSN tag, brand column Wikidata tags. And over one million main column entomology, column Wikidata on the objects on OpenShredMap database. Okay, then Eugene. Yeah, thanks, Dennis. So basically, Dennis give you an introduction of what OpenShredMap is and how we can connect these two open data projects together. So you can link between OSM to Wikidata and vice versa from Wikidata to OpenShredMap. So what I'll be doing now or demonstrating now are some of the things that where Wikimedia and OpenShredMap projects are sharing data with each other. So for example, we make extensive use of OpenShredMap here in Wikimedia. So here's an example. If you go to a typical Wikivoj page on Wikivoj, usually there's an interactive map that you can use to pan around and look at the various points of interests. So for example here, we have the Wikivoj page for Marina Bay and that top square is an interactive map and it actually shows a map that is based on OpenShredMap. So if you edit things in OpenShredMap, that eventually gets reflected on that interactive map that you can see in Wikivoj. This square is powered by the Cartotirian MapTile service and it is used by the Cartographer Media Week extension which provides the interactive maps that you see in the Wikimedia projects. There's also another aspect is if we link OpenShredMap objects together with the Wikidata items, you can display the geometry as seen in OpenShredMap directly in Wikidata or Wikimedia co-projects. So for example, the Wikimedia Commons category for the downtown core area of Singapore, there's an interactive map there and that geometry there, that shape, comes straight directly from OpenShredMap because we've already linked the OpenShredMap object to its corresponding Wikidata item In 2018, the foundation released localized map tiles for Cartotirian and what they do is they leverage OpenShredMap's name tags. So here's an example of the Japanese layer for the map tile service. So it shows all Japanese labels and that's because we've already linked like countries and cities in OpenShredMap with their corresponding Wikidata items and because those Wikidata items already have Japanese labels. We can show those labels straight on the map as you can see here. Although some labels, for example, Monaco don't have Japanese labels yet as of this time but yeah, if they're missing Japanese labels you can add them in Wikidata and they will be reflected eventually. How about on the other side? We actually use a lot of Wikimedia and Wikidata stuff in OpenShredMap as well. So to give an example, brands. So Dennis mentioned earlier the name suggestion index. So the idea here is that we want to be consistent with how we tag things like branches of shops and stores in OpenShredMap. So what we do is if we want, for example, to tag a fast food restaurant of a particular brand in OpenShredMap, we use the service called name suggestion index which is powered by Wikidata in order to provide consistent tagging for stores. For example, here's an example for McDonald's. So if we select McDonald's in OpenShredMap, they're automatically tagged with Wikidata item that corresponds to McDonald's. There's also federation. Softbox is a Sparkle endpoint for OpenShredMap data and you can use this and federate it with the Wikidata query service in order to query both OpenShredMap and Wikidata items at the same time. And unfortunately, you won't be able to demonstrate it, but if you're familiar with how to do federated queries using Sparkle, you can query both OpenShredMap and Wikidata at the same time. There's also Geocoding. In 2019, the OpenShredMap Foundation had the Google Summer Code project to use Wikidata tags in Nominatem. So Nominatem is a software used in OpenShredMap to do Geocoding. That is if you provide an address, it returns coordinates corresponding to that address. And what we do is if OpenShredMap objects are tagged with the Wikidata items, that information or data is used to provide more accurate results when querying stuff in Nominatem. There's also localization. So Mapbox, MapTiler, and other companies that use OpenShredMap use Wikidata to provide localized map products. So for example, if OpenShredMap do not have localized names stored in OpenShredMap, they can query linked Wikidata items to provide even more labels for places. So this is an example of a MapTiler layer showing both Russian and English names in the New York area. Also, the OpenShredMap project has its own Wiki using the MediaWiki software. And we've also installed the Wikibase extension in the OpenShredMap Wiki. And we use this in order to provide machine-readable data for better reading of OpenShredMap tags. Okay, so those are some examples of how we're using OpenShredMap in Wikidata and vice versa. And here are some examples of projects and initiatives that communities and affiliates are using to link OpenShredMap and Wikidata together. So my colleague, Dennis, from Taiwan, they host monthly meetups for Wikidata and OpenShredMap. And one of their ongoing projects is to map and link data on villages and rivers, among other things. I think you also do think cemeteries, right? Yeah, and this is an example of their tool trying to keep track of which villages in Taiwan have already been mapped and linked between OpenShredMap and Wikidata. Our colleagues in India, specifically the Wikimediants of Kerala User Group, together with OpenShredMap Kerala, collaborate with each other to, again, similar with Taiwan. They try to map various places and link them together between Wikidata and OpenShredMap. So they're doing administrative areas, rivers, train stations, and similar places. Of course, we do not just want to link data between OpenShredMap and Wikidata, per se. That's not an end in itself. We want to do things, interesting things. So Open Knowledge Belgium did this open equals street names project. And what they did was, after mapping all of the streets in Brussels, they tried to tag the source of the names of those streets to the persons in Wikidata. So, for example, if you have, like, for example, Luru Adelaide and something like that, you can connect that with using the name etymology, Wikidata tag, to the corresponding person after whom that street is named. And what they found out was that over 90% of streets in Brussels were named after men, as opposed to just 107% after female. And they were able to do that because of the link between OpenShredMap and Wikidata and the gender property of the humans stored in Wikidata. There's actually lots of projects similar to OpenStreet, equal street names. There's already over 60 cities all over the world that have adopted or adapted this project worldwide. So, Daniel Santini created the Open etymology map using his OpenStreetMap Wikidata framework. And what this shows is it shows you, on an interactive map, when you click on objects in OpenStreetMap, you get the Wikidata item based on the person who that object or place is named after. So for example, the Kavanaugh Bridge here in Singapore was actually named after William or for Kavanaugh, which is the last India appointed governor of the straight settlement. So there. So you can actually use Daniel's framework to do similar projects like this one. There's also the OpenAirport map. So what this does is since airports, most airports are already linked to their corresponding Wikidata items between OpenStreetMap and Wikidata. So if you go to OpenAirport map, you can just Google this. You can search for an airport and you can see an interactive map showing the details of the airport as map in OpenStreetMap. And then on a sidebar, you can see data pulled directly from Wikidata. So for example, you can see here the banner for Wikibay voyage, the logo, and a graph showing the passenger counts or passenger, yeah, passenger counts for Amsterdam Airport Shipple. So, okay. Not everything is fine and dandy between OpenStreetMap and Wikidata. We have a lot of different issues. First of these is copyright. So one thing is that in Wikidata, we can't import coordinates from OpenStreetMap. The reason for that is since you know that Wikidata is licensed CC0, the problem is OpenStreetMap is licensed, other than OpenData-based license. And that means that you cannot just copy stuff from OpenStreetMap to Wikidata. So the problem there is that since OpenStreetMap was started in the United Kingdom, they have this concept of what we call database rights, which is not present in the United States where Wikidata is hosted. And this conflicts actually with the facts or not copyrightable doctrine in the United States. By subversa, OpenStreetMap will not import your data from Wikidata despite the CC0 license. The reason for that is in Wikidata and in Wikipedia in general, you're allowed to go to Google Maps and get coordinates there and use those coordinates to populate the coordinates templates in Wikidata or Wikipedia. But the problem is with OpenStreetMap, we strictly forbid people to consult Google Maps because it is a proprietary project. So it is an established principle in OpenStreetMap that we do not import geodata from Wikipedia and also Wikidata. Another thing, paid mapping. Paid editing in Wikimedia is frowned upon, but paid mapping is quite common in OpenStreetMap. So there's actually nearly one in six edits in 2019. We're done by companies that are contributing to OpenStreetMap. In the upper right part, you can see the various companies that contribute to OpenStreetMap. You can see familiar names there, Apple, Facebook, Amazon, Microsoft, they all contribute to OpenStreetMap. And actually, if you go through their mapping services, for example, there's also Grab here. So if you have already used Grab here in Singapore, go to their Settings page or About page. Somewhere there, you can see OpenStreetMap. And the bottom graph here shows the size of the mapping teams employed by these companies to edit in OpenStreetMap. The actually, as of 2021, the largest mapping team is actually from Apple. So if you use Apple Maps, chances are you're actually looking at data that was sourced from OpenStreetMap. Okay, finances. As of June 2022, the Wikimedia Foundation has net assets of $250 million and expenses of $146 million. However, the OpenStreetMap Foundation only uses a very, very small fraction of that. So as of 2023, it only has an approved budget of less than one million euros. And because of that, there's a big discrepancy between how people, between both communities, look at how we fund projects with each other. There's actually a very vocal section in the OpenStreetMap community that do not want OpenStreetMap to become as big as the Wikimedia Foundation. So there's that. So my last part of the presentation is the OSM Wikidata-licking tool. So this is a tool that was developed by Edward Betts in order to add Wikidata tags to OpenStreetMap objects. So you can go to osm.wikidata.link and I won't really demonstrate how to use it. We can talk about this later after the presentation. But the idea is that after you log in to the tool using your OpenStreetMap account, you can select a place of interest, let the tool run, basically it uses its algorithms to do some matching between OpenStreetMap and Wikidata. And then after that, you're presented with a list of OpenStreetMap objects and then you just check or uncheck these OpenStreetMap objects. And after you click save, they will have the Wikidata tags added to OpenStreetMap. So here's an example. So if you go to the website, you can search for a place. I would suggest something smaller, not like a country. So smaller is better, so that you can show much fewer matches. And after you search for a place and select it, it will do its matching. And here's a log of it trying to match objects in OpenStreetMap with Wikidata items. Actually, when I did this, it took so long. So I went with a smaller place, downtown core. So for the downtown core, the tool was able to find 40 candidates that are possible matches between OpenStreetMap and Wikidata. So what I can do here is I can filter them and do via your settings so that it can filter and do what I want to match. So here's an example match. So the Bayfront Bridge between Marina Bay Sands and Singapore Flyer, that currently didn't have a Wikidata tag. And what I did here was I clicked the checkbox on the top left, because I was able to confirm or verify that this matches the corresponding Wikidata item, Q177, blah, blah, blah. So after doing that, and I can select in other objects as well, I just click on Save and then I can, I have a confirmation page here, making just double checking to ensure that I want to add these Wikidata tags to the correct items or objects in OpenStreetMap. And after that, I have a change comment here similar to the comment when you're saving in Wikipedia or Wikidata, after clicking Save, there. So when I go back to OpenStreetMap, the Wikidata tag is now added to the bridge as map in OpenStreetMap. So there we have Wikidata, Q177, blah, blah, blah. So mappers are already using this tool. So there's uploads done by 444 mappers. And together they've contributed 25,000 change sets. So change sets are basically like edits done in OpenStreetMap. And of those, in those change sets, we were able to add 727,000 Wikidata links using this tool. And that's basically 26% of all Wikidata tags that are currently visible in OpenStreetMap. So the way that the tool is able to do its matching is it looks at the entity type. So for example, with the example before the bridge, we have the OpenStreetMap tag manmade is equal to bridge. And in the Wikidata item, it has to be an instance or a subclass of a bridge. And then we also look at coordinates. They have to be close to each other. And the name or the street address or its identifier also has to match between Wikidata and OpenStreetMap in order for it to find candidate matches. So for those identifiers, Edward uses these 16 identifiers as potential sources for matches. So for example, we have railway station code, IATA, ICOW, airport codes, and World Heritage site ID, website, et cetera. And currently Edward is developing a second version of the tool that hopefully loads a lot faster because it doesn't have to do its matching process in a batch, but it may be a bit harder to use. As you can see, the map looks quite busy. You have to be able to interpret the different colors here. But the idea is that if you're familiar with version one, using the version two should be much faster to use, especially if you're familiar with OpenStreetMap already. So you can use version two by going to map.osm.wikidata.link. Okay, demo. We don't have the time right now to do an actual demo, but if you're present here later this afternoon, after the afternoon break, we can show you or demo to you or teach you how to use this tool. Version one at the export space area, or maybe at the concourse area, we'll just provide announcements, starting at 3.30 later this afternoon. So there, thank you very much. Are there any questions? Anyone have questions or online have any questions here? Forgot to mention, okay, first. Yeah, thank you for the presentation. My question is, you mentioned about importing data from Wikidata into OpenStreetMap, but specifically mentioned that the problem is with geolocations, but what about labels? Because you find labels in OpenStreetMap which are not translated into other languages and those labels are available in Wikidata, can those be imported into OpenStreetMap and the vice versa? Okay, so Joffrey's question was, since we already have these labels in Wikidata, can we add those labels to OpenStreetMap? So the answer to that is complicated because in OpenStreetMap, we have this concept of what we call on the ground principle. That means that we don't just add data just because you can translate names or labels. So for example, a rural village in Poland typically won't have a Chinese name. So unless you're able to find an actual map showing Chinese names of that rural village in Poland, you just cannot add that Chinese name in OpenStreetMap because of the on the ground principle. People just don't speak Chinese in rural Poland. So it's frowned upon to just add Chinese names in OpenStreetMap for every place in OpenStreetMap, but major cities, countries, continents, islands, things like that, they generally have Chinese names and that's okay. I have some supplement for questions that in Singapore, that they use simplified Chinese. So if you're importing Chinese name in Singapore, then you should type in the simplified version of Chinese. Yes. Hi, the question is similar to the previous one. So regarding the labels, my question is if it's acceptable to do the opposite. So importing labels from OpenStreetMap to Wikidata and what happens if those conflict? And my second question is I understand that the coordinates, importing coordinates to OpenStreetMap is not acceptable, but what about the geoshapes? So I know that in comments right now you can upload geoshapes. So how should the community handle the duplication of the shapes that are in OpenStreetMap versus in comments so that we can work better together and not replicate the work into places? Okay, so for your first question, so it's generally frowned upon to import names from OpenStreetMap to Wikidata because we require things in Wikidata to be public domain or CC0. And the problem is that unless you have a source, a compatible source for your names, you just cannot copy directly from OpenStreetMap to Wikidata because of the Open Database license of OpenStreetMap. As for your second question regarding the geodata or map data in comments, we can actually import data from OpenStreetMap to comments. You just select the Open Database license as the license of that data when you upload that to comments. Thank you. I'm afraid this is all the time we have for Q&A, but Eugene and Dennis will be happy to answer your questions after the session. Thanks, everybody. Thank you.