The main text of the dissertation has given information about the overview of the project. This appendix is aimed at detailing how to recreate the ArcView Project from the data on the CD, and how to run the various models. With this information, and the data provided, it should be possible to re-create each separate phase of the Project independently, or to work through the whole project and recreate the whole thing.
The various models were created to run from, and store data in, a directory c:\00data, so the first step would be to copy the Folder 00Data from the CD to the C Drive.
The key data for the Project is within the folder zProjectData and consists of the shape files 100mGrd; proj1k; proj5k, and projParish. These files contain the raw data which was manipulated to create the various models. Also needed are the Extensions Spatial Analyst, Model Builder, Database Access and Geoprocessing to be loaded.
The Models have combined the Vector Conversion and ADI creation Phases into one model.
To run the Model it first needs to be opened in Model Builder. The Models are stored in the Folder 00Data\ADIData, with each model being stored in the appropriate sub folders. For example the AeMe model lives in the folder 00Data\ADIData\AeMe\AeMeADI, and so on.
Once the model is opened it can be run form Model builder and should create the appropriate data.
Once the ADI has been created it can be saved in the format <ModelName> ADIGrd within the 00Data\ADIData folder, where Model name is AeMe or equivalent.
These created Grids have also been provided to enable the later stages to be re-created without needing to go through the above stage.
The different DCADI's have different methods of creation, but they share some features. The models and data for the supplied data are all stored in the folder 00Data\DCADIData\DCADIV# for the appropriate numbered DCADI. These processes also need the Extensions Spatial Analyst, Model Builder, Database Access and Geoprocessing to be loaded.
To run the first three ADI models, all the ADI Grid themes need to be added as Grid Data Sources to a Project, found in the folder 00Data\ADIData. Once this has been done, for the first three DCADI's it is merely a matter of running the appropriate model to generate the DCADI.
This data is best displayed using the Standard deviation Classification in the Legend Editor Dialog box, as the default display makes it appear as if there areas with no data.
Experimentation has shown that the optimal way to display this layer appears to be using the Equal Interval classification, with the number of classes set to one more than the maximum value. E.g. in the example provided the maximum value is 7, so the Number of classes has been set to 8.
There were some problems with this DCADI, as detailed in the main text. However, a cut down model version 3a is included to show how the process should work, and it is possible to see the errors created if version 3 is run. This data is best displayed using the Standard deviation Classification in the Legend Editor Dialog box.
To produce this DCADI, an additional extension Grid Machine Version 6.53 is needed. This is needed to convert the raster grid into Point themes. The Point themes have been provided and are stored in the folder 00Data\pt. Each of these themes then needs to be exported into an Access database. This was done by exporting the Attribute table of the Shape files as Delimited Text files (also provided in 00Data\Databases\ADITxt).
These files were then imported in an Access database (provided at 00Data\Databases) and linked into a single table (1DCADIV4Original : does not include AeMe data). However, it was noted on re-importing this data into ArcView that the data did not appear as expected, as the area of no data in the top right corner had vanished, and data was missing from the bottom row of the data. It was realised that the fact there was missing data needed to be accounted for. The missing grids were identified (see Gap.txt and Gap Table in database).
The data was then exported into Excel and the correct Gaps placed in the data. This Excel data was re-imported into Access (as table 2DCADIV4Excell ) and then the UaMe theme was added into the data (as table 3DCADIV4PreEx2). This data was added separately as it contained no missing grids.
This table was re-exported to Excel (see 0DCADIV4Export2 ) to allow the creation of the extra fields i.e. DCADIV1; Medieval, DP. (Note: this is probably achievable within Access, but was done in Excel as it is simpler). This data was finally re-imported into Access as Table 0DCADIV4.
This table was exported from Access as Dbase V file called 0DCADIV4.dbf. At this point, a copy of the Vector 100mGrd Shape file was made, and renamed DCADIV4. This file was edited in ArcView to remove all the fields except the ID field. Both these files are provided in 00Data\DCADIData\DCADIV4.
Finally, it was possible to bring the 0DCADIV4.dbf table into ArcView and link it to the Shape File DCADIV4, using the Join Command. To do this the attribute table of the Theme DCADIV4.shp needed to be opened, and the 0DCADIV4.DBF file added to the tables in the project. These could then be joined using the ID field as the linking field.
© Internet Archaeology
URL: http://intarch.ac.uk/journal/issue21/1/downloads2.html
Last updated: Wed April 25 2007