| equals other label | 2001-8-25 | jl | f374 | [Input File: L825jl.j] |
| category | !! | !! | installation | [Input File: !!] |
| definition (typological label) | 2000-7-09 | jl | wall | [Input File: K711jl.j] |
| description (summary) | 2000-7-11 | jl | possible wall, bricky-looking material in semicircle around edge of k27. Apparently the cause of the fissure f321 and f303. However, its purpose and construction are still unknown. It is not a brick wall, although the top layer does look bricky. Instead, it is probably a mud wall, made by layering successive layers of mud brick on top of each other. | [Input File: K711jl.j] |
| best view | 2001-2-26 | jl | V13d1071 | [Input File: M815jl.j] |
| 2001-2-26 | jl | V13d1212 | [Input File: M815jl.j] |
| type of contact: latest events | 2000-7-20 | jl | f336 (accumulation) abuts f326 (wall) | [Input File: K720jl.j] |
| 2000-7-20 | jl | f338 (floor, type a) abuts f326 (wall) | [Input File: K720jl.j] | |
| 2000-7-20 | jl | f344 (accumulation A) abuts f326 (wall) | [Input File: K720jl.j] | |
| 2000-7-22 | jl | f345 (accumulation A) abuts f326 (wall) | [Input File: K722jl.j] | |
| 2000-7-26 | jl | f348 (floor, type a) abuts f326 (wall) | [Input File: K726jl.j] | |
| 2000-8-06 | jl | [Input File: K806jl.j] | ||
| 2000-8-06 | jl | f349 (pavement, type c) abuts f326 (wall) | [Input File: K806jl.j] | |
| type of contact: contemporary events/movable items | 2002-9-15 | ms | q971 (pottery, bones, q-items) sits in f326 (wall) | [Input File: M915jl.j] |
| 2002-9-15 | ms | q981 (pottery, q-items) sits in f326 (wall) | [Input File: M915jl.j] | |
| 2002-9-15 | ms | q973 (pottery, bones) sits in f326 (wall) | [Input File: M915jl.j] | |
| 2002-9-15 | jl | q979 (pottery) sits in f326 (wall) | [Input File: M915jl.j] | |
| 2002-9-15 | ms | q971.1 (lithic artifact) sits in f326 (wall) | [Input File: M915jl.j] | |
| 2002-9-15 | ms | q981.1 (sample) sits in f326 (wall) | [Input File: M915jl.j] | |
| type of contact: earliest events | 2000-7-11 | jl | f326 (wall) abuts f320 (accumulation C) | [Input File: K711jl.j] |
| 2000-7-11 | jl | f326 (wall) abuts f328 (accumulation) | [Input File: K711jl.j] | |
| 2000-7-11 | jl | f326 (wall) abuts f330 (accumulation) | [Input File: K711jl.j] | |
| 2000-7-11 | jl | f326 (wall) abuts f321 (hole) | [Input File: K711jl.j] | |
| 2000-7-11 | jl | f326 (wall) abuts f307 (accumulation) | [Input File: K711jl.j] | |
| 2000-7-11 | jl | f326 (wall) abuts f308 (accumulation) | [Input File: K711jl.j] | |
| 2000-8-06 | jl | f326 (wall) abuts f349 (pavement, type c) | [Input File: K806jl.j] | |
| 2000-8-06 | jl | f326 (wall) covers f352 (stone installation) | [Input File: K806jl.j] |
| evidence | 2001-8-13 | jl | In order to have any stabiliy, the mud ledge must have accumulated against another surface, presumably the accumulation within a36. | [Input File: L813jl.j] |
| assumption | 2001-8-13 | jl | Presumably, the mud ledge increased apace with the ^a within a36. However, there are two possible reconstructions of this event: first, k26 and k27 increased at roughly the same pace, so the ledge was never more than half a meter (or whatever appropriate size) high. In this case, it served to keep to the accumulation within k27 out of k26. Second, k27 continued in use as a well after a36 was constructed, so k26 increased in elevation for a long time as k27 remained lower. In this case, the mud ledge probably served to keep the contents of k26 out of k27. | [Input File: L813jl.j] |
| stratum (to which element belongs) | 2000-7-10 | jl | sB4 | [Input File: K710jl1.j] |
| 2000-7-10 | jl | sB5 | [Input File: K710jl1.j] | |
| 2000-7-10 | jl | sB6 | [Input File: K710jl1.j] | |
| 2000-7-10 | jl | sB7 | [Input File: K710jl1.j] | |
| 2001-9-16 | jl | sC6 | [Input File: L915jl1.j] | |
| 2001-9-16 | jl | sC7 | [Input File: L915jl1.j] | |
| 2001-9-16 | jl | sC8 | [Input File: L915jl1.j] | |
| phase (to which element belongs) | 2000-7-10 | jl | [Input File: K710jl1.j] |
| view/drawing of features |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||