Flood Risk in NYC: A Product for Insurance Professionals
Introduction
According to Swiss Re, flooding is classified as a secondary peril, posing greater modeling challenges compared to hurricanes and earthquakes. The unpredictability of flood occurrences, both in terms of timing and location, adds to the complexity. The limited adoption of flood catastrophe models by insurance professionals can be attributed to these difficulties. Current flood catastrophe models do not have a high degree of confidence, as U.S. flood models are still in their infancy.
The product we’ve created proves valuable for insurance professionals by offering insights into the locations outlined in a schedule of values. While it doesn’t fall under the category of a catastrophe model, it furnishes valuable information. This information aids insurance professionals, including underwriters and actuaries, in making well-informed decisions regarding the provision of flood insurance for individuals, groups, companies, or government entities.
As a Product
This section explains where in the product development life cycle this product currently stands.
Genesis: Class Project to Product
Our team initiated this project by exploring numerous publicly available NYC datasets. After extensive discussions, we collectively decided to transform our final class project into a product roadmap and a startup idea. This document marks the beginning of that journey. It serves as our running Proof of Concept (POC) for a new Software as a Service (SaaS) product.
There’s a wealth of free information provided by the City of New York, ripe for businesses to leverage. Navigating this data is not straightforward, given the various ways of describing geographic data, such as block IDs, zone IDs, addresses, grid coordinates, etc. However, mastering this allows for the creation of an elegant and integrated information symphony.
Phase 1: POC (Completed)
This phase involved our initial end-to-end process to ensure data linkability.
- Compile a list of precisely formatted addresses (for our demo, we used all CUNY campuses).
- Look up these addresses in the NYC “master” address API system to obtain primary keys and grid coordinates for linking to other systems.
- Cross-reference these addresses with a major NYC Dataset, Pluto.
- Merge this data with Pluto and filter it to focus on insurance data.
- Implement an underlying polygon system, akin to outlining zip codes on a map.
- Determine if the target element (i.e., the CUNY address) falls within the specified polygon.
Phase 2: Alpha - The Working Product
The alpha version needs to operate in a more real-time manner, such as uploading a spreadsheet of addresses and receiving output instantly.
To progress from POC to alpha release, we need to add:
- A database, such as Postgres Aurora.
- A modern authentication system.
- A method for correcting ambiguous addresses (e.g., “W 4th St” - is it West 4th Street?). NYC offers an API for this.
- A web framework to facilitate CSV uploads into the system.
- A display mechanism for output, which will be in HTML format, with one HTML file generated per run.
- Integration of the runtime R code with AWS Lambda.
Future Development
Once the foundational elements are operational, we plan to incorporate additional datasets, such as crime statistics, school literacy rates, and building and fire code violations.