Jupyter book 2 (#17)

* start updating

* wip update to 1

* updates to tuto 01

* update book

* baseline interacting with python notebook

* add web mapping to syllabus

* new action

* remove previous action

Author: mariogiampieri

.github/workflows/deploy.yml

@@ -0,0 +1,47 @@
+# This file was created automatically with `myst init --gh-pages` 🪄 💚
+# Ensure your GitHub Pages settings for this repository are set to deploy with **GitHub Actions**.
+
+name: MyST GitHub Pages Deploy
+on:
+  push:
+    # Runs on pushes targeting the default branch
+    branches: [main, jupyter-book-2]
+env:
+  # `BASE_URL` determines the website is served from, including CSS & JS assets
+  # You may need to change this to `BASE_URL: ''`
+  BASE_URL: /${{ github.event.repository.name }}
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: 'pages'
+  cancel-in-progress: false
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Pages
+        uses: actions/configure-pages@v3
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18.x
+      - name: Install MyST Markdown
+        run: npm install -g mystmd
+      - name: Build HTML Assets
+        run: myst build --html
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: './_build/html'
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/static.yml

@@ -7,3 +7,6 @@ wip/
 Book/
 _config.yml
 _toc.yml
+
+# MyST build outputs
+_build

.gitignore

@@ -1,3 +1,14 @@
 {
-    "markdown-pdf.displayHeaderFooter": false
-}
+  "markdown-pdf.displayHeaderFooter": false,
+  "jupyter.widgetScriptSources": ["jsdelivr.com", "unpkg.com"],
+  "[python]": {
+    "editor.formatOnType": true,
+    "editor.defaultFormatter": "ms-python.black-formatter",
+    "editor.formatOnSave": true
+  },
+  "black-formatter.showNotifications": "always",
+  "notebook.formatOnSave.enabled": true,
+  "notebook.formatOnCellExecution": true,
+  // this is extra but will help
+  "notebook.diff.ignoreMetadata": true
+}

.vscode/settings.json

@@ -1,6 +1,6 @@
-# CDP Mapping Systems Summer 2024
+# CDP Mapping Systems Summer 2025
 
-Repository for CDP Mapping Systems summer 2024 course
+Repository for CDP Mapping Systems summer 2025 course
 
 ## Important Links
 
@@ -11,11 +11,4 @@ Repository for CDP Mapping Systems summer 2024 course
 
 ## Getting started
 
-1. Install [VSCode](https://code.visualstudio.com/)
-2. Join course [Github page](https://github.com/mapping-systems/cdp-mapping-systems) from the invitation email I send. Fork the repository to your account and clone it to your local machine.
-3. Create a new Python environment. I recommend using [Conda](https://conda.io/projects/conda/en/latest/user-guide/install/index.html) for this, but you can also use virtualenv. This will protect our system Python installation from any changes we make.
-   1. If you're using Conda, you can create a new environment with the following command:
-      ```
-      conda create -n [pick-a-name] python=3.12
-      ```
-4. In VSCode, install `Black Formatter`. Using a consistent formatter will help us keep our code clean and readable and reduce minor changes in our commits. We will use `Black` as our default formatter
+Visit the [Getting Started](Tutorials/00_Getting_Started.md) tutorial notebook to set up your programming environment and get started with the course.

Assignment_Descriptions/00_Getting_Started.md

@@ -1,6 +1,6 @@
-# Mapping Systems Summer 2024
+# Mapping Systems Summer 2025
 
-Tuesday and Thursdays, 6-8pm @ 300 Buell South
+Tuesday and Thursdays, 6-8pm @ 209 Fayerweather
 
 Instructor: Mario Giampieri (mag2382@columbia.edu)
 
@@ -78,6 +78,7 @@ Geoprocessing / vector data analysis basics using `geopandas`, `pyogrio`, `panda
   **Readings**:
 
   - Miller, H.J., 2004. Tobler’s First Law and Spatial Analysis. Annals of the Association of American Geographers 94, 284–289.
+  - Iconoclasistas, 2016. Manual of Collective Mapping: Critical cartographic resources for territorial processes of collaborative creation.
   - Wilson, M.O., 2018. The Cartography of W.E.B. Dubois’ Color Line, in: Batlle-Baptiste, W., Rusert, B. (Eds.), WEB Du Bois’s Data Portraits: Visualizing Black America. Princeton Architectural Press.
   - (optional) Entrikin, J.N., 1991. The Betweenness of Place, in: Entrikin, J.N. (Ed.), The Betweenness of Place: Towards a Geography of Modernity. Macmillan Education UK, London, pp. 6–26. [https://doi.org/10.1007/978-1-349-21086-2_2](https://doi.org/10.1007/978-1-349-21086-2_2)
   - (optional) Maantay, J., Ziegler, J., 2006. Spatial Data and Basic Mapping Concepts, in: GIS for the Urban Environment.
@@ -113,10 +114,29 @@ Ways to think about and measure distance and spatial relatedness
   **Exercise:** [03_Networks](/Assignment_Descriptions/03_Networks.md)
 
 ### Week 04
+Web mapping, interactive visualization, and crowd-sourced information
+#### Class 07: Web mapping
+- Introduction to web mapping
+- Web 2.0 and the rise of interactive mapping
+- Case study: OpenStreetMap and the Humanitarian OpenStreetMap Team
+- Web map basic components 
+
+  **Readings**
+  - NEOGEOGRAPHY AND` THE PALIMPSESTS OF PLACE: WEB 2.0 AND THE CONSTRUCTION OF A VIRTUAL EARTH - GRAHAM - 2010 - Tijdschrift voor Economische en Sociale Geografie - Wiley Online Library [WWW Document], n.d. URL https://onlinelibrary-wiley-com.libproxy.mit.edu/doi/full/10.1111/j.1467-9663.2009.00563.x (accessed 6.15.25).
+  - Haklay, M., Weber, P., 2008. OpenStreetMap: User-generated street maps. IEEE Pervasive Computing 7, 12–18. [https://doi.org/10.1109/MPRV.2008.80](https://doi.org/10.1109/MPRV.2008.80)
+  - Schröder-Bergen, S., Glasze, G., Michel, B., Dammann, F., 2022. De/colonizing OpenStreetMap? Local mappers, humanitarian and commercial actors and the changing modes of collaborative mapping. GeoJournal 87, 5051–5066. https://doi.org/10.1007/s10708-021-10547-7
+
+#### Class 08: Web mapping (Tutorial)
+- Use `leafmap`, `ipyleaflet`, and `folium` to create interactive web maps
+- Loading data via API 
+- Launching a basic web map
+**Exercise:** [04_Web Mapping](/Assignment_Descriptions/04_Web_Mapping.md)
+
+### Week 05
 
 Raster analysis, STAC specification, change over time
 
-#### Class 07: Measuring Change
+#### Class 09: Measuring Change
 
 - Introduction to raster data
 - Historical context for measuring change over time
@@ -128,21 +148,11 @@ Raster analysis, STAC specification, change over time
   - Couclelis, H., 1992. People manipulate objects (but cultivate fields): Beyond the raster-vector debate in GIS, in: Frank, A.U., Campari, I., Formentini, U. (Eds.), Theories and Methods of Spatio-Temporal Reasoning in Geographic Space, Lecture Notes in Computer Science. Springer Berlin Heidelberg, Berlin, Heidelberg, pp. 65–77. [https://doi.org/10.1007/3-540-55966-3_3](https://doi.org/10.1007/3-540-55966-3_3)
   - Homer, C., Dewitz, J., Jin, S., Xian, G., Costello, C., Danielson, P., Gass, L., Funk, M., Wickham, J., Stehman, S., Auch, R., Riitters, K., 2020. Conterminous United States land cover change patterns 2001–2016 from the 2016 National Land Cover Database. ISPRS Journal of Photogrammetry and Remote Sensing 162, 184–199. [https://doi.org/10.1016/j.isprsjprs.2020.02.019](https://doi.org/10.1016/j.isprsjprs.2020.02.019)
 
-#### Class 08: Supervised classification using earth observation (EO) data (Tutorial)
+#### Class 10: Supervised classification using earth observation (EO) data (Tutorial)
 
 - Use `leafmap`, `rasterio`, `ipyleaflet` to find, download, classify, composite, and analyze raster data
 - **Desk crits**
 
-### Week 05
-
-Wrapping up + developing future practice
-
-#### Class 09: Wrapping up + Looking Forward
-
-- Additional workshop on advanced topic or guest lecture (TBD based on class interest)
-
-#### Class 10: Desk crits / work session
-
 ### Week 06
 
 Preparing for final colloquium presentations + presentations on August 14th

README.md

@@ -0,0 +1,40 @@
+# Getting started
+
+1. Install [VSCode](https://code.visualstudio.com/)
+2. Create a new Python environment. I *strongly* recommend using [Conda](https://conda.io/projects/conda/en/latest/user-guide/install/index.html) for this, but you can also use virtualenv. This will protect our system Python installation from any changes we make.
+   - If you're using Conda, you can create a new environment with the following command (with no brackets around the name). You could choose a name like `gis` or `cdp` for example:
+      ```
+      conda create -n [pick-a-name] python=3.12
+      ```
+    Be sure to replace `[pick-a-name]` with a name of your choice for the environment. You can activate the environment (with no brackets around the name) with:
+      ```
+      conda activate [pick-a-name]
+      ```
+    It is important to do this step before installing any packages, as it ensures that all packages are installed in the new environment rather than the system Python installation.
+3. Install the required packages for the course. You can do this by running:
+   ```
+   pip install -r requirements.txt
+   ```
+   This will install all the packages listed in the `requirements.txt` file, which includes all the packages we will use in the course. If you open that file, you will see package names and the versions that we will use. This ensures that everyone is using the same versions of the packages, which helps avoid compatibility issues. (This is a primary reason to use a virtual environment, as packages change over time and we want to avoid breaking changes.)
+
+4. In VSCode, install `Ruff`. Ruff is a linter that will help us catch errors in our code and enforce coding standards. It is a fast and efficient linter that works well with Python. You can install it by searching for "Ruff" in the VSCode extensions marketplace.
+5. In VSCode, install `Black Formatter`. Using a consistent formatter will help us keep our code clean and readable and reduce minor changes in our commits. We will use `Black` as our default formatter. You can install it by searching for "Black Formatter" in the VSCode extensions marketplace.
+6. Make sure that your vscode settings are set to use `Black` as the default formatter. You can do this by adding the following lines to your `settings.json` file:
+   ```json
+   "[python]": {
+        "editor.formatOnType": true,
+        "editor.defaultFormatter": "ms-python.black-formatter",
+        "editor.formatOnSave": true
+    },
+    "[jupyter]": {
+        "editor.defaultFormatter": "ms-python.black-formatter"
+    },
+    "notebook.lineNumbers": "on",
+    "ruff.importStrategy": "useBundled",
+    "black-formatter.importStrategy": "fromEnvironment",
+    "notebook.formatOnSave.enabled": true,
+    "black-formatter.showNotifications": "always",
+    "notebook.formatOnCellExecution": true,
+    "notebook.diff.ignoreMetadata": true,
+   ```
+   This will ensure that your code is automatically formatted with `Black` when you save it, and that `Ruff` is used for linting.