Hoi,
For your information there are several things Wikidata can already do.
- When for instance a district is associated with a "shape", multiple
shapes could be known and dated by Wikidata.
- It could know of the existence of maps and when a map is defined in a
way that allows for queries, typically the four corners of a map allow for
the calculation of a radius
- we can query maps to find out if a specific coordinate and
consequently item is in that map.
- Finally, there are several examples of the results of queries shown on
a map. Reasonator has a button that shows a map for every item that is in a
15km range of the item involved. Colossus has buid tool that shows classes
on a map based in Wikidata info..
Thanks,
GerardM
[1]
http://tools.wmflabs.org/wikidata-todo/around.html?lat=47.378611111111&lon=8.54
[2] http://tools.wmflabs.org/wp-world/wikidata/superclasses.php?lang=en
On 16 May 2014 00:21, Andrew Green <[email protected]> wrote:
> Folks, this looks really fantastic, way to go!!
>
> I'd really love to contribute to this, as time allows, BTW.
>
>
> * Data (one or more sets of data, can be geojson, topojson, tsv, csv,
>> layers from OSM [3], OHM [4], etc.)
>>
> <snip />
>
> * Datasets in WikiData using an alternative data model
>>
> I'm especially interested in what could be done with Wikidata queries, and
> hooking those into a Wiki's metadata. I think this has tons of potential
> for analyzing contributions to Wikipedia in a collaborative way. A bit a la
> Wikimetrics but with many more options for pulling in and hooking up data
> of various sorts, on-wiki.
>
> It would also be great to hook this into activity feeds for sets of users
> or articles, for example, so you could go back and forth between a stream
> of edits and aggregate data about them, or maybe even overlay a graph on a
> stream of edits along a timeline.
>
> Finally, it would be nice to be able to define data transformations and
> visualizations in a modular way. For example, if one user has an
> interesting data set or Wikidata query that pulls in information on events
> related to a certain topic, and another user has defined a nice way of
> visualizing events on a timeline, a third might be able to use the first
> user's data with the second user's visualization defintion, or even bring
> in data on a different set of events, and display both sets in a single
> visualization, etc., etc. Mmm, just a thought...
>
>
> It's a word that means "to illuminate": Limn [5].
>>>
>> 3) It's a word that is difficult to translate.
>>
> How about "Munge"? As in, it munges data so you can view it in different
> ways? That's easy to translate! Rhymes with "grunge"...
>
> Cheers,
> Andrew
>
>
> On 15/05/14 15:59, Dan Andreescu wrote:
>
>> By the way, the Vega work is deployed to this wiki:
>>
>> http://analytics-wiki.wmflabs.org/mediawiki/Main_Page#Visualization
>>
>> Jon/DJ/Aude, if you want I can add a more generic proxy name for that wiki
>> and put your stuff on there too? It's in the analytics project in labs
>> but
>> I'm happy to give anyone rights to it.
>>
>>
>> On Thu, May 15, 2014 at 1:35 PM, Dan Andreescu <[email protected]>
>> wrote:
>>
>> I like Visual:, any +1s? +2s?
>>>
>>> The only downside might be a slight conflict with VisualEditor
>>>
>>>
>>> On Thu, May 15, 2014 at 11:20 AM, dan-nl <[email protected]
>>> >wrote:
>>>
>>> PictureIt:
>>>> Envision:
>>>> Imagine:
>>>>
>>>> On May 15, 2014, at 17:06 , Jon Robson <[email protected]> wrote:
>>>>
>>>> Visual: ?
>>>>> On 14 May 2014 10:44, "Derk-Jan Hartman" <[email protected]
>>>>> >
>>>>> wrote:
>>>>>
>>>>> PS, i'm building an instance that is running this extension.
>>>>>>
>>>>>> On Wed, May 14, 2014 at 12:34 AM, Jon Robson <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> During the Zurich hackathon, DJ Hartman, Aude and I knocked up a
>>>>>>> generic maps prototype extension [1]. We have noticed that many maps
>>>>>>> like extensions keep popping up and believed it was time we
>>>>>>> standardised on one that all these extensions could use so we share
>>>>>>> data better.
>>>>>>>
>>>>>>> We took a look at all the existing use cases and tried to imagine
>>>>>>> what
>>>>>>> such an extension would look like that wouldn't be too tied into a
>>>>>>> specific use case.
>>>>>>>
>>>>>>> The extension we came up with was a map extension that introduces a
>>>>>>> Map namespace where data for the map is stored in raw GeoJSON and can
>>>>>>> be edited via a JavaScript map editor interface. It also allows the
>>>>>>> inclusion of maps in wiki articles via a map template.
>>>>>>>
>>>>>>> Dan Andreescu also created a similar visualisation namespace which
>>>>>>> may
>>>>>>> want to be folded into this as a map could be seen as a
>>>>>>> visualisation.
>>>>>>> I invite Dan to comment on this with further details :-)!
>>>>>>>
>>>>>>> I'd be interested in people's thoughts around this extension. In
>>>>>>> particular I'd be interested in the answer to the question "For my
>>>>>>> usecase A what would the WikiMaps extension have to support for me to
>>>>>>> use it".
>>>>>>>
>>>>>>> Thanks for your involvement in this discussion. Let's finally get a
>>>>>>> maps extension up on a wikimedia box!
>>>>>>> Jon
>>>>>>>
>>>>>>> [1] https://github.com/jdlrobson/WikiMaps
>>>>>>>
>>>>>>>
>
> _______________________________________________
> Wikitech-l mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
