Closed DentonGentry closed 3 years ago
PR for part 1 of this task: https://github.com/ProjectDrawdown/solutions/pull/163
Hi, is this issue still open? I saw that this PR got merged: https://github.com/ProjectDrawdown/solutions/pull/173
PR 173 did not finish this implementation, however since this issue was opened almost a year ago, the UI has undergone substantial change. I do not believe the TopoJSON files would be useful in the current iteration of the UI.
data/world_topo_sans_antartica_highres.json is a TopoJSON file encoding the Project Drawdown regions: OECD90, Eastern Europe, Asia (Sans Japan), Middle East and Africa, Latin America, plus China, India, EU, and USA. It is used with Altair charts for map projections in the Jupyter Notebook researcher UI.
data/world_topo_with_aez.json was intended to be used for Land solutions, but the AEZ regions it contains do not match the Project Drawdown AEZ definitions closely enough so was not used. It is also so large as to be unwieldy.
spatial-aez
Boreal Forest: grows in cold environments at high latitudes, in permafrost / mostly frozen soil. Temperate Forest: grows in warmer climates, though cooler than Tropical forests.
Data sources used by Project Drawdown through most of its development did not provide enough granularity to distinguish km² of each, so the two were combined as Temperate/Boreal and the total land area used. This was unfortunate as some solutions are more appropriate for Temperate or for Boreal, but the model had to use the total area of both.
In late 2019 we decided to address this by analyzing satellite imagery to produce the specific data result for what the project needed. This effort was based off of the scripts in tools/topo which produced data/world_topo_sans_antartica_highres.json. The processing was further refined in a spatial-aez, a separate git repository within this same project.
The data on land area produced by spatial-aez is now being used in Drawdown land solution models.
TopoJSON from spatial-aez
There would be two parts to this effort:
This is marked as a good-first-issue because it would not require coming up to speed on the rest of the solution models, but it would require coming up to speed on TopoJSON and geospatial processing tools like GDAL.