Using GIS in risk analysis : a case study of hazardous waste transport

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
  <record>
    <leader>00000nab a2200000 i 4500</leader>
    <controlfield tag="001">MAP20071030124</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20080418122019.0</controlfield>
    <controlfield tag="007">hzruuu---uuuu</controlfield>
    <controlfield tag="008">980506s1997    usa||||    | |00010|eng d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">852</subfield>
    </datafield>
    <datafield tag="100" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080198923</subfield>
      <subfield code="a">Lovett, Andrew A.</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Using GIS in risk analysis</subfield>
      <subfield code="b">: a case study of hazardous waste transport</subfield>
      <subfield code="c">Andrew A. Lovett, Julian P. Parfitt and Julii S. Brainard</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">This paper provides an illustration of how a geographic information system (GIS) can be used in risk analysis. It focuses on liquid hazardous waste transport and utilizes records archived by the London Waste Regulatory Authority. This data source provides information on the origin and destination of each waste stream, but not the route followed during transport. A GIS was therefore employed to predict the paths used, taking into account different routing criteria and characteristics of the available road network. Details were also assembled on population distribution and groundwater vulnerability, thus providing a basis for evaluating the potential consequences of a waste spillage during transport. Many parts of the research would not have been possible without a GIS, and the study demonstrates the considerable potential of such software in environmental risk assessment and management</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080630683</subfield>
      <subfield code="a">Tranporte de mercancías peligrosas</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080622138</subfield>
      <subfield code="a">Residuos tóxicos y peligrosos</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080630638</subfield>
      <subfield code="a">Sistemas de Información Geográfica</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080567484</subfield>
      <subfield code="a">Teledetección</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080588953</subfield>
      <subfield code="a">Análisis de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080603038</subfield>
      <subfield code="a">Prevención de riesgos</subfield>
    </datafield>
    <datafield tag="700" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080228231</subfield>
      <subfield code="a">Parfitt, Julian P.</subfield>
    </datafield>
    <datafield tag="700" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080213541</subfield>
      <subfield code="a">Brainard, Julii S.</subfield>
    </datafield>
    <datafield tag="740" ind1="0" ind2=" ">
      <subfield code="a">Risk analysis</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="t">Risk analysis</subfield>
      <subfield code="d">New York and London</subfield>
      <subfield code="g">Vol. 17, nº 5, 1997 ; p. 625-633</subfield>
    </datafield>
  </record>
</collection>