WEBVTT

00:00:02.067 --> 00:00:04.533
Hi, this is Florian, speaking from Melbourne.

00:00:04.533 --> 00:00:09.700
In the series, "Searching with Picky", this is a little screencast I've put together.

00:00:09.700 --> 00:00:16.167
So, from the last blog post we know that Picky can search coordinates.

00:00:16.167 --> 00:00:21.667
What I'm using now is a radius of 25km, which is quite big.

00:00:21.667 --> 00:00:28.900
As you see, Switzerland is small, so you find a lot of stuff with just 25 kilometers.

00:00:28.900 --> 00:00:37.067
The data I'm using here is the iPhone data, the cell tower location data, which

00:00:37.067 --> 00:00:40.200
Apple is collecting.

00:00:40.200 --> 00:00:44.133
I describe how I extracted it, it's easy, it's an SQLite database.

00:00:44.133 --> 00:00:49.400
So I've extracted it and fed it into Picky.

00:00:49.400 --> 00:00:55.300
And now, as in the last blog post, you can search for these

00:00:55.300 --> 00:01:00.867
dots where I was, so apparently I was never here, but I was here.

00:01:00.867 --> 00:01:03.500
Once. Or here.

00:01:03.500 --> 00:01:10.710
So now let's enable the timestamp and disable the coordinates

00:01:10.710 --> 00:01:13.367
and enable the dates.

00:01:13.367 --> 00:01:16.133
So, when I bought the iPhone,

00:01:16.133 --> 00:01:23.433
I started out in Zürich, and then I moved quite a bit

00:01:23.433 --> 00:01:29.300
At the end of November, I've moved to

00:01:29.300 --> 00:01:34.000
Tessin. Some friends of mine have programmed a nice iPhone

00:01:34.000 --> 00:01:37.467
game. it's called iMapIt.

00:01:37.467 --> 00:01:40.300
You can learn about Switzerland, its places.

00:01:40.300 --> 00:01:42.600
It's quite nice, you can download it

00:01:42.600 --> 00:01:46.649
They'll be happy.

00:01:46.649 --> 00:01:50.733
And you can also see that for example

00:01:50.733 --> 00:02:00.047
I spent my new year's around here.

00:02:00.047 --> 00:02:03.967
Near St. Moritz.

00:02:03.967 --> 00:02:08.633
And then I went back again.

00:02:08.633 --> 00:02:10.767
But you don't see me

00:02:10.767 --> 00:02:13.100
on this January 9th.

00:02:13.100 --> 00:02:15.567
Fact is, I went to Berlin, and

00:02:15.567 --> 00:02:23.767
gave a talk at the excellent RUG Berlin, with my friends, which

00:02:23.767 --> 00:02:25.752
also came.

00:02:25.752 --> 00:02:28.833
It was a Swiss evening, quite cool.

00:02:28.833 --> 00:02:31.100
So yeah, as you can see

00:02:31.100 --> 00:02:33.600
how I've moved around, and at the end of the timeline

00:02:33.600 --> 00:02:38.733
which is about now, that I've moved to Australia.

00:02:38.733 --> 00:02:44.400
Melbourne.

00:02:44.400 --> 00:02:48.533
So, now let's combine these two attributes.

00:02:48.533 --> 00:02:57.933
What I can say now is, when was I around here?

00:02:57.933 --> 00:03:03.233
Aha, it was around new year's I was there.

00:03:03.233 --> 00:03:06.033
Just for me this doesn't make lots of sense.

00:03:06.033 --> 00:03:14.200
If I want to know if I was somewhere I can just disable the timestamp and click.

00:03:14.200 --> 00:03:16.533
But if you have lots of people

00:03:16.533 --> 00:03:23.667
Say, intersecting data, with lots of intersecting geospatial

00:03:23.667 --> 00:03:26.833
timestamped data.

00:03:26.833 --> 00:03:38.067
Could come quite handy if you can combine these or choose which you need.

00:03:38.067 --> 00:03:45.267
Or enable the latitude, or just the longitude.

00:03:45.267 --> 00:03:49.133
Hope it was fun, hope you learnt something.

00:03:49.133 --> 00:03:52.800
I'll describe how I did it in the blog post.

00:03:52.800 --> 99:59:59.999
Cheers!