1
00:00:04,997 --> 00:00:13,077
Thank you. So a few years ago, I talked here about the work we were doing on

2
00:00:13,077 --> 00:00:18,317
bringing OpenStreetMap-based indoor train station maps into itinerary.

3
00:00:18,857 --> 00:00:22,517
And back then, I mentioned that this would be something that would potentially

4
00:00:22,517 --> 00:00:27,317
be useful for other types of public buildings as well, with the limiting factor

5
00:00:27,317 --> 00:00:31,117
being that there are very few public buildings with indoor mapping.

6
00:00:32,037 --> 00:00:37,537
However, by pure coincidence, we happen to be in a building that has such mapping.

7
00:00:38,357 --> 00:00:44,837
So the obvious thing to do was to put the indoor map renderer into Congress

8
00:00:44,837 --> 00:00:46,217
or Conference Companion app.

9
00:00:46,597 --> 00:00:50,497
So if you are using this, at least starting with the latest gear release,

10
00:00:51,677 --> 00:00:54,737
and you are selecting a talk, you click on the room in there,

11
00:00:54,737 --> 00:00:59,157
where it shows you on the map where exactly that talk is going to be.

12
00:01:00,077 --> 00:01:04,037
Sounds simple, but there's slightly more to that.

13
00:01:05,317 --> 00:01:08,937
First of all, this is based on raw OpenStreetMap data.

14
00:01:10,397 --> 00:01:14,517
And there is a few things specific to the event that might not be appropriate

15
00:01:14,517 --> 00:01:16,877
to put into OpenStreetMap.

16
00:01:17,137 --> 00:01:20,717
Like this room is usually called A007.

17
00:01:21,277 --> 00:01:26,217
We call it Talk Room 1. done, or there's a registration desk in the hallway,

18
00:01:26,757 --> 00:01:30,797
that's not something we can put into regular OpenStreetMap data.

19
00:01:31,177 --> 00:01:33,757
So what we have for that is, we have,

20
00:01:34,454 --> 00:01:39,034
we we can apply event specific open street map change sets so it's basically

21
00:01:39,034 --> 00:01:43,774
like a diff or patch on top of the baseline data and that's how we bring in

22
00:01:43,774 --> 00:01:44,954
for example our room names,

23
00:01:45,734 --> 00:01:48,674
um similar for the styles so the the map renderer

24
00:01:48,674 --> 00:01:53,574
uses something called map css so that's like web css just matching to map content

25
00:01:53,574 --> 00:01:59,114
rather than document content and with that we make our talk rooms blue and our

26
00:01:59,114 --> 00:02:04,294
both rooms green and show them at the lower zoom level already and for everything

27
00:02:04,294 --> 00:02:06,014
else, it cascades to the base style.

28
00:02:07,854 --> 00:02:13,194
And we have support for time-dependent content. So if you open the map from

29
00:02:13,194 --> 00:02:16,794
this talk, you see talk rooms, but you don't see both rooms.

30
00:02:17,374 --> 00:02:20,814
If you go to Kevin's training on Monday, open the map from there,

31
00:02:20,954 --> 00:02:25,474
you see both rooms, but no talk rooms, because we show the map how it looks

32
00:02:25,474 --> 00:02:27,634
like at the point of that talk.

33
00:02:27,854 --> 00:02:30,734
And that is going to be different between the week and the weekend.

34
00:02:30,734 --> 00:02:34,254
It um another thing

35
00:02:34,254 --> 00:02:39,834
i mentioned um in my talk a few years ago is that routing would be something

36
00:02:39,834 --> 00:02:45,714
we want to have but at that time uh that seemed to be uh entirely out of reach

37
00:02:45,714 --> 00:02:50,834
because there is to my knowledge at least no free software implementation of the.

38
00:02:52,374 --> 00:02:59,514
Necessary polygon-based routing algorithms at least not in the geospace um a

39
00:02:59,514 --> 00:03:02,974
few months ago at the CCC Congress, we, by pure coincidence,

40
00:03:03,354 --> 00:03:09,034
met somebody from Würzburg who pointed us to a library used in 3D game engines,

41
00:03:09,274 --> 00:03:13,454
which has all the algorithms we need. That's a bit of a fun.

42
00:03:14,695 --> 00:03:20,635
Um translation problem right so we think in escalators and tactile paving and

43
00:03:20,635 --> 00:03:22,375
they think in teleporters and

44
00:03:22,375 --> 00:03:30,915
lava um but it it actually works so a few months ago we we managed even,

45
00:03:31,895 --> 00:03:36,915
to get some some useful results out of worst case scenarios like the paris metro through.

46
00:03:38,735 --> 00:03:44,595
It, however, has very high requirements on the quality of the mapping,

47
00:03:44,715 --> 00:03:46,395
much, much higher than for the display.

48
00:03:47,175 --> 00:03:51,935
And that's also why this is currently disabled in the Congress version you have.

49
00:03:52,095 --> 00:03:56,835
So the routing engine is there, but the event configuration disables this because

50
00:03:56,835 --> 00:04:01,335
the staircases here are messed up, making the elevators unreachable.

51
00:04:02,395 --> 00:04:05,795
So this is hopefully something we'll be able to fix during the week.

52
00:04:06,635 --> 00:04:09,635
But for now, that's still off.

53
00:04:11,195 --> 00:04:15,955
And then, of course, this is all nice and fun, but is this actually useful? Do we need this?

54
00:04:17,495 --> 00:04:22,295
For an event like this, probably not. So, I mean, if you're in the hallway,

55
00:04:22,595 --> 00:04:28,615
pretty much all relevant rooms you have in line of sight, so the map doesn't add that much.

56
00:04:29,995 --> 00:04:35,315
If you have ever been to 4STEM, them, you might have a different appreciation

57
00:04:35,315 --> 00:04:37,535
for a map for a conference.

58
00:04:39,235 --> 00:04:42,755
And then in a bit of a different take of the accessibility goal,

59
00:04:43,875 --> 00:04:49,695
if you imagine stairs being a problematic obstacle for you, having a router

60
00:04:49,695 --> 00:04:56,495
that allows you to customize it exactly to your needs might also be a lot more valuable. available.

61
00:04:56,895 --> 00:05:03,095
And of course, all of this is library code and not specific to Congress,

62
00:05:03,235 --> 00:05:06,235
so we're going to use that in itinerary as well, of course.

63
00:05:06,955 --> 00:05:09,675
Yep, that's it. Thank you.