How professorlevesseur/mtssmaps works
Main components
• User Interface: The application uses Streamlit for its UI, with a dedicated .streamlit configuration directory and multiple page modules in the pages folder (e.g., “01_District_Code_Matchmaker.py”, “02_ISD_Map_Maker.py”, etc.).
• Data Processing and Code Matching: The tool processes and matches educational organization codes. There are spreadsheet examples and CSV files (found under codes and examples folders) that provide input data for the core logic (code matching and mapping).
• Generation: The geojson directory contains various geographical boundary files (e.g., Intermediate School Districts, School Districts, etc.) which feed data into the map visualization modules.
• Deployment & Configuration: Important deployment files include the Procfile, runtime.txt, setup.sh, and requirements.txt. These indicate the project’s deployment on platforms like Heroku or other cloud-hosted environments.
File structure and how components interact
• Frontend (Streamlit UI): The Streamlit framework handles page routing and interactivity. Each file in the pages directory represents a distinct page or function (code matching, map creation for ISDs, districts, PSAs, etc.).
• Data Input and Preparation: Users upload spreadsheets containing either educational organization names or codes. These spreadsheets are processed using scripts (for example, in District_Map_Maker.py) and example files are provided for reference.
• GeoJSON Integration: The geojson folder holds the boundary data used by the mapping functions. This ensures that the heat maps and pin-based overlays on the maps reflect the precise geographical boundaries.
• Code Matching Engine: Some scripts (in pages and District_Map_Maker.py) likely implement the logic to match uploaded data with corresponding educational codes.
• External Configuration: Files in .streamlit and scripts like Procfile setup the environment for running the Streamlit app in production.