Inframodel transfer files fully conform to the LandXML v1.2 schema, but some extensions have been made using the Feature-mechanism. This section lists these Inframodel extensions, providing an index to the Inframodel Feature Dictionary: the <FeatureDictionary> element in Inframodel transfer file with the name 'inframodel' (specifying the <Feature> elements in the file with attribute source as 'inframodel' and the attribute code being labeled with ''IM_' -prefix).
NB: In addition to these extensions, Inframodel specifies many restrctions on the use of LandXML elements and their attributes. These restrictions are described in chapters 1 to 11 of this document.
Type coding systems define the purpose of geometric elemnents (points, lines and surfaces) as well as other types of elements (such as plan features, pipes and structures in pipe networks, etc).) in Inframodel file transfers. The information is set in two phases: 1) The type coding systems are declared in the project information <Project> using "IM_codings"feature extension and 2) individual type codes and their descriptions are set under each element using ("IM_coding" feature extension).
The main systems set in the project information are:
It is possible to set the same system for several categories. It is also possible to set alternative or additional type coding systems (e.g. InfraRYL) for use within an organization or in a software used.
Details: | Header information | 1.6 Type coding systems |
Individual type codes are set for the following elements in inframodel file transfers:
Individual type codes are set in the individual element, or in the parent element, whose children inherit the values. Type codes are set using the "IM_Coding" feature extension, either as terrain codes terrainCoding, surface codes surfaceCoding or object/feature codes infraCoding. Alternative or additional type coding systems are set with assigned name as proprietary codes proprietaryInfraCoding.
Details: | Surfaces | 2.1.3 Type coding | |
Route planning | 3.2.2 Type coding | ||
Water supply | 8.5 Structures | ||
Water supply | 8.6 Pipes | ||
Plan features in Roads/streets, Railways or Waterways | 9.2.1.7 Type coding |
The details of a plan are described for each project part:
If the project consists of sub-projects that have different rates of progress, the plan contents of the file are divided into sub-projects according to the same division. The plan information contains the planName, planCode, the planState and the plan description planDesc. The plan state is described according to a scheme agreed on by the parties of the project.
Details: | Surfaces | 2.1.1 Plan information | |
Route planning | 3.2.1 Plan information | ||
Water supply and sewerage | 8.2.1 Plan information |
The string line model is composed of line string alignments <IrregularLine>. Their order with an <Alignment> is irrelevant. The string line model used in Inframodel is based on the Leica RoadRunner software.
The string line model is defined under an <Alignment> in the "IM_stringlineLayers" extension. The constituent line strings and their locations are set by layer in the "IM_stringlineLayer" child element. The order of description of the line strings does not matter, the alignments are identified by their unique name <Aligenment>.name, which are listed in the element, separated by commas. A layer is assigned a name and optionally a centerline. When describing a layered structure the layers of the string line model are assigned surface codes SurfaceCoding. The same line string may belong to several different layers. Layer are listed starting from the top downwards.
Details: | Route planning | 3.5 Route string line model |
Cross-section parameters contain parametric information considered crucial for each route type. They are set for the stationing reference alignment in the <CrossSects>.<CrossSect> "IM_crossSect" extension under the <Alignment> element. The chosen cross-section parameters are set in fields (<Property>). It is advisable to describe all parameters for each cross-section. If the some parameters change, the cross-section where the parameter begins to change and the end of the transition are described.
The described parameters vary by route type:
Details: | Road and street design |
4.4.1 Cross-section parameters | |
Railway design | 5.5 Cross-sections and track information | ||
Waterway design | 6.3 Waterway cross-section parameters |
It is possible to describe additional details for the water supply and sewerage network structures described in inframodel file transfers. The parameters are:
Details: | Water supply and sewerage |
8.5.1 Circular structures | |
8.5.2 Rectangular structures | |||
8.5.3 Inlets and outlets of pipes | |||
8.5.4 Pipe joints, connections and intersections | |||
8.5.5 Equipment |
Describing pipe details is optional in inframodel file transfers. It is possible to set the following attributes:
Details: | Water supply and sewerage |
8.6.1 Circular pipe | |
8.6.2 Egg pipe | |||
8.6.3 Elliptical pipe | |||
8.6.4 Rectangular pipe | |||
8.6.5 Channel |
To assing northing and easting coordinates to railway <Alignment>.<StationEquation>, the parameters are:
Details: | Railway design |
5.4 KM-posting |
Switch details at railway track <Alignment>.<CoordGeom>.<Line>,
the parameters are:
Details: | Railway design |
5.3.3 Swithces |
Planimetric features belonging to a particular route design are described in <Roadways>.<Roadway>.<PlanFeature>, or in other cases in <PlanFeatures>.<PlanFeature>, by following data:
Details: | Road and street design |
4.6.1 Plan features | |
Railway design | 5.7.1 Plan features | ||
Waterway design | 6.6.1 Plan features | ||
General | 9 Planimetric features |