Pull Request: Load Data from Local Parquet File & Expose API Endpoint

[SammyGIS]

Summary

This PR adds:

• Functionality to load flood data (Parquet file) locally geospatial data from a
• A new API endpoint to serve the data via FastAPI.

Context

This update supports efficient local data access during development and testing. It avoids external storage and aligns with the project’s current architecture.

Next Steps

• Fully integrate the new endpoint with the main API logic and existing routing structure.
• Optimize performance by:
  • Creating a local spatial database (duckdb table).
  • Enabling spatial indexing for faster query performance.
  • Try to see if the data can be cached for fast processing

Feedback Requested

Looking for feedback on:

• Code structure and readability
• Efficiency of loading data from local storage
• Integration of the new endpoint into the existing API — is the approach clean and maintainable?
• Suggestions for optimizing the geospatial queries setup