We are now in the process of making a transition from hosting our current UI on earth to the Server GIS. We have migrated our Avkat project folder to GIS and are in the process of migrating our 2 Sql Server databases (Avkat and Avkat_MySql). We have run into a snag recently when looking through our project folder. It is currently unknown as to which of the UI code is actually running live. Once we identify the code of our current working version, we will then upload it to our proteus directory on GitHub. GitHub will help us manage our subsequent versions as we begin to manipulate the code. To get Proteus running live on GIS we must change the pointers to our databases. In our current live version the databases live on Geodata. Once we migrate our databases to GIS, we will be able to establish GIS as our full hosting server for the Avkat project. Doing so will help tremendously from an organizational standpoint. We are still waiting on the help of John Wall do direct us on the logistics of pushing proteus live onto GIS.
Category Archives: Setting Up
The last 5 weeks we have encountered numerous setbacks as well as many successes in moving forward.
- We have set up a workspace in the Visualization Lab at the College of Charleston Santee Cooper GIS Lab.
- This workstation currently has two machines running with arcgis 10.0 and numerous other programs
- We have three more machines ready to be imaged after the first two to provide extra work stations
- We have set up a development server called gis.cofc.edu with the programs necessary.
To set up our beta server we had to:
- Successfully identify where all of the databases are stored.
- We are in the process of copying the databases to the beta server for testing purposes.
- Find all of the relevant code for the website and then upload to our github repository for versioning
- We have copied the majority of the data from geodata and earth to our new beta server for testing
Problems we have encountered include:
- We attempted to implement arcgis server 10.1 on our beta server with the assistance of a local charleston called ROK Tech.
- After discussing our options we have decided to revert to the stable version of arcgis server 10.0, the newer version has many problems still to be solved and is not suitable at this time for live production hosting.
- We communicated with other members of the proteus team who had done the initial setup of the current alpha version of the website UI. Due to their busy schedules and their not being on location with us it took time to sort out where all of our data was located.
We will continue to work diligently on the beta server migration. Our next step is to setup a live closed beta of the current website UI that will be hosted on gis.cofc.edu. This will allow us to continue on to upgrading the UI, as we will then be starting with the base version that is the current standard.
We will be using a variety of software for this summer which will build upon previous work for the Avkat Archaeological Project. Prior work has been dominated by the creation of an SQL database coded in MySQL. A front-end was created for this database using PHP for query optimization. This database has stored all tabular and image data for the project, however spatial information has been lacking.
ArcSDE is used to store spatial information. Recently the MySQL database was translated to PostgreSQL which employs pgAdminIII. This allows for better communication between the SQL database and the ArcSDE geodatabase.
Currently, we are working on building data queries which result in tables and views which can then be queried by end users. It is important to note here the difference between the two – tables and views. Tables result in a more static image of the data within the SQL database. This means that as the data is changed within SQL database, the table either stays the same or breaks due to information loss. Views, on the other hand, update their information thereby allowing end-user queries on the most recent version of the data. While it seems that views are more ideal than tables, there are situations where a table could be useful. Such a situation could include when a researcher does not need the most up-to-date dataset.
Future work will include uploading this information to ArcServer and at least one web-mapping application (WMA) will be created. Information is uploaded to ArcServer in order to serve out geospatial data which, in this case, has been joined to tabular data. REST services will then be created via ArcServer REST API. These REST services will then be consumed by the WMA.
It might be useful to provide an example for how this applies more directly to archaeological research. Field research for the Avkat Archaeological Project tied artifact information to an observation point, which can correspond with zero to infinity artifacts. These artifacts have been recorded on paper forms which have been entered into a SQL database which stores data in a tabular format.
Geospatial data will then be tied to the tabular data by using ArcSDE. ArcSDE functions as middleware between the tabular and geospatial data. This means that the spatial observation points can then be tied (i.e. joined) to the tabular data. This is where differing versions can be created. For example, here we can join the observation points to a broad overview of all artifacts found at that point or to specific assemblages such as lithics or pottery. The beauty of this is that when the geospatial data is queried, i.e. through selection, the query retrieves all relevant/joined tabular data. Similarly, when tabular data is queried through the WMA the spatial information can also be referenced (i.e. highlighted). This provides a valuable tool to the analyst wishing not only understand the assemblage quantitatively, but also spatially.
A researcher conducting pottery analysis can observe an anomaly of interest at a given point and select nearby points to see if this anomaly continues into other areas. We additionally seek to provide the ability to download relevant data in both tabular and geospatial formats.
This past week we began working on the Avkat Informatics Project. We planned this development to be more or less linear. However, we discovered that this will not be possible due to a number of obstructions.
Welcome to the Avkat Archaeological Project’s Informatics development blog! This blog will be providing information throughout the summer on the creation of web mapping applications associated with the Avkat Archaeological Project. There are three facets that this project will be focusing on this summer:
- Cleaning data to enhance analysis
- Organizing and enhancing the current ArcSDE geodatabase environment with an eye to long-term data curation
The Avkat web mapping application will eventually serve a variety of purposes including data dissemination, visualization, and analysis initially targeted at the needs of principal investigators of the Avkat Archaeological Project. Further goals include the expansion of the web portal’s functionality to support the needs of the wider academic and lay community and developing the underlying data structure to provide wide applications to a variety of research needs in the social, humanistic, and natural sciences.
Financial support for this digital initiative comes from the Department of History at Princeton University and the Department of Classics and School of Languages, Cultures, and World Affairs at the College of Charleston. Logistical and technical support is provided by the Santee Cooper GIS Laboratory at the College of Charleston.
Meet the Team
Dr. James Newhard – Is Assistant Director of the Avkat Archaeological Project and leads the development of the project’s archaeoinformatics. His research interests include geospatial applications in archaeology, archaeological methodology, and landscape studies. He has conducted fieldwork in Turkey, Greece, Albania, and the United States.
Dr. Norman Levine – Is geospatial director to the Avkat Archaeological Project and Director of the Santee Cooper GIS Laboratory at the College of Charleston. His research interests include natural and environmental hazards, geoarchaeology, and geospatial informatics and visualizations.
John Wall – Is the geospatial developer for the Avkat Archaeological Project. His primary research interests include data visualization and analysis through various geospatial environments and remote sensing technologies. He has conducted research in Turkey, Ireland, and United States.
Kurt Goldstein – Is the database manager for the Avkat Archaeological Project. His primary interests include database integrity, optimization, and versatility.
The Avkat Archaeological Project
The Avkat Archaeological Project is an interdisciplinary, multifaceted regional survey project conducted between 2007 and 2009 in the Republic of Turkey. The project has sought to integrate large, complex datasets of varying types towards an understanding of the regional history of a small section of north central Anatolia.