DataDataData Base: But, We Should Call  IT "InfoBase" 

Introduction:

• This lecture explores the evolution of databases into what might more accurately be termed "infobases."

• The discussion focuses on the shift from value-based grids to feature-based systems, the role of queries, and the integration of databases into architectural and urban planning contexts.

From Grids to Databases:

1. The Grid and Its Evolution:

   • The spreadsheet is based on the grid, where cells contain values or results derived from functions.

   • This creates a branched system, allowing for dynamic "what-if" thinking.

2. Introducing Features:

   • The transition to a database occurs when grids are reorganized based on features rather than just values.

   • In a database, the vertical lines become "fields" (features or categories), and the horizontal lines become "records" (containers of information).

3. Homogeneous Fields:

   • For a database to function effectively, each field must contain homogeneous data (e.g., numerical, alphabetical, or geometric).

   • This homogeneity allows databases to handle complex information, including 3D models, raster images, and more.

Key Components of a Database:

1. Fields and Records:

   • Fields are the categories or attributes that describe data (e.g., name, height, location).

   • Records are individual entries that compile information across all fields.

2. Infinite Possibilities:

   • Databases can theoretically have infinite fields and records, enabling comprehensive descriptions of even the smallest elements.

3. Querying:

   • Queries are the backbone of databases, enabling users to extract specific information based on conditions (e.g., finding houses built before 1930).

   • Queries allow for logical combinations of fields, offering powerful ways to analyze and interact with data.

Applications in Everyday Life:

1. Airline Databases:

   • Modern flight search engines exemplify the power of open data and query-driven systems, allowing users to filter flights by price, date, and destination.

2. Open Data and Brokers:

   • Open data regulations require organizations to publish standardized information, enabling brokers to aggregate and optimize this data for user-friendly applications.

   • Examples include platforms like Uber and Airbnb, which rely on centralized databases to manage and present vast amounts of information.

3. Urban Planning and Architecture:

   • Databases can store and organize architectural and urban data, such as building plans, 3D models, and historical records.

   • GIS (Geographic Information Systems) integrates database concepts with maps, enabling spatial queries and visualization of information (e.g., locating all buildings built before a specific year).

Relational Databases:

1. Interlinking Data:

   • Databases and spreadsheets can be interconnected, creating relational databases where data flows between systems.

   • Example: A database query result (e.g., average age of a class) can be integrated into a spreadsheet for further calculations.

2. Dynamic Modeling:

   • Relational databases enhance modeling by combining the analytical power of spreadsheets with the structured storage of databases.

Significance in Architecture:

1. Foundation for BIM (Building Information Modeling):

   • Databases and spreadsheets underpin BIM, enabling detailed, data-rich models for design, construction, and maintenance.

2. Mapping and Queries in Urban Contexts:

   • Architects can use databases to query and map features such as building sizes, historical periods, or structural characteristics, providing valuable insights for urban planning.

Key Takeaways:

1. From Data to Info:

   • The term "infobase" reflects the transformation of raw data into structured, queryable information.

2. Integration of Features:

   • Databases organize complex, heterogeneous data types, including numerical, textual, and geometric information.

3. Architectural Applications:

   • Understanding database principles is essential for leveraging tools like BIM and GIS, which are critical for modern architectural practice.

Conclusion:

• This lecture highlights the power of databases as tools for organizing, querying, and visualizing information.

• By adopting "what-if" thinking and integrating features, architects and planners can harness databases to redefine design, analysis, and decision-making processes.

Next class ➡️