TU Delft Spacefinder

App to easily find available spaces on the TU Delft Campus.

🚀 spacefinder.tudelft.nl

Architecture

Key technology used in the Spacefinder:

• Nuxt + Mapbox for an interactive web app including a map of the campus.
• Netlify for deployments (CI/CD + hosting).
• DatoCMS for content management by TU Delft team (see data).
• Supabase to store and aggregate wifi data for locations (see data).

See tudelft-spacefinder in Bitwarden for links to the Netlify, DatoCMS and Supabase instances.

%%{
    init: {
        'theme': 'base',
        'themeVariables': {
            'edgeLabelBackground': '#FFFFFF',
            'lineColor': '#0000FF',
            'mainBkg': '#FFFFFF',
            'primaryBorderColor': '#0000FF',
            'primaryTextColor': '#000000',
            'tertiaryColor': '#FFFED9'
        }
    }
}%%

flowchart
    subgraph "Spacefinder back-end"
        Repository[("<strong>Code repository</strong><br>GitHub")]
        CMS[("<strong>Content CMS</strong><br>DatoCMS")]
        CI("<strong>CI + Hosting</strong><br>Netlify")
        DB[("<strong>Occupancy DB</strong><br>Supabase")]
    end

    subgraph "TU Delft back-end"
        WifiData("<strong>Wifi data</strong><br>Kafka")
    end

    App("<strong>Web app</strong><br>Nuxt + Mapbox")

    Repository -- git commit --> CI
    CMS -- publish --> CI
    CI -- serve --> App
    WifiData -- consume --> DB 
    DB -- subscribe --> App

Data

The Spacefinder combines data from different sources:

• Locations: the TU Delft provides a list of locations as a CSV file. The file is generated from a system of TU Delft Education and Student Affairs (ESA) and emailed to the Spacefinder team. The location data is stored in the codebase (src/data/studieplekken.csv) and compiled into useable files (src/data/buildings.json and spaces.json) during build-time.
• Content: a DatoCMS instance is used for enriching building content and managing the rich text content used in the application. The use of a CMS makes this content easily editable by (TU Delft members of) the Spacefinder team. The content data is dumped during build-time (src/data/*page.json), so there's no run-time dependency on the CMS.
• Opening hours: the TU Delft provides opening hours for (some) buildings and spaces via a Microsoft Graph API.
• Occupancy data: the TU Delft provides real-time data on location occupancy via a Kafka stream. The stream contains device counts for wifi access points on the TU Delft campus. Since the data is continuously updated, it's handled during run-time. The Spacefinder consumes this data every 5 minutes via a serverless function and stores it in a Supabase database. The database contains triggers to convert device counts per wifi access point to device counts per space and per building. The client-side Spacefinder app subscribes to the device counts per space and building and displays them in the UI.

The data sources and data flow is visualised in the diagram below:

%%{
    init: {
        'theme': 'base',
        'themeVariables': {
            'edgeLabelBackground': '#FFFFFF',
            'lineColor': '#0000FF',
            'mainBkg': '#FFFFFF',
            'primaryBorderColor': '#0000FF',
            'primaryTextColor': '#000000',
            'tertiaryColor': '#FFFED9'
        }
    }
}%%

flowchart

    subgraph "Data sources"
        OccupancyData("<strong>Occupancy data</strong><br>(TU Delft Kafka)")
        SpacefinderCms("<strong>CMS content</strong><br>(DatoCMS instance)")
        OpeningHours("<strong>Opening hours</strong><br>(Microsoft Graph)")
    end

    subgraph "Application run-time"
        SpacefinderDb("<strong>Spacefinder database</strong><br>(Supabase instance)")
        DynamicApp("<strong>Dynamic app</strong><br>(in browser)")
    end

    subgraph "Static deployment"
        ContentFiles("<strong>Content files</strong><br>(src/data/...json)")
        StaticApp("<strong>Static app</strong><br>(Netlify instance)")
    end

    OpeningHours -. "<strong>consume data</strong><br>(cron)" .-> SpacefinderDb
    OccupancyData -. "<strong>consume data</strong><br>(cron)" .-> SpacefinderDb
    SpacefinderCms -. "<strong>dump content</strong><br>(build-time)" .-> ContentFiles
    SpacefinderDb -- "<strong>subscribe to data</strong><br>(real-time)" --> DynamicApp
    ContentFiles -. "<strong>import data</strong><br>(build-time)" .-> StaticApp
    StaticApp -- "<strong>visit spacefinder.tudelft.nl</strong><br>(load once)" --> DynamicApp

Decision log

Key decisions that are made during the course of the project are documented in docs/decision-log/. Please read the log so you understand why decisions are made and document key decisions when you make them.

---

Development

Requirements

• Node.js (see .nvmrc for correct version).
• Docker to run Supabase locally.

Getting started

• Clone the repository.
• Run npm ci to install the dependencies.
• Copy .env.example to .env and set the environment variables. Copy them from tudelft-spacefinder in Bitwarden or ask a dev team member.
• Run app in development mode (npm run dev), see all scripts with npm run.

Local Supabase

In order to make changes to the database schema a local Supabase instance is needed.

• Login with npx supabase login.
• Run npm run supabase:start to start a local Supabase instance.
• Use the output API url and key to set the environment variables SUPABASE_URL & SUPABASE_KEY.

Migration

• After changing the database schema run npm run supabase:db:diff followed by a migration name, e.g. npm run supabase:db:diff -- create_xyz.
• Possibly alter the seeding data to match the schema changes.
• Reset the local database to ensure everything works with npm run supabase:db:reset.
• Committed migrations that are merged to the main branch are automatically deployed.