<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">445890460</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180317145614.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170323e20111101xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s11116-011-9357-6</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s11116-011-9357-6</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">Income-contingent user preferences in policy evaluation: application and discussion based on multi-agent transport simulations</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Benjamin Kickhöfer, Dominik Grether, Kai Nagel]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Standard economic policy evaluation allows the realization of projects if the aggregated economic benefit outweighs their costs. The use of one single aggregated welfare measure for evaluating and ranking projects has often been criticized for many reasons. A major issue is that differentiated effects on individuals or subgroups of the population are not taken into consideration. This leads to the need for transport planning tools that provide additional information for politicians and decision makers. The microscopic multi-agent simulation approach presented in this paper is capable of helping to design better solutions in such situations. In particular, it is shown that the inclusion of individual income in utility calculations allows a better understanding of problems linked to public acceptance. First, individual income-contingent utility functions are estimated based on survey data in order to describe human mobility behavior. Subsequently, using the MATSim framework, the implementation is tested in a test scenario. Furthermore, and going beyond Franklin (2006), it is shown that the approach works in a large-scale real world example. Based on a hypothetical speed increase of public transit, effects on the welfare distribution of the population are discussed. It is shown that the identification of winners and losers seems to be quite robust. However, results indicate that a conversion or aggregation of individual utility changes for welfare analysis is highly dependent on the functional form of the utility functions as well as on the choice of the aggregation procedure.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer Science+Business Media, LLC., 2011</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Policy evaluation</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Public acceptance</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Individual utility function</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Income-dependency</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Welfare economics</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Agent-based modeling</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Kickhöfer</subfield>
   <subfield code="D">Benjamin</subfield>
   <subfield code="u">Transport Systems Planning and Transport Telematics, Berlin Institute of Technology (TU Berlin), 10587, Berlin, Germany</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Grether</subfield>
   <subfield code="D">Dominik</subfield>
   <subfield code="u">Transport Systems Planning and Transport Telematics, Berlin Institute of Technology (TU Berlin), 10587, Berlin, Germany</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Nagel</subfield>
   <subfield code="D">Kai</subfield>
   <subfield code="u">Transport Systems Planning and Transport Telematics, Berlin Institute of Technology (TU Berlin), 10587, Berlin, Germany</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Transportation</subfield>
   <subfield code="d">Springer US; http://www.springer-ny.com</subfield>
   <subfield code="g">38/6(2011-11-01), 849-870</subfield>
   <subfield code="x">0049-4488</subfield>
   <subfield code="q">38:6&lt;849</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">38</subfield>
   <subfield code="o">11116</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s11116-011-9357-6</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s11116-011-9357-6</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Kickhöfer</subfield>
   <subfield code="D">Benjamin</subfield>
   <subfield code="u">Transport Systems Planning and Transport Telematics, Berlin Institute of Technology (TU Berlin), 10587, Berlin, Germany</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Grether</subfield>
   <subfield code="D">Dominik</subfield>
   <subfield code="u">Transport Systems Planning and Transport Telematics, Berlin Institute of Technology (TU Berlin), 10587, Berlin, Germany</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Nagel</subfield>
   <subfield code="D">Kai</subfield>
   <subfield code="u">Transport Systems Planning and Transport Telematics, Berlin Institute of Technology (TU Berlin), 10587, Berlin, Germany</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Transportation</subfield>
   <subfield code="d">Springer US; http://www.springer-ny.com</subfield>
   <subfield code="g">38/6(2011-11-01), 849-870</subfield>
   <subfield code="x">0049-4488</subfield>
   <subfield code="q">38:6&lt;849</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">38</subfield>
   <subfield code="o">11116</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
