https://urkesh.org/MZ/A/B07/D/F/0011.htm

Unit Book B7

B7f11

Processed on 2025-11-27

1. OVERVIEW

Roster Date Author Record
Category !! !! surface
Best definition 2010-09-15 pC floor, type d [Input: U913PC.J]
Best image 2010-09-18 !!
v12 [Input: U928PC.J]

2. IDENTIFICATION

Designation

Roster Date Author Record
Description (summary) 2010-09-27 pC A surface poorly preserved, compacted naturally. It was found directly east of f9 in k101. [Input: U912PC1.J]

3. STRATIGRAPHY

Recovery/Assignment

Roster Date Author Record
Strategy (projected or implemented) 2010-09-27 pC We decided to leave f11 and dig south of it continuing removing f8 [Input: U912PC1.J]
Argument 2010-09-27 pC It was very difficolt to expose it without removing the surface, whle it was not really compact, but while pavement f9 strats suddently in k101 and while it should be a path, fAB suggested that f11 should be the continuation of the path f9. It is also located At the same elevation as f9 [Input: U912PC1.J]

Volumetric Localization

Roster Date Author Record
Locus 2010-09-15 pC k101 [Input: U913PC.J]
M#/elev @top 2010-09-15 pC m1818 [Input: U913PC.J]

Contact Association

Roster Date Author Record
Type of contact: latest events 2010-09-15 pC f13 (accumulation D) abuts f11 (floor, type d) [Input: U912PC1.J]
2010-09-14 pC f8 (collapse) covers f11 (floor, type d) [Input: U912PC1.J]
Type of contact: earliest events 2010-09-27 pC f11 (floor, type d) abuts f9 (pavement, type c) [Input: U912PC1.J]

6. REFERENCE

Analogical Record

Roster Date Author Record
View/drawing of features

v12
2010-09-18 pC [Input: U928PC.J]

v13
2010-09-18 pC [Input: U928PC.J]

v14
2010-09-18 pC [Input: U928PC.J]

v15
2010-09-18 pC [Input: U928PC.J]

v15a
2010-09-18 pC [Input: U928PC.J]

v16
2010-09-18 pC [Input: U928PC.J]