Standards List

This Standard defines the open CityGML Conceptual Model for the storage and exchange of virtual 3D city models. The CityGML Conceptual Model is defined by a Unified Modeling Language (UML) object model. This UML model builds on the ISO Technical Committee 211 (ISO/TC 211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the city models share the same spatiotemporal universe as the surrounding countryside within which they reside.
A key goal for the development of the CityGML Conceptual Model is to provide a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.
The class models described in this standard are also available at https://github.com/opengeospatial/CityGML3-Workspace/tree/1.0/UML/CityGML

This Standard documents the OGC GML Implementation Specification (IS) for the CityGML 3.0 Conceptual Model. The CityGML 3.0 conceptual model is a Platform Independent Model (PIM). It defines concepts in a manner which is independent of any implementing technology. As such, the CityGML Conceptual Model cannot be implemented directly. Rather, it serves as the base for Platform Specific Models (PSM). A PSM adds to the PIM the technology-specific details needed to fully define the CityGML model for use with a specific technology. The PSM can then be used to generate the schema and other artifacts needed to build CityGML 3.0 implementations.
This standard defines the PSMs and schemas for the CityGML 3.0 Implementation Specification (IS) for Geography Markup Language (GML) implementations. The GML schemas are explained in an overview and design decisions that have been made are documented as well.

This document provides a high-level ontology and lexicon for describing on-road ADS-operated vehicle behavioral competencies and driving maneuvers that comprise routine/normal performance of the complete DDT, as defined in SAE J3016. It provides definitions of behavior, maneuver, scenario, and scene. This initial high-level lexicon and ontology are developed for ADS driving behaviors, including considerations for hierarchy of behaviors, and relationships among maneuvers, operational design domain (ODD) elements, and object and event detection and response (OEDR). Considerations for describing scenarios using this lexicon and ontology are discussed. This document describes ADS-operated vehicle motion control maneuvers during routine/normal operation. Maneuvers of other road users are not evaluated. This document assumes left-hand drive vehicles and road infrastructure. Applicability to right-hand drive vehicles and roadway infrastructure would require adjustment to such vehicles and conditions.

ASAM OpenCRG defines a file format for the description of road surfaces. It was originally developed to store high-precision elevation data from road surface scans. The primary use for this data is in tire, vibration or driving simulation. Precise elevation data allows realistic endurance simulation of vehicle components or the entire vehicle. For driving simulators, it allows a realistic 3D-rendering of the road surface. The file format can also be used for other types of road surface properties, e.g. for the friction coefficient or grey values.
The standard describes a method to store the data in a specific layout, called ""curved regular grid"" (abr. CRG). The advantages of this method are high memory efficiency, low computation time for file generation and data processing in simulation tools, and high accuracy of positioning the data onto road networks.
The basic principle for describing the road surface is to place the data into a grid along a road reference line. Line segments are described by a start position and heading angle. The grid is produced by longitudinal cuts (columns) and lateral cuts (rows) along consecutive line segments. Each cell in this grid has a value, typically the elevation. The road center line also includes the end position, which can be used to detect and correct a potential drift of the placement of the data on roads.
ASAM OpenCRG defines ASCII and binary file formats with clear-text headers. The header contains road parameters for the reference line and the overall configuration of the longitudinal sections, a definition of the data format (ASCII and binary), the sequence of data which is expected in the trailing data block, and modifier and option parameters. Furthermore, OpenCRG-files may contain references to other files (typically containing the actual data) to handle different parameters for the same data set.

ODS (Open Data Services) focuses on the persistent storage and retrieval of testing data. The standard is primarily used to set up a test data management system on top of test systems that produce measured or calculated data from testing activities. Tool components of a complex testing system can store data or retrieve data as needed for proper operation of tests or for test data post-processing and evaluation. A typical scenario for ODS in the automotive industry is the use of a central ODS server, which handles all testing data produced by vehicle test beds. The major strength of ODS as compared to non-standardized data storage solutions is that data access is independent of the IT architecture and that the data model of the database is highly adaptable yet still well-defined for different application scenarios. Despite this flexibility, clients can query the data from the database and still correctly interpret the meaning of the data. This is achieved by various means through the standard.

The ASAM OpenDRIVE format provides a common base for describing road networks with extensible markup language (XML) syntax, using the file extension xodr. The data that is stored in an ASAM OpenDRIVE file describes the geometry of roads, lanes and objects, such as roadmarks on the road, as well as features along the roads, like signals. The road networks that are described in the ASAM OpenDRIVE file can either be synthetic or based on real data.
The main purpose of ASAM OpenDRIVE is to provide a road network description that can be fed into simulations to develop and validate ADAS and AD features. With the help of ASAM OpenDRIVE, these road network descriptions can be exchanged between different simulators. Providing a standardized format for road descriptions also enables the industry to reduce the cost of creating and converting these files for their development and testing purposes. Road data may be manually created from road network editors, conversion of map data, or originate from converted scans of real-world roads.

The CityGML standard defines a conceptual model and exchange format for the representation, storage and exchange of virtual 3D city models. It facilitates the integration of urban geodata for a variety of applications for Smart Cities and Urban Digital Twins, including urban and landscape planning; Building Information Modeling (BIM); mobile telecommunication; disaster management; 3D cadastre; tourism; vehicle & pedestrian navigation; autonomous driving and driving assistance; facility management, and; energy, traffic and environmental simulations.

ASAM OSI (Open Simulation Interface) provides easy and straightforward compatibility between automated driving functions and the variety of driving simulation frameworks available. It allows users to connect any sensor, via a standardized interface, to any automated driving function and to any driving simulator tooling. It simplifies integration and thus significantly strengthens the accessibility and usefulness of virtual testing.

ASAM OTX in conjunction with ISO 13209 (OTX) can be used in any application area where the definition of test procedures for documentation purposes or in an automation system is required. Typical application areas in the automotive industry are in ECU diagnostics testing, ECU calibration and EOL-testing.
In 2012, ISO published the new standard ISO 13209 ""Open Test Sequence Exchange"" (OTX), part 1 to 3, which has the main purpose to define a language and exchange format for the specification of executable test sequences. OTX has originally been developed for the area of ECU diagnostics testing, but is not limited to this area. Soon after the first OTX-based systems appeared on the market, end users required additional functionality, which were promptly implemented by tool suppliers. Some of the requested functionality, such as file processing or specific complex data types, impeded the exchangeability of OTX files and the interoperability of test systems. Consequently, there was a need to further standardize the additional functionality.

ASAM OpenLABEL specifies the different labeling methods that can be applied to multi-sensor data streams, for example, 2D bounding boxes for image data. With ASAM OpenLABEL, several labeling methods are provided which enable users to label common data streams, such as images or point clouds. Besides adding labels to multi-sensor data streams (labeling), ASAM OpenLABEL also provides methods to add tags to scenarios (tagging). These tags can be used to categorize scenarios and make them searchable in large databases. They can also provide additional information about the individual scenario, such as who captured or created the scenario, and with what setup was the scenario captured.
ASAM OpenLABEL provides a common data structure for organizing annotations for labeling multi-sensor data streams and tagging simulation and test scenarios.