Getting from point A in London to Point B doesn't really need AI per-se. It's at worst a heuristics problem, and at best it's simply procedural.
Eg. getting from Bank to Mansion House is best done on foot - but that can be known by various factors:
- The distance from any platform at Bank and any District/Circle line platform at Monument (ostensibly the same station, but my god the walk between them is a long way)
- The distance from any platform at Bank and the street
- The distance of the exits at Bank (of which there are many, over quite a wide area) and the exits at Mansion House (of which there are a couple, either side of a wide road)
- The speed people walk, and the levels of congestion in the walkways at one or both stations (which can be approximated by time of day)
I guess you could get fancy and throw in the current weather conditions, and maybe road traffic conditions, and the time it takes for the pedestrian crossings to change to "green man" (although jay-walking is okay here, so you probably don't have to wait that long every time). You could also improve the resolution of the time estimates by looking at which carriage the person was in when they arrived at the station (and on which line), and thus how far they were from the platform exit.
So to navigate you really don't need much AI. There are (albeit complex - but only as complex as you like) definitive answers. Of course, putting voice rec and natural language processing on the front of it makes it an AI project, but it's just "AI operates a website" because there are already London navigators available.
Not to belittle anyone's work here, and it's good to see someone using London as a playground, but I'm wondering what's actually been achieved here?