AND Trenches GIS-Import FeatureCollection
Type: object
Description
This schema defines a GeoJSON FeatureCollection tailored specifically for the Advanced Network Design system, designed to facilitate the import of trench data into an AND project. It includes detailed specifications for trench-related features and their attributes to ensure comprehensive data integration and management. The name of the geojson file to be imported is mandatory ‘trenches.geojson’. Note that the definitions for ducts and other related infrastructure components are managed separately in a distinct schemas to maintain clarity and modularity when preparing data to be imported.
Required Properties
type
features
Properties
The following properties are defined for this object:
type
Type:
string
Allowed Values
"FeatureCollection"
features
Type:
array
Items
Each item in this array must adhere to the following schema:
GeoJSON Feature:
features
Type:
object
Required Properties
type
properties
geometry
Properties
The following properties are defined for this object:
type
Type:
string
Allowed Values
"Feature"
id
Type:
string
Description
the ID of external system which will be stored within ‘RefId’ property of instanciated AND Object
Target: RefId of object
Default Value
The default value for this item is:
null
properties
Type:
object
Properties
The following properties are defined for this object:
identification
Type:
string
Description
Identification name will be used to do a logical collect over ids which represent segments within the trench with that name
Target: InstallationNumber of the object
type
Description
The trench type ‘earth’ or ‘air’. This type may be used also to assign children-ducts together with id
Component-mapping: true
Value-mapping: true
Target: map to TrenchLayingType.xml and store in trench property ‘Laying Type’. It will be ignored when ‘layingtype’ is valid
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
1
2
Default Value
The default value for this item is:
1
Type:
string
Allowed Values
"trench(earth)"
"trench(air)"
Default Value
The default value for this item is:
"trench(earth)"
component_id
Description
Allows an explicit mapping to an AND library object via mapping setup
Component-mapping: true
Target: not stored - used for mapping only
This item must also validate against exactly one of the following schemas:
Type:
integer
Type:
string
owner
Type:
string
Description
The owner of that trench
Target: Is stored in DB and location info ‘Owner’. At begin of import all occuring owners (strings) will be collected and searched in DB by name. The existing ones mapped, the new ones added (with message)
status
Description
Specifies the status of the trench (enum)
Value-mapping: true
Target: will be mapped into ObjAttribute::State from States.xml
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
50
100
200
300
400
420
440
450
480
500
600
700
800
900
Default Value
The default value for this item is:
50
Type:
string
Allowed Values
"n/a"
"inherit"
"Evaluation"
"Decision"
"Planning"
"Planned"
"Ordered"
"Booked"
"Interrupted"
"Building"
"Built"
"Operation"
"Standing Idle"
"Out of Order"
Default Value
The default value for this item is:
"n/a"
color
Type:
string
Description
Color in RGB / RGBA format (e.g., ‘rgba(0, 0, 255, 1.0)’ for blue; Alpha channel will be ignored)
Component-mapping: true
Value-mapping: true
Target: the rgb-value will be mapped to one of 127 fix colors of AND
Examples
The following are example values for this schema:
-
"rgba(0, 0, 255, 1.0)"
-
"rgb(0, 0, 255)"
-
layer
Type:
string
Description
Name of the layer where this trench will be placed on
Component-mapping: true
Value-mapping: true
Target: will be mapped into ObjAttribute::Layer - if layer not found the it will not be added automatically
system_id
Type:
string
Description
Filter to technical system - will be used to assign to project/design
Target: Triplet or DaaVar, if the assignment is configured in the metadata
data
Type:
object
Description
Company defined additional JSON information
Target: Triplet or DaaVar, if the assignment is configured in the metadata - will be handled internally as string
width
Type:
number
Description
The width of the trench
Target: trench property
depth
Type:
number
Description
The depth of that trench
Target: trench property ‘Depth’. Negative values mean a height
length
Type:
number
Description
The measured length - makes sense in schematic drawings
Target: measured length of line-object
marking_band
Type:
string
Description
The desciption of a marking band if present
Target: trench property ‘Warning Tape’
mounting_cost
Type:
number
Description
Specifies the mounting costs in h/m
Target: trench property ‘Mounting Costs’
material_cost
Type:
number
Description
Specifies the material costs
Target: Triplet or DaaVar, if the assignment is configured in the metadata
installation_year
Type:
string
Description
The installation year
Target: trench location info property
surface
Description
Specifies the surface type of the trench (enum)
Component-mapping: true
Value-mapping: true
Target: map to surface of SurfaceType.xml and store in trench property ‘Surface Type’
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
1000
1001
1002
1003
1004
1005
Type:
string
Allowed Values
"unknown"
"unmetaled"
"tarred"
"concreted"
"paved"
"paved (sealed)"
layingtype
Description
Specifies the laying type of the trench (enum)
Component-mapping: true
Value-mapping: true
Target: map to layingtype of TrenchLayingType.xml and store in trench property ‘Laying Type’
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
Type:
string
Allowed Values
"unknown"
"buried"
"tray installation"
"arial"
"dry installation"
"within construction"
"Street crossing"
"Train route crossing"
"Bridge route crossing"
"River route crossing"
trenching_method
Description
Specifies the trenching method type of the trench (enum)
Component-mapping: true
Value-mapping: true
Target: map to trenching_method of ConstructionMethod.xml and store in trench property ‘Construction Principle’
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1299
Type:
string
Allowed Values
"unknown"
"Conventional Excavation"
"Cable Ploughing"
"Micro Trenching"
"Mini Trenching"
"Macro Trenching"
"Hydraulic Rotary Water Drilling"
"Soil Displacement"
"With Sewer Trench"
"With Water Trench"
"Aerial Mounting"
"Other"
accuracy
Description
Specifies the accuracy type of the trench (enum)
Component-mapping: true
Value-mapping: true
Target: map to accuracy of Accuracy.xml and store in trench property ‘Accuracy’
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
1300
1301
1302
1303
Type:
string
Allowed Values
"unknown"
"planned"
"estimated"
"accurate"
permission
Description
Specifies the permission type of the trench (enum)
Value-mapping: true
Target: map to permission of Permit.xml and store in trench properties
This item must also validate against exactly one of the following schemas:
Type:
integer
Allowed Values
1400
1401
1402
1403
1404
Type:
string
Allowed Values
"neutral"
"not needed"
"pending"
"obtained"
"rejected"
cross_section_shape
Description
Specifies the cross section type of the trench - can be used for mapping with trench-template or library component
Component-mapping: true
Target: Triplet or DaaVar, if the assignment is configured in the metadata
This item must also validate against exactly one of the following schemas:
Type:
integer
Examples
The following are example values for this schema:
-
1800
-
1801
-
1802
-
1803
-
1804
-
1805
-
1806
-
1807
-
1899
-
Type:
string
Examples
The following are example values for this schema:
-
"unknown"
-
"round"
-
"quadratic"
-
"rectangular"
-
"trapezoid"
-
"hexagonal"
-
"octagonal"
-
"oval"
-
"other"
-
owner_type
Description
Specifies the owner type of the trench which can be used for mapping with trench-template
Component-mapping: true
Target: Triplet or DaaVar, if the assignment is configured in the metadata
This item must also validate against exactly one of the following schemas:
Type:
integer
Examples
The following are example values for this schema:
-
1900
-
1901
-
1902
-
1903
-
1904
-
Type:
string
Examples
The following are example values for this schema:
-
"neutral"
-
"own inventory"
-
"foreign inventory"
-
"communal inventory"
-
"partner inventory"
-
GeoJSON LineString:
geometry
Type:
object
Description
Defines the GeoJSON LineString geometry representing the entire trench segment layout. This geometry may be adjusted to align with connection points on associated objects.
Target: stored in the objects geometry - the line-geometry can be adjusted to pins of objects where they are connected to
Required Properties
type
coordinates
Properties
The following properties are defined for this object:
type
Type:
string
Allowed Values
"LineString"
coordinates
Type:
array
Minimum number of items:
2
Items
Each item in this array must adhere to the following schema:
coordinates
Type:
array
Minimum number of items:
2
Items
Each item in this array must adhere to the following schema:
coordinates
Type:
number