Infrastructure Development for a London-based Disaster Test Scenario

Ongoing project...

Objective | Scenario | Methodololy | Modelling Process | I-X Integration

Objective

This project aims to develop a geographic information model based on part of the City of London, so that such an information can be used by the RoboCup Rescue simulator . The idea is to use this scenario to analyse and improve the performance emergency response teams in disaster situations like that:
"One hour ago an aeroplane crashed on the City of London. The aeroplane, a civil cargo transport, had begun to break up before impact, scattering debris and fuel over the entire area. As a result, multiple fires have broken out, roads are blocked, and a number of people, many injured, some seriously, are now trapped in burning buildings." [Source]

A second important step in this project is to define and implement the methods that support an appropriate integration of the simulator to the framework that intends to be demonstrated/evaluated. In our case this framework is being developed according to the e-Response proposal and, in particular, the I-X Architecture for planning and coordination.

A summary of the aims of this project is presented in follow:
  • Modelling of a geographic information set (node.bin, road.bin and building.bin) based on part of London;
  • Definition of a semantic level that contains additional information about the scenario objects;
  • Integration between simulator and planning/coordination architecture.
More details about this project can be found here.

Scenario

The scenario for our model is represented by the City of London, region showed in orange in the map below. This region is one of the most important areas of London due to the number of important historical and financial buildings, also presenting a considerable concentration of civilians and intense traffic in the roads. Together, such features characterise London city as a problematic region in case of disasters. The description in follow gives an abstract idea about this region.

"The City of London is home to the 'Square Mile', the main financial district of London, and as such many of the buildings are given over to office use, with residential use relatively low. Nonetheless, the City has around 8,000 residents, many of whom are concentrated in the Barbican Estate, the City's largest residential sector. The Estate, home to around 4,000 people, contains three of London's tallest buildings (Cromwell Tower, Shakespeare Tower and Lauderdale Tower, each 42 stories and 123 metres high), as well as the Barbican Centre, a centre for the arts, drama and business expositions, the City of London School for Girls, the Museum of London and the Guildhall School of Music and Drama. In addition, located within the City are a number of famous landmarks of historic, cultural or symbolic significance, including St. Paul's Cathedral, the Old Bailey, the Inns of Court, St. Bartholomew's Hospital (no A&E), the Bank of England and, on the fringes of the City, the Tower of London, as well as a number of more recent prominent additions to London's skyline, such as the Tower 42 (the "NatWest Tower") and 30 St. Mary Axe (the "Swiss Re Tower" or the "Gherkin"). Several important bridges across the Thames are located within the City, as are a number of mainline railway stations and Tower Gateway Docklands Light Railway station. The Central, Circle, District, Northern and Waterloo and City underground lines and the London Post Office Railway (now mothballed) pass under the sector." [Source]

In an initial moment we are focusing our model in the Southeast of London City (down right corner in the map, bounded by the red trace-line). The satellite photo shows the details of this region, such as the Tower of London and London Bridge (actually they are not officially part of City of London).



        Map source: http://www.cityoflondon.gov.uk Detailed map
Satellite images are a powerful resource to our modelling process because we can have a better notion about the region and its features. For example we can retrieval, with a reasonable precision, information about, for example, ground area of buildings, shape of buildings and roads, length and width of roads and general relative positions of such objects. For that it is important to consider the scale used by the image, in this case about 1cm to 100m in the real world.

Note that, during the real disaster operation, the command and control center must consider a wider area thah that directly affected by the disaster. For example, essential resources such as hospitals will be away from this area.



Map source: http://maps.google.co.uk

See also the interactive satellite image for this region.

Scale: |_____________| = about 200 meters.                                                       



Methodology

The efforts associated with this project can be divided into principal modules: the geographic information modelling process and the simulator/I-X integration. The steps of each of these modules are detailed in follow:
  • Geographic Information Modelling Process

    • Step 1.: Scenario definition with acquisition of maps (with scale) that give a clear idea about the objects of this scenario (roads, buildings, river, open areas and so on);

    • Step 2.: Information retrieval of roads' properties. Such properties are: name, length, width, width for walkers, road kind (elevation road, bridge or tunnel) and number of lanes;

    • Step 3.: Information retrieval of buildings' properties. Such properties are: name/number, entrance position(s), number of floors, kind of building (wooden, steel frame or reinforced concrete), area of the ground floor and total area of all floors;

    • Step 4.: Use of a modelling tool that convert all this information in data to be used by the RoboCup Rescue simulator (node.bin, road.bin and building.bin). In our case, this tool is JGISEdit. Download and details about this tool are available here;

  • Simulator/I-X Integration

    • Step 5.: Definition of a semantic layer that maps simulation information about the scenario objects to a common sense representation. an examples in this direction is the use of buildings and roads names rather than object simulation codes;

    • Step 6.: Implementation of skeleton agents that contains functions associated with the representational translation of data between the two platforms. For example, consider the geographic information format. While the simulator uses the orthogonal distance (x,y) from a pre-defined point to a specific object, in millimetres, to indicate the position of such a object; I-X agents use latitude/longitude values for that;

    • Step 7.: Organisation of the stuff related to the simulation execution on the I-X platform: map, object images and any other resource.

Results and comments about the performance of such steps are disclosed in the next sections.


Modelling Process

Step 1.: Scenario Definiton
As discussed at the beginning of this document, our initial focus is on the Southeast part of City of London. Good source of resources, such as maps and images, for this scenario are:
Step 2.: Roads Properties

Ref.NameLength (m)Width (m)Width/walk (m)TypeN. lanesStrip
01Gracechurch Street325205normal4no
02Whittington Avenue506.72normal2no
03Lime Street Passage62.56.72normal2no
04Pudding Lane1006.72normal2no
05Botolph Lane87.56.72normal2no
06Philpot Lane87.56.72normal2no
07Loyal Lane1004.71normal1no
08Saint Mary at Hill1256.72normal2no
09Rood Lane87.56.73normal1no
10Lime Street225103normal2no
11Idol Lane112.53.30normal1no
12Fencourt756.72normal2no
13Mincing Lane137.56.42normal2no
14Saint Dunstan's Hill10041.5normal1no
15Billter Street1256.72normal2no
16Mark Lane2506.72normal2no
17London Street112.541.5normal1no
18Fenchurch Place12541.5normal1no
19Seething Lane1506.72normal2no
20Trinity Square137.56.72normal2no
21Savage Gardens57.56.72normal2no
22Cooper's Row1506.73normal2no
23Fenchurch Street Station15041.5normal1no
24Lloyd's Avenue137.55.31.5normal1no
25Northumberland Alley1006.72normal2no
26Jewry Street2009.32.5normal2no
27Vine Street287.255.31.5normal1no
28King William Street200256normal4yes
29Minories400122.7normal3no
Ref.NameLength (m)Width (m)Width/walk (m)TypeN. lanesStrip
30Tower Bridge Approach275209.3normal2no
31Leadenhall Street375204normal4no
32Leadenhall Market505.31.5normal1no
33Leadenhall Place755.31.5normal1no
34Ship Tavern Passage7582.5normal2no
35Cullum Street87.582.5normal2no
36Fenchurch Avenue112.56.72normal2no
37Fenchurch Street450103normal3no
38Aldgate125174normal4yes
39Talbot Court4541.5normal1no
40Eastcheap175103normal4no
41Monument Street1256.72.5normal2no
42Lower Thames Street375174normal4yes
43Fish Street Hill9583normal2no
44Great Tower Street200103normal4no
45Dunster Court8083normal2no
46Star Alley406.72.5normal2no
47Tower Hill125174normal4yes
48Crosswall125103normal2no
49Hart Street112.5103normal2no
50Crutched Friars75103normal2no
51Pepys Street167.5103normal2no
52Muscovy Street62.5103normal2no
53Carlisle Avenue7583normal2no
54India Street5583normal2no
55Lower Thames Path5501515normal1no
56Byward Street225174normal4yes
57Tower Hill Path1181515normal1no
58Gloucester Court57.56.72normal2no
See the map with the roads' number references here.

Observation: values in this table are not precise and some of them are fictitious.

Step 3.: Buldings Properties

Ref.Obj.Name (building or one of its establishments)AddressGround Area (m2)Total Area (m2)Floors Type
01224Waterstones Booksellers2, Whittington Avenue199.984799.9364steel
02225Flats Building9, Lime Street Passage96.592579.5526steel
03226Barbour & Sons12, Ship Tavern Passage344.0322064.1926steel
04227Austin Reed Ltd.13, Fenchurch Street130.4241304.24010concrete
05236The Ship11, Talbot Court206.9841034.9205steel
06237AIG Europe37, Fenchurch Street232.6241163.1205steel
07238Greggs13, Eastcheap244.2401221.2005steel
08239The Britannia20, Monument Street166.432998.5926concrete
09240Tesco6, Eastcheap56.736340.4166steel
10241Speakers for Business1, Pudding Lane95.760574.5606concrete
11242Coral20, Fish Street Hill138.512831.0726concrete
12243Snax41, Fish Street hill123.848743.0886concrete
13244St. Magnus House3, Lower Thames Street81.400976.80012concrete
14264Express Newspaper10, Lower Thames Street55.008660.09612steel
15263Billingsgate Management Ltd.16, Lower Thames Street133.3041599.68412concrete
16297Cafe Nero88, Leadenhall Street262.5682100.5448steel
17298Chapters105, Leadenhall Street334.8324077.98412concrete
18299Flats Building4, Leadenhall Place205.7201851.4809steel
19296Flight Centre17, Lime Street701.2083506.0405concrete
20303Flats Building10, Fencourt341.4962048.8146concrete
21300Blades8, Cullum Street306.3041837.8246steel
22304Cafe Taj80, Fenchurch Street105.304842.4328steel
23275Swattybetty5, Rood Lane220.4403306.60015concrete
24276Flats Building3, Rood Lane245.1922206.7289steel
25246Benjys26, Eastcheap150.9681358.7129concrete
26247The Royal Town Institute41, Botolph Lane149.136894.8166concrete
27248London School of Commerce36, Botolph Lane90.032540.1926concrete
28250City Harvest37 Eastcheap119.840719.0406steel
29249Werna House31, Monument Street184.5681107.4086concrete
30251Reliance Bank23, Loyal Lane188.5121131.0726steel
31262The Vigilant Trust House20, Lower Thames Street104.480835.8408concrete
32261FB Offices30 Lower Thames Street137.456274.9122concrete
33277HSBC60, Fenchurch Street496.04810913.05622concrete
34279British Telecom11, Great Tower Street327.3843928.60812steel
35252Global Visas20, Saint Mary at Hill214.0482140.48010concrete
36253International Medical Press36, Saint Mary at Hill111.360890.8808concrete
37256Japanese Canteen19, Great Tower Street117.552705.3126concrete
38257St. Marys Court4, St. Durstan's Hill197.808197.8081wooden
39260Custom Hq.40, Lower Thames Street335.2642011.5846concrete
40302Flats Building20, Fencourt103.296619.7766steel
41305Lamas Ltd.105, Fenchurch Street279.4162514.7449steel
42399Nuclear Risk Injurers42, Mincing Lane277.8323333.98412steel
43400Japan England Insurance64, Mark Lane304.0322432.2568steel
44313Lorega Ltd.28, Great Tower Street363.3604360.32012concrete
Ref.Obj.Name (building or one of its establishments)AddressGround Area (m2)Total Area (m2)Floors Type
45259Nordic Bank20, St. Durstan's Hill 55.0083376.4646steel
46258Man Group Plc.50, Lower Thames Street102.824616.9446concrete
47293Institute of London Underwriters22, Billter Street495.6082973.6486concrete
48292Lloyds Bank113, Leadenhall Street417.3042503.8246steel
49294Auberge56, Mark Lane121.208727.2486steel
50295Blacks16, London Street89.104534.6246steel
51316Superdrug1, Fenchurch Place53.696322.1766steel
52320Fenchurch Station10, Crutched Friars327.752655.5042steel
53308St. Olaves Church8, Hart Street127.448764.6886steel
54321Market Bar2, Crutched Friars145.2321161.8568steel
55309The city2, Seething Lane154.432617.7284steel
56315Novotel London10, Pepys Street337.1042696.8328Steel
57307Costa Coffe74, Mark Lane649.4563896.7366concrete
58272Rattner Mackenzie Ltd.35, Seething Lane577.8243466.9446concrete
59314Red Rose37, Crutched Friars101.176809.4088steel
60273English Club26, Savage Gardens227.1842271.84010steel
61271Tower View13, Byward107.360858.8808steel
62274Tower Green1, Tower Hill464.728464.7281wooden
63268Easygroup42, Gloucester Court415.576831.1522steel
64269GNI Ltd.60, Lower Thames Street313.0561252.2244steel
65270E D & F Man Holdings Ltd 70, Lower Thames Street408.3841633.5364steel
66265Centurium House100, Lower Thames Street404.8322428.9926concrete
67317NatWest116, Fenchurch Street Station87.984351.9364steel
68323Lazio Ltd.109, Fenchurch Street72.280289.1204steel
69322JLT Services5, Lloyd's Avenue162.744813.7205steel
70290Norwich Union1, Lloyd's Avenue199.3601196.1606steel
71289AXA Insurance1, Aldgate505.7282022.9124concrete
72291Travel Alliance Ltd.7, Jewry Alliance Ltd.227.2001363.2006concrete
73281London Metropolitan University31, Jewry Street159.880959.2806concrete
74280St. Johns House50, Vine Street163.792982.7526concrete
75282Medical Centre75, Crosswall449.4482696.6686steel
76283Barclays Bank24, Minories230.6881384.1286steel
77286Benjys3, Cooper's Row336.7681010.3043steel
78284Defence House Executive42, Minories137.576550.3044steel
79288Grange City Hotel8, Cooper's Row611.3042445.21612concrete
80285BSC Management150, Minories89.512537.0726steel
81287Hospital Block4, Tower Hill537.760537.7601wooden
82266The casemates6, Tower Hill429.600429.6001wooden
83267Tower of London1, Tower Hill4657.7005657.7001wooden
84301Ecclesiastical Insurance Group19, Billter Street168.7681012.6086steel
85278RBS5, Great Tower Street241.0082892.09612concrete
86245Fuego1A, Pudding Lane115.568693.4086steel
87324Kennedys50, Mark Lane20.44881.7924steel
88319Halifax159, Fenchurch Street79.920319.6804steel
See the map with the buildings' number references here.

Observation1: values in this table are not precise and some of them are fictitious.
Observation2: the ground floor and total areas are calculated by the modelling tool. Thus we don't need to complete such values in this step.
Observation3: the names and addresses of buildings or their establishments are real, however their position in the road are not precise.
Observation4: the parameter "Obj." represents an internal identifier, which is specified by the modelling tool to each object of the scenario.

Step 4.: Modelling Tool


We are using JGISEdit as modelling tool to this London-based scenario. When we create a new project in this tool, we first need to specify the following parameters:
  • Left-Top coordinate (meters) - specifies the position of the scenario's left top corner. All the positions of the objects (nodes, buildings, roads and agents) in the scenario are given as the orthogonal distance (x,y) from this position. In our case we are using the the value (0,0) as the left-top corner coordinate;

  • Map Extent (meters) - specifies the total width and height of the scenario, or its area. In our case, this values are [width=888, height=695];

  • Raster file - specifies a optional image file that can be used as a background image for the map that is being modelled.
The package with the first version (Version 1.0) of our London-based scenario can be found here. Such package contains the following six files: gisini.txt, node.bin, road,bin, building.bin, galpolydata.dat and shindopolydata.dat. We are not using the two last files because they are specific to earthquakes events. Note that, rather than earthquakes, this project is interested in events associated with fire related disasters. The paper " Tools for checking & creating ***polydata.dat files" is a good resource if you are interested in the outcome format of the files.

Note that this scenario is still in a stage of tests and several of its features should change or be decided soon. These features are:

Number of buildings = 88
Number of roads = 57
Number of refugees = 01
Number of fire stations = 01
Number of police offices = 01
Number of hospitals = to be decided
Number of fire brigades = 10
Number of police forces = 10
Number of ambulances = to be decided
Number of civilians = to be decided
Number of fire points = 02

Future versions tend to increase the area and details of the scenario. Furthermore is also possible to set more precise values to the objects' properties. New requirements depend on the ongoing use of this scenario during the demonstrations of the AKT research group.



I-X Integration

Step 5.: Skeleton Agents

The architecture that is being used for this initial version is illustrated bellow. Agents are divided into two groups: RCR agents and I-X agents. RCR agents are provided in the simulator package (yapapi) and represent very simple agents that can be used as a basis for more complex implementations. I-X agents are the components that we have implemented and that are being evaluated inside the RCR environment. The main elements of this architecture are introduced in follow:
  • Police forces (PF) - one of their function is to cover the environment and send problems to the Police Office, which forwards such problems to the appropriate agent. For example, if any fire is discovered by a PF, a message is sent to the fire station via the police office;

  • Fire Station - accounts for receive the fire messages, creating new activities to be allocated to its fire brigades in an optimal way. This process can be manually carried out by users, or autonomously by the fire station agent. Handlers associated with this process can be provided as plug-ins;

  • Fire Brigades - if they do not have activities to be performed, they tend to stay in refugee places, where they can refill their water tanks. When they receive activities from the fire station, in the form Extinguish ?building, they try to find the best route to the specific building place to extinguish the fire in such a building;

  • Gray communication channel - uses the two basic RCR methods to perform communication between two or more agents. These two methods are: tell(message) and head(sender,message)

  • Red communication channel - uses the two basic I-X method to transmit and receive messages: sendObject(destination,contents) and handleInput(message), where message can bean issue, an activity, a constraint, a report or a chat message.

  • Blue communication channel - IX agents are, in this application, hybrid agents because they implement inner classes that represent RCR agents. In this way, the communication between IX and RCR agents are done via the RCR methods, however special functions are used to translate information between them because the internal formats used by RCR and IX agents are different.


We need to understand two forms of information translation performed during the blue communication. The base of facts of RCR agents (we are considering their implementation via the YAPAPI) is represented as a unique object (world) that contains several other objects, each of them modelling a specific object of this world (building, road, civilian, etc.). So the first method of translation consists in mapping the objects attributes to the I-X constraint format. An example is given below to a building:



Considering this example, we can see that the information translation is a direct and easy process. However, there is a problem associated with the position due to the different semantic used for each system (RCR and I-X). While the RCR simulator uses the orthogonal distance (x,y) from a pre-defined point to a specific object, in millimetres, to indicate the position of such an object; I-X agents use latitude/longitude values for that. Thus, we need to use a additional method of translation. For this case in particular we are using the regression method, a numerical technique of fitting a simple equation to real data points. This is possible because we know the set of position RCR values and their correspondent I-X values. Then, we just need to find a function that map a set to the other set. An example of result of this process is shown in follow.

public Double convertLongitude(int x) {
     double m = 65.532;
     double b = -48572.5553;
     double longitude = ((m*(x/1000))+b)/100000;
     return new Double(longitude);
}

This is the function, codified in Java, that is being used to convert x values to longitude values. The mathematical tool used to obtain that function was Data Lab - Version 2.1, which is available in a limited version (evaluation copy) for free. The same tool can be used to convert y values to latitude values.

This method of converting positions works well for small areas, like City of London. The inconvenient detail is that it is not a general method so that different areas will need different equations. A more general method is to use the UTM (Universal Transverse Mercator) projection. This approach is likely to be explored in future works.


Step 6.: Semantic Layer

The Semantic Layer accounts for augmenting the information about the disaster environment. In this way, there are two specific ideas associated with this layer: (1) to provide human-directed information rather than internal code or reference of objects, and (2) to produce new information that can improve the simulation purpose. Functions in this direction are:
  • Buildings' address - buildings are referred in the RCR as a unique integer value, such as 256. Thus, the attributes representation of this building using I-X constraints is ((attribute 256) = value). Note that this is not an appropriate representation for human users;

  • Roads' names - as buildings, roads are also referred as a unique integer value. Furthermore, due to internal representation used by RCR simulator, the same road can be represented for a set of segments. For example, the Billter Street is represented for the set (412,411,486,485);

  • Fire floor - the simulator just indicates the reference of the building in fire. An interesing information could be de levels that are in fire. This information could be used during the reasoning of fire brigade allocation so that the most appropriate agent could be sent to each fire site.

A brief explanation about the implementation of such functions are given in the table below.

Buildings' address functions
Couple of functions where the first receives a RCR building reference number and returns the address of this building. In a similar way, the second function receives the address and returns the RCR reference. Note that here the relation between the two sets is 1:1.
Roads' name functions
Also involves two functions: the first function receives a RCR road reference number and returns the name of this road. The second receives an array of road references (route), returning the corresponded road names for this route. Differently of buildings, here we have a 1:n relation between the sets. In other words, each RCR integer value corresponds to a unique road name, while a road name corresponds to a subset of integer values. The package documentation brings more details about this feature.
Fires' floors function
As this information does not exist in the simulator, it is generated in an aleatory way by the semantic level. This can be performed by a Random number generator function, which must observe the total number of levels of the building


Step 7.: I-X Application Package

I-London is an I-X application that evaluates planning and coordination ideas using the RoboCup Rescue Simulator and the London scenario discussed here. The I-London manual in follow, available in pdf and doc versions, gives details about the features and configuration of this application. The QuickStart document is a practical way of setting and running the application. For that, users must have installed the current version of the I-X package. Then the I-London Zip file (available soon) must be extracted in the ix-/apps directory.

Documents:

I-London Manual (PDF version)
I-London Manual (DOC version)
I-London Quick Start




AIAI Artificial Intelligence Applications Institute
Centre for Intelligent Systems and their Applications
School of Informatics, The University of Edinburgh
Page maintained by c.siebra@ed.ac.uk, Last updated: Wed Mar 22 00:39:41 2006