Aerius Module theory: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The Aerius module calculates NOX and NH3 pollution on Natura 2000 areas by using the [https://connect.aerius.nl/api/doc/ AERIUS Connect Api].
{{unavailable}}
 
See the [[Aerius module overview]] for an overview of the general concept, input and output.  
==Concept==
# Existing or to be constructed buildings create NOX and NH3 emissions. These emissions also possibly pollute Natura 2000 areas.
# The emissions are categorized by Aerius into sectors and sub types within these sectors.
# Each sector has its own feature description, for which Aerius can calculate the corresponding emissions.
# A {{software}} session represents a single situation in an Aerius calculation. This means that the Natura 2000 pollution is calculated for the current state of the project session, not per individual feature.


==Calculation==
==Calculation==
# Buildings are converted into one or more GML features identifiable by the Aerius Connect Api.  
# [[Building]]s are converted into one or more GML features for identifying by the Aerius Connect API.  
# These features are represented as a line for roads or a center-point otherwise.
# These features are represented as a line for roads, otherwise a center-point.
# These features are combined into a collection and put in a situation feature.
# These features are combined into a collection and put in a situation feature.
# This situation is send to the Aerius Connect Api and a calculation job is started
# This situation is sent to the Aerius Connect API and a calculation job is started
# This job is polled until completed.
# This job is polled until completed.
# When completed, the calculation results are retrieved and processed.
# When completed, the calculation results are retrieved and processed.
# Emissions for the various features (roads, construction plans, construction machines) related to a building are summed up and stored under the [[Nox_(Aerius_Overlay)|NOX]] and [[Nh3_(Aerius_Overlay)|NH3]] [[Overlay_Key|keys]] for that building.
# Emissions for the various features related to a Building are stored under the [[Nox_(Aerius_Overlay)|NOX]] and [[Nh3_(Aerius_Overlay)|NH3]] attributes for that Building. If the Building is a [[Building#Categorization|road]], the traffic emissions are shown. Otherwise, the emissions for plan, work and living and mobile machines are summed and shown here.
# Natura 2000 Hexagon polygons are converted to grid cells with their respective NOX and NH3 mol/ha/year values.
# Natura 2000 Hexagon polygons are converted to grid cells with their respective NOX and NH3 mol/ha/year values.
# Natura 2000 Hexagon polygons values are also stored as an array in the Aerius Overlay under the [[Nox_overlay_attribute_(Aerius_Overlay)|NOX]] and [[Nh3_overlay_attribute_(Aerius_Overlay)|NH3]] attributes.
# Natura 2000 Hexagon polygons values are also stored as an array in the Aerius Overlay under the [[Nox_overlay_attribute_(Aerius_Overlay)|NOX]] and [[Nh3_overlay_attribute_(Aerius_Overlay)|NH3]] attributes.
Line 25: Line 20:


==Considerations==
==Considerations==
* Only buildings are processed for specific attributes such as number of light traffic, create surface office and shop space, used fuel per year for construction and direct emissions of NOX and NH3.
* NOX and NH3 deposition is returned by the Aerius Connect API as hexagon features, which are stored in the Aerius Overlay's grid. Only when Natura 2000 areas are inside the project bounds, these hexagons can be seen. The array of individual values in mol/hectare/year per hexagon are also stored in the Aerius overlay under the [[Nox_overlay_attribute_(Aerius_Overlay)|NOX]] and [[Nh3_overlay_attribute_(Aerius_Overlay)|NH3]] keys respectively. These values are sorted by the highest 100 values for the hexagons and therefore not restricted by the project bounds.
* Per sector these attributes are converted to individual Aerius features. These features are encoded using the GML-format, which is the primary data format the AERIUS Connect Api accepts.
* Only buildings are processed for specific attributes such as number of light traffic, office and shop area size, used fuel usage per year for buildings and direct emissions of NOX and NH3.
* A single building can therefore be send as multiple features, one for each sector. For some types of feature, the Aerius Connect Api calculates NOX- and NH3-emission values, which are written back into the building
* Per sector these attributes are converted to individual Aerius features. These features are encoded using the GML-format, which is the primary data format the AERIUS Connect API accepts.
* Only the sum of NOX emissions is stored per building, not per sector. NH3 emissions likewise.
* A single building can therefore be send as multiple features, one for each sector. For some types of features, the Aerius Connect Api calculates NOX- and NH3-emission values, which are written back into the building.
* NOX and NH3 pollution is returned by the Aerius Connect Api as hexagon features, which are stored in the Aerius overlay's grid. Only when Natura 2000 areas are inside the project bounds, these hexagons can be seen. The array of individual emission values are also stored in the Aerius overlay under the NOX and NH3 attribute respectively.
* Only the sum of NOX emissions is stored per building, not per sector. Likewise for NH3 emissions. The traffic sector is an exception to this, traffic emissions are stored per road buildings.  
* Depending on the amount of features send to the Aerius Connect Api, the calculation jobs can take considerable time. The Aerius module stops waiting for a job after 5 minutes.
* Depending on the amount of features send to the Aerius Connect API, the calculation jobs can take considerable time. The Aerius module stops waiting for a job after 5 minutes.
 
{{Template:Aerius Module buttons}}

Latest revision as of 13:54, 3 November 2023

This functionality is currently unavailable or non-functional.

See the Aerius module overview for an overview of the general concept, input and output.

Calculation

  1. Buildings are converted into one or more GML features for identifying by the Aerius Connect API.
  2. These features are represented as a line for roads, otherwise a center-point.
  3. These features are combined into a collection and put in a situation feature.
  4. This situation is sent to the Aerius Connect API and a calculation job is started
  5. This job is polled until completed.
  6. When completed, the calculation results are retrieved and processed.
  7. Emissions for the various features related to a Building are stored under the NOX and NH3 attributes for that Building. If the Building is a road, the traffic emissions are shown. Otherwise, the emissions for plan, work and living and mobile machines are summed and shown here.
  8. Natura 2000 Hexagon polygons are converted to grid cells with their respective NOX and NH3 mol/ha/year values.
  9. Natura 2000 Hexagon polygons values are also stored as an array in the Aerius Overlay under the NOX and NH3 attributes.

Technical Overview

  • Platform to aerius.jpg
  • Aerius to platform.png

Considerations

  • NOX and NH3 deposition is returned by the Aerius Connect API as hexagon features, which are stored in the Aerius Overlay's grid. Only when Natura 2000 areas are inside the project bounds, these hexagons can be seen. The array of individual values in mol/hectare/year per hexagon are also stored in the Aerius overlay under the NOX and NH3 keys respectively. These values are sorted by the highest 100 values for the hexagons and therefore not restricted by the project bounds.
  • Only buildings are processed for specific attributes such as number of light traffic, office and shop area size, used fuel usage per year for buildings and direct emissions of NOX and NH3.
  • Per sector these attributes are converted to individual Aerius features. These features are encoded using the GML-format, which is the primary data format the AERIUS Connect API accepts.
  • A single building can therefore be send as multiple features, one for each sector. For some types of features, the Aerius Connect Api calculates NOX- and NH3-emission values, which are written back into the building.
  • Only the sum of NOX emissions is stored per building, not per sector. Likewise for NH3 emissions. The traffic sector is an exception to this, traffic emissions are stored per road buildings.
  • Depending on the amount of features send to the Aerius Connect API, the calculation jobs can take considerable time. The Aerius module stops waiting for a job after 5 minutes.


Benchmarks button.png
Aerius button.png
Aerius Module
Benchmarks button.png
Getting started button.png
Tutorials
Benchmarks button.png
Overview button.png
Overview
Benchmarks button.png
Theory button.png
Theory
Benchmarks button.png
Benchmarks button.png
Benchmarks
Retrieved from "https://support.tygron.com/w/index.php?title=Aerius_Module_theory&oldid=56131"