A holistic microclimate model

You are here: Technical Model Webpage » ENVI-met Applications Homepage » envimet

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
apps:envimet [2018/11/26 13:06] – enviadminapps:envimet [2018/11/26 15:21] – [Databasesystem and DBManager] enviadmin
Line 15: Line 15:
   * **ForcingCreator** assisting you to generate files for the new full-forcing based on meassured data or EPW files    * **ForcingCreator** assisting you to generate files for the new full-forcing based on meassured data or EPW files 
   * Converter tool from EDX files into the **NetCDFformat**   * Converter tool from EDX files into the **NetCDFformat**
-  * **Plug-in for Rhino Grasshopper/Ladybug** to create ENVI-met Area Input files and Simulation files and start ENVI-met from Grashopper+  * **Plug-in for Rhino Grasshopper/Ladybug** to create ENVI-met Area Input files and Simulation files and start ENVI-met from Grashopper **(to be released individually in early December)**
  
  
Line 26: Line 26:
  
  
-==== Databasesystem and DBManager ====+==== Databasesystem, DBManager and related ====
   * The ENVI-met database system has been extended to 6-char IDs to allow a better organisation of IDs. The system will automatically convert old 2-char IDs   * The ENVI-met database system has been extended to 6-char IDs to allow a better organisation of IDs. The system will automatically convert old 2-char IDs
   * The DBManager features a new tool to calculate pollutant emissions from car traffic based on standard emission factors   * The DBManager features a new tool to calculate pollutant emissions from car traffic based on standard emission factors
-  * +  * Receptor names can have any length now
  
 ==== Vegetation model  ==== ==== Vegetation model  ====