https://urkesh.org/MZ/A/A16/D/A/0012.htm

Unit Book A16

Version 1a

A16a12

Processed on 2024-08-10

1. OVERVIEW

Roster Date Author Record
Equals other label 2014-11-06 cJC f192 (^ pavement) [Input: YY06CJC.j]
Best definition 2001-08-18 !! ^ pavement [Input: L724LR.j]
Summary 0000-00-00 pC Stone pavement of the palace courtyard, composed of flat big limestones, damaged by various pits (f250, f189, f216) [Input: R805PC.j]
Best image 0000-00-00 pC [Input: R805PC.j]

2. IDENTIFICATION

Designation

Roster Date Author Record
Definition 2001-08-18 lR ^ pavement [Input: L724LR.j]
Description (summary) 2001-08-18 lR stone pavement with bricks underneath [Input: L724LR.j]

3. STRATIGRAPHY

Recovery/Assignment

Roster Date Author Record
Daily notes about recovery of elements 2002-09-22 lR The situation below the tomb f206 is rather unclear. In this area the tomb a16 cut all the way to the stones and placed the bodies i60 i54 on top of the stones. When all of the burial was removed including the bricks of f233 and f234 on the north side it revealed to have stones below them part of a12, but these stones are lower than the rest of the pavement. One stone seen through the burial cut is at the same level of the pavement and appears that the stones either slope down or are part of a stairway/step. Between the high stones and low stones is the packing f344 characterized by its blocky structure and reddish/purple color. This packing covers the eastern area around f206 cut and it is unclear whether the stones continue under the red packing. To the south it appears that the stones are in a line and may form a corner. In k202 the stone pavement comes to a sudden end. It is unclear whether the end was intentional or that the stones were removed at a later time. The end does not form a clear line to suggest any function. [Input: N303LR.j]
2002-09-26 fAB Two small holes were found on the pavement- one stone that resemble post holes. They are f336 and f335 [Input: M926LR.j]
2002-09-29 lR The stone pavement was cut by f189, which removed the stones and exposed a series of baked bricks underneath, a24. These bricks measure 30 x 30 centimeters and alternate from a pale yellow color to an orange color with cracks running through the bricks. These bricks are baked, hard, and arranged in rows. There are 8 rows of bricks visible with some damage in the northern and southern portion. [Input: N303LR.j]
2002-10-05 lR Today I began drawing the stone courtyard starting from the NE corner working towards the west then south. This project required the help of the surveyor bp who set up a grid in lower A16. Three points were surveyed r500 - r503, which are the frame for the grid. From these surveyed nails strings were measured in using a tape measure at two meter intervals. Five strings running North-South and five strings running East to West. The last interval in the south measures less than 2 meters and the last interval in the west measures 152 centimeters. Once the strings of the grid were in place I then placed a 1x1 meter metal grid with 20 centimeter increments inplace between the corners of the strung grid, directly ontop of the stone courtyard allowing a 20cm "boxes" to measures all lines of the stones. This method although tedious (one 2x2 meter square takes between 30min-1hour and total there are 22 squares) proved to be the most accurate for drawing the stones. One simply needs to stand directly overhead the grid and draw. The scale used for this drawing is 1:2 meaning one millimeter on the graph paper measures 2cm in real space. This scale was chosen since the detail of the stones was lost when a smaller scale was used. The use of the 1:2 scale requiered 8 sheets of graph paper taped together and the use of a large clipboard. [Input: MX05SB.j]

Volumetric Localization

Roster Date Author Record
Locus 2001-06-17 fAB k108 [Input: L724LR.j]
2001-08-18 lR k109 [Input: L724LR.j]

Spatial Aggregation

Roster Date Author Record
Features within aggregate 2000-12-18 !! f192 (^ pavement), f193 (^ pavement), f224 (^ accumulation), f235 (^ pavement) [Input: A-CUMUL.j]
q-lots within aggregate 2000-12-18 !! q653 [Input: A-CUMUL.j]

Time Sequencing

Roster Date Author Record
Stratum (to which element belongs) 2000-12-18 !! s530AAH [Input: A-CUMUL.j]
2015-05-20 !! s380AAH [Input: ZA520CJC.j]
Phase (to which element belongs) 2000-12-18 !! h4jAAH [Input: A-CUMUL.j]
2015-05-20 !! h4jAAH [Input: ZA520CJC.j]
2015-05-20 !! h5cAAH [Input: ZA520CJC.j]

6. REFERENCE

Analogical Record

Roster Date Author Record
Photo of context (v view)

2002-07-17 lR [Input: -M726-A.j]

2002-07-30 lR [Input: L818LR2.j]
View/drawing of aggregate

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]

2007-08-03 pC [Input: R803PC.j]