gde_calculations_prototype merge requestshttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests2022-02-04T18:42:50+01:00https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/22Reduced number of parameters used to define building classes and general new-...2022-02-04T18:42:50+01:00Cecilia NievasReduced number of parameters used to define building classes and general new-ESRM20 updateMain changes:
- Reduced number of parameters used to define building classes
- Added alternative ESRM20 file naming (the pattern of file names has changed with respect to the old in-progress version)
- Made currency and cost fields conf...Main changes:
- Reduced number of parameters used to define building classes
- Added alternative ESRM20 file naming (the pattern of file names has changed with respect to the old in-progress version)
- Made currency and cost fields configurable parametershttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/21Fixed bug in get_area_polygon_on_Earth()2021-11-08T17:31:30+01:00Cecilia NievasFixed bug in get_area_polygon_on_Earth()This MR closes https://git.gfz-potsdam.de/dynamicexposure/legacy/gde_calculations_prototype/-/issues/12.This MR closes https://git.gfz-potsdam.de/dynamicexposure/legacy/gde_calculations_prototype/-/issues/12.https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/20Draft: Resolve "Function get_area_polygon_on_Earth does not work properly"2021-11-08T17:29:53+01:00Cecilia NievasDraft: Resolve "Function get_area_polygon_on_Earth does not work properly"Closes #12Closes #12https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/19Adjust occupancy sub-types classification and narrow down commercial building...2021-09-07T17:56:47+02:00Cecilia NievasAdjust occupancy sub-types classification and narrow down commercial building classes based on occupancy typeThis merge request addresses these two issues:
1. *Narrowing down commercial building classes based on occupancy type*: The GDE prototype code assigns SERA building classes and their probabilities to each OBM building, based on its loca...This merge request addresses these two issues:
1. *Narrowing down commercial building classes based on occupancy type*: The GDE prototype code assigns SERA building classes and their probabilities to each OBM building, based on its location. The previous version of the code only narrows down the possible building classes as a function of the number of storeys, when the latter is available in OSM/OBM. This new feature allows for further narrowing down of the commercial building classes using the `OCCUPANCY_TYPE` field of the SERA CSV files. If the occupancy type of the building is sufficiently constrained in OBM, then we can only assign, for example, "Trade" building classes to OBM buildings labelled as COM1, and so on.
2. *Adjusting occupancy sub-types considered from OBM to reflect sub-types considered in ESRM20*: ESRM20's exposure model comprises the following occupancies categories and their subtypes:
* Residential:
* residential buildings considered in national censuses and statistics (they usually include mixed commercial and residential use)
* Commercial:
* offices
* wholesale and retail trade
* hotels and restaurants
* Industrial:
* manufacturing
* mining
* quarrying
* constructionhttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/18Adaptation of the GDE prototype code to work with quadtiles instead of 10-arc...2021-07-21T16:55:32+02:00Cecilia NievasAdaptation of the GDE prototype code to work with quadtiles instead of 10-arcsec cellsThis new version of the GDE prototype code works with zoom-level 18 quadtiles instead of 10-arcsec cells.
Apart from minor adjustments in several scripts, the major changes are associated with:
- Complete modification of `GDE_TOOLS_worl...This new version of the GDE prototype code works with zoom-level 18 quadtiles instead of 10-arcsec cells.
Apart from minor adjustments in several scripts, the major changes are associated with:
- Complete modification of `GDE_TOOLS_world_grid.py` to define zoom-level 18 quadtiles.
- Creation of function to retrieve GHS built-up area from the [OBM Tiles database](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/database-obmtiles) in `GDE_TOOLS_psql.py`.
- Creation of function to retrieve completeness values from the [OBM Tiles database](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/database-obmtiles) in `GDE_TOOLS_psql.py`.
- Fixing of a bug in `transform_dict_into_dataframe` of `GDE_TOOLS_read_SERA.py` when the sum in row is zero.https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/17Modified scripts further down the processing line to work well with the new d...2021-06-07T16:09:35+02:00Cecilia NievasModified scripts further down the processing line to work well with the new definition of industrial cellsThis is the last merge request associated with the definition of the industrial exposure of several European countries in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid (dynamicexposure/collaboration#40)...This is the last merge request associated with the definition of the industrial exposure of several European countries in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid (dynamicexposure/collaboration#40). Previous merge requests have dealt with new functions needed by the new feature. This last one gathers small changes that were needed for the rest of the existing code to keep on working properly.
Previous merger request: !16
*Note: This merge requests have to do with scripts written before agreeing on style and other coding formatting issues. I have not changed the formatting of these files.*
\\approve @fd
\\rfc @ds
\\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/16Completed module and tools that create industrial cells around input points2021-06-04T18:10:17+02:00Cecilia NievasCompleted module and tools that create industrial cells around input pointsThe industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the ...The industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the full definition of the 30-arcscec grid. We need to define the polygons of the cells of which the given points are centroids in order to then treat them as the equivalent of "districts" for the industrial case.
This merge request is the sixth of several that aim at implementing this feature. The following is included in this sixth merge request:
- Added the last three functions to `GDE_TOOLS_create_industrial_cells.py`:
- `export_modified_aggregated_model_file()`: this function writes the DataFrame that contains the SERA exposure model modified to make reference to the cell IDs to a CSV file.
- `export_cells_to_geodatafile()`: this function creates a geospatial data file of a given format, with the IDs and geometries of the generated cells.
- `which_countries_on_a_grid()`: this function retrieves the list of countries for which the industrial exposure is defined on a 30-arcsec grid in the SERA exposure model. This information is provided in the EFEHR repository within an Excel spreadsheet called "European_Exposure_Model_Data_Assumptions.xlsx".
- Added the callable script `SERA_creating_industrial_cells.py`. This is the script that can be run to generate and export the industrial cells of a country or a list of countries. The output consists of a geodata file that contains the geometries of the cells, an updated version of the input SERA industrial exposure model, that includes the IDs of the generated cells, and a series of log files.
- Updated `GDE_config_file_TEMPLATE.ini` to include a section dedicated to `SERA_creating_industrial_cells` and the new parameter `boundaries_type` under the `File Paths` section.
- Updated `GDE_TOOLS_read_config_file.py`, the tools that read and process the parameters specified in the configuration file, to be able to process the new parameters.
- Expanded the documentation to cover this new feature:
- Adjusted `02_Execution.md`
- Adjusted `04_Core_Scripts.md`
- Added `08_Industrial_Cells.md` (and associated image files), fully dedicated to explaining the new feature
This feature is associated with dynamicexposure/collaboration#40
Previous merger request: !15
*Note: print statements are used to indicate errors/problems as a full logger functionality is not yet part of the prototype code (quite a manual logging system is set up in some core scripts, though; a full logger functionality will probably not be incorporated to the prototype code but go directly in the refactoring).*
\\approve @fd
\\rfc @ds
\\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/15Added core function to create cells around SERA industrial points of a country2021-05-17T16:46:58+02:00Cecilia NievasAdded core function to create cells around SERA industrial points of a countryThe industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the ...The industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the full definition of the 30-arcscec grid. We need to define the polygons of the cells of which the given points are centroids in order to then treat them as the equivalent of "districts" for the industrial case.
This merge request is the fifth of several that aim at implementing this feature. The following is included in this fifth merge request:
- Added three functions to `GDE_TOOLS_create_industrial_cells.py`:
- `generate_country_industrial_cells()`: This is the core function of this functionality and uses all other previously added functions. It goes all the way from an input exposure file from an aggregated model of a country to providing as output the associated cells, adjusted to avoid gaps and overlaps. The geometries of the cells are trimmed to lie within the country boundaries. The user can select whether to carry out quality/consistency checks and to keep on adjusting the geometries if one of these checks fails.
- `get_distance_centroids()`: This function is one of the consistency checks of `generate_country_industrial_cells()` and it calculates the distance between the original points in the aggregated exposure model and the centroids of the cells' geometries. It is run before trimming the cells as per the country boundaries.
- `get_relative_area_range()`: This function is one of the consistency checks of `generate_country_industrial_cells()` and it calculates a measure of the variability of the area of the geometries of the cells.
- Added tests for these functions to `test_GDE_TOOLS_create_industrial_cells.py`.
- Added test files needed for the test of `generate_country_industrial_cells()` to `tests/data/GDE_TOOLS_create_industrial_cells`.
This feature is associated with dynamicexposure/collaboration#40
Previous merger request: !14
*Note: print statements are used to indicate errors/problems as a full logger functionality is not yet part of the prototype code (quite a manual logging system is set up in some core scripts, though; a full logger functionality will probably not be incorporated to the prototype code but go directly in the refactoring).*
\\approve @fd
\\rfc @ds
\\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/14Added subsequent functions to create cells around SERA industrial points2021-05-06T18:02:33+02:00Cecilia NievasAdded subsequent functions to create cells around SERA industrial pointsThe industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the ...The industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the full definition of the 30-arcscec grid. We need to define the polygons of the cells of which the given points are centroids in order to then treat them as the equivalent of "districts" for the industrial case.
This merge request is the fourth of several that aim at implementing this feature. The following is included in this fourth merge request:
- Added seven functions to `GDE_TOOLS_create_industrial_cells.py`:
- `auto_adjust_overlaps_gaps()`: This function resolves overlaps/gaps between cells by averaging the coordinates of the corresponding boundaries. The inputs include a full GeoDataFrame of cells and another one of their intersections. The function goes one by one each of the intersections. It calls `define_threshold_angle()`, `angles_from_coords()`, `determine_cardinal_point()` and `adjust_coord_of_polygons()`.
- `adjust_coord_of_polygons()`: This function adjusts the geometry of the two input polygons so that there is no overlap or gap between them. The relative position of one polygon with respect to another is given as input too and is used to determine which coordinates to adjust, by calling `retrieve_coords_to_adjust()`.
- `retrieve_coords_to_adjust()`: This function returns the position of the coordinates that need to be changed in two cells/tiles whose relative position is given by the input string.
- `determine_cardinal_point()`: This function "translates" each angle in the input array into a direction in terms of "cardinal points".
- `guarantee_radians()`: This function converts the input into radians if given in degrees.
- `angles_from_coords()`: This function calculates the angle formed by an east-west line and a segment formed by the two input points.
- `define_threshold_angle()`: This function defines the threshold angle to consider one cell at a particular cardinal point with respect to another cell. The threshold angle depends only on the widths of the cells.
- Added tests to three of these functions to `test_GDE_TOOLS_create_industrial_cells.py`. The test of the other four functions would be trivial.
This feature is associated with dynamicexposure/collaboration#40
Previous merger request: !13
*Note: print statements are used to indicate errors/problems as a full logger functionality is not yet part of the prototype code (quite a manual logging system is set up in some core scripts, though; a full logger functionality will probably not be incorporated to the prototype code but go directly in the refactoring).*
\\approve @fd
\\rfc @ds
\\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/13Added more functions to create cells around SERA industrial points2021-05-06T10:14:04+02:00Cecilia NievasAdded more functions to create cells around SERA industrial pointsThe industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the ...The industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the full definition of the 30-arcscec grid. We need to define the polygons of the cells of which the given points are centroids in order to then treat them as the equivalent of "districts" for the industrial case.
This merge request is the third of several that aim at implementing this feature. The following is included in this third merge request:
- Added six functions to `GDE_TOOLS_create_industrial_cells.py`:
- `build_adjusted_cells_dataframe()`: update the geometries of the input GeoDataFrame as indicated by the coordinates in a dictionary given as input (the dictionary which is output of `adjust_coords()`).
- `overlap_by_full_geom_intersection()`: carry out the intersection of all the geometries in the input GeoDataFrame with each other, going row by row. Used to detect overlaps (and gaps when the cells in the input GeoDataFrame have been expanded by a buffer, in combination with `swell_cells_with_buffer()` and other steps).
- `define_col_names()`: auxiliary function for `overlap_by_full_geom_intersection()` to define column names.
- `swell_cells_with_buffer()`: expand the cells in the input GeoDataFrame as per the offsets given as input. Used to detect gaps between cells (combined with a geometry subtraction in a separate step).
- `enforce_boundaries_lon()`: auxiliary function for `swell_cells_with_buffer()` to force longitude values in the input array to be in the range [-180.0,+180.0].
- `enforce_boundaries_lat()`: auxiliary function for `swell_cells_with_buffer()` to force latitude values in the input array to be in the range [-90.0,+90.0].
- Added tests to those six functions to `test_GDE_TOOLS_create_industrial_cells.py`.
This feature is associated with dynamicexposure/collaboration#40
Previous merger request: !12 (merged)
_Note: print statements are used to indicate errors/problems as a full logger functionality is not yet part of the prototype code (quite a manual logging system is set up in some core scripts, though; a full logger functionality will probably not be incorporated to the prototype code but go directly in the refactoring)._
\approve @fd
\rfc @ds
\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/12Added further functions to create cells around SERA industrial points2021-04-30T19:01:49+02:00Cecilia NievasAdded further functions to create cells around SERA industrial pointsThe industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the ...The industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the full definition of the 30-arcscec grid. We need to define the polygons of the cells of which the given points are centroids in order to then treat them as the equivalent of "districts" for the industrial case.
This merge request is the second of several that aim at implementing this feature. The following is included in this second merge request:
* Added three functions to `GDE_TOOLS_create_industrial_cells.py`:
* `create_dict_all_coordinates()`: create a dictionary with all coordinates of the corners of the cells, to be used as input for `create_dict_unique_coordinates()`
* `create_dict_unique_coordinates()`: create a dictionary with unique values of the coordinates of the corners of the cells, to a certain precision (given by the output of `create_dict_all_coordinates()`)
* `adjust_coords()`: adjust all the coordinates of the corners of the cells by taking the average value of all instances of that coordinate that "should be the same", as identified by `create_dict_unique_coordinates()`
* Added tests to those three functions to `test_GDE_TOOLS_create_industrial_cells.py`.
This feature is associated with https://git.gfz-potsdam.de/dynamicexposure/collaboration/-/issues/40
Previous merger request: !11
*Note: print statements are used to indicate errors/problems as a full logger functionality is not yet part of the prototype code (quite a manual logging system is set up in some core scripts, though; a full logger functionality will probably not be incorporated to the prototype code but go directly in the refactoring).*
\\approve @fd @ds
\\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/11Added initial functions to create cells around SERA industrial points2021-03-15T15:46:19+01:00Cecilia NievasAdded initial functions to create cells around SERA industrial pointsThe industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the ...The industrial exposure of several European countries is defined in the European Seismic Risk Model 2020 (ESRM20, or SERA model) on a 30-arcsec grid. The ESRM20/SERA files only provide points (lon, lat) in which buildings exist, not the full definition of the 30-arcscec grid. We need to define the polygons of the cells of which the given points are centroids in order to then treat them as the equivalent of "districts" for the industrial case.
This merge request is the first of several that aim at implementing this feature. The following is included in this first merge request:
- Added `GDE_TOOLS_create_industrial_cells.py` with four initial functions:
- `define_corners()`: define the four corners of the cell, given the centroid
- `define_cell_polygon()`: create a Shapely polygon of the cell using the four corners
- `retrieve_unique_points()`: determine the unique points (lon, lat) that exist in an input Pandas DataFrame (which will contain the SERA input model, in which the same points repeat themselves for different building classes), according to a defined precision
- `define_cells_in_dataframe()`: define cell geometries around input centroids given in a Pandas DataFrame of unique points (the output of `retrieve_unique_points()`), by calling `define_corners()` and `define_cell_polygon()`
- Added `test_GDE_TOOLS_create_industrial_cells.py` with tests for all those functions, except for define_cell_polygon() as it just defines a polygon using Shapely (i.e. we'd be testing Shapely, not our code).
This feature is associated with https://git.gfz-potsdam.de/dynamicexposure/collaboration/-/issues/40
_Note: print statements are used to indicate errors/problems as a full logger functionality is not yet part of the prototype code (quite a manual logging system is set up in some core scripts, though; a full logger functionality will probably not be incorporated to the prototype code but go directly in the refactoring)._
\approve @fd @ds
\fyi @tara @shindehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/10Merge branch Dev aggreg01: new tools for aggregated exposure models2021-01-15T18:35:23+01:00Cecilia NievasMerge branch Dev aggreg01: new tools for aggregated exposure modelsNew set of tools to store aggregated exposure models
- New file GDE_TOOLS_aggregated_models.py
- Function write_admin_unit_to_hdf() writes data on administrative units to an HDF5 file
- Function write_bdg_class_to_hdf() writes data on b...New set of tools to store aggregated exposure models
- New file GDE_TOOLS_aggregated_models.py
- Function write_admin_unit_to_hdf() writes data on administrative units to an HDF5 file
- Function write_bdg_class_to_hdf() writes data on building classes to an HDF5 filehttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/9Dev gde docs 22020-11-13T10:56:33+01:00Cecilia NievasDev gde docs 2Extensive documentation of the GDE prototype code in its present status.Extensive documentation of the GDE prototype code in its present status.https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/8Dev minor bugs 22020-11-10T14:06:14+01:00Cecilia NievasDev minor bugs 2Minor bugs fixed:
- Solving issue #6: full_files set to True when calling get_admin_level_definition in SERA_mapping_admin_units_to_cells; full_files made explicit input parameter of give_totals_SERA_per_country in GDE_TOOLS_read_SERA
-...Minor bugs fixed:
- Solving issue #6: full_files set to True when calling get_admin_level_definition in SERA_mapping_admin_units_to_cells; full_files made explicit input parameter of give_totals_SERA_per_country in GDE_TOOLS_read_SERA
- Solving issue #5: corrected destination folder in GDE_plot_maps
- Solving issue #4: added comma to separate thousands in the format of numbers printed to screen/logshttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/7Replace -999 values of GPW empty cells with zero2020-10-06T15:35:07+02:00Cecilia NievasReplace -999 values of GPW empty cells with zeroThe HDF5 files containing the parsed GPW v4.0 layers indicate -999 when a cell is empty. The tools that read such values need to interpret them as zero. This merge request addresses #1.The HDF5 files containing the parsed GPW v4.0 layers indicate -999 when a cell is empty. The tools that read such values need to interpret them as zero. This merge request addresses #1.https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/6Two minor bug fixes in SERA rebuild 01 associated with issues 2 and 3: wrong ...2020-10-06T15:04:09+02:00Cecilia NievasTwo minor bug fixes in SERA rebuild 01 associated with issues 2 and 3: wrong variable name, sat_27f_model not supportedTwo minor bug fixes in SERA rebuild 01 associated with issues #2 and #3: wrong variable name, sat_27f_model not supported.Two minor bug fixes in SERA rebuild 01 associated with issues #2 and #3: wrong variable name, sat_27f_model not supported.https://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/5New feature: export full GDE model as HDF5 files2020-10-06T14:22:55+02:00Cecilia NievasNew feature: export full GDE model as HDF5 filesThis new feature makes GDE tiles (in the form of HDF5 files) a proper output of the GDE code. Up to this point the only output stored as such were the visual CSV files (by cell and admin unit) created to be visualised in QGIS and the Ope...This new feature makes GDE tiles (in the form of HDF5 files) a proper output of the GDE code. Up to this point the only output stored as such were the visual CSV files (by cell and admin unit) created to be visualised in QGIS and the OpenQuake input files that can be used to run damage/risk calculations.
The figure below illustrates the structure of each of the HDF5 files. The different colours make reference to the specific functions that fill in a particular part of the file, as per the legend in the bottom right corner. Notes in colour with the legend "if did not exist" imply that the particular sub-group/data array/attribute may be created by more than one of the functions, depending on the actual content of the cell (whether there are OBM buildings or not, whether the cell belongs to more than one administrative unit and SERA/OBM buildings are in some but not all units, etc).
![GDE_tiles_structure_and_code_that_generates_them](/uploads/154bab10af63d83f50a8b30ab3e79808/GDE_tiles_structure_and_code_that_generates_them.png)
*Notes to the figure:*
*N1: Functions called from GDE_TOOLS_access_OBM_HDF.py > retrieve_OBM_buildings_in_cell_from_hdf5()*
*N2: Functions called from GDE_gather_SERA_and_OBM.py.*BacklogDanijel SchorlemmerDanijel Schorlemmerhttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/4First step of transferring documentation to Gitlab2020-10-06T14:23:45+02:00Cecilia NievasFirst step of transferring documentation to Gitlab- Dependencies added to README.md
- docs sub-folder created
- docs/01_Introduction.md created: introduction, overview of the procedure, overview of the code, copyright, copyleft, license, acknowledgements
- docs/02_Execution.md created: ...- Dependencies added to README.md
- docs sub-folder created
- docs/01_Introduction.md created: introduction, overview of the procedure, overview of the code, copyright, copyleft, license, acknowledgements
- docs/02_Execution.md created: details on the execution order, pre-requisites, assumptions
- docs/guide_to_use_of_config_file.csv: file to aid the understanding of which sub-sections of the configuration file are needed to run each scriptDanijel SchorlemmerDanijel Schorlemmerhttps://git.gfz-potsdam.de/globaldynamicexposure/libraries/gde_calculations_prototype/-/merge_requests/3Bug fixes associated with having adapted the code to run with the config file2020-09-10T18:28:50+02:00Cecilia NievasBug fixes associated with having adapted the code to run with the config file- A couple other bugs associated with having changed the names of some variables when adapting the code to run with the config file.
- The definition of the list of cells to run evolved with time and different files. When adapting the co...- A couple other bugs associated with having changed the names of some variables when adapting the code to run with the config file.
- The definition of the list of cells to run evolved with time and different files. When adapting the code to run with the config file I created one function that is now applied to all files (this is what the "Cells to Process" part of the config file controls). However, I had left behind some print statements, etc, that needed to be expanded to consider the larger number of possibilities that using this unified function brought (i.e. defining by country, admin ID, arbitrary list, random from country or by bounding box).
- Added a print('Done!') statement at the end of each script (some had it, some did not). This facilitates interpreting when the code has finished running when running it remotely and recording the screen output to a log file.