Giter VIP home page Giter VIP logo

viewer's Introduction

MIT License

Woodwell Risk data viewer

The purpose of this site is to increase public access to climate risk data while showcasing some of the datasets the Risk group uses to communicate climate risk to the communities and external partners it works with.

Data sources

Water stress

Wildfires

Temperature

Coastal risk

Processing steps

Vector data

Our boundary files came from Natural Earth. So far, we have used:

  • 10m land and ocean boundaries [link]
  • 10m country- and state-level boundaries [link].

All SHP files were converted to GeoJSON format in GeoPandas. From there, we used Tippecanoe to convert the GeoJSON files to Mapbox .mbtiles format and used the Mapbox tool mbutil to convert those tiles to .pbf format.

Raster data

For back-end data analysis/transformation of NetCDF and TIF files, we used Python and R. Those rasters were then converted to Zarr pyramids using CarbonPlan's ndpyramid package.

Acknowledgements

This site's interface and functionality rely heavily on code developed by CarbonPlan. Specifically, we used the maps, components, and layouts libraries. We took inspiration from CarbonPlan's forest risks code repository to create an updated and modified user interface for this data viewer. You can read more about CarbonPlan's research and software development work here.

viewer's People

Contributors

jakidxav avatar

Stargazers

Seth Gorelik avatar

Watchers

Carlos Dobler avatar

viewer's Issues

Single value “region picker”

It would be nice to query an individual grid cell and get its value, rather than the default behavior of the region picker that takes the spatial average.

Coastline is too detailed

Can we test how displaying a simpler coastline looks like? The "issue" is that, when zoomed out, the current coastline makes certain regions with complex coasts (e.g. Tierra del Fuego, Western Canada, Scandinavian Peninsula) look too "crowded", and hence, too white (black) under the dark (light) mode.

Compute data by vector layer

Look into computing averages / distributions of values for any vector layer, not just the region picker circle boundaries. This could be useful if we wanted to overlay a layer and be able to compute statistics as users hover over them.

Data viz charts

Add distribution plots, data values through time / warming level instead of plain averages when the region picker is opened

Change chart values based on slider min/max

It would be nice to be able to dynamically change the min / max bounds of the x-axis on the bar chart with the slider that controls the colormap min / max when the <RegionPicker /> component is in use.

This isn't that hard to do, but one big problem is that the colormap slider doesn't actually remove values from the map. Instead, it hides them (for sequential colormaps) or changes their color (for diverging colormaps). This can be verified by using the <RegionPicker /> while changing the slider values.

So we either would need to be able to change / remove values from the raster itself or somehow rebin the existing raster values based on the min / max values from the slider.

Group data together into single zarrs

This will make the site render even faster, remove the flicker when switching between warming levels for a specific climate risk, and make it easier to those compare warming levels without resetting the colorbar limits. However, implementing this feature will mean rewriting significant parts of the code.

Difference plots

It would be nice to have difference plots for each layer relative to some warming level / time period. This could be a hard-coded layer, or we could try and implement it so that the user to compute the difference between any two warming levels.

Finish README

Add intro text, table of data + sources, and info on how to run the site from the terminal

NEX methodology section

This will be particularly useful in explaining more about how we calculate warming levels years, which models are being used in NEX input data, and which years are being used for each model.

The best place for this documentation may not be on this site, though. It would be better to include it on the README or in the methodologies site as it will be long.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.