Module Vegetation - Revision history

Lucian: /* Property */

2017-03-28T15:40:52Z

‎Property

2017-03-28T15:40:29Z

‎Property

2017-03-28T15:40:10Z

‎Property

2017-03-28T15:39:45Z

‎Property

2017-03-28T15:39:13Z

‎Property

2017-03-28T15:37:32Z

‎Agricultural Practices

2017-03-28T15:35:05Z

‎How to pre-process vegetation properties

2017-03-28T15:33:20Z

‎If Vegetation is not used

2017-03-28T15:32:47Z

‎Agricultural Practices

2017-03-28T15:32:03Z

‎Property

@@ Line 10: / Line 10: @@
 === Property ===
 Vegetation model was redesigned to be structured in properties instead of vegetation types.
-The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see /*How to pre-process vegetation*/ ).
+The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see How to pre-process vegetation).
 In the previous structure, applications with several vegetation covers could rapidly increase input file lines and input errors. Moreover, as they are not graphed in time serie or hdf the visual inspection could take longer.

@@ Line 10: / Line 10: @@
 === Property ===
 Vegetation model was redesigned to be structured in properties instead of vegetation types.
-The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see /*[How to pre-process vegetation*/ ).
+The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see /*How to pre-process vegetation*/ ).
 In the previous structure, applications with several vegetation covers could rapidly increase input file lines and input errors. Moreover, as they are not graphed in time serie or hdf the visual inspection could take longer.

@@ Line 10: / Line 10: @@
 === Property ===
 Vegetation model was redesigned to be structured in properties instead of vegetation types.
-The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see [How to pre-process vegetation]).
+The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see /*[How to pre-process vegetation*/ ).
 In the previous structure, applications with several vegetation covers could rapidly increase input file lines and input errors. Moreover, as they are not graphed in time serie or hdf the visual inspection could take longer.

@@ Line 10: / Line 10: @@
 === Property ===
 Vegetation model was redesigned to be structured in properties instead of vegetation types.
-The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see [[How to pre-process vegetation]]).
+The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see [How to pre-process vegetation]).
 In the previous structure, applications with several vegetation covers could rapidly increase input file lines and input errors. Moreover, as they are not graphed in time serie or hdf the visual inspection could take longer.

@@ Line 10: / Line 10: @@
 === Property ===
 Vegetation model was redesigned to be structured in properties instead of vegetation types.
-The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see How to pre-process vegetation).
+The advantage of this structure is that in the input file the number of properties is fixed (no matter the complexity of the vegetation cover) and input can be preprocessed for the entire grid (see [[How to pre-process vegetation]]).
 In the previous structure, applications with several vegetation covers could rapidly increase input file lines and input errors. Moreover, as they are not graphed in time serie or hdf the visual inspection could take longer.

@@ Line 16: / Line 16: @@
 === Agricultural Practices ===
-Vegetation module was also restructured in a way that what user gives for each cell is what is the agricultural practice present (constant, variable in space, variable in space and time (rotations) and a file where the agricultural practices are defined as a recipe where the user can add or delete ingredients or actions.
+Vegetation module was also restructured in a way that what user gives for each cell what is the agricultural practice present (constant, variable in space, variable in space and time (rotations) and a file where the agricultural practices are defined as a recipe where the user can add or delete ingredients or actions.
 In this way, the user may manage its agricultural practices adding an unlimited number of fertilization or pesticide applications, change planting, and harvest dates, change the crop used or create new adapted agricultural practices for a general land use or go to the detail for each specific farm management actions. For more details see the examples at the end.

@@ Line 369: / Line 369: @@
 === How to pre-process vegetation properties ===
-Fill Matrix was updated to fill grids without interpolation. Instead of space stations (X,Y coordinate) user has to provide a vegetation grid with ID's and the values assigned to each ID (time serie or single value). Fill Matrix reads ID in the grid and searches for the value to fill the cell. If cells are not filled error message is sent.
+Fill Matrix was updated to fill grids without interpolation. Instead of space stations (X,Y coordinate) the user has to provide a vegetation grid with ID's and the values assigned to each ID (time serie or single value). Fill Matrix reads ID in the grid and searches for the value to fill the cell. If cells are not filled error message is sent.
 See [[FillMatrix]] for more details

@@ Line 26: / Line 26: @@
 then transpiration is not computed.
-However, the user may want to still evaporate water from soil surface. To do so, evapotranspiration must be enabled in basin data file:
+However, the user may want to still evaporate water from the soil surface. To do so, evapotranspiration must be enabled in basin data file:
   EVAPOTRANSPIRATION : 1
-and reference evapotranspiration defined (property standard). In this case all the reference evapotranspiration will be in the form of potential evaporation.
+and reference evapotranspiration defined (property standard). In this case, all the reference evapotranspiration will be in the form of potential evaporation.
 ===If Vegetation is readed from file ===