Add wikidata id concordance to features

[nvkelso]

Customer request to add wikidata ids wikipedia links to features (in the POIs layer).

[nvkelso]

Some questions:

• Examples of Wikipedia OSM tags on POIs and other features
• What is the use case for the tags?
• Why limit this only to the POIs layer?

[zerebubuth]

Examples:

• WMF offices
• Madison square park
• Admiral Farragut Memorial
• The statue of Liberty - note that this also has wikipedia:es language variants, and a wikidata tag. We should bring those through too.
• FDR Drive - not a POI, but has wikipedia info.

One interesting example that I expected to find, but did not appear to have a wikipedia tag, was the famous bit of Lombard. Opportunity for improvement.

I assume the use-case for the tags are to show extra information about the history or context of a particular object. To have a "more info" link which opens up a wikipedia page in another tab, for example. Or just to make it easier to collate the data for bundling into an offline tourist map, perhaps?

I think we should add this to all layers, although on layers other than POIs we probably want to remove the tag at mid zooms to avoid getting in the way of merging.

[erikschlegel]

I agree and mispoke about adding it to only the POI layer as places /
landmarks can span across the places / landuse / POI and other mapzen
vector layers. Our current use-case is that we're extracting points of
interest and places by using Mapzens vector tile service. In the event
where an openstreetmap POI has a wikipedia link, we provide users with the
ability to request for more information which is basically the first
paragraph from the intro in Wikipedia. I'm currently using Overpass as a
short-term workaround, until the vector service has the wikipedia tags
available. Great point on coalescing the variant wiki link tags into a
single field(i.e. wikipedia / wikipedia:es) similar to what you're doing
with the 'kind' field. This would be such an incredibly useful data set to
include in the vector tile service. My only concern about including a "more
info" link is that if the media wiki API service hosts changes then all the
links break, and also dealing with the multiple output types. Including the
wikipedia page title reference(s) into the Mapzen vector service would be a
great start.

All the best,

Erik

On Tue, Jun 14, 2016 at 6:31 AM, Matt Amos [email protected] wrote:

Examples:

• WMF offices http://www.openstreetmap.org/node/2817389220
• Madison square park http://www.openstreetmap.org/way/22899286
• Admiral Farragut Memorial
  http://www.openstreetmap.org/node/1251496241
• The statue of Liberty http://www.openstreetmap.org/way/32965412 -
  note that this also has wikipedia:es language variants, and a wikidata
  tag. We should bring those through too.
• FDR Drive http://www.openstreetmap.org/relation/109736 - not a
  POI, but has wikipedia info.

One interesting example that I expected to find, but did not appear to
have a wikipedia tag, was the famous bit of Lombard
http://www.openstreetmap.org/way/402111597. Opportunity for improvement.

I assume the use-case for the tags are to show extra information about the
history or context of a particular object. To have a "more info" link which
opens up a wikipedia page in another tab, for example. Or just to make it
easier to collate the data for bundling into an offline tourist map,
perhaps?

I think we should add this to all layers, although on layers other than
POIs we probably want to remove the tag at mid zooms to avoid getting in
the way of merging.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#858 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AHSDmTd21jThCDF23NUYD_Y1AUxenq0eks5qLoMagaJpZM4I0kEH
.

[zerebubuth]

Hi Erik,

Sorry if I wasn't clear - I meant to suggest passing through the wikipedia (and wikipedia:*) tags as they currently are in OSM, which is mostly page title references. As you say, it's better to use the page title not the link so that the client can construct the appropriate "more info" URL itself, or look up the content from a local device cache, or something else.

[erikschlegel]

Hey Matt,

Does the vector tile service provide the street intersection nodes by any
chance? If not, would the returned polyline shapes provide the intersecting
point(s) for 2 roads which happen to intersect?

All the best,

Erik

On Tue, Jun 14, 2016 at 9:27 AM, Matt Amos [email protected] wrote:

Hi Erik,

Sorry if I wasn't clear - I meant to suggest passing through the wikipedia
(and wikipedia:*) tags as they currently are in OSM, which is mostly page
title references. As you say, it's better to use the page title not the
link so that the client can construct the appropriate "more info" URL
itself, or look up the content from a local device cache, or something else.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#858 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AHSDmfU9EnY6yLCDvGRbIcu0-SQjT4gkks5qLqw8gaJpZM4I0kEH
.

[zerebubuth]

Hi Erik,

Our tiles don't contain a separate point geometry for street intersections, although the point would normally be part of the linestring geometries of both the roads. I caveat "normally" because we currently simplify road geometries at zoom levels between 8 and 15 (inclusive), which may result in intersection points being elided if the road is mostly straight.

Would having separate point geometries with the main and cross street names be useful?

[nvkelso]

Verified:

[nvkelso]

Actually, looks like the WOF portion of this isn't totally working?

Western Addition should link to Q7987437 via WOF's 85856855 concordance.

[zerebubuth]

Thanks for checking that!

There's at least one bug: tilezen/raw_tiles#32

However, that should only affect high-zoom tiles, and we do include WOF neighbourhoods at z11, which I think should be generated directly from the database (because our metatile size means a nominal z11 tile is a z10 512px tile, which is generated from a z8 metatile/job). But an example (Miramar, San Diego) also shows no wikidata_id. So I'll need to do more debugging 😕

[nvkelso]

Still missing wikidata_id from high zooms as reported in #858 (comment).

[zerebubuth]

🤦‍♂️ 🤬 💥 ⁉️

Looks like I forgot to click "merge" on tilezen/raw_tiles#32... D'oh!

I guess this means we won't be using the v18e build as 1.8 final 😞, sorry.

[nvkelso]

Doh! Easy explanation, though :)

[nvkelso]

Verified in new build, closing.