Archaeological objects are objects shaped by culture and are the subject of a thorough Archaeological documentation. The Objects are originally created or influenced by humans, either in action or in thought. The Class Archaeological object's is a powerful Tool to describe an Object's shape, character and context. Archaeological objects are also used as primary units for collecting Observation objects and it is also the unit that is divided into Excavation units.
Archaeological objects can be both single Objects, building stones (like for example a Post-hole) and Object structures, a chain of Relations with other A-objects (like for example a House related to a number of Post-holes). The Object structures can be concrete (like a construction) or abstract time Structures (like phases) or abstract spatial Structures (like a Farm structure).
Archaeological objects can be divided into SubClasses and each SubClass can have a separate set of Attributes. In the Default metadata template the Attribute type is used for the SubClass division.
The Archaeological object has no predefined Properties.
The Archaeological object is created when a GeoObject is measured and it can also be created as new Object in the System.
|
Object |
Archaeological objects |
|
ObjectId |
I s generated from the GeoObject's first Point number. |
|
Measurement code: |
Example: |
|
GeoObject type |
All GeoObject types are valid. The Archaeological object can have a number of Boundaries (type 2) that describe its extension. The Archaeological object can be measured with an interface (type 8). Two Archaeological objects are then created at import. One Object is the fill and the one Object is the cut. Your Measurement number (the first Point number and the Measurement object) means the fill Object and the interface receives a new ObjectId. A stratigraphic Relation is automatically created between the Objects.. |
|
Class code in the Default template |
A (MetaId 11) |
|
SubClass designator in default metadata template |
Means the type of Archaeological object. SubClasses can be defined in the Metadatabase. 1) No SubClass |
|
Object reference |
The Archaeological object's Point number (200) creates a new Archaeological object. Another Archaeological object reference in the Database creates a new GeoObject to the referred Object. |
|
Secondary reference |
1) to an ObjectId that represents an Archaeological
object (10) |
|
Relations |
1) when you have a secondary Object reference a Relation is created to the Parent object. |
How I proceed to: