Import Configuration
The configuration settings for the import
command are divided into "importOptions"
for general import
settings and "readOptions"
for input file settings and format-specific options.
The names and purposes of the JSON properties align closely with their counterparts in the command-line options. Where applicable, the description of each JSON property links to the command-line option for more details. |
Import options
The example below illustrates the JSON structure for the import options.
{
"importOptions": {
"mode": "importAll",
"indexMode": "keep",
"failFast": false,
"numberOfThreads": 4,
"batchSize": 20,
"tempDirectory": "/my/path/to/temp",
"affineTransform": [0.0,1.0,0.0,0.0,1.0,0.0,0.0,0.0,0.0,0.0,1.0,0.0],
"lineage": "myLineage",
"updatingPerson": "myUpdatingUser",
"reasonForUpdate": "myReasonForUpdate",
"filterOptions": {...}
}
}
General import options
Property | Description | Default value |
---|---|---|
Import mode: |
|
|
Index mode: |
|
|
Fail fast on errors. |
|
|
Number of threads to use for parallel processing. |
||
|
Number of top-level features that are committed to the database in a single transaction. A higher batch size might improve import performance but requires more memory. |
20 |
Store temporary files in this directory. |
||
Transform coordinates using a 3x4 matrix in row-major order. The matrix coefficients are represented as array. |
||
Lineage to use for the features. |
||
Name of the user responsible for the import. |
database user |
|
Reason for importing the data. |
Filter options
The "filterOptions"
property is a container object for the following filtering options.
{
"filterOptions": {
"featureTypes": [ (1)
{
"name": "bldg:Building"
},
{
"name": "Road",
"namespace": "http://3dcitydb.org/3dcitydb/building/5.0"
}
],
"ids": ["foo","bar"],
"bbox": {
"coordinates": [10.0,10.0,20.0,20.0],
"srs": { (2)
"srid": 4326,
"identifier": "http://www.opengis.net/def/crs/EPSG/0/4326"
}
},
"bboxMode": "intersects",
"countLimit": {
"limit": 1000,
"startIndex": 20
}
}
}
1 | The "name" property is mandatory. To avoid ambiguity, use the format "prefix:name" with a namespace alias as prefix or
specify the full namespace using the "namespace" property. |
2 | Use either "srid" , "identifier" , or both to define the target CRS. |
Property | Description | Default value |
---|---|---|
Array of JSON objects specifying the features to process. Each object must include the |
||
Array of identifiers defining the features to process. |
||
Defines a 2D bounding box as a spatial filter using a |
||
Bounding box mode: |
|
|
The |
Read options
The JSON structure for storing read options is shown below. Format-specific settings are provided within the
"formatOptions"
container object, with the input format name used as the key for the corresponding settings.
You only need to provide format-specific options for the file formats that match your input files. |
{
"readOptions": {
"failFast": false,
"numberOfThreads": 4,
"encoding": "UTF-8",
"tempDirectory": "/path/to/temp",
"computeEnvelopes": true,
"formatOptions": {
"CityGML": {...},
"CityJSON": {...}
}
}
}
General read options
Property | Description | Default value |
---|---|---|
Fail fast on errors. |
|
|
Number of threads to use for parallel processing. |
||
Encoding of input file(s). |
||
Store temporary files in this directory. |
||
Compute and overwrite extents of features. |
|
CityGML options
The "CityGML"
property is a container object for CityGML-specific format options.
{
"CityGML": {
"includeXALSource": false,
"xslTransforms": [
"/path/to/myFirstStylesheet.xsl",
"/path/to/mySecondStylesheet.xsl"
],
"appearanceOptions": {
"readAppearances": true,
"themes": ["foo","bar"]
},
"useLod4AsLod3": false,
"mapLod0RoofEdge": false,
"mapLod1MultiSurfaces": false,
"createCityObjectRelations": true,
"resolveCrossLodReferences": true
}
}
Property | Description | Default value |
---|---|---|
Include XML snippets of xAL address elements. |
|
|
An array of XSLT stylesheets to transform the input, referenced by filename and path (absolute or relative). The stylesheets are applied in the specified order. |
||
The |
||
Use LoD4 as LoD3, replacing an existing LoD3. |
|
|
Map LoD0 roof edges onto roof surfaces. |
|
|
Map LoD1 multi-surfaces onto generic thematic surfaces. |
|
|
|
Create |
|
|
Resolves geometry references between different LoD representations of the same feature. |
|
CityJSON options
The "CityJSON"
property is a container object for CityJSON-specific format options.
{
"CityJSON": {
"mapUnsupportedTypesToGenerics": true,
"appearanceOptions": {
"readAppearances": true,
"themes": ["foo","bar"]
}
}
}
Property | Description | Default value |
---|---|---|
Map city objects from unsupported extensions onto generic city objects. |
|
|
The |