| Latest revision |
Your text |
| Line 1: |
Line 1: |
| − | Open data standards, often represented as file formats allow AEC tools to exchange datasets in a transparent and reliable manner. These could be file formats like [[IFC - Industry Foundation Classes|.ifc]] or [[Scalable_Vector_Graphics_(SVG)|.svg]] or they could be database formats or more generically data schemas that can be used in many ways (IFC can be both) | + | Open data standards allow AEC tools to exchange datasets in a transparent and reliable manner. |
| | | | |
| − | This page is a directory of open file formats and data standards. For a comparison of some popular file formats see [[File format comparison]]
| + | {|class="wikitable" |
| − | | |
| − | {|class="wikitable sortable" | |
| − | ! Image
| |
| | ! Name | | ! Name |
| | ! Description | | ! Description |
| | ! Website | | ! Website |
| | |- | | |- |
| − | |
| |
| | | 3D Tiles (b3dm, i3dm, pnts, cmpt) | | | 3D Tiles (b3dm, i3dm, pnts, cmpt) |
| | | TODO | | | TODO |
| | | TODO | | | TODO |
| | |- | | |- |
| − | | [[File:Building_Collaboration_Format_icon.png|64px]] | + | | Brick |
| − | | [[BCF - BIM Collaboration Format]] | + | | TODO |
| | + | | TODO |
| | + | |- |
| | + | | Building Collaboration Format (BCF) |
| | | "The BIM Collaboration Format (BCF) allows different BIM applications to communicate model-based issues with each other by leveraging IFC models that have been previously shared among project collaborators. BCF was created for facilitating open communications and improving IFC-based processes to more readily identify and exchange model-based issues between BIM software tools, bypassing proprietary formats and workflows." | | | "The BIM Collaboration Format (BCF) allows different BIM applications to communicate model-based issues with each other by leveraging IFC models that have been previously shared among project collaborators. BCF was created for facilitating open communications and improving IFC-based processes to more readily identify and exchange model-based issues between BIM software tools, bypassing proprietary formats and workflows." |
| | | [https://www.buildingsmart.org/standards/bsi-standards/bim-collaboration-format-bcf/ BCF at buildingSmart] | [https://en.wikipedia.org/wiki/BIM_Collaboration_Format BCF at Wikipedia] [https://technical.buildingsmart.org/standards/bcf/ BCF at buildingSmart] | | | [https://www.buildingsmart.org/standards/bsi-standards/bim-collaboration-format-bcf/ BCF at buildingSmart] | [https://en.wikipedia.org/wiki/BIM_Collaboration_Format BCF at Wikipedia] [https://technical.buildingsmart.org/standards/bcf/ BCF at buildingSmart] |
| | |- | | |- |
| − | |
| |
| − | | BHoM: Buildings and Habitats object Model
| |
| − | | The core BHoM contains objects from wide ranging domains across the disciplines of engineering, architecture, our environment and the physical world, as well as defining concepts within programming, machine learning, mathematics, geometry and planning to name a few.
| |
| − | | [https://bhom.xyz/ BHoM official website]
| |
| − | |-
| |
| − | | [[File:Brick_schema_logo.png|64px]]
| |
| − | | Brick
| |
| − | | Brick is an open-source effort to standardize semantic descriptions of the physical, logical and virtual assets in buildings and the relationships between them. Brick consists of an extensible dictionary of terms and concepts in and around buildings, a set of relationships for linking and composing concepts together, and a flexible data model permitting seamless integration of Brick with existing tools and databases.
| |
| − | | [https://brickschema.org/ Brickschema official website]
| |
| − | |-
| |
| − | |
| |
| − | | Building Topology Ontology
| |
| − | | "Building Topology Ontology (BOT) as a core vocabulary to this approach. It provides a high-level description of the topology of buildings including storeys and spaces, the building elements they contain, and their web-friendly 3D models. We describe how existing applications produce and consume datasets combining BOT with other ontologies that describe product catalogues, sensor observations, or Internet of Things (IoT) devices effectively implementing BIM Maturity Level 3."
| |
| − | | [https://w3c-lbd-cg.github.io/bot/ Draft] [https://www.ogc.org/standards/citygml CityGML OGC official website]
| |
| − | |-
| |
| − | | [[File:CityGML-Logo2.png|64px]]
| |
| | | CityGML | | | CityGML |
| | | CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. | | | CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. |
| | | [http://www.citygml.org/ CityGML official website] | | | [http://www.citygml.org/ CityGML official website] |
| − | [https://www.researchgate.net/publication/342802332_BOT_the_Building_Topology_Ontology_of_the_W3C_Linked_Building_Data_Group research paper] | + | [https://www.ogc.org/standards/citygml CityGML|OGC official website] |
| | |- | | |- |
| − | |
| |
| − | | Digital Buildings Project
| |
| − | | The Digital Buildings project is an open-source, Apache-licensed effort to create a uniform schema and toolset for representing structured information about buildings and building-installed equipment. A version of the Digital Buildings ontology and toolset is currently being used by Google to manage buildings in its portfolio.
| |
| − | | [https://github.com/google/digitalbuildings Github]
| |
| − | |-
| |
| − | |
| |
| − | | Digital Twins Definition Language ( + RealEstateCore)
| |
| − | | The Digital Twins Definition Language (DTDL) is a language for describing models and interfaces for IoT digital twins. Digital twins are models of entities in the physical environment such as shipping containers, rooms, factory floors, or logical entities that participate in IoT solutions. Using DTDL to describe a digital twin's capabilities enables the IoT platform and IoT solutions to leverage the semantics of the entity.
| |
| − | | [https://github.com/Azure/opendigitaltwins-dtdl Github] [https://github.com/Azure/opendigitaltwins-building Building Github]
| |
| − | |-
| |
| − | |
| |
| − | | [[dotbim]]
| |
| − | | Introducing an open-source, accessible, simple, minimalist file format for BIM. Built to be easy to read and write. Created by BIM developers for BIM developers.
| |
| − | | [https://github.com/paireks/dotbim Github]
| |
| − | |-
| |
| − | |
| |
| − | | [[Drawing Exchange Format (DXF)]]
| |
| − | | Drawing Exchange Format (DXF) is a file format designed by Autodesk to allow exchange with their AutoCAD software. While they publish specs it is not an open format as they alone control iterations to the format. Autodesk and the Open Design Alliance sell commercial licenses for accessing DXF files. There is generally good support for DXF is libre software.
| |
| − | | [https://en.wikipedia.org/wiki/AutoCAD_DXF DXF at Wikipedia]
| |
| − | [https://www.google.com/search?client=firefox-b-d&q=autodesk+dxf+reference DXF Reference]
| |
| − | |-
| |
| − | |
| |
| | | Green Building XML (gbXML) | | | Green Building XML (gbXML) |
| | | "It is the language of buildings that allows disparate 3D building information models (BIM) and architectural/engineering analysis software to share information with each other" | | | "It is the language of buildings that allows disparate 3D building information models (BIM) and architectural/engineering analysis software to share information with each other" |
| | | [https://www.gbxml.org/ gbXML official website] | | | [https://www.gbxml.org/ gbXML official website] |
| | |- | | |- |
| − | |
| |
| | | GeoJSON | | | GeoJSON |
| | | GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON). It defines several types of JSON objects and the manner in which they are combined to represent data about geographic features, their properties, and their spatial extents. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984, and units of decimal degrees. | | | GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON). It defines several types of JSON objects and the manner in which they are combined to represent data about geographic features, their properties, and their spatial extents. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984, and units of decimal degrees. |
| Line 72: |
Line 32: |
| | [https://tools.ietf.org/html/rfc7946 RFC7946 official website] | | [https://tools.ietf.org/html/rfc7946 RFC7946 official website] |
| | |- | | |- |
| − | |
| |
| | | GeoPackage (gpkg) | | | GeoPackage (gpkg) |
| | | GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. The GeoPackage Encoding Standard describes a set of conventions for storing the following within an SQLite database: vector features, tile matrix sets of imagery and raster maps at various scales, attributes (non-spatial data) and extensions. | | | GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. The GeoPackage Encoding Standard describes a set of conventions for storing the following within an SQLite database: vector features, tile matrix sets of imagery and raster maps at various scales, attributes (non-spatial data) and extensions. |
| | | [https://www.geopackage.org/ GeoPackage official website] | | | [https://www.geopackage.org/ GeoPackage official website] |
| | |- | | |- |
| − | |
| |
| | | GL Transmission Format (glTF) | | | GL Transmission Format (glTF) |
| | | "[https://godotengine.org/article/we-should-all-use-gltf-20-export-3d-assets-game-engines Why we should all support glTF 2.0 as THE standard asset exchange format for game engines]" on GODOT open source game engine blog. | | | "[https://godotengine.org/article/we-should-all-use-gltf-20-export-3d-assets-game-engines Why we should all support glTF 2.0 as THE standard asset exchange format for game engines]" on GODOT open source game engine blog. |
| Line 84: |
Line 42: |
| | [https://www.khronos.org/gltf/ glTF official website] | | [https://www.khronos.org/gltf/ glTF official website] |
| | |- | | |- |
| − | | | + | | Hierarchical Data Format (HDF, HDF4, HDF5) |
| − | | Honeybee Schema
| + | | TODO |
| − | | A JSON-based schema to describe analytical building physics models that is used and developed by the Ladybug Tools project and Pollination, which can work across multiple building analysis tools (e.g. EnergyPlus, Radiance).
| + | | TODO |
| − | | [https://github.com/ladybug-tools/honeybee-schema Honeybee Schema repository] [https://www.ladybug.tools/honeybee-schema/ Honeybee Schema website]
| |
| − | |-
| |
| − | |
| |
| − | | Hypar Elements
| |
| − | | Elements is a cross-platform library for creating building elements. It's meant to be used by architects, engineers, and other building professionals who want to write code that generates buildings. | |
| − | | [https://hypar-io.github.io/Elements/index.html Hypar elements specification] | |
| | |- | | |- |
| − | | | + | | Industry Foundation Classes (IFC, ifc, ifcxml, ifczip) |
| − | | [[Industry Foundation Classes (IFC)|Industry Foundation Classes]] (IFC, ifc, ifcxml, ifczip)
| |
| | | "IFC is a standardized, digital description of the built asset industry. It is an open, international standard (ISO 16739-1:2018) and promotes vendor-neutral, or agnostic, and usable capabilities across a wide range of hardware devices, software platforms, and interfaces for many different use cases." (from buildingSmart) | | | "IFC is a standardized, digital description of the built asset industry. It is an open, international standard (ISO 16739-1:2018) and promotes vendor-neutral, or agnostic, and usable capabilities across a wide range of hardware devices, software platforms, and interfaces for many different use cases." (from buildingSmart) |
| | | [https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/ IFC at buildingSmart] [https://en.wikipedia.org/wiki/Industry_Foundation_Classes IFC at Wikipedia] | | | [https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/ IFC at buildingSmart] [https://en.wikipedia.org/wiki/Industry_Foundation_Classes IFC at Wikipedia] |
| | |- | | |- |
| − | | [[File:Materialsdb_image.png|64px]] | + | | JavaScript Object Notation (JSON) |
| − | | materialsdb | + | | TODO |
| − | | "..allows providers to independently manage their own building material database and does not require a central database. The building physics software can access the various decentralised databases via a DLL (Dynamic Link Library). The xml file delivered by the providers contains two sets of data: a list of materials and a catalogue of pre-calculated elements. It contains all the information required by building physics software, i.e. geometry, thermal properties, acoustic properties, life cycle energy and emissions data, etc. The format developed is flexible enough so that it is not necessary for providers to provide the full set of data."
| + | | TODO |
| − | | [http://www.materialsdb.org materialsdb.org] | |
| | |- | | |- |
| − | |
| |
| | | Open Shading Language (OSL) | | | Open Shading Language (OSL) |
| | | TODO | | | TODO |
| | | TODO | | | TODO |
| | |- | | |- |
| − | |
| |
| | | OpenCDE | | | OpenCDE |
| | | "Current industry practice of data exchange between common data environments is inefficient and costly. Commercial reasons aside, [https://www.designingbuildings.co.uk/wiki/Common_data_environment_CDE CDE] Vendors have real technical challenges for developing sustainable integrations." | | | "Current industry practice of data exchange between common data environments is inefficient and costly. Commercial reasons aside, [https://www.designingbuildings.co.uk/wiki/Common_data_environment_CDE CDE] Vendors have real technical challenges for developing sustainable integrations." |
| | | [https://technical.buildingsmart.org/idea/vendor-user-alignment-via-opencde-api/ opencde at buildingSmart] | | | [https://technical.buildingsmart.org/idea/vendor-user-alignment-via-opencde-api/ opencde at buildingSmart] |
| | |- | | |- |
| − | |
| |
| | | Polygon File Format (PLY) | | | Polygon File Format (PLY) |
| | | TODO | | | TODO |
| | | TODO | | | TODO |
| | |- | | |- |
| − | |
| |
| − | | Project Haystack
| |
| − | | Project Haystack is an open source initiative to streamline working with data from the Internet of Things. We standardize semantic data models and web services with the goal of making it easier to unlock value from the vast quantity of data being generated by the smart devices that permeate our homes, buildings, factories, and cities. Applications include automation, control, energy, HVAC, lighting, and other environmental systems.
| |
| − | | [https://project-haystack.org/ Official website]
| |
| − | |-
| |
| − | |
| |
| | | Radiance (hdr, rad, mat, etc) | | | Radiance (hdr, rad, mat, etc) |
| | | TODO | | | TODO |
| | | TODO | | | TODO |
| | |- | | |- |
| − | | | + | | Scalable Vector Graphics (SVG) |
| − | | Real Estate Core | + | | TODO |
| − | | RealEstateCore is a common language that will enable control over buildings and development of new services – the facilitator of the promises of a digital transformation. RealEstateCore is a domain ontology preparing buildings to interact with the Smart City. | + | | TODO |
| − | | [https://www.realestatecore.io/ Official website] - [https://doc.realestatecore.io/3.3/full.html Specification]
| |
| | |- | | |- |
| − | | | + | | SQLite |
| − | | SAREF: the Smart Applications REFerence ontology | + | | TODO |
| − | | The Smart Applications REFerence ontology (SAREF) is intended to enable interoperability between solutions from different providers and among various activity sectors in the Internet of Things (IoT), thus contributing to the development of the global digital market. | + | | TODO |
| − | | [https://saref.etsi.org/core/v3.1.1/ SAREF Docs]
| |
| − | |-
| |
| − | | [[File:SAF_logo.png|64px]]
| |
| − | | [[Structural Analysis Format (SAF)]]
| |
| − | | SAF is an initiative from the Nemetschek Group to improve the collaboration between structural engineers by developing an open exchange format for exchanging data between structural analysis software based on the Excel format. It is focusing on a practical, easy to use, format that can be used in daily practise by structural engineers. It is meant as open format and we look forward to you joining this initiative
| |
| − | | [https://saf.guide website]
| |
| − | |-
| |
| − | | [[File:1200px-SVG_logo.svg.png|64px]]
| |
| − | | [[Scalable Vector Graphics (SVG)]]
| |
| − | | SVG is an image format developed by the [https://da.wikipedia.org/wiki/World_Wide_Web_Consortium World Wide Web Consortium (W3C)] for vector graphics. SVG uses an XML format and is easy to generate on the fly and edit in many programs. [[Inkscape]] and [[Krita]] are leading examples of vector graphics editors using the SVG format, but many other programs can export to SVG.
| |
| − | | [https://www.w3.org/TR/SVG2/ website]
| |
| − | |-
| |
| − | |
| |
| − | | Speckle Objects Kit
| |
| − | | Objects Kit is the default Speckle 2.0 Kit. It includes geometry and element base classes as well as conversions routines for the AEC applications that we officially support. Objects uses .NET Standard 2.0 and has been tested on Windows and MacOS.
| |
| − | | [https://speckle.guide/dev/objects.html Speckle Object Kit Docs]
| |
| − | |-
| |
| − | |
| |
| − | | STEP
| |
| − | | ISO 10303 is an International Standard for the computer-interpretable representation of product information and for the exchange of product data. The objective is to provide a neutral mechanism capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving.
| |
| − | | [http://www.steptools.com/stds/step/IS_final_p21e3.html Public ISO final draft]
| |
| | |- | | |- |
| − | | [[File:USDLogoUnsized.svg|64px]]
| |
| | | Universal Scene Description (USD) | | | Universal Scene Description (USD) |
| − | | "USD is a high-performance extensible software platform for collaboratively constructing animated 3D scenes, designed to meet the needs of large-scale film and visual effects production. USD provides robust interchange between digital content creation tools with its expanding set of schemas, covering domains like geometry, shading, lighting, and physics. USD’s unique composition features have powerful benefits. For example, composition provides rich and varied ways to combine individual assets into larger assemblies, and enables workflows that let many users collaborate simultaneously without conflict." Text from the [https://graphics.pixar.com/usd/release/index.html USD website]. Nvidia is exploring '[https://aecmag.com/collaboration/nvidia-looking-to-encode-the-ifc-schema-in-usd/ encoding IFC in USD]' | + | | TODO |
| − | | [https://graphics.pixar.com/usd/release/index.html Dedicated website]. Licensed with [https://github.com/PixarAnimationStudios/USD/blob/release/LICENSE.txt Apache 2.0] | + | | TODO |
| − | |-
| |
| − | |
| |
| − | | VIM-format
| |
| − | | The VIM format is a modern and efficient open 3D data interchange format designed for BIM and manufacturing data optimized for efficient loading and rendering on low-power devices. Unlike other 3D data formats, VIM is designed to carry substantial amounts of complex relational data and instanced geometry in an efficient and standardized manner with minimal pre-processing.
| |
| − | | [https://github.com/vimaec/vim-format VIM-format Github]. Licensed with [https://github.com/vimaec/vim-format/blob/develop/license.txt MIT]
| |
| | |- | | |- |
| − | |
| |
| | | Wavefront OBJ (OBJ) | | | Wavefront OBJ (OBJ) |
| | | TODO | | | TODO |
| | | TODO | | | TODO |
| | |- | | |- |
| − | | | + | | Extensible Markup Language (XML) |
| − | | XKT | + | | TODO |
| − | | The XKT format compresses large double-precision models to a compact payload that loads quickly over the Web into a xeokit viewer running in the browser. We can use xeokit-convert to convert several source formats into XKT, such as IFC, glTF and CityJSON. | + | | TODO |
| − | | [https://github.com/xeokit/xeokit-convert/blob/main/specs/index.md XKT schema]. Licensed with [https://github.com/xeokit/xeokit-convert/blob/main/LICENSE Affero GPL V3]
| |
| | |} | | |} |
| − |
| |
| − | [[Category:Drawing_Exchange_Format_(DXF)]]
| |
| − | [[Category:Directories]]
| |
| − | [[Category:File formats]]
| |
