Follow

Customer-Provided Esri® Geo-database Requirements for Use with Pontem GIS Mapping

PONTEM/ESRI® GEO-DATABASE INTRODUCTION

This document is intended to be a guide for Pontem clients considering building a geo-database "in-house" to be used in a future implementation of the Pontem system.  This article contains the following sections: 


Pontem’s Cemetery Data Manager software with Esri®-engineered GIS mapping provides a two-way interface with the “Grave” layer in the Esri® geodatabase (GDB) and the Pontem database 

Pontem’s software requires a layer be created in the GDB for each layer of the cemetery grave addressing schema (i.e., “Section,” “Lot,” and “Grave”).  Though Pontem’s software can display additional layers, we recommend only “Aerial,” “Road,” and “Landscape” layers be used in addition to those related to actual grave addressing.

GRAVE ADDRESSING HIERARCHY EXPLAINED

Each cemetery is divided into smaller organizational units, the highest level usually being called “Section.” Each “Section” is divided into smaller units, such as “Lots” or “Rows.”  This division continues until you reach the “Grave” unit.  Altogether, this information creates the “Grave Address.” 

For example, Calvary Cemetery is divided into sections, sections into rows, and rows into graves. In this case, the GDB requires a “Feature Class Layer” each for “Section,”  “Row,” and “Grave.”

Pontem uses the complete grave address in its Cemetery Data Manager database to match the complete grave address in the required fields of the GDB.  When an exact match is found, a link is made and data such as owner and occupant names and the grave’s status (“Available,” “Sold,” “Occupied,” etc.) are added to the “Grave Layer Attribute Table” in the GDB and displayed visually within Pontem’s Cemetery Data Manager software. 

A grave polygon that does not find a match in the database is given a special status to make it stand out on the map. A grave in the database that does not find a match in the GDB is listed in a report of all such graves.

MAP DOCUMENTS AND DIGITAL DATA

An Esri® GDB developed for use with Pontem’s software must include several “Feature Class” layers, one for each component of the cemetery grave address hierarchy. The examples illustrated in this section use the components of “Cemetery Boundary,”  “Section,”  “Row,” and “Grave.”

Samples of optional items such as landscape features, buildings, roads, sidewalks, and utilities are also illustrated for your information.

In order for any map to function correctly, the layers MUST be assigned the same Esri® Projection. Failure to do so may result in loss of function outside Pontem’s Cemetery Management software application, and may lead to delays in map setup if the layers used to set up the map are not in a consistent projection.

Each of the grave address layers must be polygons only.  Additional layers can be polygon, polyline, or point layers.

AERIAL LAYER

Maps are generally created using an aerial for the background.  This is not necessary, but typically yields a more favorable display. (An aerial layer is optional)

 
Figure 1 – Aerial


Figure 2 – Shapefiles w/ Aerial

CEMETERY BOUNDARY LAYER

This layer shows roughly the outline of the cemetery. The only attribution needed is the “Cemetery Name.”


Figure 3 – Cemetery Boundary Polygon

SECTION LAYER

This layer contains polygons for each section in the cemetery. The only additional field needed is “Section” (Field Type= Text).  Each polygon must be attributed with the name or number of that section.


Figure 4 – Section Polygons

ROW LAYER

This layer contains polygons for each row in the cemetery. The only additional field needed is “Row “ (Field Type= Text).  Each polygon must be attributed with the name or number of that row.


Figure 5 – Row Polygons 

GRAVE LAYER

This layer contains polygons for each grave in the cemetery and connects to Pontem’s Cemetery Management Software database. The additional required fields are:

  • One field for each grave address hierarchy layer (Field Type = Text)
    • Cemetery Grave Address is Section, Row, Grave – Add Fields for Section, Row, and Grave
    • Cemetery Grave Address is Section, Block, Lot, Grave – Add Fields for Section, Block, Lot, and Grave
  • All Grave Address Fields must be fully attributed.  If some fields are not used everywhere, they can be left blank.

This layer connects the Esri® GDB to the Pontem database. Grave addresses in the “Grave Layer” must find exact matches in the Pontem database.

The Esri® GDB can also be used to create missing graves in the Pontem database.  


Figure 6 – Grave Polygons  

 

AUXLIARY LAYERS

In addition to the standard layers noted above, auxiliary layers can be included. These layers can include, but are not limited to Roads/Driveways, Utilities, Landscape features, Trees, Flag Poles, Sidewalks/Walkways, and Buildings (offices, work sheds, mausoleums, etc.).  Figures 8 and 9 illustrate some examples of auxiliary layers that can be included.


 Figure 8 – Street Lights, Landscape and Sidewalk features

Layer

Purpose

Type

Color

Roads

Roads and Driveways

Polygon

Tan

Landscape

Trees and Shrubs

Polyline

Green

Sidewalk

Sidewalks and Hardscape

Polyline

Blue

Buildings

Offices, Work Sheds, Mausoleums

Polygon

Pink

 


Figure 9 – Watering Stations, Buildings and Flag Poles

Layer

Purpose

Type

Color

Roads

Roads and Driveways

Polygon

Tan

Landscape

Trees and Shrubs

Polyline

Green

Sidewalk

Sidewalks and Hardscape

Polyline

Blue

Buildings

Offices, Work Sheds, Mausoleums

Polygon

Pink

 

Technical Requirements

The following is a list of technical requirements for submitting customer-provided Esri® geodatabase files to Pontem Software:

  • ArcGIS 10.1, 10.2, 10.3
  • File Geodatabase
  • All cemeteries must be in a single GDB
    • Each cemetery organized as a “Feature Dataset”
    • Each layer within a cemetery organized as “Feature Class”
  • Layers
    • All layers, including the aerial, must use the same Esri® projection
      • Must be a “standard/well-known esri ID” projection
    • Grave Layer
      • Must contain only “Grave” polygons
      • Attribute must contain only the following fields:
        • OBJECTID
        • Shape_Length
        • Shape_Area
        • Shape
        • Grave Field (Field Type = Text)
        • One Field for level of the Grave Address hierarchy
      • Optional: Attribute fields for latitude and longitude (Field Type = Double)
    • One layer for each level of the grave address hierarchy
      • Must contain only polygons for that level (i.e., section layer has “Section” polygons)
      • Attribute must contain only the following fields:
        • OBJECTID
        • Shape_Length
        • Shape_Area
        • Shape
        • One Field for this level of the Grave Address hierarchy (Field Type = Text)
        • Example: Section layer has Field Name Section, with related attributes
    • Landscape Layer(s)
      • These layers contain landscape features (trees, shrubs), roads, buildings, utilities
        • May be polyline or point layers
      • This data can be placed on one layer or multiple layers
      • Only attribute field Pontem will use will be a Label Field (Field Type = Text)
    • Optional: Aerial Layer
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk