IP Concerns For AI-Driven Flood Simulation Models For Barangay-Level Planning.

12 Mar 2026 --
0 Comments

1. Context: AI Flood Simulation Models & IP Issues

AI-driven flood simulation models are used for:

Predicting flood risk at barangay/community level

Planning evacuation routes, drainage systems, and local infrastructure

Integrating satellite, weather, and hydrological data

IP concerns arise because:

Algorithm Ownership: AI models and code may be copyrighted or patented.

Data Ownership: Flood risk data may be proprietary or sensitive.

Derivative Works: Combining datasets or modifying models may create IP issues.

Licensing Issues: Using third-party models or data without proper licenses may infringe IP.

Trade Secrets: Proprietary modeling techniques may need protection.

2. Case Analyses

Case 1: Feist Publications, Inc. v. Rural Telephone Service Co., 499 U.S. 340 (1991) – US

Facts:
Feist published a directory using factual data (names, addresses) from Rural Telephone’s listings. Rural sued for copyright infringement.

Issue:
Are raw facts (like flood level measurements or rainfall data) copyrightable?

Ruling:

Facts themselves are not copyrightable, only original selection/organization can be.

Feist won the case.

Implication for Flood Modeling:

Raw flood data (river levels, rainfall, barangay maps) can usually be used without infringing IP.

IP protection may apply if a company has curated, structured, or annotated datasets in a novel way.

Case 2: Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014) – US

Facts:
Alice Corp. had patents for a computer-implemented method for reducing financial settlement risk. CLS argued it was an abstract idea.

Ruling:

Algorithms implementing abstract ideas on a computer are not patentable unless they contain an “inventive concept”.

Implication for AI Flood Models:

A generic AI model predicting floods using standard machine learning techniques may not be patentable.

Patent protection is possible if the model incorporates novel hydrological computation techniques or unique AI architectures.

Case 3: SAS Institute Inc. v. World Programming Ltd., [2013] UKSC 24 – UK

Facts:
World Programming created software compatible with SAS software. SAS sued, claiming copyright infringement.

Ruling:

Creating compatible software without copying code does not infringe.

Implication:

AI flood simulation models can be re-implemented independently even if they mimic functionality of another system.

Copying proprietary code or training data without permission would be infringement.

Case 4: Oracle America, Inc. v. Google LLC, 593 U.S. ___ (2021) – US

Facts:
Google used Java APIs to develop Android. Oracle sued.

Ruling:

Functionality is generally not copyrightable; structure/sequence may be.

Google’s limited use was fair use.

Implication for AI Flood Models:

Using standard APIs or public hydrology libraries in simulations is usually safe.

Modifying proprietary APIs without a license can still create IP issues.

Case 5: University of London Press Ltd. v. University Tutorial Press Ltd., [1916] 2 Ch 601 – UK

Facts:
Dispute over copyright of exam questions.

Ruling:

Implication:

AI flood model methodology (e.g., “run neural network on rainfall data to predict flood”) is an idea, not copyrightable.

Protectable elements: code, report formats, visual outputs of flood simulations.

Case 6: Diamond v. Chakrabarty, 447 U.S. 303 (1980) – US

Facts:
A genetically engineered bacterium was claimed as patentable.

Ruling:

Human-made inventions can be patented, even if they are based on natural phenomena.

Implication:

If a flood simulation AI incorporates novel algorithms or system designs not found in nature, patent protection may be possible.

Case 7: Apple Inc. v. Samsung Electronics Co., 678 F.3d 1314 (Fed. Cir. 2012) – US

Facts:
Apple alleged Samsung infringed design patents of the iPhone interface.

Implication:

Visualizations and dashboards of AI flood models (e.g., maps, flood heatmaps) can be design-protected.

Copying these visual designs without license may constitute infringement.

3. Key Takeaways for AI Flood Simulation IP

IP Aspect	Takeaway
Data	Raw flood and rainfall data is usually free to use; curated/annotated datasets may be protected.
Algorithm	Abstract ML models are usually not patentable; novel AI methods or architectures may be.
Code	Copyright protects code, not ideas. Independent implementations are allowed.
Outputs	Reports, maps, dashboards may have design or copyright protection.
Third-party tools	Use APIs and software only under license to avoid infringement.
Trade Secrets	Proprietary modeling methods should be protected contractually.