Staging

.github/workflows/rebuild-cache.yml

@@ -52,6 +52,15 @@ jobs:
       - name: Install dependencies
         run: npm install
 
+      - name: Import CSV to database
+        env:
+          SUPABASE_URL: ${{ secrets.SUPABASE_URL }}
+          SUPABASE_SERVICE_KEY: ${{ secrets.SUPABASE_SERVICE_KEY }}
+          STAGING: ${{ steps.env.outputs.STAGING }}
+        run: |
+          echo "Importing events.csv to ${{ steps.env.outputs.ENV_NAME }} database..."
+          node import-csv.js
+
       - name: Rebuild cache
         env:
           SUPABASE_URL: ${{ secrets.SUPABASE_URL }}

.github/workflows/update-cache.yml

@@ -0,0 +1,107 @@
+name: Update Data Cache
+
+on:
+  push:
+    branches:
+      - main
+      - staging
+    paths:
+      - 'events.csv'
+      - 'geometries/**'
+
+  workflow_dispatch:
+    inputs:
+      environment:
+        description: 'Environment to update'
+        required: true
+        default: 'staging'
+        type: choice
+        options:
+          - staging
+          - production
+
+jobs:
+  update-cache:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Determine environment
+        id: env
+        run: |
+          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
+            echo "environment=${{ github.event.inputs.environment }}" >> $GITHUB_OUTPUT
+          elif [ "${{ github.ref }}" = "refs/heads/main" ]; then
+            echo "environment=production" >> $GITHUB_OUTPUT
+          else
+            echo "environment=staging" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Import CSV to database
+        env:
+          SUPABASE_URL: ${{ secrets.SUPABASE_URL }}
+          SUPABASE_SERVICE_KEY: ${{ secrets.SUPABASE_SERVICE_KEY }}
+          STAGING: ${{ steps.env.outputs.environment == 'staging' }}
+          GITHUB_ACTIONS: true
+        run: |
+          if [ "${{ steps.env.outputs.environment }}" = "staging" ]; then
+            STAGING=true node import-csv.js
+          else
+            node import-csv.js
+          fi
+
+      - name: Upload geometry files to storage
+        env:
+          SUPABASE_URL: ${{ secrets.SUPABASE_URL }}
+          SUPABASE_SERVICE_KEY: ${{ secrets.SUPABASE_SERVICE_KEY }}
+          STAGING: ${{ steps.env.outputs.environment == 'staging' }}
+          GITHUB_ACTIONS: true
+        run: |
+          if [ "${{ steps.env.outputs.environment }}" = "staging" ]; then
+            STAGING=true node upload-geometries.js
+          else
+            node upload-geometries.js
+          fi
+
+      - name: Sync geometries table with storage
+        env:
+          SUPABASE_URL: ${{ secrets.SUPABASE_URL }}
+          SUPABASE_SERVICE_KEY: ${{ secrets.SUPABASE_SERVICE_KEY }}
+          STAGING: ${{ steps.env.outputs.environment == 'staging' }}
+          GITHUB_ACTIONS: true
+        run: |
+          if [ "${{ steps.env.outputs.environment }}" = "staging" ]; then
+            STAGING=true node sync-geometries-table.js
+          else
+            node sync-geometries-table.js
+          fi
+
+      - name: Rebuild cache
+        env:
+          SUPABASE_URL: ${{ secrets.SUPABASE_URL }}
+          SUPABASE_SERVICE_KEY: ${{ secrets.SUPABASE_SERVICE_KEY }}
+          STAGING: ${{ steps.env.outputs.environment == 'staging' }}
+          GITHUB_ACTIONS: true
+        run: |
+          if [ "${{ steps.env.outputs.environment }}" = "staging" ]; then
+            STAGING=true node rebuild-cache.js
+          else
+            node rebuild-cache.js
+          fi
+
+      - name: Summary
+        run: |
+          echo "✅ Cache updated successfully for ${{ steps.env.outputs.environment }}"
+          echo "Branch: ${{ github.ref_name }}"
+          echo "Commit: ${{ github.sha }}"

CONTRIBUTING.md

@@ -19,7 +19,7 @@ Each row in `events.csv` represents one change to a service. Service creation ev
 
 ## CSV structure
 
-14 columns capture service attributes:
+15 columns capture service attributes:
 
 | Column           | Description                | Example                                      | Required?     |
 | ---------------- | -------------------------- | -------------------------------------------- | ------------- |
@@ -32,6 +32,7 @@ Each row in `events.csv` represents one change to a service. Service creation ev
 | `platform`       | Booking app                | `Robotaxi`                                   | If applicable |
 | `fares`          | Charges fares?             | `Yes` / `No`                                 | If applicable |
 | `direct_booking` | Can book AV directly?      | `Yes` / `No`                                 | If applicable |
+| `service_model`  | Service model              | `Flexible` / `Stop-to-Stop`                  | If applicable |
 | `supervision`    | Supervision level          | `Autonomous` / `Safety Driver`               | If applicable |
 | `access`         | Access policy              | `Public` / `Waitlist`                        | If applicable |
 | `fleet_partner`  | Fleet partnerships         | `Moove`                                      | If applicable |
@@ -43,10 +44,10 @@ Each row in `events.csv` represents one change to a service. Service creation ev
 For `service_created` events, fill in all service attributes:
 
 ```csv
-2025-09-10,service_created,Zoox,Las Vegas,zoox-las-vegas-september-10-2025-boundary.geojson,Zoox Robotaxi,Zoox,No,Yes,Autonomous,Public,,https://techcrunch.com/2025/09/10/zoox-opens-its-las-vegas-robotaxi-service-to-the-public/,Zoox Las Vegas service
+2025-09-10,service_created,Zoox,Las Vegas,zoox-las-vegas-september-10-2025-boundary.geojson,Zoox Robotaxi,Zoox,No,Yes,Stop-to-Stop,Autonomous,Public,,https://techcrunch.com/2025/09/10/zoox-opens-its-las-vegas-robotaxi-service-to-the-public/,Zoox Las Vegas service
 ```
 
-Required: `date`, `event_type`, `company`, `city`, `vehicles`, `platform`, `fares`, `direct_booking`, `supervision`, `access`, `source_url`
+Required: `date`, `event_type`, `company`, `city`, `vehicles`, `platform`, `fares`, `direct_booking`, `service_model`, `supervision`, `access`, `source_url`
 
 ## Updating a service
 
@@ -80,6 +81,12 @@ Note: Multiple platforms separated by `;` (semicolon). This allows filtering by
 2024-11-12,access_policy_changed,Waymo,Los Angeles,,,,,,,Public,,https://waymo.com/blog/2024/11/waymo-one-open-to-all-in-los-angeles,Access policy update
 ```
 
+### Service model change
+
+```csv
+2026-03-15,service_model_updated,Zoox,Las Vegas,,,,,,,Flexible,,,https://example.com,Service now allows flexible travel
+```
+
 ## Event types
 
 **Service lifecycle:**
@@ -95,6 +102,7 @@ Note: Multiple platforms separated by `;` (semicolon). This allows filtering by
 - `fares_policy_changed` - Fare policy changes
 - `access_policy_changed` - Access changes
 - `supervision_updated` - Supervision level changes
+- `flexibility_updated` - Travel flexibility changes
 - `fleet_partner_changed` - Fleet partnership changes
 
 ## Field values
@@ -113,6 +121,8 @@ Add new values when documenting companies, vehicles, platforms, or policies not
 
 **Direct Booking:** `Yes` (book AV directly), `No` (may or may not get AV, like Waymo on UberX)
 
+**Flexibility:** `Point-to-Point` (riders can travel freely between any points in the service area), `Stop-to-Stop` (riders can only travel to/from predetermined stops)
+
 **Supervision:** `Autonomous`, `Safety Driver`, `Safety Attendant`
 
 **Access:** `Public`, `Waitlist`