Image Image Image Image Image Image Image Image Image Image

Being Brunel |

Scroll to top



Mapping the Eurocodes

Mapping the Eurocodes

Have you ever wondered why the Eurocodes are so damn annoying to use? I know I have. On my litany of things I hate about the Eurocodes are the way it always feels like you need to get 25 documents together before you can even begin to design anything. Finally, when bored on the train, I decided to see just how valid my complaints were, and how bad the problem is.

Let me present to you an interactive (click on the preview to browse) network graph mapping the references between the Eurocodes:


About the Data

For this map a ‘reference’ is an explicit mention of the code number (e.g. EN 1994-1-2). To avoid picking up the introduction that lists all the Eurocodes, I have excluded any references before the “1 General” header. To make the map clearer I have also ignored general ‘family’ references (e.g. mentions of the EN 1994 suite, rather than a specific part). I have also excluded NA references, etc. as it’s complicated enough without adding the non-EN documents you require.

Believe it or not, I didn’t painstakingly comb through every page of the Eurocodes to collect this data. I made a bot to do it. If you want to know how I made this map, you can check out the source code for the data extractor and plot data file builder here: on my GitHub. Unfortunately this means that the four Eurocodes PDFs with, inexplicably, encoded text have been omitted from this map:

  • EN 1995-1-1
  • EN 1993-6
  • EN 1993-1-10
  • EN 1991-1-4

But I never liked them anyway!

So next time you set sail on a voyage through the Eurocodes; don’t forget the map (or set it as your wallpaper!).

Submit a Comment

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.


  1. Ed Dablin

    Good work! Would OCR fix the issue of encrypted text? I use pdf xchange reader which is free.

    • Possibly- although that would substantially put up the analysis time; maybe for another update!

  2. It would be really interesting to see how AASHTO LRFD compares – though that’s just one giant (and I mean giant) document.

    • I used to think that big documents are unwieldy; but it’s nothing to having to juggle 10-20 medium size texts. Alas I’ve never had the chance to design to AASHTO, so I can’t speak from experience.

      • I have just spent my entire lunch hour trying to understand how the Eurocodes work. My initial goal was just to figure out the total number of pages for comparison to AASHTO’s 1,960 pages. And. Oh. My. Goodness. Eurocodes be crazy. “In total there are 58 EN Eurocode parts distributed in the ten Eurocodes.” I’m feeling pretty happy with my nice neat 15 chapters of AASHTO right now!

        • And the 58 documents all have National Annexes, so that’s 116 before you then get a clause that tells you to look at an auxiliary code!


  1. […] ’em or loathe them the Eurocodes have certainly changed things. And while I might argue about the execution, the Eurocodes have done a lot to help unify and allow us to benefit from design and construction […]

  2. […] epic Gulfs of Disapproval. I’m looking at the efforts to establish digital engineering, the Eurocodes, the CDM Regs. It seems that it’s easy for us to dismiss things and create a cloud of […]