Hi all,
For those who were able to come to Boulder, Colorado for the annual State
of the Map US conference this past weekend—thanks and I hope that you
enjoyed the Colorado weather and hospitality!
It was a really nice program <https://2017.stateofthemap.us/program/> and
it was especially cool to see more and more of the projects that the
community has been chatting about and working on in their spare time
finally come to life and are in production!
All the talks on Friday and Saturday were videotaped
<https://www.youtube.com/playlist?list=PLqjPa29lMiE2k2Sp5L5rb6ntduG9dt0te>,
and you can see lots of snapshots
<https://www.flickr.com/search/?user_id=95444237%40N08&sort=date-posted-desc…>
of folks at Folsom Field and a few of the evening socials.
Cheers,
Deb
--
deb tankersley
Product Manager, Discovery
Wikimedia Foundation
I've been playing a bit with maps recently and identified a set of low
hanging fruit, that are currently lacking, prohibitive and/or need
improvement. These are great opportunities for those enthusiastic about
maps. Most are rather small, but not enough of a priority for the
foundation to work on.
1. Create a directory of tile providers services that are
opensource/opendata etc..
We seem to have a lot of different tile providers and services
integrated, but we don't really keep track of who does and uses what. There
is a nice https://leaflet-extras.github.io/leaflet-providers/preview/ that
would be awesome to have as toolforge focused for wikimedia. This can
improve our mutual knowledge of such tile providers. It took me a long time
to get a decent understanding of all the tiles that we have/can use in the
bazillion other tools.
2. Because http://tools.wmflabs.org/locator/coordinates.php incorporates
google maps and was somewhat broken to begin with, I started experimenting
with a new version: http://tools.wmflabs.org/locator/coordinates2.php just
for fun. This tool is mostly used by the Dutch Wikimedia community to add
coordinates to their wiki and they really want to keep their satellite
view. It can also be used for en.wikipedia and commons.
There is another tool called https://tools.wmflabs.org/locator-tool/, which
is specific to Commons. It would be interesting to see if we can generalise
that tool to be more wiki agnostic, using the abstractions that the locator
tool has.
3. I'm working on running an experiment with a gadget on the mobile
website, to see if there can be made a case for stronger mobile web
integration with our new map service
https://phabricator.wikimedia.org/T174538
4: The JS modules in Kartographer need some love. More support for JS hooks
and promises, will make them much easier to reuse them. For instance, it's
impossible to use the map link or mapframe modules and provide slight
enhancements or integrations, because you can't tell when they have
finished opening etc.
5: Split off Special:NearBy of MobileFrontend and enhance it with
maps.wikimedia.org
6: The list of sidebar services cannot be easily changed right now and is
hardcoded in the extension.
Moving it into a MediaWiki: json file would greatly improve this.
https://phabricator.wikimedia.org/T152971
Ergo, many opportunities, hope this inspires people !!!
DJ
Seen many of you here at Wikimania (👋 Susannah, Deb, Andy, Katie) and at
6:30pm after the group photo, OpenStreetMap Montreal is organizing a
mapping party -- let's gather outside to talk maps and create maps.
-Mikel
ps tomorrow at 2pm in Joyce/Jarry, holding a Mapathon!
Hello and thanks for writing :)
Norwegian Wikipedia already has mapframe enabled—have you had a chance to
play with the code yet? If not, learning how to use mapframe is fairly easy
for basic things and help can be found here:
https://www.mediawiki.org/wiki/Maps/how_to:_embedded_maps.
More information about the map project and service can be found here:
https://www.mediawiki.org/wiki/Maps. Also, for general discussion and
questions, please send an email to: Maps-l(a)lists.wikimedia.org for great
knowledge sharing opportunities.
Let me know if you have further questions after taking a look at the
documentation. As Guillaume mentioned in his email, our engineering
resources are quite small right now, but I think everything you're wanting
to do can be done right now.
Cheers,
Deb
--
deb tankersley
irc: debt
Product Manager, Discovery
Wikimedia Foundation
On Mon, Jul 31, 2017 at 3:31 PM, Guillaume Lederrey <glederrey(a)wikimedia.org
> wrote:
> Hello!
>
> Great to see that you have interesting projects around maps! At this
> point, the maps team is very reduced, and we are not in a position
> where we can offer much support. That being said, we'll do what we
> can! There is already some limited integration between maps and
> wikidata, which might be sufficient to do some of what you want to do.
> But honestly, I'm very much not familiar with that part.
>
> I added Deb in CC to this mail. She's our product owner and she is
> probably the best person to orient you in the right direction, or at
> least make sure your idea are captured somewhere...
>
> I hope we can find a way to move that forward!
>
> Have fun!
>
> Guillaume
>
> On Mon, Jul 31, 2017 at 8:18 PM, Hans A. Rosbach
> <hans.a.rosbach(a)gmail.com> wrote:
> > Hi.
> >
> > I saw you posted to Maps-l about usage of Kartographer. It seems to me
> you
> > have come quite far with that on fr-wiki, and I'm interested in such a
> > solution for no-wiki.
> >
> > I would like to get in contact with someone who has both knowledge in the
> > topic and is willing to discuss this with me. If that is you, fine,
> > otherwise perhaps you could introduce me to someone.
> >
> > I would like to get to the point where it is sufficient to add something
> > like {{kart}} (map in Norwegian) into an article, getting sufficient
> > information from Wikidata to display the mapframe. Another case is
> replacing
> > the position maps in infoboxes with an interactive mapframe. A geogroup
> > usage like you discussed in may is obviously also of interest.
> >
> > Regards,
> >
> > Hans A: Rosbach
> >
> > User haros on wikipedia.
> >
> > I also have e-mail haros.at.wikipedia(a)gemil.com
>
>
>
> --
> Guillaume Lederrey
> Operations Engineer, Discovery
> Wikimedia Foundation
> UTC+2 / CEST
>
Hi everybody,
(With apologies for cross-posting...)
You may have seen the recent communication [1
<https://www.mediawiki.org/wiki/Wikimedia_Engineering/June_2017_changes>]
about the product and tech tune-up which went live the week of June 5th,
2017. In that communication, we promised an update on the future of
Discovery projects and we will talk about those in this email.
The Discovery team structure has now changed, but the new teams will still
work together to complete the goals as listed in the draft annual plan.[2]
A summary of their anticipated work, as we finalize these changes, is
below. We plan on doing a check-in at the end of the calendar year to see
how our goals are progressing with the new smaller and separated team
structure.
Here is a list of the various projects under the Discovery umbrella, along
with the goals that they will be working on:
Search Backend
Improve search capabilities:
-
Implement ‘learning to rank’ [3] and other advanced machine learning
methodologies
-
Improve support for languages using new analyzers
-
Maintain and expand power user search functionality
Search Frontend
Improve user interface of the search results page with new functionality:
-
Implement explore similar [4]
<https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Testin…>
-
Update the completion suggester box [5]
<https://www.mediawiki.org/wiki/Extension:CirrusSearch/CompletionSuggester>
-
Investigate the usage of a Wiktionary widget for English Wikipedia [6]
Wikidata Query Service
Expand and scale:
-
Improve ability to support power features on-wiki for readers
-
Improve full text search functionality
-
Implement SPARQL federation support
Portal
Create and implement automated language statistics and translation updates
for Wikipedia.org
Analysis
Provide in-depth analytics support:
-
Perform experimental design, data collection, and data analysis
-
Perform ad-hoc analyses of Discovery-domain data
-
Maintain and augment the Discovery Dashboards,[7] which allow the teams
to track their KPIs and other metrics
Maps
Map support:
-
Implement new map style
-
Increase frequency of OSM data replication
-
As needed, assist with individual language Wikipedia’s implementation of
mapframe [8] <https://www.mediawiki.org/wiki/Maps/how_to:_embedded_maps>
Note: There is a possibility that we can do more with maps in the coming
year; we are currently evaluating strategic, partnership, and resourcing
options.
Structured Data on Commons
Extend structured data search on Commons, as part of the structured data
grant [9] via:
-
Research and implement advanced search capabilities
-
Implement new elements, filters, relationships
Graphs and Tabular Data on Commons
We will be re-evaluating this functionality against other Commons
initiatives such as the structured data grant. As with maps, we will
provide updates when we know more.
We are still working out all the details with the new team structure and
there might be some turbulence; let us know if there are any concerns and
we will do our best to answer them.
Best regards,
Deborah Tankersley, Product Manager, Discovery
Erika Bjune, Engineering Manager, Search Platform
Jon Katz, Reading Product Lead
Toby Negrin, Interim Vice President of Product
Victoria Coleman, Chief Technology Officer
[1] https://www.mediawiki.org/wiki/Wikimedia_Engineering/June_2017_changes
[2]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/…
[3] https://en.wikipedia.org/wiki/Learning_to_rank
[4]
https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Testin…
[5]
https://www.mediawiki.org/wiki/Extension:CirrusSearch/CompletionSuggester
[6]
https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Testin…
[7] https://discovery.wmflabs.org/
[8] https://www.mediawiki.org/wiki/Maps/how_to:_embedded_maps
[9] https://commons.wikimedia.org/wiki/Commons:Structured_data
Forwarding to the Wikimedia Maps mailing list.
Pine
---------- Forwarded message ----------
From: Edward Betts <edward(a)4angle.com>
Date: Wed, Jun 7, 2017 at 11:39 PM
Subject: [Wikidata] Tool for users to add wikidata tags to OpenStreetMap
To: wikidata(a)lists.wikimedia.org
I've built a tool for mappers to match things in OSM with Wikidata and add
the
appropriate wikidata tag to OSM.
https://osm.wikidata.link/
Users can search for a administrative area or city, then pick an area to
analyse. It works best if mappers pick areas they're familiar with.
The matcher can take a few minutes to run. It grabs items from Wikidata and
figures out a target set of tags and keys to search for. Then it downloads
OSM
data and looks for matches. The matching is based on tags and names,
currently
the wikipedia tags aren't considered.
Map data is from the OSM Overpass API. Large (more than 1,000 sq km) or
dense
areas might fail with a timeout error.
The results are cached in the system and are available here:
https://osm.wikidata.link/places
Once the matching process is complete the mapper is given a tabbed page with
the results. The five tabs are:
Match candidates - things on OSM that might be considered for tagging
Already tagged - matches that are already tagged in OSM
No match - items from Wikidata with no match found in OSM
Wikidata query - the query used to find Wikidata items
Overpass query - the Overpass query to find OSM objects in this area
To start tagging the mapper is able to login to OSM via OAuth. Tick boxes
will
appear next to the likely matches, the mapper can tick the box next to the
matches they want to upload, then add a change comment and upload them using
their own OSM account. Uploads within an area are combined into a single
changeset.
If the mapper sees an obviously incorrect match they can use the 'report bad
match' option to warn other mappers and provide feedback that I can use to
improve the algorithm.
This tools doesn't add any new objects to OSM. The only change it makes is
adding a wikidata tag to existing things.
My approach is to aim for a one-to-one mapping between Wikidata and OSM. If
there are two or more things in OSM that look like a Wikidata item then it
isn't a good match. This means for example that most road and rail bridges
won't be tagged because they are represented as two OSM ways. I might change
this at some point.
There are occasional duplicates in Wikidata, this tool should spot them and
refuse to add wikidata tags until the Wikidata duplicate is resolved.
The bug/todo list is here: https://github.com/EdwardBetts/osm-wikidata/
issues
Any ideas or suggestions are welcome.
--
Edward.
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
Joshua Minor, 08/06/2017 00:53:
> The Places feature currently uses the iOS provided Apple MapKit library
> and Apple maps. This is not a decision the team made easily, but after
> much feedback and research, we believe this is the only option for now.
> A couple important notes:
>
> 1. This is only used in the Places tab, as a means of search and
> discovery. These maps are NOT used in the encyclopedia itself, and
> do not replace, prevent or circumvent work by editors to add open
> maps to articles on wikis.
> 2. Our users' privacy is preserved. We don't share what articles you're
> reading with Apple, and Apple has put significant technical and
> legal oomph into preserving privacy for their built-in maps library.
>
> If you have concerns or questions, please check out the page we wrote
> explaining the situation in much more detail[1]. We also welcome your
> addition to the Discussion either on wiki, on the task request to
> replace Apple Maps[3] or via email.
>
> [1] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS/Maps_service
> <https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS/Maps_service>
> [2] https://phabricator.wikimedia.org/T157763
Thanks. I've replied there:
https://phabricator.wikimedia.org/T157763#3337113
Nemo
Forwarding.
Pine
---------- Forwarded message ----------
From: Yuri Astrakhan <yuriastrakhan(a)gmail.com>
Date: Tue, Jun 6, 2017 at 9:07 PM
Subject: [OSM-talk] OSM+Wikidata intro video
To: OpenStreetMap talk mailing list <talk(a)openstreetmap.org>, "
tagging(a)openstreetmap.org" <tagging(a)openstreetmap.org>
The RDF/SPARQL database that has both OpenStreetMap and Wikidata data in
the same table is alive and well, and getting considerable usage. To make
it better understood by even wider community, I made an intro video with
some examples. This database mostly benefits the object tag validation and
research at this moment, as its geometry support is still in the works.
The wiki page has also seen a lot of cleanup, explaining how quality
control can be done. I hope that other tools such as JOSM and especially
MapRoulette will be able to use it directly. Also, please contribute your
SPARQL queries to the wiki page.
https://www.youtube.com/watch?v=KDiKzbuIhtshttps://wiki.openstreetmap.org/wiki/Wikidata_RDF_database
_______________________________________________
talk mailing list
talk(a)openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk