Public launch

What's Changed

• Chakra UI v3 Migration: The frontend has undergone a significant upgrade to Chakra UI v3, impacting component usage, styling definitions, and overall UI framework. This involved refactoring various components like List, Card, Switch, Popover, and InputGroup to align with the new API and design system.

• Monitoring and Analytics Integration: Sentry has been integrated into the backend for robust error tracking, and Posthog has been added to the frontend for analytics, providing better visibility into application performance and user behavior.

• Enhanced Development Workflow: The README.md has been extensively updated with clearer and more detailed instructions for local and Docker-based development, including a new process for handling encrypted environment variables. Python dependency management has transitioned from pip to uv for faster and more reliable builds, and pre-commit hooks have been refined.

• Dynamic Map Layer Toggling: New functionality has been introduced to allow users to dynamically toggle the visibility of different hazard layers (soft story, liquefaction, tsunami) directly from the UI, enhancing map interactivity.

• Refactored Hazard Data Handling: Frontend hazard data fetching logic has been encapsulated within a new useHazardDataFetcher hook, improving code organization and error handling. Backend GeoJSON exports are now optimized to only regenerate when underlying data has changed, boosting ETL efficiency.

• Improved Soft Story and Liquefaction Logic: The backend logic for soft story properties now more accurately differentiates between compliant and non-compliant buildings. Additionally, new API endpoints have been added to specifically retrieve high and very high susceptibility liquefaction zones, providing more granular hazard information.

Alpha release

• Migration from Chakra UI v2 to v3 and Next.js v13 to v15.
• Enhanced ETL Data Processing: added upsert logic and a new system for tracking GeoJSON export metadata.
• Observability and Analytics Integration: Sentry has been integrated into the FastAPI backend. Additionally, PostHog has been set up for client-side analytics.
• Improved Developer Experience and Documentation: The project's documentation has been substantially updated with clearer setup instructions, detailed troubleshooting guides, and refined Git workflow guidelines. VS Code extension recommendations were also added to promote code consistency.
• Refined Hazard Data Accuracy: The backend API for soft story properties now filters out buildings that have completed their retrofit work. This ensures that the application provides more accurate and relevant hazard information to users by excluding properties that are no longer considered at risk.