Implementation of a GIS: Cemetery Application



[pic]

World Printing Production

Team Members: Sean Whitehead, Project Manager

William Shamburg, Asst. Project Manager

Regan Presley, GIS Analyst

Erik Olden, GIS Analyst

Chris Skeete, Webmaster

Analysis of the San Marcos Cemetery for future expansion and mapping

Prepared for:

The Friends of San Marcos Cemetery

Prepared by:

World Printing Production

December 2, 2007

Table of Contents

[pic]

Introduction

Abstract ………………………………………………………………….4

Problem Statement..….…………………………………………………....4

Literature Review

Case 1……………..……………………………………………………….6

Case 2 …….……………………………………………………………...7

Case 3……..……………………………………………………………….7

Methods

Integrated Cemetery Mapping App………..……………………………...8

Software …………….…………………………………………..8

Implementation……………………………………………………8

Website design…………………...………………………………17

Up keep…………………..………………………………………18

Spatial Analysis ………..………………………………………………..18

Data…………………………………………………………...…………………22

Flow Chart………………………………………………………..….…..24

Discussion……………...……………………………………………………......25

Results………………………………………………………………….………..28

Conclusion ...........................................................................................................31

References ……..……………………………………………….………32

Appendix I

Metadata……………..………………………………………………….33

Appendix II

Contributions……………………………………………………………48

Introduction:

Abstract:

The City of San Marcos Cemetery is an important part of the rich heritage of San Marcos. The cemetery dates back to the year 1846 when the first person was buried in the cemetery. This cemetery, much like many others, holds valuable information and many stories from the past. Cemeteries are a vital facet of our heritage, they must be preserved and kept in the best of order or they will likely perish. World Printing Productions has created order for the City of San Marcos Cemetery with our cemetery preservation project. The cemetery preservation project is a movement initiated by WPP to collect and organize data to create a GIS for the Friends of San Marcos Cemetery Committee. With a GIS for the cemetery the administrators of the cemetery can better grasp the capacity of the cemetery. A GIS for the cemetery will also provide the community with much greater access to the grounds and its rich history.

Problem Statement:

Based on the vastness of the cemetery and the time that was allotted to our team to have a useful finished product, we have decided to focus all of our time and resources on one specific section of the cemetery. We chose this route because if we tried to analyze the entire cemetery in the time given we could not produce a finished product, but more of a broad analysis with several loose ends. We also decided to focus on one area because we could then create a “formula” that our predecessors can apply to the rest of the cemetery in order to complete the preservation project for the San Marcos cemetery. The area that we have chosen is the entire Rose Lawn addition, which included sections A, B, and C. The reason we chose this area is because it is an area that is roughly %80 full, it has several easements not yet filled, and it is of adequate size to know that our methods could be applied to any other area in the cemetery.

The cemetery has two major problems that our GIS will help to solve; the first of these hurdles is a very time sensitive one that cannot be solved only better understood. The cemetery is filling at an alarming rate and having a better understanding of not only when it will most likely fill but also ways to conserve space are very important to the future of the cemetery. After surveying our study area and researching a variety of other cemeteries, we have come to a spectrum of possible scenarios that could buy the San Marcos Cemetery very precious time before hitting maximum capacity. In our report we have given suggestions on how to better preserve the space available in the cemetery, also we have provided an idea of how much space is still available under various scenarios. The second problem that the cemetery is facing is general disorganization. Many valuable staff hours have been wasted helping people find their loved ones in the cemetery. WPP has created an Integrated Cemetery Mapping Application (I.C.M.A.) for the city of San Marcos which allows people to locate the exact location of an internment from anywhere around the world via the internet. The I.C.M.A. will allow a user to type an interments name into a familiar search based interface and come up with a location code that can be used on a larger kiosk map at the entrance of the cemetery. The I.C.M.A. will also link the person searching for an interment to a map of the cemetery, which will then bring said person to the interments exact geographical location in the cemetery. This will allow people to locate interments within the cemetery with very little or no help from cemetery staff. The I.C.M.A. will also allow genealogists from anywhere around the world to perform their own research without leaving there home.

Literature review

Case 1.

Cemetery preservation and administration projects are not only very common but also a very lucrative business. There is already a plethora of cemetery administration and mapping software available to private and state cemeteries. A very popular application is Cemetery Information Management System or CIMS for short. The full CIMS version has two parts one for accounting and finances and the other portion is a mapping application very similar to what WPP has accomplished. The company that produced CIMS is called Ramaker inc., which is an engineering firm based out of Wisconsin. There are several different applications of the software; the three that pertain directly to our research is the CIMS application, the eCIMS application, and the CIMS kiosk application. The eCIMS application allows users to search roads and plots from the internet. Visually and analytically, eCIMS is very similar to our I.C.M.A. The CIMS kiosk is a very interesting application that is loaded into a touch screen kiosk which can be provided by Ramaker inc. and allows customers to locate inters while on the cemetery grounds.

Case 2.

As far as GIS is concerned Boulder, Colorado has usually been on top of their game. For years they have had a GIS enabled website using ArcIMS that gave citizens access to information on zoning, flood control, and historic preservation. It just seemed obvious that they should have their historical cemetery information on a GIS as well. In 2001, the Columbia Cemetery Preservation project manager approached a GIS team to figure out if a web based GIS could be created for the cemetery. The city had large amounts of data already compiled pertaining to the cemetery, so it was just a problem of organizing it and putting it in a GIS. The Columbia cemetery in Boulder, much like the cemetery in San Marcos is owned by the city of Boulder and managed by the Parks and Recreation Department. Each grave has been photographed and attached to the interments information so every time you locate someone you can not only see where they are in the cemetery, you can also look at a picture of their grave. Ultimately WPP hopes to see the San Marcos cemeteries finished product to be similar to the project in Boulder.

Case 3.

Some geographers from the University of West Florida, mostly professors, have been slowly building a GIS for the St. Michaels cemetery in Pensacola, Florida since 2003. It is an ArcIMS based application with layers from tombs and burials to vegetation and roads. The St. Michaels cemetery has had a problem with running into graves that have not been cataloged, much like the San Marcos cemetery. Sometime next year the St. Michaels cemetery will have information added to the website from G.P.R. data that they will collect in 2007.

Methods:

The Integrated Cemetery Mapping Application

Before we begin, please understand that there are different ways to setup, implement and maintain the Integrated Cemetery Mapping Application (I.C.M.A.). We will give you the way we decided to setup the I.C.M.A. This way is not the most efficient way to setup the website. This is just one way of creating the I.C.M.A. We recommend that the person(s) who will continue to maintain the I.C.M.A. is someone familiar with website design and database management.

Software

The instructions we use will assume that you are using Microsoft Office 2007. We also used MySQL to store the names and locations of the database. The MySQL database requires to be set up on a web server that has a MYSQL component turned on. We also made sure that a “PHP to MySQL connector” is used to ensure that the PHP could communicate with your MySQL database. You will also need a software package that will allow you to manipulate the database. We used Navicat 8.0 for MySQL to manipulate the database. Adobe Dreamweaver MX is the software package that we used to design the website. Dreamweaver can be used to connect to the web server through an FTP connection. If you do not have a website design program, then you will need an FTP program to place the web files on the web server.

Implementation

The San Marcos Cemetery Burial Report can be found as excel spreadsheet. The actual data will be exported from the Pontem Cemetery Management Software that the San Marco City Finance Department uses to produce the San Marcos Burial Report. The data which is represented in Figure 1 will be unclean and unusable in its current format. We start cleaning the data by taking the location field of the original data and using the “Text to Columns” command which is found under the data tab to separate the location into a unique code that could be used to link the names of the database to the location plots of the cemetery.

[pic]

Figure 1. Original San Marcos Burial Report in Excel Format

After we separate the location field into the five different columns we remove the column that contains “San Marcos” because it is not needed. We then label the different columns that we separated by code name. The first column is labeled as the addition code. The second column is labeled as the section code. The third column is labeled as the block code and the label as the lot code. The excel spreadsheet is too big to load into a database. We sort by the addition and copy and paste each of the different additions into separate excel spreadsheets. We name the spreadsheets by the name of the addition. We take the addition column and using the cell format command we will customize the column so that it will have the “0#” format. We can set this up by highlighting the column and right clicking on the column heading and choosing “cell format…”. We then click on the word “custom” on right side of the window. In the box labeled “type:”, we type 0# in the field. We repeat the same procedure for the lot and block column except we type 00# for both the lot and the block column. We then use the formula =XX&XX&XX where XX represents the cell location for each of the four codes. An example of this is A3. This means that A column and the 3 row. This formula is placed in the cell following the last code column. This will combine the four codes into one code which can be filled down throughout the excel spreadsheet. This code is the code that will combine the different locations of the cemetery. We label this code LocationID. We add the a veteran column that has ‘No’ copied all the way down to speed up the process for later steps in the I.C.M.A..

The name column is also separated using the text to column command from earlier to separate the name into a first and last. Figure 2 shows the Rose lawn addition as a clean excel spreadsheet that can be loaded into the database.

[pic]

Figure 2. Rose lawn excel spreadsheet

The next step is assuming that you have turned on the web server and loaded the MySQL component of the webserver. We start up the Navicat 8.0 and click on the connection button. We then set the connection properties for server where the database will reside. Figure 3 shows the Navicat window when you open the application. Figure 4 shows the connection properties for connecting to the sever.

|[pic] |[pic] |

|Figure 3. Navicat Window |Figure 4. Connection Properties Window |

After verifying the connection, we create the different tables. There will be two tables. One table is the Interment table which holds the names of the deceased and the location table that holds the locations of plots of the cemetery. The fields we add are the IntermentID, LastName, FirstName, BirthDate, DeathDate, Veteran, Branch, WarEra and LocationID. The IntermentID field will be set as the primary key for the Interment table. This will be a private field that will contain a unique key that will auto increment and help move our database to normalization. The IntermentID field will be the only integer type field. The other fields are data that we will add later and they will all be text. The LocationID will be Foreign Key from our Location table. We will not allow a null value for this field to make sure that there is no one in the database that is not associated with a location in the cemetery. Figure 5 shows the table design window for the Interment table with all the fields listed.

[pic]

Figure5. Interment Table Design

The Location table will be set up the same way. The fields used in the Location table will be LocationID, Addition, Section, Lot, Block, LocationLink. The LocationID field will be the primary key for this table. All other fields will be data that we will add later. Figure 6 shows the design mode for the Location table. All the fields in the Location Table will be text type. We will come back to the Location table.

[pic]

Figure6. Location Table Design

We now will take the addition excel spreadsheet and import it into the database. After closing the design mode of any open tables we will double click on the Interment table and click on Import Wizard. Figure 7 shows the Import Wizard Window with the Excel file chosen. We follow the steps to load the excel spreadsheet into the database. We make sure that the fields in the spreadsheet match the fields in the database. If they do not match, then you will get errors.

[pic]

Figure7. Import Wizard Window

After we load the data into the database, we then can begin the verification process of the interments table. This process includes going to the cemetery and verifying that the names in the database match the names on the ground. We use the scanned image of the survey map along with names in the database to verify the names. We also add the birthdates and the death dates to the database. We also change the veteran status from ‘No’ to ‘Yes’ if it is verified along with adding the branch and war era to the database. This will complete the interments data for the database.

We now will create a excel spreadsheet that will contain all the locations of the cemetery. We use a excel spreadsheet because it is easy to copy repeating data throughout the section. We made three different excel spreadsheets for each section of the Rose lawn Addition. This is not necessary as long as the excel file does not get to large. Navicat will not import large excel files. The fields in the excel spreadsheet are the same fields in the Location Table of the database. The LocationID will be coded the same as the Interment table. The LocationID is specified as a two character addition, section, a three character block and three character lot, i.e. 03A003008.

The scanned maps are used to make sure every lot in that section is added to the database. The Addition field will be the name of the addition. The Block and Lot field will be the corresponding number. The LocationLink will be the web address for the html file of the actual lot in the cemetery. This will be a map generated in ArcMap that is exported as a JPEG file and placed on an html document. We will talk more about setting up the html document in future steps. It is best to keep a standard that can be copied across the different sections. Figure 8 shows a excel spreadsheet of the Rose lawn locations in Section A.

[pic]

Figure 8. Rose lawn Section A Locations

Once we get the excel spreadsheet of the locations we will import it the same way we imported the interments excel spreadsheet into the MySQL database using Navicat. Figure 10 shows the Location table with all the data loaded.

[pic]

Figure 10. Location Table for MySQL

Website Design

The website can be setup anyway that you wish. We created three PHP files for the actual search. The first PHP file is called db_login.php which will contain the login information for the MySQL database. The second PHP file is the actual query function. It is called db_search.php. When someone types something in the search box, that information is passed to this function. The final PHP file is the actual search box. This page is what the public sees, so we would recommend using a web design program to improve the look of the website. After we created the map of the location and exported it to a JPEG file. We place it in an html file. We then use a Cascade Style Sheet to create a box that can be layered on top of the picture of the map. This box is used to highlight the lot that will be searched. This html file is then saved as the name found in the LocationLink of that specified location. The box is then moved to a new lot and the html is saved as another name that matches that location in the database. This process is repeated for every location.

Maintain and Upkeep

The database now can be accessed anytime to insert more interments at any time. The locations should change very little but more locations can be added the same way. Different PHP files that contain a particular query for what you are looking for can be added.

Spatial Analysis Of Remaining Plots And Potential Space Saving Scenarios

Visualization through Arc Map will be used to determine the amount of remaining lots in Rose lawn A, B and, C. The three most common segments of easements that prevail throughout out Rose lawn are 15’, 13’ and 4’. Traditionally burial plots have been positioned into blocks of four and eight. The larger easements were originally surveyed at 15’ and 13’, but unnecessary concrete curbs that surround the blocks have shrunk the easements considerably. This misuse of space has decreased the easements as much as 3’ in some segments. In order to determine the extent of usable easement space, measure from the edge of the block’s concrete curb across the large easement to the concrete edge of the adjacent block. Once this has been performed for every set of adjacent blocks in an easement, the threshold for potential plots can then be determined. It is important that the smaller 4’ easement be maintained at all times for service and maintenance use.

In the first scenario, the remaining cemetery capacity was determined by using traditional 5’ x 10’ country burial plots. Blocks of plots were placed in the large easements, following the original pattern. This scenario will allow for an additional 258 plots to be used. (see figure 1)

[pic]

Figure 1

The next scenario just as before, uses 5’ x 10’ country burial plots and will follow the same traditional burial pattern using easements. Although in this scenario we are recommending that sections of Oak Lawn and Heavenly Hills be removed as non-essential roads, to allow for additional burial space. Removal of these unnecessary roads will allow for an additional 322 plots.(see figure 2)

[pic]

Figure 2

The final and most space efficient set of recommendations uses 4’ by 9’ burial plots along with the fore mentioned road removal and easement use plans. The orientations of the blocks are rotated to sit perpendicular to the existing plot blocks. This scenario will yield an additional 422 plots.(see figure3)[pic]

Figure 3

In order to maximize on potentially usable easement space, a few randomly placed unnecessary sidewalks must be removed. A prime example of this exists in Rose lawn A. These sidewalks surround blocks of plots, using the entire easement. When making field observations the group encountered a family who had a loved one in a block that is surrounded by sidewalks. We asked them what their opinion of the sidewalk is, and they promptly replied that is a waste of space. Taking the family’s sentiments into consideration, we have determined that it would be wise to remove these unnecessary sidewalks.

Data

There are several GIS datasets that had to be either acquired (secondary data) or created (primary data) for this project. Each set of data in GIS is called a data layer and is displayed in a map that is included with our final deliverables. All data used for this project should be considered “best available” data. The list below shows the different data layers used through the duration of this project.

• The first layers that were obtained for initial project review and project scoping are considered secondary. These data layers were obtained from the Capital Area Council of Governments (CAPCOG). This organization distributes GIS data to both public and private organizations for use on any type of project needing GIS. The data layers acquired from CAPCOG are as followed:

o Streets centerline shapefile covering Hays County: this file shows the location of all streets in Hays County and contains data such as street name.

o Ariel Images of the study area were obtained in USGS Quarter Quadrangle sections so that we could have pictures of the cemetery taken at 2 foot resolution from a bird’s eye view.

• The next data layer to be created was a street system for the cemetery since streets on the grounds were never mapped or registered with the county. This data was created by using the Ariel Images and is therefore considered primary data. Street names were also entered into the database of this data layer and displayed on all project maps.

• Possibly the most important spatial data acquired was the old survey maps of each addition, section, block, and plot within the cemetery. These maps were scanned in to create digital copies that will be preserved forever. Once digital copies were created we were able to import these images into the GIS software to place to an actual location on Earth. The images were overlayed onto a spatial reference system by the use of the cemetery streets. These images enabled us to create the most important primary data of the project.

• After speaking with many City government departments, we were able to acquire a digital copy of the burial report from the City of San Marcos finance department. This database is in Excel Spreadsheet format. This file helped us so that we would not have to do manual data entry and type in interment’s names and other data located in this burial report.

• Using the georeferenced survey maps of the different cemetery sections, we were able to digitize polygon shapefiles of each lot in the Rose lawn addition. This primary data became the framework of the project because this shapefile is what the digital database of interments from the City is joined to. This file contains attribute data that shows the interment’s name, birth and death date, and location in the Rose lawn addition.

• We then created a shapefile of outlines of other sections and additions within the cemetery. We created this primary data using the survey maps and a hand drawn map acquired from Pennington Funeral Home Director, Jonathon Snell. This data was used to create the overall maps of the cemetery.

All data will be provided on a CD at the completion of this project.

Flow Chart

[pic]

Discussion:

There are a lot of problems, theories, or just interesting questions that we came across while doing our study that we would like to discuss in this portion of our report. One of the big problems that the cemetery has come upon multiple times is running into old burials that were never cataloged, many of them probably stem from the cemeteries earlier years. In the 1800’s the city of San Marcos did not have a system for cataloging the interments in the cemetery. Our studies have shown that many cities run into a similar problem, because when the city first starts its founders probably never imagine that there town will ever grow to its potential. I believe that this same scenario happened in San Marcos. Poor planning like this makes for many problems in the future. There have been several situations where a family has purchased an entire cemetery block and realized once they start to dig that there are already people under their block that had just not been cataloged. This poses an immense problem for the cemeteries administrators because they cannot just dig up the people that are there, but they still have to honor the purchase of the current owners. Our answer to this problem is G.P.R., Ground Penetrating Radar. There is a company called Geo Model Inc. that has realized that this is a major dilemma in cemeteries, so they have equipped a small trailer that can be pulled by a lawn mower or tractor with a G.P.R. and now for more precise measurements GeoModel has created a version that is smaller and more precise that can be pulled by a person (see figure 1). The G.P.R. is a device that shoots radar signals into the ground which reflect back to the G.P.R. unit at different frequencies depending on what they hit.

[pic]

Figure1. G.P.R. unit

The frequency action produces images on a screen essentially showing whether there is a body under the ground or not (See figure 2). [pic][pic]

Figure 2. Image of underground burials

If the San Marcos cemetery employed Geo Model Inc.’s services for the cemetery they could finally figure out for sure whether un-cataloged bodies are under suspected areas in the cemetery or not.

Another problem that the San Marcos cemetery has run into is people putting large memorials on the out skirts of easements that have not been completely filled in yet. This is a problem because machinery used to dig the burials can no longer access the center of the easement to dig, this leaves possible areas for burial useless because machinery cannot access them. For this reason WPP suggests that a cemetery preservation policy be implemented which should contain rules that all burials must follow in order to ensure maximum efficiency of space.

Other options for saving space include using mausoleums. Mausoleums are above ground burials, the cemetery has one already but it is relatively small. The main reason for using a mausoleum in the San Marcos cemetery is because a significant portion of the property is on top of a large shallow layer of limestone that would be far too costly to dig into. A lot of the property is useless for sub terrain burials, so the answer is a Mausoleum. It would consist of several large concrete rooms that contain 20 or more interments stacked on top of one another, which conserves even more space. There is already one mausoleum on the grounds, but its size in comparison to the rest of the cemetery is insignificant. The terrain at the front of the property needs to be taken advantage of and a mausoleum is the only option because of the sub terrain.

The final item we would like to discuss is the future for our project; WPP has got the ball rolling on what could be a monumental preservation project for the San Marcos cemetery. The cemeteries inefficiency has gone on far too long and it is now time to take what we have started and keep it going. As I wrote about in the literature review portion of our report, many other cities similar to San Marcos have started there preservation project because they have realized the importance of their communities cemetery. WPP would really like to see its work be implemented and expanded upon. As our community grows rapidly the task of preserving and organizing our precious city cemetery becomes exponentially difficult.

Results

After devising methods to accurately measure area, both in use as well as available space WPP has come to several conclusions about the available area in the cemetery. The two most plausible methods of adding interments while saving space is to remove roads within the Rose Lawn addition and change the remaining plot sizes. At first, road removal was not a likely option, as there was fear that access by maintenance vehicles would be limited. After surveying the area we came to the realization that we could remove the two roads within Rose Lawn and keep the two outside roads essentially making Rose Lawn one large section with plenty of space for any kind of maintenance vehicle. The I.C.M.A. would have to re worked because all of the block numbers would have to change, but ultimately the cemetery with the roads cut out would free up 322 possible plots at maximum capacity, which is 82 more than its maximum capacity with the roads. At a projected average of 80 burials a year that saves the cemetery an extra year by applying our “formula” to Rose Lawn alone which is 2.75 acres of the approximate 45 acres that make up the entire cemetery. With the roads Oak Lawn and Heavenly Hills removed service vehicles will still have adequate space to move with relative freedom throughout the Rose Lawn grounds. Along with the road removals we have also created a shape file which shows a few sidewalks within the cemetery that would be beneficial to remove as well.

There are several different plot sizes that a cemetery can use for its interments burial. A “country burial” which is what the San Marcos cemetery uses is a 5’x10’ burial plot. This is commonly used in rural areas where space is not really a problem based on the area’s population, hints the name “country burial”. The other burial plot size is seen more in large city cemeteries where there is a large population and the cemetery is more concerned with conserving area, these plot sizes are 4’x9’. This leads to the next measure that we propose the cemetery take in order to save space. We propose that the remanding interments use a 4’x9’ plot size. This combined with the road elimination would potentially free up 422 possible plots at maximum capacity, which is 182 more plots then if the cemetery continued on its current path with the Oak Lawn and Heavenly Hill roads still intact and the 5x10 burial plot size. The number of possible plots refers to the number of plots that are available for purchase. This is important to know because many people will buy an entire block for their family whether they are deceased or not. This creates multiple plots that have been purchased but there are no interments in them yet. Many customers are confused by this because there are several seemingly open areas of land that look like they could be used but are in fact already purchased. Several other possibilities that may help in the GIS include a vegetation layer, as well as a soil layer so that the administrators of the cemetery will know what they are digging into. A soil layer would also help figure out where the lime stone slab under the front portion of the property starts and stops, this would help decide where to place a mausoleum. As part of the final deliverable that WPP will present to the City of San Marcos, we have digitally scanned the paper maps that the cemetery previously used to locate interments in the cemetery. The paper maps that had been used since the 80’s are on the verge of extinction and we deemed it imperative that they be digitally preserved immediately. Without the two main copies of the maps our work would almost be useless, as the maps are vital to digitizing the plots in the rest of the cemetery. Several copies of the scanned maps will be given to the administrators of the cemetery as a part of our final deliverables.

Conclusion:

The Friends of San Marcos Cemetery came to WPP with two major problems that needed attention. The first problem was one of organization, the cemetery had thousands of interns and no real way for interment loved ones to locate them. This problem was a serious one that became very frustrating to the administrators of the cemetery. WPP has created an Integrated Cemetery Mapping Application in order to combat this problem. The I.C.M.A. allows users to locate interments within the cemetery, from anywhere around the world via the internet. The second problem WPP faced was a very difficult one. The cemetery is rapidly running out of space and the administrators of the cemetery need to figure how to save space in the cemetery as well as what kind of space they have available. WPP has surveyed and calculated the cemetery grounds and created a GIS that shows how much space is left in our study area under various space saving situations. Our Preservation Project has been focused on one specific study area within the cemetery due to time constraints. In our final deliverables we have organized our data and methods into a “formula” which cemetery administrators can apply to the rest of the cemetery.

References

"Cemetery Information Managment System." CIMS Cemetery Software. 20 Nov. 2007. Ramaker & Associates, Inc. 28 Nov. 2007 .

|T|

|o|

|p|

|o|

|f|

|F|

|o|

|r|

|m|

|B|

|o|

|t|

|t|

|o|

|m|

|o|

|f|

|F|

|o|

|r|

|m|

Hamilton, Stu. "St. Michals Cemetery Project." University of West Florida GIS. 1 Dec. 2007. University of West Florida. 1 Dec. 2007 .

Locating Graves." GeoModel, Inc. 8 May-June 2006. GeoModel, Inc. 2 Dec. 2007 .

Noble, Rob. "PlotFinder: a Custom GIS for the Cemetery Industry." ESRI. 2007. ESRI. 2 Dec. 2007 .

Appendix I: Metadata

5 by 10 Burial Capacity

Metadata:

_ Identification_Information

_ Data_Quality_Information

_ Spatial_Data_Organization_Information

_ Spatial_Reference_Information

_ Entity_and_Attribute_Information

_ Distribution_Information

_ Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: World Printing Productions (Texas State University)

Publication_Date: 12/5/05

Title:

5 by 10 Burial Capacity

Geospatial_Data_Presentation_Form: vector digital data

Online_Linkage: \\Geoserve\Data\G4427YL\GroupThree\Analysis\east_west_cap.shp

Description:

Abstract:

5 by 10 burial plots, current standard size of San Marcos Cemetery plots.

Purpose:

5 by 10 polygons used to simulate burial capacity, if cemetery continues to use this

format, with suggested road removals

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 12/05/07

Currentness_Reference:

publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -97.958952

East_Bounding_Coordinate: -97.957565

North_Bounding_Coordinate: 29.889189

South_Bounding_Coordinate: 29.887900

Keywords:

Theme:

Access_Constraints: none

Use_Constraints:

none

Page 1 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata17.htm 12/3/2007

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: San Marcos Cemetery Association

Contact_Person: Shannon Fitzpatrick

Contact_Position: President

Contact_Voice_Telephone: 512-667-4207

Contact_Electronic_Mail_Address: sf15@txstate.edu

Security_Information:

Security_Classification: Unclassified

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog

9.2.2.1350

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

Data is to be used for visualization purposes only

Lineage:

Process_Step:

Process_Description:

Copy and paste polygons into easements and over the roads that are to be

removed while maintaining service easements.

Process_Date: 11/31/01

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: G-polygon

Point_and_Vector_Object_Count: 369

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Lambert Conformal Conic

Lambert_Conformal_Conic:

Standard_Parallel: 28.383333

Standard_Parallel: 30.283333

Longitude_of_Central_Meridian: -99.000000

Latitude_of_Projection_Origin: 27.833333

Page 2 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata17.htm 12/3/2007

False_Easting: 1968500.000000

False_Northing: 13123333.333333

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000000

Ordinate_Resolution: 0.000000

Planar_Distance_Units: survey feet

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: 5 x 10 burial plot

Entity_Type_Definition:

5 x 10 polygon burial plot

Attribute:

Attribute_Label: FID

Attribute_Definition:

Internal feature number.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition:

Feature geometry.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Coordinates defining the features.

Attribute:

Attribute_Label: SHAPE_Leng

Attribute:

Attribute_Label: SHAPE_Area

Attribute_Definition:

Area of feature in internal units squared.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Page 3 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata17.htm 12/3/2007

Positive real numbers that are automatically generated.

Distribution_Information:

Resource_Description: Downloadable Data

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Transfer_Size: 0.048

Metadata_Reference_Information:

Metadata_Date: 20071203

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: World Printing Production

Contact_Person: Regan Presley

Contact_Position: analyst

Contact_Address:

Address_Type: REQUIRED: The mailing and/or physical address for the

organization or individual.

City: REQUIRED: The city of the address.

State_or_Province: REQUIRED: The state or province of the address.

Postal_Code: REQUIRED: The ZIP or other postal code of the address.

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Extensions:

Online_Linkage:

Profile_Name: ESRI Metadata Profile

Page 4 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata17.htm 12/3/2007

4 x 9 capacity

Metadata:

_ Identification_Information

_ Data_Quality_Information

_ Spatial_Data_Organization_Information

_ Spatial_Reference_Information

_ Entity_and_Attribute_Information

_ Distribution_Information

_ Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: REQUIRED: The name of an organization or individual that developed

the data set.

Publication_Date: REQUIRED: The date when the data set is published or otherwise

made available for release.

Title:

4 x 9 capacity

Geospatial_Data_Presentation_Form: vector digital data

Online_Linkage: \\Geoserve\Data\G4427YL\GroupThree\Analysis\four_nine_cap.shp

Description:

Abstract:

4 x 9 burial plots, suggested size of new burial plot format.

Purpose:

4 x 9 polygons used to simulate burial capacity, with suggested road removals

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 12/28/07

Currentness_Reference:

publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -97.958950

East_Bounding_Coordinate: -97.957492

North_Bounding_Coordinate: 29.889155

South_Bounding_Coordinate: 29.887900

Keywords:

Theme:

Access_Constraints: none

Use_Constraints:

Page 1 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata18.htm 12/3/2007

none

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: San Marcos Cemetery Comission

Contact_Person: Shannon Fitzpatrick

Contact_Position: President

Contact_Voice_Telephone: 512-667-4207

Contact_Electronic_Mail_Address: sf15@txstate.edu

Security_Information:

Security_Classification: Unclassified

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog

9.2.2.1350

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

Data is to be used for visualization purposes only

Lineage:

Process_Step:

Process_Description:

Copy and paste polygons into easements and over the roads that are to be

removed while maintaining service easements.

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: G-polygon

Point_and_Vector_Object_Count: 860

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Lambert Conformal Conic

Lambert_Conformal_Conic:

Standard_Parallel: 28.383333

Standard_Parallel: 30.283333

Longitude_of_Central_Meridian: -99.000000

Latitude_of_Projection_Origin: 27.833333

Page 2 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata18.htm 12/3/2007

False_Easting: 1968500.000000

False_Northing: 13123333.333333

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000000

Ordinate_Resolution: 0.000000

Planar_Distance_Units: survey feet

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: 4 x 9 polygon

Entity_Type_Definition:

4 x 9 polygon burial plot

Attribute:

Attribute_Label: FID

Attribute_Definition:

Internal feature number.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition:

Feature geometry.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Coordinates defining the features.

Attribute:

Attribute_Label: SHAPE_Leng

Attribute:

Attribute_Label: SHAPE_Area

Attribute_Definition:

Area of feature in internal units squared.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Page 3 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata18.htm 12/3/2007

Positive real numbers that are automatically generated.

Distribution_Information:

Resource_Description: Downloadable Data

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Transfer_Size: 0.112

Metadata_Reference_Information:

Metadata_Date: 20071203

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: World Printing Productions (Texas State University

Contact_Person: Regan Presley

Contact_Position: Analyst

Contact_Address:

Address_Type: REQUIRED: The mailing and/or physical address for the

organization or individual.

City: REQUIRED: The city of the address.

State_or_Province: REQUIRED: The state or province of the address.

Postal_Code: REQUIRED: The ZIP or other postal code of the address.

Contact_Voice_Telephone: .

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Extensions:

Online_Linkage:

Profile_Name: ESRI Metadata Profile

Page 4 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata18.htm 12/3/2007

Sidewalk Removals

Metadata:

_ Identification_Information

_ Data_Quality_Information

_ Spatial_Data_Organization_Information

_ Spatial_Reference_Information

_ Entity_and_Attribute_Information

_ Distribution_Information

_ Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: World Printing Productions (Texas State University)

Publication_Date: 11/28/07

Title:

sidewalk removals

Geospatial_Data_Presentation_Form: vector digital data

Online_Linkage: \\Geoserve\Data\G4427YL\GroupThree\Analysis\removals.shp

Description:

Abstract:

Easement removals

Purpose:

Proposed sidewalk removals

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 11/28/07

Currentness_Reference:

publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -97.957823

East_Bounding_Coordinate: -97.957662

North_Bounding_Coordinate: 29.888775

South_Bounding_Coordinate: 29.888584

Keywords:

Theme:

Access_Constraints: none

Use_Constraints:

none

Point_of_Contact:

Page 1 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata20.htm 12/3/2007

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: San Marcos Cemetery Association

Contact_Person: Shannon Fitzpatrick

Contact_Position: President

Contact_Voice_Telephone: 512-667-4207

Contact_Electronic_Mail_Address: sf15@txstate.edu

Security_Information:

Security_Classification: Unclassified

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog

9.2.2.1350

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

For visualization purposes only

Lineage:

Process_Step:

Process_Description:

Identified potential sidewalks that could be removed to allow for burials in

easement. Draw polygon in size and shape of sidewalk for visualization

purposes.

Process_Date: 12/28/07

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: G-polygon

Point_and_Vector_Object_Count: 3

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Lambert Conformal Conic

Lambert_Conformal_Conic:

Standard_Parallel: 28.383333

Standard_Parallel: 30.283333

Longitude_of_Central_Meridian: -99.000000

Latitude_of_Projection_Origin: 27.833333

Page 2 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata20.htm 12/3/2007

False_Easting: 1968500.000000

False_Northing: 13123333.333333

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000000

Ordinate_Resolution: 0.000000

Planar_Distance_Units: survey feet

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1983

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: sidewalk removals

Entity_Type_Definition:

sidewalks to be removed

Attribute:

Attribute_Label: FID

Attribute_Definition:

Internal feature number.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition:

Feature geometry.

Attribute_Definition_Source:

ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Coordinates defining the features.

Attribute:

Attribute_Label: Id

Overview_Description:

Distribution_Information:

Resource_Description: Downloadable Data

Standard_Order_Process:

Page 3 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata20.htm 12/3/2007

Digital_Form:

Digital_Transfer_Information:

Transfer_Size: 0.000

Metadata_Reference_Information:

Metadata_Date: 20071203

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: World Printing Productions (Texas State University)

Contact_Person: Regan Presley

Contact_Position: Analyst

Contact_Address:

Address_Type: REQUIRED: The mailing and/or physical address for the

organization or individual.

City: REQUIRED: The city of the address.

State_or_Province: REQUIRED: The state or province of the address.

Postal_Code: REQUIRED: The ZIP or other postal code of the address.

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Security_Information:

Metadata_Security_Classification: Unclassified

Metadata_Extensions:

Online_Linkage:

Profile_Name: ESRI Metadata Profile

Page 4 of 4

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata20.htm 12/3/2007

sanmarcosnorthsw.sid

Metadata:

_ Identification_Information

_ Spatial_Data_Organization_Information

_ Spatial_Reference_Information

_ Distribution_Information

_ Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: CAPCOG

Publication_Date: 2006

Title:

sanmarcosnorthsw.sid

Geospatial_Data_Presentation_Form: raster digital data

Online_Linkage:

W:\G4427YL\GroupThree\data\CAPCOG\Domains\capcogorg\wwwroot\Information_Clearinghouse\data\WEBimagery_06

\sanmarcosnorthsw.sid

Description:

Abstract:

San Marcos North SW Quater Quadrangle Orthophotography

Purpose:

Used for visualization and mapping techniques

Supplemental_Information:

Used by WPP (Texas State University)

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds

to the ground.

Currentness_Reference:

REQUIRED: The basis on which the time period of content information is determined.

Status:

Progress: Complete

Maintenance_and_Update_Frequency: None planned

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: REQUIRED: Western-most coordinate of the limit of coverage expressed in longitude.

East_Bounding_Coordinate: REQUIRED: Eastern-most coordinate of the limit of coverage expressed in longitude.

North_Bounding_Coordinate: REQUIRED: Northern-most coordinate of the limit of coverage expressed in latitude.

South_Bounding_Coordinate: REQUIRED: Southern-most coordinate of the limit of coverage expressed in latitude.

Keywords:

Theme:

Theme_Keyword_Thesaurus: REQUIRED: Reference to a formally registered thesaurus or a similar authoritative source of

theme keywords.

Theme_Keyword: REQUIRED: Common-use word or phrase used to describe the subject of the data set.

Access_Constraints: none

Use_Constraints:

none

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Raster

Raster_Object_Information:

Raster_Object_Type: Pixel

Row_Count: 11574

Column_Count: 10141

Vertical_Count: 1

Page 1 of 2

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata24.htm 12/3/2007

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: row and column

Coordinate_Representation:

Abscissa_Resolution: 2.000000

Ordinate_Resolution: 2.000000

Distribution_Information:

Resource_Description: Downloadable Data

Metadata_Reference_Information:

Metadata_Date: 20071203

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: REQUIRED: The organization responsible for the metadata information.

Contact_Person: REQUIRED: The person responsible for the metadata information.

Contact_Address:

Address_Type: REQUIRED: The mailing and/or physical address for the organization or individual.

City: REQUIRED: The city of the address.

State_or_Province: REQUIRED: The state or province of the address.

Postal_Code: REQUIRED: The ZIP or other postal code of the address.

Contact_Voice_Telephone: REQUIRED: The telephone number by which individuals can speak to the organization or

individual.

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Extensions:

Online_Linkage:

Profile_Name: ESRI Metadata Profile

Page 2 of 2

file://C:\Documents and Settings\rp1145\Local Settings\Temp\metadata24.htm 12/3/2007

Appendix II. Contribution of Each Team Member

Creation of Final Report

Sean Whitehead – Wrote Intro, Discussion, Results, Lit. review, Formated report, .

William Shamburg – wrote Data section

Chris Skeete – wrote Methods: The Internat Cemetery mapping Application, Flow Chart

Regan Presley – Wrote Methods: Analysis, and Appendix 1: Metadata

Creation of Final Poster

Erik Olden – Oversaw its creation, took care of plotting

William Shamburg – created maps for poster

Chris Skeete – Screen shots of the ICMA

Reagan Presley – Overall creation/instructor approval.

Creation of Internet Cemetery Mapping Application

Chris Skeete – Oversaw its creation

Data Collection

Sean Whitehead – Field data collection, Survey Maps

William Shamburg – Digital Database Acquisition

Chris Skeete – Digital database Acquisition

Regan Presley – Field data collection

Erik Olden – Field data collection

Data Analysis

Regan Presley – created analysis of saving space in Roselawn

William Shamburg – created methods of Shapefile to database join

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download