Edit and Update: Enhancements to Cal-ITP Data Services Documentation

docs/analytics_onboarding/overview.md

@@ -32,16 +32,19 @@
 
 **Python Libraries:**
 
-- [ ] **calitp-data-analysis** - Cal-ITP's internal Python library for analysis | ([Docs](calitp-data-analysis))
-- [ ] **siuba** - Recommended data analysis library | ([Docs](siuba))
-- [ ] [**shared_utils**](https://github.com/cal-itp/data-analyses/tree/main/_shared_utils) and [**here**](https://github.com/cal-itp/data-infra/tree/main/packages/calitp-data-analysis/calitp_data_analysis) - A shared utilities library for the analytics team | ([Docs](shared-utils))
+- [ ] [**calitp-data-analysis**](https://github.com/cal-itp/data-infra/tree/main/packages/calitp-data-analysis/calitp_data_analysis) - Cal-ITP's internal Python library for analysis | ([Docs](calitp-data-analysis))
+- [ ] [**siuba**](https://siuba.org/) - Recommended data analysis library | ([Docs](siuba))
+- [ ] [**shared_utils**](https://github.com/cal-itp/data-analyses/tree/main/_shared_utils) - A shared utilities library for the analytics team | ([Docs](shared-utils))
 
 **Caltrans Employee Resources:**
 
+- [ ] [**Organizational Chart**](https://pmp.onramp.dot.ca.gov/organizational-chart) - Data and Digital Services Organizational Chart
 - [ ] [**OnRamp**](https://onramp.dot.ca.gov/) - Caltrans employee intranet
 - [ ] [**Service Now (SNOW)**](https://cdotprod.service-now.com/sp) - Caltrans IT Service Management Portal for IT issues and requesting specific software
 - [ ] [**Cal Employee Connect**](https://connect.sco.ca.gov/) - State Controller's Office site for paystubs and tax information
 - [ ] [**Geospatial Enterprise Engagement Platform - GIS Account Request Form**](https://sv03tmcpo.ct.dot.ca.gov/portal/apps/sites/#/geep/pages/account-request) (optional) - User request form for ArcGIS Online and ArcGIS Portal accounts
+- [ ] [**Planning Handbook**](https://transportationplanning.onramp.dot.ca.gov/caltrans-transportation-planning-handbook) - Caltrans Transportation Planning Handbook
+- [ ] [**California Public Employees Retirement System**](https://www.calpers.ca.gov/) - System that manages pension and health benefits
 
  
 (get-help)=

docs/analytics_tools/jupyterhub.md

@@ -14,14 +14,15 @@ Analyses on JupyterHub are accomplished using notebooks, which allow users to mi
 
 01. [Using JupyterHub](#using-jupyterhub)
 02. [Logging in to JupyterHub](#logging-in-to-jupyterhub)
-03. [Connecting to the Warehouse](#connecting-to-the-warehouse)
-04. [Increasing the Query Limit](#increasing-the-query-limit)
-05. [Increase the User Storage Limit](#increasing-the-storage-limit)
-06. [Querying with SQL in JupyterHub](querying-sql-jupyterhub)
-07. [Saving Code to Github](saving-code-jupyter)
-08. [Environment Variables](#environment-variables)
-09. [Jupyter Notebook Best Practices](notebook-shortcuts)
-10. [Developing warehouse models in Jupyter](jupyterhub-warehouse)
+03. [Default vs Power User](#default-user-vs-power-user)
+04. [Connecting to the Warehouse](#connecting-to-the-warehouse)
+05. [Increasing the Query Limit](#increasing-the-query-limit)
+06. [Increase the User Storage Limit](#increasing-the-storage-limit)
+07. [Querying with SQL in JupyterHub](querying-sql-jupyterhub)
+08. [Saving Code to Github](saving-code-jupyter)
+09. [Environment Variables](#environment-variables)
+10. [Jupyter Notebook Best Practices](notebook-shortcuts)
+11. [Developing warehouse models in Jupyter](jupyterhub-warehouse)
 
 (using-jupyterhub)=
 
@@ -39,6 +40,22 @@ JupyterHub currently lives at [notebooks.calitp.org](https://notebooks.calitp.or
 
 Note: you will need to have been added to the Cal-ITP organization on GitHub to obtain access. If you have yet to be added to the organization and need to be, ask in the `#services-team` channel in Slack.
 
+(default-user-vs-power-user)=
+
+### Default User vs Power User
+
+#### Default User
+
+Designed for general use and is ideal for less resource-intensive tasks. It's a good starting point for most users who don't expect to run very large, memory-hungry jobs.
+
+Default User profile offers quick availability since it uses less memory and can allocate a smaller node, allowing you to start tasks faster. However, if your task grows in memory usage over time, it may exceed the node's capacity, potentially causing the system to terminate your job. This makes the Default profile best for smaller or medium-sized tasks that don’t require a lot of memory. If your workload exceeds these limits, you might experience instability or crashes.
+
+#### Power User
+
+Intended for more demanding, memory-intensive tasks that require more resources upfront. This profile is suitable for workloads that have higher memory requirements or are expected to grow during execution.
+
+Power User profile allocates a full node or a significant portion of resources to ensure your job has enough memory and computational power, avoiding crashes or delays. However, this comes with a longer wait time as the system needs to provision a new node for you. Once it's ready, you'll have all the resources necessary for memory-intensive tasks like large datasets or simulations. The Power User profile is ideal for jobs that might be unstable or crash on the Default profile due to higher resource demands. Additionally, it offers scalability—if your task requires more resources than the initial node can provide, the system will automatically spin up additional nodes to meet the demand.
+
 (connecting-to-the-warehouse)=
 
 ### Connecting to the Warehouse

docs/analytics_tools/knowledge_sharing.md

@@ -2,7 +2,7 @@
 
 # Helpful Links
 
-Here are some resources data analysts have collected and referenced, that will hopefully help you out in your work. Have something you want to share? Create a new markdown file, add it [to the example report folder](https://github.com/cal-itp/data-analyses/tree/main/example_report), and [message Amanda.](https://app.slack.com/client/T014965JTHA/C013N8GELLF/user_profile/U02PCTPSZ8A)
+Here are some resources data analysts have collected and referenced, that will hopefully help you out in your work.
 
 - [Data Analysis](#data-analysis)
   - [Python](#python)
@@ -11,12 +11,14 @@ Here are some resources data analysts have collected and referenced, that will h
   - [Merging](#merging)
   - [Dates](#dates)
   - [Monetary Values](#monetary-values)
+  - [Tidy Data](#tidy-data)
 - [Visualizations](#visualization)
   - [Charts](#charts)
   - [Maps](#maps)
   - [DataFrames](#dataframes)
   - [Ipywidgets](#ipywidgets)
   - [Markdown](#markdown)
+  - [ReviewNB](#reviewNB)
 
 (data-analysis)=
 
@@ -128,6 +130,20 @@ def adjust_prices(df):
     return df
 ```
 
+(tidy-data)=
+
+### Tidy Data
+
+Tidy Data follows a set of principles that ensure the data is easy to work with, especially when using tools like pandas and matplotlib. Primary rules of tidy data are:
+
+- Each variable must have its own column.
+- Each observation must have its own row.
+- Each value must have its own cell.
+
+Tidy data ensures consistency, making it easier to work with tools like pandas, matplotlib, or seaborn. It also simplifies data manipulation, as functions like `groupby()`, `pivot()`, and `melt()` work more intuitively when the data is structured properly. Additionally, tidy data enables vectorized operations in pandas, allowing for efficient analysis on entire columns or rows at once.
+
+Learn more about Tidy Data [here.](https://vita.had.co.nz/papers/tidy-data.pdf)
+
 (visualization)=
 
 ## Visualization
@@ -159,7 +175,6 @@ def add_tooltip(chart, tooltip1, tooltip2):
 
 ### Maps
 
-- [Examples of folium, branca, and color maps.](https://nbviewer.org/github/python-visualization/folium/blob/v0.2.0/examples/Colormaps.ipynb)
 - [Quick interactive maps with Geopandas.gdf.explore()](https://geopandas.org/en/stable/docs/reference/api/geopandas.GeoDataFrame.explore.html)
 
 (dataframes)=
@@ -188,3 +203,10 @@ def add_tooltip(chart, tooltip1, tooltip2):
 - [Add a table of content that links to headers throughout a markdown file.](https://stackoverflow.com/questions/2822089/how-to-link-to-part-of-the-same-document-in-markdown)
 - [Add links to local files.](https://stackoverflow.com/questions/32563078/how-link-to-any-local-file-with-markdown-syntax?rq=1)
 - [Direct embed an image.](https://datascienceparichay.com/article/insert-image-in-a-jupyter-notebook/)
+
+(reviewNB)=
+
+### ReviewNB on GitHub
+
+- [Tool designed to facilitate reviewing Jupyter Notebooks in a collaborative setting on GitHub](https://www.reviewnb.com/)
+- [Shows side-by-side diffs of Jupyter Notebooks, including changes to both code cells and markdown cells and allows reviewers to comment on specific cells](https://www.reviewnb.com/#faq)

docs/analytics_tools/saving_code.md

@@ -9,11 +9,16 @@ Doing work locally and pushing directly from the command line is a similar workf
 ## Table of Contents
 
 1. What's a typical [project workflow](#project-workflow)?
+
 2. Someone is collaborating on my branch, how do we [stay in sync](#pulling-and-pushing-changes)?
+
    - The `main` branch is ahead, and I want to [sync my branch with `main`](#rebase-and-merge)
    - [Rebase](#rebase) or [merge](#merge)
    - Options to [Resolve Merge Conflicts](#resolve-merge-conflicts)
+   - [Other Common Issues](#other-common-github-issues-encountered-during-saving-codes)
+
 3. [Other Common GitHub Commands](#other-common-github-commands)
+
    - [External Git Resources](#external-git-resources)
    - [Committing in the Github User Interface](#pushing-drag-drop)
 
@@ -111,6 +116,17 @@ If you discover merge conflicts and they are within a single notebook that only
     `git checkout --theirs path/to/notebook.ipynb`
 - From here, just add the file and commit with a message as you normally would and the conflict should be fixed in your Pull Request.
 
+(other-common-github-issues-encountered-during-saving-codes)
+
+### Other Common Issues
+
+- Untracked Files:
+  Sometimes, files are created or modified locally but are not added to Git before committing, so they are not tracked or pushed to GitHub. Use `git add <filename>` to track files before committing.
+- Incorrect Branches:
+  Committing to the wrong branch (e.g., main instead of a feature branch) can cause problems, especially if changes are not meant to be merged into the main codebase. Always ensure you're on the correct branch using git branch and switch branches with `git checkout <branch-name>` before committing.
+- Merge Conflicts from Overlapping Work:
+  When multiple analysts work on the same files or sections of code, merge conflicts can occur. Creating feature branches and pulling regularly to stay updated with main can help avoid these conflicts.
+
 (other-common-github-commands)=
 
 ## Other Common GitHub Commands

docs/analytics_tools/tools_quick_links.md

@@ -7,16 +7,10 @@
 | Tool                                                                                               | Purpose                                 |
 | -------------------------------------------------------------------------------------------------- | --------------------------------------- |
 | [**Analytics Repo**](https://github.com/cal-itp/data-analyses)                                     | Analytics team code repository.         |
-| [**Analytics Project Board**](https://github.com/cal-itp/data-analyses/projects/1)                 | Analytics team work management.         |
+| [**Analytics Project Board**](https://github.com/cal-itp/data-analyses/projects/1)                 | Analytics team list of active issues.   |
 | [**notebooks.calitp.org**](https://notebooks.calitp.org/)                                          | JupyterHub cloud-based notebooks        |
 | [**dashboards.calitp.org**](https://dashboards.calitp.org/)                                        | Metabase dashboards & Business Insights |
 | [**dbt-docs.calitp.org**](https://dbt-docs.calitp.org/)                                            | DBT warehouse documentation             |
 | [**analysis.calitp.org**](https://analysis.calitp.org/)                                            | Analytics portfolio landing page        |
 | [**Google BigQuery**](https://console.cloud.google.com/bigquery)                                   | Our warehouse and SQL Querying          |
 | [**Google Cloud Storage**](https://console.cloud.google.com/storage/browser/calitp-analytics-data) | Cloud file storage                      |
-
- 
-
-```{admonition} Still need access to a tool on this page?
-Ask in the `#services-team` channel in the Cal-ITP Slack.
-```

docs/analytics_welcome/how_we_work.md

@@ -27,26 +27,6 @@ The section below outlines our team's primary meetings and their purposes, as we
 | #**data-office-hours**   | Discussion | A place to bring questions, issues, and observations for team discussion.                   |
 | #**data-warehouse-devs** | Discussion | For people building dbt models - focused on data warehouse performance considerations, etc. |
 
-## Collaboration Tools
-
-(analytics-project-board)=
-
-### GitHub Analytics Project Board
-
-**You can access The Analytics Project Board [using this link](https://github.com/cal-itp/data-analyses/projects/1)**.
-
-#### How We Track Work
-
-##### Screencast - Navigating the Board
-
-The screencast below introduces:
-
-- Creating new GitHub issues to track your work
-- Adding your issues to our analytics project board
-- Viewing all of your issues on the board (e.g. clicking your avatar to filter)
-
-<div style="position: relative; padding-bottom: 62.5%; height: 0;"><iframe src="https://www.loom.com/embed/a7332ee2e1c040edbf2d11da70b4c3ea" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
-
 (analytics-repo)=
 
 ### GitHub Analytics Repo

docs/analytics_welcome/overview.md

@@ -15,6 +15,10 @@ After you've read through this section, continue reading through the remaining s
 
 ______________________________________________________________________
 
+- [Data and Digital Services Organizational Chart](https://pmp.onramp.dot.ca.gov/downloads/pmp/files/Splash%20Page/org-charts-10-2024/DDS_OrgChart_October2024-signed.pdf)
+
+______________________________________________________________________
+
 **Other Analytics Sections**:
 
 - [Technical Onboarding](technical-onboarding)

docs/publishing/sections/6_metabase.md

@@ -9,3 +9,7 @@ An [Airflow DAG](https://github.com/cal-itp/data-infra/tree/main/airflow/dags) n
 Any tweaks to the data processing steps are easily done in scripts and notebooks, and it ensures that the visualizations in the dashboard remain updated with little friction.
 
 Ex: [Payments Dashboard](https://dashboards.calitp.org/dashboard/3-payments-performance-dashboard?transit_provider=mst)
+
+## Metabase Training Guide 2024
+
+Please see the [Cal-ITP Metabase Training Guide](https://docs.google.com/document/d/1ag9qmSDWF9d30lGyKcvAAjILt1sCIJhK7wuUYkfAals/edit?tab=t.0#heading=h.xdjzmfck1e7) to see how to utilize the data warehouse to create meaningful and effective visuals and analyses.

docs/publishing/sections/7_gcs.md

@@ -2,8 +2,16 @@
 
 # GCS
 
-NOTE: If you are planning on publishing to [CKAN](publishing-ckan) and you are
-using the dbt exposure publishing framework, your data will already be saved in
-GCS as part of the upload process.
+### Public Data Access in GCS
+
+Some data stored in Cloud Storage is configured to be publicly accessible, meaning anyone on the internet can read it at any time. In Google Cloud Storage, you can make data publicly accessible either at the bucket level or the object level. At the bucket level, you can grant public access to all objects within the bucket by modifying the bucket policy. Alternatively, you can provide public access to specific objects.
+
+Notes:
+
+- Always ensure that sensitive information is not exposed when configuring public access in Google Cloud Storage. Publicly accessible data should be carefully reviewed to prevent the accidental sharing of confidential or private information.
+- External users can't browse the public bucket on the web, only download individual files. If you have many files to share, it's best to use the [Command Line Interface.](https://cloud.google.com/storage/docs/access-public-data#command-line)
+- There is a [function](https://github.com/cal-itp/data-analyses/blob/f62b150768fb1547c6b604cb53d122531104d099/_shared_utils/shared_utils/publish_utils.py#L16) in shared_utils that handles writing files to the public bucket, regardless of the file type (e.g., Parquet, GeoJSON, etc.)
+
+NOTE: If you are planning on publishing to [CKAN](publishing-ckan) and you are using the dbt exposure publishing framework, your data will already be saved in GCS as part of the upload process.
 
 TBD.