Zoning Data API for Generative Architecture 3D Envelopes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current digital zoning data providers output data in a structure that is not directly usable by generative architecture model software, preventing the generation of three-dimensional (3D) representations of geospatial data.

Innovation Solution

A server configured to output structured digitized zoning data via an application programming interface (API) to generative architecture model software, allowing for the extraction and transmission of zoning restriction attributes and parameters in a predefined data exchange format.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing digital zoning data providers output data with too much optionality, then the data provides flexibility for various interpretations, but the data cannot be directly usable by generative architecture model software

Engineering Contradiction:
Improvedata flexibilityVSAvoiddirect usability
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent transforms zoning data from an unstructured format with excessive optionality into a structured format with specific parameters (building height limits, setback requirements, floor area ratios, etc.). This parameterization enables generative architecture software to directly interpret and utilize the zoning data without requiring manual interpretation or customization, thus resolving the contradiction between data flexibility and direct usability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent introduces an intermediary processing layer that converts raw zoning data into a standardized structured format before delivering it to generative architecture software. This intermediary transformation process maintains the adaptability of the original data while creating a usable intermediate representation that software can directly consume, bridging the gap between flexible source data and software requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If zoning data is extracted and packaged into a predefined data exchange format, then the data can be transmitted via API to generative architecture model software, but additional processing steps are required

Engineering Contradiction:
Improvedata transmission capabilityVSAvoidprocessing steps
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-structuring and pre-packaging zoning data into the required data exchange format before transmission. By preparing the data in advance with all necessary transformations, validations, and formatting completed beforehand, the system reduces the complexity of processing steps needed at transmission time, making the overall operation easier despite the additional preparatory work.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by automatically extracting, structuring, and packaging zoning data without requiring manual intervention. The automated processing pipeline handles all transformation steps, reducing the need for human operators to manage the complexity of data preparation, thus improving ease of operation while managing processing complexity through automation.

Inventive Principle:
Principle #25Self-service

3Productivity

If structured zoning data is provided via API, then automated extraction of zoning restriction attributes is enabled, but the system requires a standardized data structure

Engineering Contradiction:
Improveautomated data extractionVSAvoiddata structure standardization
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments zoning data into distinct, standardized components such as building height limits, setback requirements, floor area ratios, and use restrictions. By dividing the complex zoning information into discrete, well-defined segments with standardized formats, the system enables automated extraction and processing while managing the complexity through modular organization of data elements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal standardized data structure that can serve multiple functions: it enables automated extraction by generative architecture software, facilitates API transmission, and accommodates various types of zoning restrictions. This multi-functional standardized format increases productivity across different applications while managing complexity through a single versatile data model.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250044910A1Method of presenting structured digitized zoning data via an application programming interface to generative architecture model software
Publication Date: 2025.02.06 ZONEOMICS INC
  • US20250044910A1 patent drawing
  • US20250044910A1 patent drawing
  • US20250044910A1 patent drawing

AI summary

A method presents structured digitized zoning data, by a server including a processor and a memory, via an application programming interface (API) to a client computer for displaying three-dimensional (3D) representations of geospatial data generated by generative architecture model software on a graphical user interface (GUI) on the client computer. The method includes extracting from a zoning data record, by the processor, as a function of the zoning restriction request and as a function of a default and/or a conditional zoning use class, the zoning restriction attributes associated with the zone and the zoning restriction parameters for the zoning restriction attributes by retrieving, from the zoning data record, the zoning restriction attributes associated with the zone in the zoning data record and each zoning restriction parameter for the default and/or conditional zoning use class associated with the zoning restriction attributes in the zoning data record; packaging, by the processor, the extracted zoning restriction attributes and zoning restriction parameters into a data object in a predefined data exchange format associated with the API; and transmitting, by the processor, the data object, as an API response, to the generative architecture model software to generate a visual representation of the extracted zoning restriction parameters on the GUI on the client computer.