notebooks
notebooks copied to clipboard
pysal
jupyter/ipython notebooks demonstrating PySAL functionality
This is lower priority but important nevertheless. It involves replacing the Jupyter book logo for a PySAL one and other changes we'd like to make to the appearance of our...
This needs to be on the fly with a structure that represents the notebooks pull into `content` (see #46). In addition, the `data/toc.yml` file also can have a base structure...
some polite ribbing in the lightning talk suggested we stop importing using aliases. PySAL devs also might want to revisit the `libpysal.api` recommendations, if this is a prevailing sentiment.
We have a lot of great content so our challenge is having it all discoverable and centralized. @weikang9009 has done some great work on the [landing site](https://github.com/pysal/pysal.site) for the meta...
Use these notebooks for source material on subpackages & use cases for our initiative on designing our better documentation
This could be done with a Makefile that 1. fetches the upstream 2. parses the branches 3. inserts the correctly-formatted hyperlinks into a unique `workshops.md` file 4. concatenates the readme...
This will be done in the spatial regression book chapter, and should be ported to the next time these notebooks are used. 1. look at the residual map of aspatial...
eventually, replace this with the gds book spatial regression chapter, which is excellent on this front
This should: 1. grab each branch of this repo we want to put into test coverage (I'd say all of them!) 2. use that workshop's `environment.yml` to set up an...