Skip to content

Spatial data output extents do not match, and water determination is not based on the land/cell spatial data #49

@aldivi

Description

@aldivi

Create a new spatial data extent that is consistent throughout all moirai processing, output spatial data with the same extent of valid cells, and output a water area raster diagnostic file.

This starts with the build_land_area.r script, which should be added to this repo. This script completes some land area by merging some hyde and sage data, and supposedly updates the potveg file (there is a bug). The cell area file is also updated because it is used as a land mask.

This build_land_area.r script needs to updated and completed, using the current country raster file to create the valid land mask by intersecting with cell area data that has been fully extended longitudinally beyond its current mask. This new land mask will include water; full and partial water pixels, with some of this being coastal ocean and the rest being inland water. So the difference between the cell and land area will be the water area.

Specific tasks:
Update the input data as described above.
Update the land cell processing so that the valid cells are set properly.
Check to make sure that all the processing uses the proper set of valid cells.
Check and update all of the spatial data outputs so that they have the same valid cells.
Output a water area raster diagnostic file.
Check all calculations and outputs to make sure that they are associated with the proper cells.

I should be able to continue this in the aldivi/country_rast_update branch because it is related and I want to use the new country and basin rasters.

Also see issues #39 (to complete it) and #40 (the country/basin raster issue).
I am also creating a related issue to consider adding water area to the actual moirai outputs.
I am also creating a related issue to consider outputting serbia and montenegro separately.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions