Community based residential facilities (CbrfPt)

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: Department of Consumer and Regulatory Affairs

Publication_Date: 20030331

Title: Community based residential facilities (CbrfPt)

Geospatial_Data_Presentation_Form: vector digital data

Online_Linkage:

<http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=CbrfPt&downloadTYPE=ESRI>

Online_Linkage:

<http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=CbrfPt&downloadTYPE=KMZ>

Larger_Work_Citation:

Citation_Information:

Originator: DC GIS

Title: DC Geographic Information System

Geospatial_Data_Presentation_Form: vector digital data

Description:

Abstract:

Community-Based Residential Facility (CBRF) locations. The dataset contains locations and attributes of CBRFs, 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.
CBRF locations were identified from a database provided by the various agencies, and consolidated and geoprocessed by OCTO staff.
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: 20030331

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -77.109778

East_Bounding_Coordinate: -76.913802

North_Bounding_Coordinate: 38.990929

South_Bounding_Coordinate: 38.814563

Data_Set_G-Polygon:

Data_Set_G-Polygon_Outer_G-Ring:

G-Ring_Point:

Keywords:

Theme:

Theme_Keyword_Thesaurus: none

Theme_Keyword: health

Theme_Keyword: Community

Theme_Keyword: Residential Facility

Theme_Keyword: Care

Theme_Keyword: Shelter

Theme_Keyword: Service

Theme_Keyword: society

Theme_Keyword: Youth

Place:

Place_Keyword: Washington, D.C.

Place_Keyword: District of Columbia

Place_Keyword: DC

Place_Keyword: DC GIS

Place_Keyword: DCGIS

Use_Constraints:

For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>

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: 10 am - 5 pm

Data_Set_Credit:

Department of Consumer and Regulatory Affairs (DCRA); DC Office of the Chief Technology Officer (OCTO); other agencies- OCTO consolidated CBRF 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: Various Agencies

Publication_Date: 3/31/03

Title: CBRF database

Other_Citation_Details: Access Database

Online_Linkage: <http://www.octo.dc.gov/>

Type_of_Source_Media: database

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 3/31/2003

Source_Currentness_Reference: publication date

Source_Citation_Abbreviation: CBRF

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

Process_Step:

Process_Description:

Data Collection:
Through the application's functionality and usability requirements, the data team composes 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, staff liaisons ask agency personnel about data availability and acquisition. For third-party data, DC does a cost-benefit analysis and either finds alternatives, purchases, or licenses the data. In some cases, staff can create data from existing sources and then add needed attribution.

Process_Date: 5/31/03

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: GIS Data Coordinator

Contact_Organization: D.C. Office of the Chief Technology Officer

Contact_Address:

Address: 200 I Street SE, 5th Floor

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: [email protected]

Hours_of_Service: 10 am - 5 pm

Process_Step:

Process_Description:

Data Preparation:
After the collection, staff prepare the data for inclusion in the data store. This step involves: 1.) configuring the datasets into a common form; 2.) geocoding tabular data to a common address base; or 3.) generating or converting paper documents into digital format.
For geocoding, staff use the owner-point and SIS street centerline datasets as address bases. Through automated procedures, staff cleaned and standardized the irregular owner-point premise address information into street number, name, type, and quadrant fields.
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 work. Staff match as many as possible through research. Since not all of the records geocode, staff note the final matching figures (number of hits, rejects, and the total). For Community-Based Residential Facilities, 595 out of 600 records matched, or approximately a 99% hit rate.
For features that are in multiple layers, staff identify the conflicting layers and duplicated features. In some cases, staff ascertain the layer containing the best data for a particular feature and remove the other layers. In others, staff merge the attributes in the multiple layers into one. Where features cluster, staff plot conflicting layers onto the map to locate areas of possible duplication.
For some point layers, staff capture planimetric building footprints as a backdrop for visual aesthetics. The GIS_ID (a unique feature identifier) links the points with the appropriate building polygon(s). The point layer contains the attributes.

Process_Date: 5/31/03

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: GIS Data Coordinator

Contact_Organization: D.C. Office of the Chief Technology Officer

Contact_Address:

Address: 200 I Street SE, 5th Floor

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: [email protected]

Hours_of_Service: 10 am - 5 pm

Process_Step:

Process_Description:

Data QA/QC
After data preparation, staff perform qa/qc. Various processes (visual checks, automated procedures, edge-matching routines, specialized checks, and field verification) check the spatial and attribute accuracy, usability, and data dictionary adherence, specialized (such as connectivity and directionality), and load parameters.
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. Where needed, staff move the feature to the correct location using the base layers as a guide. Also, staff use the orthophotography as a base for moving spatial elements over the correct features.
For web links, staff check the validity of existing links and find corresponding web sites that directly represent the feature. Usually, staff enter the feature's primary name into several web search engines and review the results to find that direct link.

Process_Date: 5/31/03

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: GIS Data Coordinator

Contact_Organization: D.C. Office of the Chief Technology Officer

Contact_Address:

Address: 200 I Street SE, 5th Floor

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: [email protected]

Hours_of_Service: 10 am - 5 pm

Process_Step:

Process_Description:

Final Data Preparation:
For final preparation, staff ensure all of the needed items are present (extra items are deleted), the metadata is complete and current, the shapefile has the proper projection, and a spatial index exists. If not already done, a GIS_ID (unique id for features in the layer) is computed using automated tools.

Process_Date: 5/31/03

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: GIS Data Coordinator

Contact_Organization: D.C. Office of the Chief Technology Officer

Contact_Address:

Address: 200 I Street SE, 5th Floor

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: [email protected]

Hours_of_Service: 10 am - 5 pm

Process_Step:

Process_Description:

Data Load:
After final preparation, 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, staff register the layer into the appropriate tables and establish the unique feature-ids specific to that layer. Then, staff populate feature, search, address, web url, contact, and data source tables, where applicable. For point layers, staff calculate each feature's geographic extent and populate the features table. Lastly, staff intersect each layer 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_Person_Primary:

Contact_Person: GIS Data Coordinator

Contact_Organization: D.C. Office of the Chief Technology Officer

Contact_Address:

Address: 200 I Street SE, 5th Floor

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: [email protected]

Hours_of_Service: 10 am - 5 pm

Process_Step:

Process_Description:

QA/QC on Data Load Staff perform spatial checks comparing the test database with source files to check for completeness, spatial integrity, and proper attribution. First, staff compare the test database feature-dataset list with the the master dataset database. By running summary programs on the geodatabase, staff can easily review its contents. Then, staff overlay the layers in test database with their external counterparts, using different symbology, and note any discrepancies. Staff also label the features with their proper names and spot-check attributes. Finally, staff compare the record or feature counts between both layers and note differences. Staff perform attribute checks on the ORACLE database to ensure the existence and validity of views, paying particular attention to critical ones. Again, staff compare the list of views in the test database with master view documentation. For integral views, staff check field definitions and contents against documented standards. For items marked as "not null" and primary keys, staff note null values.

Process_Date: 5/31/03

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: GIS Data Coordinator

Contact_Organization: D.C. Office of the Chief Technology Officer

Contact_Address:

Address: 200 I Street SE, 5th Floor

Contact_Facsimile_Telephone: (202) 727-5660

Contact_Electronic_Mail_Address: [email protected]

Hours_of_Service: 10 am - 5 pm

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: C:\OCTOGIS\Data\ABRA\AbraLicenseePt.shp.xml

Process_Contact:

Contact_Information:

Contact_Address:

Address: 200 I Street SE, 5th Floor

Process_Step:

Process_Description:

Source processing Information
Original data dump from March 31, 2003 to an Access database. OCTO, in compilation from DCRA, DOH - HRA, DMH, CFSA, DHS - YSA, DHS - FSA, DMPSJ (for Bureau of Prisons (Fed), DC Dept of Corrections, and CSOSA (Fed)) consolidated and validated the database. Originally, there were 800 records in the database, but OCTO staff removed 236 facilities due to them being:
- An out of state facility (primarily CFSA) - Closed - An Independent Living or Outpatient facility
Other facilities were added along the way, coming to 600 by April.
This dataset is the result of the work of the City Administrator's Task Force on Community-Based Residence Facilities. It seeks to combine information from different District agencies into the same file for analytic purposes.
The dataset contains information on the following types of facilities:
- Community Residence Facilities (DOH - HRA) - MRDDA Homes (DOH - HRA; DHS - MRDDA) - Mental Health Homes (DMH) - Nursing Homes (DOH - HRA) - Residential Facilities for People Recovering from Addiction (DOH - APRA) - Halfway Houses (DOC, Fed. BOP, Fed. CSOSA) - Group Homes for Children (CFSA, DHS - YSA) - Emergency Shelters (DHS - FSA)
While every attempt was made to remove invalid records, there may be some facilities listed in the database that are no longer functioning as CBRFs, and others that were omitted from the database, but should be included.

Process_Date: 3/31/03

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Organization: OCTO

Contact_Address:

Address: 200 I Street SE, 5th Floor

Process_Step:

Process_Description: Dataset copied.

Source_Used_Citation_Abbreviation: C:\OCTOGIS\Data\DCRA\CBRF\CbrfPt

Process_Contact:

Contact_Information:

Contact_Address:

Address: 200 I Street SE, 5th Floor

Process_Step:

Process_Description: Metadata imported.

Source_Used_Citation_Abbreviation: M:\DCGISDATA_FINAL\MiscellaneousNFD\CbrfPt.shp.xml

Process_Contact:

Contact_Information:

Contact_Address:

Address: 200 I Street SE, 5th Floor

Process_Step:

Process_Description: Dataset copied.

Source_Used_Citation_Abbreviation: Server=10.2.11.14; Service=5151; User=sde; Version=SDE.DEFAULT

Process_Contact:

Contact_Information:

Contact_Address:

Address: 200 I Street SE, 5th Floor

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Entity point

Point_and_Vector_Object_Count: 595

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: State Plane Coordinate System 1983

State_Plane_Coordinate_System:

SPCS_Zone_Identifier: 1900

Lambert_Conformal_Conic:

Standard_Parallel: 38.300000

Standard_Parallel: 39.450000

Longitude_of_Central_Meridian: -77.000000

Latitude_of_Projection_Origin: 37.666667

False_Easting: 400000.000000

False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.001000

Ordinate_Resolution: 0.001000

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: DCGIS.CbrfPt

Attribute:

Attribute_Label: GIS_ID

Attribute_Definition: Sequential OCTO-GIS identifier that links points and polygons.

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: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: Status

Attribute_Definition: Geocoding status

Attribute:

Attribute_Label: SSL

Attribute_Definition: Single square lot

Attribute:

Attribute_Label: OWNERNAME

Attribute_Definition: Owner name/organization

Attribute:

Attribute_Label: HSTD_CODE

Attribute:

Attribute_Label: FACILITYID

Attribute_Definition: Facility ID

Attribute:

Attribute_Label: ADDRESS

Attribute_Definition: Street address

Attribute:

Attribute_Label: STATE

Attribute_Definition: State location

Attribute:

Attribute_Label: ADDRESS2_1

Attribute_Definition: Street address line 2

Attribute:

Attribute_Label: ZIP

Attribute_Definition: Zip code

Attribute:

Attribute_Label: CAPACITY

Attribute_Definition: Facility capacity

Attribute:

Attribute_Label: PHONE

Attribute_Definition: Telephone number

Attribute:

Attribute_Label: FACSTATUSI

Attribute_Definition: Facility Status

Attribute:

Attribute_Label: DIRECTOR

Attribute_Definition: Facility Director

Attribute:

Attribute_Label: AGE_RANGE

Attribute_Definition: Facility Population Age Range Limitation

Attribute:

Attribute_Label: GENDER

Attribute_Definition: Facility Gender Limitation

Attribute:

Attribute_Label: SUBTYPEC_1

Attribute:

Attribute_Label: SUBTYPECD

Attribute:

Attribute_Label: TYPE_CODE

Attribute_Definition: CBRF Type Abbreviation

Attribute:

Attribute_Label: MAP_

Attribute:

Attribute_Label: COFOYEAR

Attribute_Definition: Certificate of Occupancy Year

Attribute:

Attribute_Label: COFO

Attribute_Definition: Certificate of occupancy id

Attribute:

Attribute_Label: STATUS

Attribute:

Attribute_Label: PROVIDERID

Attribute_Definition: Provider ID

Attribute:

Attribute_Label: AGENCYCODE

Attribute_Definition: Agency code

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: 200 I Street SE, 5th Floor

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:

For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Transfer_Size: 0.016

Digital_Transfer_Option:

Online_Option:

Computer_Contact_Information:

Network_Address:

Ordering_Instructions: All data is available at <http://opendata.dc.gov>

Metadata_Reference_Information:

Metadata_Date: 20080626

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: 200 I Street SE, 5th Floor

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 pm

Contact_Instructions: email

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