Halfway Houses - Correctional (HalfwayHousePt)

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: Department of Corrections
Publication_Date: 20140321
Title: Halfway Houses - Correctional (HalfwayHousePt)
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publisher: DC GIS
Online_Linkage:
<http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=HalfwayHousePt&downloadTYPE=ESRI>
Online_Linkage:
<http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=HalfwayHousePt&downloadTYPE=KMZ>
Larger_Work_Citation:
Citation_Information:
Originator: DC GIS
Title: DC Geographic Information System
Geospatial_Data_Presentation_Form: vector digital data
Description:
Abstract:
Correctional Halfway House locations. The dataset contains locations and attributes of Correctional Halfway Houses, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies.
A database provided by the DC Department of Corrections (DOC) identified Halfway House locations and DC GIS staff geo-processed the data.
All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.
METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Purpose:
This data is used for the planning and management of Washington, D.C. by local government agencies.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20140321
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.040273
East_Bounding_Coordinate: -76.972697
North_Bounding_Coordinate: 38.932187
South_Bounding_Coordinate: 38.855592
Data_Set_G-Polygon:
Data_Set_G-Polygon_Outer_G-Ring:
G-Ring_Point:
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: Rehabilitation
Theme_Keyword: Facility
Theme_Keyword: society
Theme_Keyword: Halfway House
Theme_Keyword: DC Government
Theme_Keyword: Corrections
Place:
Place_Keyword: Washington, D.C.
Place_Keyword: District of Columbia
Place_Keyword: DC
Place_Keyword: DC GIS
Place_Keyword: DCGIS
Use_Constraints:
Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 441 4th St NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Data_Set_Credit: DC Department of Corrections (DOC) database
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.780
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Data believed to be complete and accurate, subject to change. Digital version compared with original source data for accuracy and completeness. Validated by source and/or responsible agency.
Logical_Consistency_Report: In process of validation by source and/or responsible agency.
Completeness_Report:
Data believed to be complete and accurate, subject to change. Digital version compared with original source data for accuracy and completeness. Validated by source and/or responsible agency.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report: In process of validation by source and/or responsible agency.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report: N/A
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Department of Corrections (DOC)
Publication_Date: 9/1/2002
Title: DOC database
Online_Linkage: <http://doc.dc.gov/>
Type_of_Source_Media: database
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 9/19/2002
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: DOC
Source_Contribution: locations and attributes
Source_Information:
Source_Citation:
Citation_Information:
Originator: Alexandria Mapping Company
Publication_Date: 2002
Title: Metro Washington DC
Edition: 34th
Publication_Information:
Publication_Place: Alexandria, VA
Publisher: ADC
Online_Linkage: <http://www.adcmap.com>
Source_Scale_Denominator: 24000
Type_of_Source_Media: atlas
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 8/1/2002
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: ADC - Washington DC Metro
Source_Contribution: location
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Department of Corrections
Publication_Date: 2005
Title: DOC Website
Online_Linkage: <http://doc.dc.gov/>
Type_of_Source_Media: website
Source_Citation_Abbreviation: Department of Corrections
Source_Contribution: Attribution
Process_Step:
Process_Description:
Data Collection:
Through the application's functionality and usability requirements, OCTO GIS staff compose a list of data layers needed for the application. From this, staff determine the appropriate source and location for each layer, and assess the effort needed to get it.
Some layers, already part of the DC Atlas, are incorporated into the data store. For DC agency data, agency liaisons ask DC personnel about data availability and acquisition. For third-party data, OCTO-GIS evaluates options and either finds alternatives, purchases, or licenses the data. In some cases, staff create data from existing sources and then add required attribution.
Process_Date: 5/31/03
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Process_Step:
Process_Description:
Data Preparation:
After the collection, the data team prepares the data for qa/qc and inclusion in the data store. This step involves: 1.) configuring the datasets into a common form; 2.) geocoding tabular data using a common address base; 3.) generating or converting paper documents into digital format; 4.) populating required fields; and 5.) resolving data duplication and conflicts.
For geocoding, staff use a derivative of the Office of Tax and Revenue (OTR) owner-point database and the District Department of Transportation's (DDOT) street inventory system (SIS) street centerline file as the address base. Through automated procedures on the owner-point derivative file, personnel clean and standardize the irregular premise address information into street number, name, type, and quadrant fields. Also, staff use the merged SIS file containing the five centerlines classifications (street, alley, drive, service road, and ramp).
First, staff match tabular data to the standardized owner-points. Then, the rest are matched to the street centerline file. After this, staff compose a list of the unmatched records needing further research. Since not all of the records geocode, staff note the final matching figures (number of hits, rejects, and the total).
For web links, team members check the validity of existing links and find matching web sites that directly represent the feature. Staff use several web search engines to find appropriate web links. DC government sites are primarily used, when available.
To eliminate data redundancy, staff identify possible conflicting layers and duplicate features. In some cases, staff pick the best source. In others, the attributes in the multiple layers are consolidated. Sometimes, staff map the conflicting layers and investigate feature clusters as areas of potential duplication.
Where applicable, team members move points to the center of the corresponding buildings. Staff then select the building footprints and assign the appropriate GIS_ID value that links the points with the appropriate building polygon(s).
Process_Date: 5/31/03
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Process_Step:
Process_Description:
Data QA/QC
After data preparation, the data team performs qa/qc. Various processes check the following parameters: 1.) spatial and attribute accuracy; 2.) data usability; 3.) data dictionary adherence; 4.) specialized metrics, such as connectivity and directionality; and 5.) data load success. These checks are, as follows:
Visual - staff perform a structured visual check of the data, using on-screen, plotting, and customized routines, and, at times, comparing it to the source documents.
Edge-matching - For grided datasets, staff review the spatial capture, connectivity, and attribution of data across tile boundaries, where applicable.
Automated - Staff compare the data to documented standards and source files through automated procedures and reports.
Specialized - Staff review more specific data parameters, such as directionality, connectivity , and topology.
Edit Verification - Staff ensure that previous errors are fixed to specifications. ? Field Verification - Occasionally, through field work, team members compare the GIS data with the real world.
Data Loading - Staff evaluate the success and evaluate the process of loading raw data into a structured database.
Since most of the data use addresses as the spatial reference, staff compare the data against base layers (buildings, roads, street centerlines, owner-points, parks, and orthophotography) and move features where needed.
In some cases, OCTO GIS personnel produce maps and reports for source agency review. Through an iterative process, staff modify and enhance the layer to agency specifications. For some datasets, the agency endorses the final product for data load and publication.
Process_Date: 5/31/03
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Process_Step:
Process_Description:
Final Data Preparation:
For final preparation, staff ensure all of the needed items are present (unneeded items are deleted), the metadata is complete and current, the shapefile is in the proper projection, and a spatial index exists. If not already done, a GIS_ID (unique id for features in the layer) is computed with automated tools.
Process_Date: 5/31/03
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Process_Step:
Process_Description:
Data Load:
After final preparation, OCTO GIS staff load the data into the application's test database, where SDE handles the spatial data and ORACLE manages the attribute information.
First, staff add primary key and name fields to the layer. Second, personnel register the layer into the appropriate tables and establish the unique feature-ids (the link between the spatial object and its attributes) specific to that layer. Then, staff populate feature, search, address, web url, contact, data source, and other tables, where applicable. For point layers, team members calculate each feature's geographic extent and populate the features table. Lastly, each layer is intersected with the base geography (2002 Advisory Neighborhood Commission areas, 2002 wards, zip codes, neighborhoods, and neighborhood clusters) to populate the "what's-within" tables for the web reports. Views are refreshed when needed.
Process_Date: 5/31/03
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Process_Step:
Process_Description:
Data Load QA/QC
OCTO GIS performs spatial checks comparing the test SDE database with source files to check for completeness, spatial integrity, and proper attribution. First, staff compare the test database contents with documented standards. Then, team members check the geography and attribution, as well as compare dataset parameters between both layers.
The data team performs attribute checks on the ORACLE database to ensure the existence and validity of views. Again, staff compare the database contents with documented standards. For critical views, personnel check the view structures and data against source files and documentation.
Process_Date: 5/31/03
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\DOCUME~1\roew\LOCALS~1\Temp\xmlE.tmp
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation: C:\OCTOGIS\Data\DOC\HalfwayHousePt
Process_Step:
Process_Description:
OCTO GIS staff reviewed DOC website for the current list to halfway houses and made updates to the layer accordingly.
Process_Date: 06/30/05
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 441 4th st NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Process_Step:
Process_Description:
The data was updated from records provided by DC Department of Corrections. The database contained the main fields, such as name and address. Staff researched the other attribution and populated what could be identified.
Process_Date: 01/23/07
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 441 4th St NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Process_Step:
Process_Description:
The data was updated from records provided by DC Department of Corrections. The database contained the main fields, such as name and address. Staff researched the other attribution and populated what could be identified.
Process_Date: 20140321
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: OCTO
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\HalfwayHousePt.xml
Process_Date: 20140407
Process_Time: 16372200
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000011
Ordinate_Resolution: 0.000011
Planar_Distance_Units: meters
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
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: HalfwayHousePt_01242014
Attribute:
Attribute_Label: WEB_URL
Attribute_Definition: Correctional Halfway House Web Link URL
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: FACILITY
Attribute_Definition: Correctional Halfway House Name
Attribute:
Attribute_Label: LOCATION
Attribute_Definition: Correctional Halfway House Address
Attribute:
Attribute_Label: ZIP
Attribute_Definition: Correctional Halfway House Zip Code
Attribute:
Attribute_Label: CAP
Attribute_Definition: Correctional Halfway House Capacity
Attribute:
Attribute_Label: TYPE
Attribute_Definition: Correctional Halfway House Type
Attribute:
Attribute_Label: SQ_
Attribute_Definition: Correctional Halfway House Square Footage
Attribute:
Attribute_Label: DATE_
Attribute_Definition: Correctional Halfway House Opening Date
Attribute:
Attribute_Label: OP_BY
Attribute_Definition: Correctional Halfway House Operator
Attribute:
Attribute_Label: CLIENT
Attribute_Definition: Correctional Halfway House Client
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: OBJECTID
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: GIS_ID
Attribute_Definition: OCTO GIS sequential identifier
Attribute:
Attribute_Label: AID
Attribute_Definition: Master Address Repository Identifier
Attribute:
Attribute_Label: GENDER
Attribute_Definition: Correctional Halfyway House Gender Clientele
Attribute:
Attribute_Label: PHONE
Attribute_Definition: Correctional Halfway House Phone Number
Attribute:
Attribute_Label: JURISDICTION
Attribute_Definition: Correctional Halfway House Jurisdiction
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 441 4th St NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Resource_Description: Downloadable Data
Distribution_Liability:
Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.000
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Ordering_Instructions:
Most DC GIS datasets can be downloaded from "<http://dcgis.dc.gov>" on the data center page. Orders can also be made by contacting OCTO GIS at "[email protected]", especially for datasets not available for download.
Metadata_Reference_Information:
Metadata_Date: 20140319
Metadata_Review_Date: 01/07/04
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 441 4th St NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Voice_Telephone:
REQUIRED: The telephone number by which individuals can speak to the organization or individual.
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
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: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.12 on Thu Jun 25 15:31:43 2015