PDF version-A +A

PROKAS_E - Description

PROKAS_E is a modul for calculate traffic induced emission. It is available in WinMiskam and SELMAGIS PROKAS

The calculation of traffic induced emission on road segments requires the following input data:

  • Traffic situation as combination of the area of interest, road category,  tempo limit, level of service and road slope.
  • mean daily traffic volume (DTV)
  • HDV-share of the vehicle fleet
  • Optionally: absolute number of passenger cars, motorcycles, light commercial vehicles (LH), heavy duty vehicles (HDV) (mix: trucks, trailers, ..), urban buses and tour coaches

This Information should be saved in the SD3-Format  (ASCII- or ESRI-Shape-Format).

Additionally PROKAS_E requires one or more emission factor tables (EFT3-Format) according to a representativ year (Annex 3).

PROKAS_E implements the following functionality:

  • Loading a SD3-File (ASCII and ESRI-Shapeformat)
  • Loading and showing EFT3-File(s)
  • Errorreporting of input data
  • Selection of user defined pollution substances
  • Considering additional Stop&Go shares [also seperated by light vehicles (LV) and heavy vehicles (HV)]
  • Emission calculation for PM10 and PM2.5 in tunnel and for bad road conditions uses modified E-factors.
  • Emission calculation as emission sum of all vehicle categories or
  • seperated by vehicle categories or sumerized by LV und HV
  • Emission Calculation for each road segment and saving as SD3-File (ASCII- or Shape-Format)
  • All input data and paramters (e.g. emission factors as table) are documentated in a log-file, in an Excel-file.
  • Hint: working with SD3-files as ASCII-Format the functionality of PROKAS_E is limited. (e. g. delete columns)

 

 

 

Extract of smple data

Emission factor table (EFT3-File) Extract:

 

SD3-File

The SD3-File uses a format, which includes the coordinates of the road segment, the road width, specific emission density of each substance, the amount of traffic, the heavy vehicle share, traffic situation and the source height above ground. for each segment a record should be defined. Each line has to be defined only with two points. In the ascii format the columns are seperated with semicolons.