|
1 | 1 | Change Log
|
2 | 2 | ==========
|
3 | 3 |
|
| 4 | +### 3.0.0-draft.2019.11.13.1 (2019-11-13) |
| 5 | + |
| 6 | +#### Changes |
| 7 | + |
| 8 | +* The attribute `engineeringCRS` was added to the class `CityModel` to define a local coordinate system in a CityGML file. |
| 9 | +The attribute is encoded as metadata property in the XML Schema. [#45](https://github.com/opengeospatial/CityGML-3.0CM/issues/45) |
| 10 | + |
| 11 | +* The Transportation module was refined. [#64](https://github.com/opengeospatial/CityGML-3.0CM/issues/64) |
| 12 | + * The new concepts `Waterway`, `Intersection`, and `Marking` were added |
| 13 | + * The `TransportationComplex` is now modelled as `AbstractTransportationSpace`, and the class |
| 14 | + `TransportationSpace` was removed. [#82](https://github.com/opengeospatial/CityGML-3.0CM/issues/82) |
| 15 | + * The classes `Track`, `Road`, `Waterway`, `Railway`, and `Square` have now the stereotype |
| 16 | + `<<TopLevelFeatureType>>`. [#81](https://github.com/opengeospatial/CityGML-3.0CM/issues/81) |
| 17 | + * The attributes `class`, `function`, and `usage` were removed from the class `AbstractTransportationSpace` |
| 18 | + and are now defined separately for the classes `Track`, `Road`, `Waterway`, `Railway`, and `Square` to |
| 19 | + allow individual codelists for each feature type. |
| 20 | + * `AuxiliaryTrafficSpace` is now a subclass of `AbstractUnoccupiedSpace` instead of `AbstractPhysicalSpace`. |
| 21 | + * The subclasses `Drain`, `Manhole`, and `RoadwayDamage` were removed and instead were added as entries to |
| 22 | + the codelist for the `class` attribute of the feature type `Hole`. |
| 23 | + * The attribute `granularity` was added to the classes `TrafficSpace` and `AuxiliaryTrafficSpace` to be able |
| 24 | + to model traffic spaces at different levels of granularity. The allowed values `area`, `way` and `lane` |
| 25 | + are defined as enumeration `GranularityValue`. |
| 26 | + * A class `HoleSurface` was introduced to be able to represent the boundary surface of a hole. |
| 27 | + * The property `trafficFlow` was renamed to `trafficDirection`, its datatype was changed to an enumeration, |
| 28 | + and it was moved from the class `Section` to the two classes `AbstractTransportationSpace` and `TrafficSpace`. |
| 29 | + * The `GM_Complex` geometry as well as the `network` associations from `TrafficSpace` and |
| 30 | + `AbstractTransportationSpace` to `GM_Complex` were removed from the Transportation module. Instead, the |
| 31 | + property `lod0MultiCurve` was added to `AbstractSpace` in the Core module, which allows for representing every |
| 32 | + space through a `GM_MultiCurve` in LOD 0. |
| 33 | + |
| 34 | +* The Dynamizer module was refined. [#94](https://github.com/opengeospatial/CityGML-3.0CM/issues/94) |
| 35 | + * The `SensorConnection` data type contains new attributes to connect to different Sensor APIs using HTTP |
| 36 | + requests, MQTT Brokers, and Security parameters. |
| 37 | + * The `AbstractAtomicTimeseries` class no longer imports the OGC standards TimeSeriesML and |
| 38 | + Observations & Measurements (O&M). Instead, by means of the three subclasses `TabulatedFileTimeseries`, |
| 39 | + `StandardFileTimeseries`, and `GenericTimeseries` it is now possible to link to standardized timeseries files |
| 40 | + such as TimeseriesML 1.0 and O&M 2.0, to link to tabulated files such as CSV, and to represent basic |
| 41 | + time-value pairs for different types of properties such as integer, double, appearances, geometries, and |
| 42 | + ImplicitGeometries. A main motivation for this change was to reduce the dependencies and tight coupling |
| 43 | + to other standards, and thus to ease implementations. |
| 44 | + * The properties `firstTimestamp` and `lastTimestamp` were added to the class `AbstractTimeseries` to make |
| 45 | + them available for all subclasses. |
| 46 | + * The data type `URI` was changed to `CharacterString` for the attributes `attributeRef`, `linkToObservation`, |
| 47 | + and `linkToSensorDescription` to be able to represent XPath expressions. |
| 48 | + * The association `isComponent` was renamed into `component`. |
| 49 | + |
| 50 | +- The Relief module was refined. [#97](https://github.com/opengeospatial/CityGML-3.0CM/issues/97) |
| 51 | + * The classes `ReliefFeature` and `AbstractReliefComponent` are now defined as subclasses of the class |
| 52 | + `AbstractSpaceBoundary`. The class `AbstractSpaceBoundary`, in turn, was introduced in the Core module as |
| 53 | + superclass of `AbstractThematicSurface`. |
| 54 | + * The class `TINRelief` is again associated with `GM_TriangulatedSurface` as in CityGML 2.0. |
| 55 | + * The class `MassPointRelief` is again associated with `GM_MultiPoint` as in CityGML 2.0. In addition, it is |
| 56 | + can also be represented using an `AbstractPointCloud`. |
| 57 | + |
4 | 58 | ### 3.0.0-draft.2019.10.18.1 (2019-10-18)
|
5 | 59 |
|
6 | 60 | #### Changes
|
|
0 commit comments