CompositeDB#
- Full name:
spatialdata.spatialdb.CompositeDB
- Journal name:
compositedb
Virtual spatial database implemented as a combination of two spatial databases. This spatial database is useful when you need to provide additional values beyond those present in an existing spatial database or some values have a different layout than others.
Implements SpatialDB
.
Pyre Facilities#
db_A
: Spatial database A.current value: ‘uniformdb’, from {default}
configurable as: uniformdb, db_A
db_B
: Spatial database B.current value: ‘uniformdb’, from {default}
configurable as: uniformdb, db_B
Pyre Properties#
description
=<str>: Description for database.default value: ‘’
current value: ‘’, from {default}
validator: <function validateDescription at 0x102e94dc0>
values_A
=<list>: Names of values to query with database A.default value: []
current value: [], from {default}
values_B
=<list>: Names of values to query with database B.default value: []
current value: [], from {default}
Example#
Example of setting CompositeDB
Pyre properties and facilities in a parameter file.
[db]
values_A = [density]
values_B = [vp, vs]
db_A = spatialdata.spatialdb.UniformDB
db_A.description = Density spatial database.
db_A.values = [density]
db_A.data = [3000*kg/m**3]
db_B = spatialdata.spatialdb.SimpleDB
db_B.description = Wave speed spatial database.
db_B.iohandler.filename = vpvs.spatialdb