Editing AEC Open Data Standards Directory
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | Open data standards | + | Open data standards allow AEC tools to exchange datasets in a transparent and reliable manner. |
− | + | {|class="wikitable" | |
− | |||
− | {|class="wikitable | ||
− | |||
! Name | ! Name | ||
! Description | ! Description | ||
! Website | ! Website | ||
|- | |- | ||
− | |||
| 3D Tiles (b3dm, i3dm, pnts, cmpt) | | 3D Tiles (b3dm, i3dm, pnts, cmpt) | ||
| TODO | | TODO | ||
| TODO | | TODO | ||
|- | |- | ||
− | | | + | | Brick |
− | | | + | | 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] | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| 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. | + | [https://www.ogc.org/standards/citygml CityGML|OGC official website] |
− | | | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | |||
| [[Drawing Exchange Format (DXF)]] | | [[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. | | 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. | ||
Line 61: | Line 28: | ||
[https://www.google.com/search?client=firefox-b-d&q=autodesk+dxf+reference DXF Reference] | [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 37: | ||
[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 47: | ||
[https://www.khronos.org/gltf/ glTF official website] | [https://www.khronos.org/gltf/ glTF official website] | ||
|- | |- | ||
− | | | + | | Hierarchical Data Format (HDF, HDF4, HDF5) |
− | + | | TODO | |
− | + | | TODO | |
− | |||
− | |||
− | |||
− | |||
− | | | ||
− | | | ||
|- | |- | ||
− | |||
| [[Industry Foundation Classes (IFC)|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] | ||
|- | |- | ||
− | | | + | | JavaScript Object Notation (JSON) |
− | | | + | | TODO |
− | + | | TODO | |
− | | | ||
|- | |- | ||
− | |||
| 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 | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| Radiance (hdr, rad, mat, etc) | | Radiance (hdr, rad, mat, etc) | ||
| TODO | | TODO | ||
| TODO | | TODO | ||
|- | |- | ||
− | | | + | | Scalable Vector Graphics (SVG) |
− | | | + | | TODO |
− | | | + | | TODO |
− | |||
|- | |- | ||
− | | | + | | SQLite |
− | | | + | | TODO |
− | | | + | | TODO |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | |||
| Universal Scene Description (USD) | | Universal Scene Description (USD) | ||
− | | | + | | TODO |
− | | | + | | TODO |
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | |||
| Wavefront OBJ (OBJ) | | Wavefront OBJ (OBJ) | ||
| TODO | | TODO | ||
| TODO | | TODO | ||
|- | |- | ||
− | | | + | | Extensible Markup Language (XML) |
− | | | + | | TODO |
− | | | + | | TODO |
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− |