snippet:
|
The goal of Enterprise Permitting & Licensing GIS History writer is to capture the shape of attached features (parcels, addresses, etc.) along with critical metadata at the time of case creation. This allows users to see all the cases that occurred on a particular plot of land without having to sift through the history of parcels as number changes occur and/or subdivisions develop. Once written to SDE, History data does not change with updates made to the underlying cases.
GIS professionals can also turn on these history layers for end users, but they are traditionally for GIS administrators to use as they see fit (e.g., reporting, additional map services, etc.). |
summary:
|
The goal of Enterprise Permitting & Licensing GIS History writer is to capture the shape of attached features (parcels, addresses, etc.) along with critical metadata at the time of case creation. This allows users to see all the cases that occurred on a particular plot of land without having to sift through the history of parcels as number changes occur and/or subdivisions develop. Once written to SDE, History data does not change with updates made to the underlying cases.
GIS professionals can also turn on these history layers for end users, but they are traditionally for GIS administrators to use as they see fit (e.g., reporting, additional map services, etc.). |
accessInformation:
|
|
thumbnail:
|
|
maxScale:
|
5000 |
typeKeywords:
|
[] |
description:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><TABLE><TBODY><TR><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>Field</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>Data Type (Size)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>Description</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>ModuleName</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This describes the Enterprise Permitting & Licensing module where the user created the object (CodeManagement, PermitManagement, PlanManagement).</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>CaseID</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(36)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the GUID of the case in the Enterprise Permitting & Licensing database. Determine the specific table relationship by looking at the MODULENAME field (i.e., PermitManagement relates to the PMPermit table; CodeManagement relates to the CMCode table; PlanManagement relates to the PLPlan table.).</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>CaseNumber</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the Enterprise Permitting & Licensing case number (i.e., permit number, plan number, or case number).</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>CaseType</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the GUID of the case type for permit or plan objects.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>WorkClass</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the GUID of the work class for permit or plan objects.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>ApplicationDate</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeDate(36)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the application date for permits and plans or the opened date for code cases.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>ProjectID</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the GUID of the associated project.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>ProjectName</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the name of the associated project.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>GISHistoryQueueID</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(36)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the GUID of the history record in the GISHistoryQueue table.</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>SpatialType</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the Enterprise Permitting & Licensing spatial type of this history object (Parcel, Address, SpatialCollection, or GISFeatures).</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="font-weight:bold;margin:8 0 8 0;"><SPAN><SPAN>SpatialID</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>esriFieldTypeString(50)</SPAN></SPAN></P></TD><TD><P STYLE="margin:8 0 8 0;"><SPAN><SPAN>This is the unique key value of the spatial element.</SPAN></SPAN></P></TD></TR></TBODY></TABLE></DIV></DIV></DIV> |
licenseInfo:
|
|
catalogPath:
|
|
title:
|
EPL History Point |
type:
|
|
url:
|
|
tags:
|
["EPL","Enterprise Permitting & Licensing","Tyler","History Layer","Point"] |
culture:
|
en-US |
portalUrl:
|
|
name:
|
|
guid:
|
|
minScale:
|
150000000 |
spatialReference:
|
|