PROJECT PROGRESS REPORTS:
Stage I Report:
- Project Setup
- Angular frontend, Python backend, SQLite database
- Defined schema for users, buildings, floor plans, and rooms
- PDF Upload
- Built upload page with building info and floor assignment
- Backend saves uploaded PDFs and detects duplicate uploads by file fingerprint (SHA-256)
- Floor Plan Extraction
- Used pdfplumber to read words, lines, and shapes from vector PDFs
- Parsed room numbers and names from the plan’s room schedule
- Fell back to room labels inside the drawing when no schedule exists
- Separated wall lines from door lines
- Building Library
- Listed uploaded facilities with their locations
- 3D Map View
- Rendered floor plans in 3D with Three.js
Stage II Report:
- Room Resources
- Added resource and availability tables to the database
- Linked resources to rooms by building and room number, so data survives re-uploads and redraws
- Created room details API and resource search API
- Automatic Resource Collection
- Matched uploaded buildings to ISU’s classroom database by name
- Scraped classroom capacity, seating, AV equipment, and boards automatically
- Read equipment labels drawn on floor plans (whiteboards, tables, printers), which works for any building
- Runs in the background after every upload and redraw
- Redraw Tool
- Users can move, add, and delete walls with undo
- Redraws are saved to the server, with the latest redraw replacing the previous one
- Rooms corrected by hand are never overwritten by automatic extraction
- Uploads
- Latest upload wins: re-uploading a floor replaces it
- New floors join existing buildings, matched by name and city
- Multi-page PDFs with one floor per page
- Fixed file paths saved on Windows not loading on Mac
- Map View
- Room details panel with capacity and equipment grouped by type
- Search by room number, name, or equipment, with matches highlighted on the map
- Route finding between two rooms with a bird’s-eye 3D view
- Edit floor plan directly from the map view
- Demo Preparation
- Collected vector based floor plans
- Cleaned test data out of the database
- Presented progress to Collins Aerospace
Stage III Report:
- [upcoming]
Stage IV Report:
- [upcoming]
MEETING MINUTES:
Week 1: Not yet assigned to teams.
Week 2: Assigned to the Facility Digital Twin project with Collins Aerospace. Introduced the team and set up a regular meeting time with the client.
Week 3: Client went over the project goals: turning floor plan PDFs into an interactive 3D map with searchable rooms and resources.
Week 4: Chose the tech stack (Angular, Three.js, Python, SQLite) and set up the repository. Researched ways to read floor plan PDFs and decided on pdfplumber.
Week 5: Built the first version of the upload page and PDF extraction. Uploaded the first test floor plans and designed the database schema.
Week 6: Prepared and presented Demo 1: uploading a PDF, extracting rooms and walls, the building library, and the 3D map view.
Week 7: Reviewed Demo 1 feedback and the Demo 2 requirements: room resources and availability, clickable rooms, resource search, navigation, redrawing rooms, and a mobile view.
Week 8: Planned Demo 2 backend work and split it into extraction/redraw and data/resources. Agreed on the floor plan data format with the frontend. Decided that redraws are saved on the server and the latest upload or redraw always wins.
Week 9: Presented current status, backend design, and next steps to Collins Aerospace. Found that ISU’s public class schedule does not list rooms, so availability has no data source yet. Decided to collect room equipment automatically from ISU’s classroom database and from labels on the floor plan.
Week 10: Presented Demo 2: uploading floor plans for several buildings, automatic room equipment collection, the room details panel, search by equipment, route finding between rooms, and the redraw tool with server saving.