LandInfra: the great example of bSI / OGC alignment · • Follows the OGC Modular Specification for extensibility • Builds upon and extends GML3.2 and 3.3 foundation for features,

ISO/TC211 Geographic information/Geomatics Copyright 2014 1

9 June 2017

Confidential ©

2015

LandInfra: the great example of

bSI / OGC alignment

Scott Simmons, Executive Director Standards Program, Open

Geospatial Consortium (OGC)


9 June 2017

Confidential ©

2015

• buildingSMART International (bSI) Infra Room

• Open Geospatial Consortium (OGC) Land and

Infrastructure Domain and Standards Working

Groups (LandInfra DWG and LandInfra SWG)

• People in THIS room!

Who?


9 June 2017

Confidential ©

2015

LandInfra / InfraGMLhttp://www.opengeospatial.org/standards/landinfra

Land Features

Roads

Railway

Alignment

Survey

Facilities

Projects

Land Division

Core

Condominiums


9 June 2017

Confidential ©

2015

Land and Infrastructure (LandInfra)

• Land and Infrastructure Conceptual Model Standard

(LandInfra)

– It’s all about the land upon which infrastructure facilities are built

– and the infrastructure facility improvements themselves

– including the surveying necessary for the construction and

recording of the facilities and land interests

• “use case driven subset of LandXML functionality, but …

supported by a UML (Unified Modeling Language)

conceptual model”

• LandInfra is a Conceptual Model, specified as an

approved OGC Standard (OGC 15-111r1), independent of

implementations but whose target is encoding standards

• InfraGML is one of those LandInfra encodings


9 June 2017

Confidential ©

2015

UML


9 June 2017

Confidential ©

2015

Flexibility of LandInfra Requirements Classes


9 June 2017

Confidential ©

2015

Extendable InfraGML: a Multi-Part Standard; each

Part contains one or more RCs

0. Core

2. Facilities and Projects

6. Survey 7. LandDivision3. Alignments

4. Roads 5. Railways

1. LandFeatures

8. Site 9. Wet Infrastructure

10. Utilities


9 June 2017

Confidential ©

2015

Facility – Facility Part - Element

Facility

Facility Part Physical Element

Building Road Railway Site

part

Facility Part Relationship

WastewaterWater Distribution

Storm Drainage

Utilities


9 June 2017

Confidential ©

2015

GML


9 June 2017

Confidential ©

2015

InfraGML Encoding Standards

• InfraGML marks a significant, pragmatic realization in the often

idealized integration of GIS/CAD/BIM

• Based on the LandInfra consensus concepts developed by OGC with

buildingSMART International

• Follows the OGC Modular Specification for extensibility

• Builds upon and extends GML3.2 and 3.3 foundation for features, data

types, spatial schema, coordinate and linear referencing, and

observation and measurement

• Provides a framework for addressing the full facility life cycle

• Capitalizes on the numerous extensions to the OGC baseline that have

been added since “GIS” Simple Features

• Parallels extensions by bSI beyond just “buildings”


9 June 2017

Confidential ©

2015

InfraGML

• Part 0 is the (concrete) Core RC which shall be supported by

all conforming applications

• Then an application can select from

– Part 1 Land Features

– Part 2 Facilities (with optional Projects)

– Part 3 Alignments

– Part 6 Survey (with optional Equipment, Observations, and

SurveyResults)

– Part 7 (2017) Land Division (with optional Condominiums)

– or any combination of these

• If Land Features and Facilities are supported, an application

can then also include Part 4 Roads (with optional Road

Cross Sections)

• If Facilities are supported, an application can then also

include Part 5 Railway


9 June 2017

Confidential ©

2015

Alignment - UML

class Alignment

Alignment2DHorizontal

Alignment2DVertical

«FeatureType»

Alignment

+ alignmentID: ID

+ purpose: CharacterString [0..1]

+ designAlternative: CharacterString [0..1]

+ linestring2DRepresentation: LineString [0..1]

+ linestring3DRepresentation: LineString [0..1]

OGC-ASTopic19-

LinearReferencing::

LinearReferencingMethod

Set

AlignmentSet

AlignmentCurve

+ crs: SC_EngineeringCRS

Geometry

OGC-ASTopic1-

FeatureGeometry::

Curve

OGC-ASTopic19-

LinearReferencing::

StartValue

+ measure: Real

+ uom: UnitOfMeasure

+ lrm: URI

«interface»

ISO-19103-

CoreDataTypes::

Measure

+ value: Number

SC_CRS

OGC-ASTopic2-

SpatialReferencingByCoordinates:

:SC_EngineeringCRS

LandInfra::LinearElement

+ referent: Referent [0..*]

OGC-ASTopic19-LinearReferencing::

LinearElement

+ base: LinearElementBase

+ defaultLRM: LinearReferencingMethod

+ measure: Measure

+ startValue: StartValue

OGC-ASTopic19-

LinearReferencing::Referent

+ name: CharacterString

+ type: ReferentType

+ position: Point [0..1]

+ location: PositionExpression [0..1]

LandInfra::RestartReferent

+ restartValue: StartValue [0..*]

«union»

LandInfra::

LinearElementBase

+ feature: AnyFeature

+ curve: Curve

+ edge: DirectedEdge

Topology

OGC-ASTopic1-

FeatureGeometry::

DirectedEdge

«FeatureType»

LandInfra::Feature

«FeatureType»

ISO-19109-

ApplicationSchema:

:AnyFeature

+vertical

0..1

+alignment

1..*

+measuredAlong

1

+geometry0..1

+horizontal

1


9 June 2017

Confidential ©

2015

Alignment - GML

<?xml version="1.0" encoding="UTF-8"?><LandInfraDatasetxmlns="http://www.opengis.net/infragml/core/1.0" xmlns:gml="http://www.opengis.net/gml/3.2" gml:id="ds1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:li="http://www.opengis.net/infragml/core/1.0" xmlns:lia="http://www.opengis.net/infragml/alignment/1.0" xmlns:gmllr="http://www.opengis.net/gml/3.3/lr" xmlns:gmllro="http://www.opengis.net/gml/3.3/lro" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/infragml/alignment/1.0 Part3Alignment0321.xsd">

<datasetID><identifier>DS3</identifier><scope>OGC LandInfraSWG</scope>

</datasetID><name>Sample Part3 Dataset</name><description>LandInfra dataset to test all possible content for Part3 Alignment</description><dateTime>2016-11-02T10:00:00</dateTime><datasetVersion>1.0</datasetVersion><application>manual</application><author>Paul Scarponcini, Bentley Systems, Inc.</author><infraVersion>1.0</infraVersion><language>English</language><defaultCRS xlink:href="crs1"/><feature>

<lia:Alignment gml:id="a1"><gml:description>sample alignment definition</gml:description><gml:name>Road 1 alignment</gml:name><lia:alignmentID>

<lia:identifier>Alignment1</lia:identifier><lia:scope>OGC LandInfraSWG</lia:scope>

</lia:alignmentID><lia:purpose>roadway centerline</lia:purpose><lia:designAlternative>DesignA</lia:designAlternative><lia:linestring2DRepresentation gml:id="l2D">

<gml:pos>0 1000</gml:pos><gml:pos>0 1100</gml:pos>


9 June 2017

Confidential ©

2015

LandInfra RC (InfraGML Core)

• Core (mandatory) RC

• The root class, LandInfraDataset:

– specifies the Land and Infrastructure dataset

– attributes provide header information

• The dataset may contain any number of:

– features (facility, land feature, land division, document, survey mark)

having featureID, name, description, spatialRepresentation,

linearlyReferencedLocation, property, and propertySet

– plus: surveys, sets, and feature associations

• The RC contains other classes and data types common

across other RCs

Part 0


9 June 2017

Confidential ©

2015

LandFeature RC

• LandFeatures include:

– topographic Features of the

land, e.g., naturally occurring

water features and vegetation

– surfaces, modelled as TINs, including the top ground terrain surface

and any subterranean surfaces which separate the underground into

layers

– layers of homogeneous material of type SolidLayer, SurfacesLayer, or

LinearLayer

• SolidLayers are spatially represented as Polyface Mesh

Solids; SurfacesLayer as top and bottom LandSurfaces

(TINs); and LinearLayers as a series of ordered cross

sectional areas Part 1


9 June 2017

Confidential ©

2015

Facility RC

• Facilities include buildings

and civil engineering works

and their associated siteworks

• A Facility has a life cycle, including planning, design,

construction, maintenance, operation, and removal phases.

• Facilities may be broken down into FacilityParts, based on

type

• FacilityPart is a logical collection of physical elements

representing manufactured or constructed parts or virtual

elements used to locate, align, or organize physical elements

Facility is dependent upon the LandInfra core

Part 2


9 June 2017

Confidential ©

2015

Project RC

• A Project is an activity related to the improvement of a facility, including design and/or construction

• A Project may be for the creation, modification, or elimination of the entire facility or a part of the facility

• Projects can have multiple parts, termed ProjectParts which relate to a single facility type (road, railway, etc.)

• Project is dependent upon Facility

Part 2


9 June 2017

Confidential ©

2015

Alignment RC

• An alignment provides a Linear Referencing System for locating physical elements;

defined

• as a 3D or simple 2D linestring representation (in any CRS)

• as a horizontal alignment: that is, a 2D projection onto a horizontal plane of a Cartesian

local engineering reference system

• as a horizontal alignment with an accompanying 2D vertical long section taken along the

horizontal alignment

• with a 3D linestring generated from the horizontal and vertical

• The Alignment RC Conceptual Model was jointly developed with bSI so that it can

function as a link between OGC GML and bSI IFC

Part 3


9 June 2017

Confidential ©

2015

Road Element Surface

String Line Cross Section

Multiple Representation Schemes


9 June 2017

Confidential ©

2015

Road RC

• For exchanging the output of a design

with someone who is likely to use the

design for purposes other than

completing the road design.

• Road specifies that part of a Facility which is a single segment

of road that is continuous, non-overlapping, and non-branching

(though it may contain intersections with other roads)

• Road can be represented with RoadElements, 3D StringLines,

or 3D surfaces and layers, or sets of each of these

• Road is dependent upon Facility and LandFeature

Part 4


9 June 2017

Confidential ©

2015

RoadCrossSection RC

• Extends the Road Requirements Class by adding the 2D CrossSection alternative way of representing a design.

• A CrossSection describes how a Road looks (or will look), in a 2D cross section view, at some specific location along its length.

• CrossSections can have CrossSectionElements and/or Areas, defined by CrossSectionPoints

• RoadCrossSection is dependent upon Road

CL

RCurbAndGutter

RSidewalk

LUnpavedShoulder

LGravelShoulder

Pavement

BaseLDitch

LCut6:1

RFill2:1

RVerge

ExistingGroundSurface

Part 4


9 June 2017

Confidential ©

2015

Railway RC

• For exchanging the output of a

design with someone who is

likely to use the design for

purposes other than completing

the railway design.

• Railway is a Feature that specifies that part of a Facility which is a single

segment of railway that is continuous, non-overlapping, and non-branching

(though it may contain intersections with other railways)

• CantSpecification is a collection of CantEvents which mark locations along

the railway where an applied cant value (difference in elevation between the

two rails) changes

• Railway is dependent upon Facility

Part 5


9 June 2017

Confidential ©

2015

Survey RC

• Surveys cover the acquisition

of points, lines, surfaces and

properties of features of interest.

The primary focus is recording

and reprocessing the

observations of the acquired objects.

• The Survey class contains header information for the surveys

• Survey is divided in sub-packages because of the number of

classes in the Observations, SurveyResults and Equipment

packages

• Survey is dependent upon the LandInfra core

Part 6


9 June 2017

Confidential ©

2015

LandDivision and Condominium RCs (2017)

Part 7


9 June 2017

Confidential ©

2015

LandInfra Phase II

• Planning has begun by the LandInfraDWG

• Possible candidates so far:

– “wet” infrastructure

– utilities

– site / landscape architecture

– environmental

– road design ?


9 June 2017

Confidential ©

2015

LandInfra / InfraGMLhttp://www.opengeospatial.org/standards/landinfra

Land Features

Roads

Railway

Alignment

Survey

Facilities

Projects

Land Division

Core

Condominiums

Storm Drainage

Water Distribution

Wastewater Underground Utilities


9 June 2017

Confidential ©

2015

What is “wet infrastructure” ?

• LandInfra differentiates between “wet” infrastructure

and “utilities”

• Wet infrastructure:

– facilities typically designed by civil engineers and owned and

operated by government agencies (though public-private

partnerships are arising)

– are usually built in public right-of-way (or easements)

– include storm drainage, wastewater, and water distribution

systems


9 June 2017

Confidential ©

2015

What are “Utilities” ?

• Utilities:

– facilities typically designed, owned, and operated by

(public or private) companies

– include electrical distribution, gas networks,

telecommunications, etc.


9 June 2017

Confidential ©

2015

LandInfra Scope

• LandInfra considers wet infrastructure to be in

scope:

– attention is paid to design information similar to what

has been done for road and railway facilities, and to

that level of detail (bSI IFCs will most likely go deeper

into design details)

– a network model is fundamental

– properties (identification, material, geometry, location,

etc.) of elements (pipe, manholes, etc.) will be included


9 June 2017

Confidential ©

2015

LandInfra Scope

• For utilities, LandInfra:

– does not anticipate that the design will be explicitly included as

facilities,

– though the detailed location of such facilities may be added for

referenceability, as it impacts the design of civil engineered

facilities

– rough location and legal protection of such facilities are covered

in this standard by easements

• Superficie Objects are already supported

– buildings or other construction, including pipes, cables or

tunnels, located above, on, or below the land parcel surface,

established and owned by a party other than the owner of that

land parcel, nonetheless linked to the land parcels on which

they are located


9 June 2017

Confidential ©

2015

Foundation for Extension

• Extensible Feature Model: features, data types, spatial schema,

coordinate and linear referencing, and observation and

measurement

• Incorporates:

– OGC-AS Topic 1 – Feature Geometry

– OGC-AS Topic 2 – Spatial Referencing By Coordinates

– OGC-AS Topic 19 – Linear Referencing

– OGC-AS Topic 20 – Observations And Measurement

– OGC 07-036 Geography Markup Language (GML)

– OGC 10-129r1 Extended schemas and encoding rules GML3.3

– ISO-19103 – Core Data Types

– ISO-19109 – Application Schema

• Full facility life cycle asset management approach for various

types of infrastructure facilities


9 June 2017

Confidential ©

2015

Extension Considerations

• Add support for the design of wet infrastructure facility

parts similar to what was done for road and railway, that

is with (state = proposed)

• Support other subsurface (utility) facility parts with

(state = existing)

– follow ASCE38-02 Collection and Depiction of Existing

Subsurface Utility Data (SUE)

– support four levels of quality and reliability of underground

information by multiple representation schemes (as for Roads)

• Work with other ongoing efforts as was done with bSI

– CityGML Utility ADE revision

– PipelineML

– this Underground Infrastructure Mapping and Modeling project

Documents

LandInfra: the great example of bSI / OGC alignment · • Follows the OGC Modular Specification for extensibility • Builds upon and extends GML3.2 and 3.3 foundation for features,