Tag Archives: OpenStreetMap

Getting enthusiasts into OpenStreetMap

I started writing this as an email to Richard Fairhurst, but then thought I’d post it to my blog. I wrote something on a similar theme just over a year ago.

Richard,

I just wanted to say that I thought your talk at the SOTMUS conference was spot on.

But when you talk about the cycling community, I think there’s an important caveat missing. Lots of people in our mapping community (or lots of the 5% who do 95% of the mapping) are enthusiastic cyclists, but few in the enthusiastic cyclist community are mappers.

I’ve not come across the London Cycling Campaign or any of the borough groups really getting involved with cycle mapping. Some members (myself included) do, but my impression is that most don’t. Despite embedding CycleStreets on their homepage and collaborating on a cycle parking campaign with them, I’ve never come across a big concerted push from LCC and local borough groups to contribute to OpenStreetMap beyond the odd mention in their magazine [edit: and a two-page spread]. The same was true of Andy’s great DfT data project. To this day, coverage of cycling infrastructure in London is patchy (although far better than any online alternative).

The same goes for lots of enthusiast communities. You’re right that a lot of people map the thing they’re enthusiastic about. But not many communities organised around those enthusiasms get mapping.

I’ve tried, here and there, to talk enthusiastic people round to OSM. I’ve talked to community campaigners I know involved with cycling, walking, food growing, trees, transition towns, vegetarianism, housing and school catchment areas. All benefit from mapping; some do it themselves with varying degrees of proficiency, usually with pen and paper, Powerpoint slides or Google Maps. But the technical hurdles of using OpenStreetMap (and in some cases simply the effort of mapping) often seem to outweigh the benefits they’d really get from the results.

After a chat over some tea or beer I have to send interested people half a dozen links to different web sites that provide the editor, the not-very-usable tutorials, the place to find tags that aren’t presets, the way to go about inventing new tags if necessary, the custom renders (often a mix of ITO and other third party sites), the way to see recent changes in your area that is actually usable, the quality controls to check your work, the places to ask for help, the other people doing similar work in London and how to discuss it with them, the inspirational examples, and so on. The diversity of web sites and tools is a strength of OpenStreetMap, but it’s also terribly confusing and it can be hard to discover the tool you’re after. Often there simply aren’t tools there to do what they want, and they don’t have the skills to roll their own nor the money to pay someone to make them.

It’s too confusing and complicated. Usually the payback isn’t enough, so they don’t even start, or give up shortly after their first dabble with an editor.

So… your idea of a community page is excellent. It could help to create a central focus for people with the same enthusiasms, saving me the effort of compiling all those links and making everything seem terribly disjointed. It will take a few bricks out of the wall holding communities back from contributing to OpenStreetMap.

Here’s my extension to your idea that seems technically within our grasp since Potlatch 2/iD and the Overpass tool. Make it really simple (a few clicks in a web-based tool) to set-up a hub for your niche interest: a community page bringing everything together, a custom editor with the appropriate presets, a nice map showing the results, data extracts (kml, json, shp), and code snippets to display the results on your own web site. You like Welsh chapels? Spend half an hour on this web form and bob’s your uncle.

As another hapless arts graduate with big time commitments to the Green Party, I don’t have the skills or time for this. I’m left cobbling together halfway-decent sites like OpenEcoMaps to try and fill a niche. It would be wonderful if the more technically gifted folk could make this a priority to turn more enthusiasts into the 5%.

Tagged

OpenEcoMaps is back!

OpenEcoMaps, eco-living maps using OpenStreetMap data, is now working again. Hooray! I decided to sit down and work out why the OpenLayers interface wasn’t working and it turned out to be quite simple to fix.

You can now browse around maps of low carbon energy generators in London, veggie restaurants in Edinburgh, allotments in Exeter, recycling facilities in Glasgow and more! The data is updated every hour, direct from OpenStreetMap, and is available on maps and downloadable/reusable KML and GeoJSON files. The code is also in Github, so you could set-up your own version for another country if you like.

OpenEcoMaps is back!

There are still some of the layers that aren’t working because the underlying data isn’t being extracted from OpenStreetMap properly. But I’m very glad that, after well over six months with it completely broken, the web site basically works again!

Tagged , , ,

OpenEcoMaps halfway back

For almost a year now, my pet project OpenEcoMaps has been broken. The vagaries of unreliable XAPI servers meant the system couldn’t download OpenStreetMap data to create all the KML files, and (I think) some changes to OpenLayers meant the web maps also stopped working. It has taken me a long time to work up the energy to fix these.

Today I can happily say one half of the system is now working again, and the underlying code is much improved.

OpenEcoMaps halfway back

OpenEcoMaps KML files, and now GeoJSON files, are being created again. Hooray! I switched from XAPI to the Overpass API; grabbed JSON which enabled me to write a more powerful function to turn this into usable objects (for example building a complete Python object for an allotment merging data from relevant nodes, ways and relations); wrote a new library to create GeoJSON files; refactored everything else to fit with these changes; and made numerous other small improvements.

You can browse, download and use the KML files and GeoJSON files with those links. To see an example, look at this KML file of low/zero carbon energy generators overlaid on Google Maps.

Now I just need to fix the web maps so you can see the lovely features on the main web site, and so people can easily embed the maps on their own web sites. I did dabble with using Leaflet before Christmas but I got stuck trying to get the icons to match styles defined in the GeoJSON file. I had a quick look at the OpenLayers code and quickly decided I had better things to do with my time! If anyone fancies giving it a go, the code is all in Github and is all released under the General Public License.

Tagged , , ,

Fixing problems with OSM-GB’s web service

The OpenStreetMap GB project aims to measure and improve the quality of OSM data in Great Britain, cleaning it up to get rid of silly little data errors, and to make this cleaned up version available in formats that local and central government types are used to.

I have been exploring whether I could use the Web Features Service as an easier source for landuse data (see my previous blogs on making a map of London’s green spaces and analysing Southwark’s landuse, which both required a somewhat complicated process to get the data set).

In the process I’ve found it’s actually a great way to identify gaps and problems in our data. Browse around the map on the OpenStreetMap homepage and you might think we have an impressive coverage of residential landuse, playing fields and parks. But probe around with the WFS and you can spot all sorts of missing data.

For example:

The red circle in this image highlights a likely gap in our data. The yellow blocks are all the different land covers – residential, retail, park, forest, school, etc. The area underlying it in blue is the extent of the SE21 postal code. So if blue is poking it means OpenStreetMap hasn’t got any object covering that land area, which could mean we’re missing something that is actually there. In this particular area, Dulwich in inner London, it’s pretty unlikely that any bit of land can’t be tagged as something – brownfield, grass, nasty disused area of asphalt!

What could that gap be? I went to check it out and found it was an incompletely mapped recreation ground, so I updated OpenStreetMap to fill the gap.

Here’s another more subtle one:

Don’t see it? That blue corridor coming from the north west into the red circle is a railway line. It divides up two yellow blocks (a residential area to the west and a park to the east). Then it runs into a big yellow block – a residential area that should really be split in two, leaving a corridor for the railway line. Again, it was easy to correct the data in OpenStreetMap.

The best thing about the OSM-GB WFS is that it’s updated daily, so I can gradually improve the data by checking back the next day and spotting something else to fix. I’m using QGIS, and setting the style property by category, categorising by the ‘boundary’ column and setting any boundary types to transparent. This stops boundary polygons obscuring all the other data. In this way I can quickly set the style to highlight anything I like, and save the data as a shapefile which I can then query to get something more sophisticated.

I’m currently following this method to get a really good dataset for the SE21 area, just to see what’s possible.

Tagged , ,

Analysing Southwark’s natural geography

Following my map of London’s green and blue infrastructure, I have been working on some analysis of the land uses.

I was inspired and encouraged to try this by Liliana’s interesting work called “imagining all of Southwark“. Lili and Ari have managed to get the council to release lots of data on properties and car parking, and they are producing analysis of this data by postal code area and by street. They haven’t managed to get anything on land uses, so I thought, why not produce this with OpenStreetMap data?

A few evenings later, here is the result shared on Google docs (direct link) covering the eight postal code areas that between them cover most of the borough (SE1, SE5, SE15, SE16, SE17, SE21, SE22, SE24):

What the data means

The “summary” worksheet shows the total land area, expressed in hectares (10,000 m2), for various different types of land coverage. I have also calculated the percentage of that postal code area that the land uses represent, which gives an interesting insight into the differences between the areas.

Some of the land uses will overlap, for example miscellaneous bits of green space are often mapped on top of residential areas. So the numbers aren’t supposed to add up to anything like 100%.

The spreadsheet also contains worksheets for each postal code area. These contain a dump of all the objects in OpenStreetMap in those postal code areas, and this is the raw data the summary spreadsheet uses to get the totals.

Flaws in the data

You should use this data with a large spoonful of salt. Here are the significant flaws I have noticed:

Postal code areas are approximate, for example the boundary between SE15 and SE22 should mark the boundary between Peckham Rye Common (SE15) and Peckham Rye Park (SE22). In my data both the park and the common show up in both of the postal codes, because the boundary isn’t quite right. Read down to my method to see why. The errors introduced are pretty tiny in most places (plus or minus a few meters along the full boundary), and probably cancel themselves out for big land uses like residential, but they probably also introduce some significant errors for parks where the boundaries go awry by 20-30m in places. Sadly there aren’t any accurate open data polygons I can use.

Data is missing because OpenStreetMap contributors haven’t mapped it. Of course the easy solution here is to get more of it mapped and up to date! My estimate of the different types is as follows:

  • Allotments: complete for the whole borough.
  • Parks and commons: all major and district parks complete.
  • Misc green spaces: very poor coverage of, for example, large areas of grass on estates, especially in SE5, the north pat of SE15 and SE17.
  • Woods/forest: all major woods complete, coverage of big clumps of trees e.g. on a housing estate or in a park is very uneven.
  • Residential: complete except for SE16.
  • Industrial, retail, commercial: large areas are complete, but small shopping parades, industrial parks and rows of offices are very patchy.
  • Brownfield/construction: patchy across the borough and sometimes out of date as sites are built on.

Data is also sometimes missing because of flaws in the Geofabrik shapefiles, not all of which I have corrected. For example, I noticed they were missing commons so I manually added those in, but I may have missed other land uses. One major omission, a shame given the interest in them, is the humble sports pitch/playing field.

How I produced this

After a lot of experimentation – I’ve never been trained to use GIS tools – I worked out this method. If you know of an easier way I’d love to hear about it.

  1. Prepare the boundary data:
    1. Extract a polygon for the London Borough of Southwark from the OS Boundary-Line data.
    2. Download the OS Code-Point-Open data, open the spreadsheet for the SE area in QGIS and use the ftools ‘Voronoi polygons’ plugin to infer polygons for the postal codes from the centroids. Post code centroids are very dense in the middle of residential areas, so the boundary between SE15 4HR and SE22 9BD is only going to be out by a few meters, but are quite far apart with large parks and commons, so the inferred boundaries get less accurate in those areas. See this map for an illustration of the Peckham Rye Park / Common problem mentioned above.
    3. Merge together postal codes into the areas (e.g. SE22 9QF, SE22 4DU etc. into SE22) by quering the shapefile for all objects with postal codes starting with SE22, then using the mmqgis merge tool to merge them into single polygons. Clean up the attributes so the shapefile just has one attribute for the correct postal code area.
    4. Clip the postal codes by the Southwark polygon and save the result – finally – as the postal codes shapefile for Southwark.
  2. Prepare the land use data:
    1. Download the  OpenStreetMap shapefiles from Geofabrik for Greater London.
    2. Download common and marsh ways/relations using the Overpass API (with the meta flag on), import the data into QGIS using the OpenStreetMap plugin, and save the data as a Shapefile.
    3. Merge together the Geofabrik natural and landuse shapefiles with my Overpass-derived shapefile into one land use shape file using the mmqgis plugin.
    4. Clip the land use file by the Southwark polygon and save the result – finally – as the land uses shapefile for Southwark.
  3. Produce the postal code stats; for each postal code:
    1. Select the postal code, and clip the land use layer to that selected code, saving it as a new shapefile.
    2. Open that shapefile, then save it in a new projection that will be in meters rather than degrees (I used  EPSG:32631 – WGS 84 / UTM zone 31N).
    3. Open the new shapefile, then run the ftools ‘Export/add geometry columns’ tool (in Vector/Geometry Tools) to add two attributes to the objects for the area and perimeter.
    4. Save the layer again as a CSV file.
  4. Produce the stats for the area of each postal code so we can calculate % of the area as well as ha for each land use:
    1. Save the Southwark postal codes polygon in the meters projection, add the geometry columns, and save as a CSV file.
  5. Collate all the data
    1. Tidy up and copy the data from each CSV file into a spreadsheet, then add in the formulae to tot everything up. You’re done!

For reference, some of the totals in the summary work off more than one land use type so here are the categories and the corresponding OpenStreetMap tags:

  • Allotments – landuse=allotments
  • Parks and commons – leisure=park / leisure=common
  • Misc green spaces – landuse=conservation / landuse=farm / leisure=garden / landuse=grass / landuse=greenfield / landuse=greenspace / landuse=meadow / landuse=orchard / landuse=recreation_ground
  • Woods and forest – landuse=forest / natural=wood
  • Residential, industrial, retail, commercial, brownfield, construction – corresponding landuse tags

Future ideas

One obvious improvement would be to get more data in. Perhaps this first analysis will encourage people to help out with that? I have also emailed Geofabrik about the flaws I have discovered in their shapefiles, so I hope those get fixed.

Another thought is to produce the stats by council ward. But given that there are far more wards, I’d like to find a quicker way of producing the stats for each ward (step three above) first.

It would also be interesting to do it by town/suburb, for example comparing Peckham to East Dulwich. But we don’t have any meaningful boundaries for those natural areas. It would be really interesting to do a mass version of “this isn’t fucking Dalston” for a whole borough, using the Voronoi polygons method to infer areas from surveys at thousands of locations around the borough. One day…

Tagged , , , , , ,

London’s natural geography

I’ve been playing around with open data from OpenStreetMap and Natural England to make a pretty map of “green and blue infrastructure” in London. Here’s the result:

You can download a PDF version suitable for printing here: natural_london.

I’m pretty happy with the result, my first real attempt to produce something useful with QGIS. The data I used was:

There’s no reason the Natural England data couldn’t be manually added to OpenStreetMap, giving us a complete dataset of natural features. I just chose to get on and do it this way rather than wait, or try to add all the data across areas of the city I don’t know well and am not going to visit any time soon. I also didn’t really need to use the Ordnance Survey data for boundaries, but it’s slightly more accurate and complete than OpenStreetMap data.

The map is probably missing lots of smaller patches of green space, including grass verges, green roofs and biodiverse brownfield sites. The biggest omission is the humble private garden. They cover 24% of London’s land!

But the map at least shows the more obvious, visible, public green spaces, and is a nice example of what a geek with no GIS training (but years of playing with OpenStreetMap) can do with free software and free data these days.

Tagged , , , , , , ,

Mapping for pedestrians

One of the odd things about contributing to OpenStreetMap is that you have no idea who is using the maps and the data. You spend hours, weeks, months, years even building up a wonderfully comprehensive database of geographic features in the area, all because it’s fun, because you believe in the project’s ideals or you need the data for your own project. But does anyone else use it? It would be depressing if the answer was “no”.

So I get cheered every time I see documents like this:

That’s an excerpt from a presentation by Southwark Living Streets. They took the Mayor of London’s transport advisor around Elephant & Castle to show how unfriendly and dangerous the area is for pedestrians, and illustrated the whole thing with OpenStreetMap. The chap who made this loves OSM, he told me he realised how useful it could be when he noticed we had put in all the footpaths through estates, making OSM the only map that reflects the reality for pedestrians in the area.

It was our coverage of footpaths that led to OpenStreetMap being used by parents challenging a school’s decision that they were outside the catchment area.

I also regularly see OSM used by cycling campaigners, for example this presentation on a cycling campaign that’s also about the Elephant & Castle area.

Then there was my collaboration with residents local to the Heygate Estate who wanted to map the trees that under threat from the redevelopment of the estate. That, I’m happy to say, has resulted in many of the mature trees being protected in the new plans.

So we have useful maps, and powerful tools for community campaigns if there’s an OSM expert about to help out.

But as I wrote last year, there’s a whole other world of data we could be adding, especially for groups concerned with streets that are designed for pedestrians and cyclists.

ITO have been beavering away on lots of amazing maps that show off this kind of data. These are two maps showing the “walkable city” on the left (the blue lines show footpaths and pavements broken up by black roads) and speed limits on the right (green is for 20 mph, orange for 30 mph).

Here are a few in an area I’ve done some work on, just to show what’s possible:

With a few tweaks to the Potlatch 2 editor on the OpenStreetMap homepage, anyone could easily add all this metadata to streets. There are presets for speed limits and surfaces, but not – yet – for sidewalks. If we could get them in – here’s the enhancement request – I think all those community campaigners already using screenshots of OpenStreetMap might just get interested in contributing data.

How great would it be if Southwark Living Streets could print out a special “walkable city” map of Elephant & Castle for their next presentation to the Mayor of London’s transport advisor?

Tagged , , , , , , , ,

Routing around pollution – any help?

While we’re benefiting from all this rain in London, which keeps air pollution at bay, I’ve been wondering about including pollution data in OpenStreetMap-based routing engines. The trouble is that I lack the technical skills to implement this, so I’m writing this post in the hope that somebody might be inspired to give it a go.

Another hazy air pollution episode in London

Air pollution is the second biggest cause of premature deaths in the UK after smoking. Here’s a little league table of nasties taken from Department of Health data:

Smoking – 87,000 premature deaths per year
Air pollution – 29,000
Alcohol – 22,000
Obesity – 9,000

The main pollutants in cities are particulates (PM10, PM2.5), nitrogen dioxide (NO2) and nitrogen oxide (NO). Unlike the pea souper fogs of years gone by, these are invisible to the human eye but very deadly. They’re most concentrated on busy congested roads and around airports – so unsurprisingly in central London, around Heathrow and City airports, and in congestion hot spots dotted around the rest of London. We have some of the worst air pollution in Europe.

Long term exposure to these critters is obviously a bad thing, so it would be nice if we could find routes to walk or cycle without being affected. To some extent it’s just a matter of avoiding main roads, but some are much worse than others and in central London there are plenty of non-A roads that should be avoided as well.

WalkIt has a neat little feature that lets you choose a “low pollution” route. This basically tries to avoid roads with high concentrations of nitrogen dioxide. But it doesn’t cover the whole of the city, it doesn’t take account of nitrogen oxide or particulates, and it’s only for pedestrians.

So… who fancies taking the London Atmospheric Emissions Inventory maps, delivered in 20m grid shapefiles, and plugging them into one of the various OpenStreetMap routing engines to provide a walking & cycling “avoid polluted roads” option for London?

Bonus points could go to anyone who uses live data from the London Air Quality Network and Defra’s air quality monitoring web site (with its latest readings from a few monitoring stations) to give more or less priority depending on conditions.

Tagged , , , , , ,

All I want from OpenStreetMap is…

Kate Chapman and Mikel Maron have written a couple of interesting posts about improvements they’d like to see in OpenStreetMap. Kate’s is the more interesting to me, being based on various experiences with the Humanitarian OpenStreetMap Team projects.

Kate, the prolific Andy Allan and others have extensively covered the usability of editing tools. Frederik Ramm has pointed out that many of the editing tasks are conceptually complex so there are limits to how much software can make it easy for newcomers to get stuck in.

But I liked Kate’s point about using data. Along with the fun of editing OpenStreetMap, the principal benefit is supposed to be that we offer all this raw data, whereas Google, Bing and co just offer pre-designed maps. But who can actually use this data?

Here are some pen portraits to illustrate a few gaps in our toolsets. They are all based on real people I’ve known trying to do something with OSM.

People for whom OpenStreetMap is fantastic

Fred is a computer expert. He makes use of  Planet and the osmium/postgis/mapnik toolchain on his dedicated server to produce a custom online map for cyclists in the UK. He’s a happy chappy, an innovator.

Sally works in GIS and knows her way around commercial products like ArcGIS. She uses Geofabrik’s excellent download service to pull shapefiles into QGIS, where she does her usual analysis as part of her job. She’s pretty happy too, an early adopter.

Nabeel runs a small company who use a lot of maps on their web site and materials. He paid a consultant to set them up with MapBox’s tools for their web maps and a custom set-up to turn out nice printable maps for their leaflets. He’s a satisfied customer in the early majority of companies for whom the extra special OSM maps are worth paying a little extra.

People that might get somewhere with OpenStreetMap

Eilidh is an enthusiastic walker, who wants to produce hiking maps of the south downs showing her favourite routes. She already contributes to OSM using her GPS and Potlatch 2. She downloads Maperitive (which she was told about by a friend after much fruitless searching around the OSM web site) and manages to produce some maps of the area, but gets stuck adding her routes and tweaking the map design. She’s an early adopter, but with her technical skills Eilidh can’t quite produce her own maps yet.

James is a bit like Eilidh, but he wanted to share a proposed cycling route with the other members of his club. How easy is this? Dead easy with Google and the many web sites that cater for his needs. He likes the OpenStreetMap maps, but there’s nothing on the web site to explain how to do this simple task. He eventually found the CloudMade’s online maps and, putting in lots of hops in the directions tool, managed to plot the route and share the URL. Sadly it isn’t on top of the OpenCycleMap style map.

Nuzhat is a blogger who writes about poverty in London. She came across the wonderful GEMMA tool and has managed to produce some really nice illustrations of the relationship between deprivation and public transport for her blog. But she can’t embed the maps on her blog, and one look at OpenLayers plugins and Leaflet code turned her off immediately.

People sadly put off by OpenStreetMap

Jeannine is a volunteer with an environment charity that are promoting food growing. She’d like to get her network’s members mapping food growing spaces in their area, put a map of them on the charity’s web site and make nice posters and leaflets. They don’t have the budget to hire a consultant, the editor is too complex for most of their members to just add an allotment or community garden, and they have no idea how to produce the maps. They move on and just use Google like everyone else.

Ian is co-ordinating his local political party’s leafleting in the run up to an election. He wants to export a map suitable for printing and draw on top lots of little areas for people to take charge of. He gets totally confused by the export tab and the mixture of half-finished buildings and points of interest confuses his helpers, so he gives up and prints off a Google map to draw on instead.

Why using data matters

Given that most OpenStreetMap tools are created by wonderful volunteers or companies looking for a niche market, you might think – so what? If there’s demand, someone will build it.

Moreover, had I written this blog post just a year ago half of those tools I described wouldn’t exist, or would have been in their very early stages and so unusable. Things are moving on fast!

But think about some of those people for a moment, and what they could bring in terms of contributing and maintaining data:

  • James and his cyclist friends track new lanes and contraflow arrangements that the council put in, and are very particular about bollards and other things mapping parties often miss. Years after we started, the London Cycle Network is still incomplete and mapping of cycle infrastructure is extremely patchy, often out of date. James & co are the best bet to fix this.
  • Jeannine and her local groups live in some of those deprived, under-mapped areas Muki Haklay is often writing about. They could continue to update areas that tend to only get visited once in a blue moon by richer OSM enthusiasts on mapping parties.
  • Ian and his helpers walk down the same patch of streets several times a year, noticing every new home that’s built, past every shop that closes down. They’re the world’s best maintenance army. In my experience, only a fraction of London is currently kept really up to date by a few dozen enthusiastic innovators.

If we could start to make OSM more useful for those people, whether on openstreetmap.org or by others starting up their own web sites (like MapBox, Geofabrik, Cloudmade and GEMMA) the database would benefit enormously.

Tagged

Trip Stylist review: stroll around the City

A mere eighteen months after it had been given to us, Rachel and I went on our Trip Stylist day out around the City of London, “exploring hidden corners and treasures“.

We started out with brunch in a very nice little café tucked so well away that it made me wonder how anyone could find it without a tip. It was a very chilly morning, so a warm start was just what we needed. Rachel had mushrooms and a poached egg on soda toast, I tucked into a savoury pancake mountain.

Our brunch, just the ticket to start the day

We set off on full stomachs along narrow streets and past a few recommended parks in nooks and plaques in crannies to the Museum of London. I’ve cycled and walked past it innumerable times, that odd bunker in the middle of a roundabout, but never entered before. The exhibition design isn’t all that easy to follow, but it took us from the days of the hippopotamus wandering around the unpopulated Thames valley, through our hunting the aurochs to extinction, past Saxon and Viking and Roman and Norman invasions… well you get the idea.

A good mix of social history and Great Figures, including a fascinating collection of newspapers, pamphlets and placards from the turbulent early 20th century. I’d never heard of the Green Shirts, a left wing movement who wanted to end wage slavery and free man from the machine so we could enjoy more leisure time!

We then walked via a few other hidden treasures to the Guildhall Art Gallery, an altogether more establishment view of the world. The collection featured the usual heroic battles and religious scenes telling the ruling class version of English history, along with Victorian representations of classical scenes such as a large striking portrait of Klytaemnestra shortly after she committed her gory deed.

Our late afternoon stroll took us to the ruined church of St Dunstan-in-the-East, a lovely little haven and a reminder of the City’s deep and convoluted roots. Built in about 1100, it sheltered black death sufferers, was damaged in the Great Fire of London but saved from destruction by local schoolboys, expanded with designs by Christopher Wren, rebuilt again in the early 19th century, bombed out during the Blitz, and finally turned into a garden in the 1960s.

St Dunstan-in-the-East church in the City of London

From here we were advised to take the bus over to Whitechapel for our evening meal and drinks, but having time to spare we kept walking. It was surprisingly enjoyable strolling around an area I’m normally scurrying or pedaling through. The curry, at Tayyabs, was of course delicious, rounding off a fun day out.

The only thing I missed was a street map of the wider area. We occasionally hit temporary road closures, or got slightly confused, or needed the loo, or wanted a cup of tea. Knowing where to nip off to would have been a great help. A tool that could print off a map taking data from OpenStreetMap with just this useful info would be the perfect complement to the guide.

Tagged , , , ,
Follow

Get every new post delivered to your Inbox.

Join 44 other followers