FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION VERSION 2006 TITLE: MOBILE HOME PARKS - 2006 Geodataset Name: GC_MOBILEHOMES_2006 Geodataset Type: SHAPEFILE Geodataset Feature: POINT Feature Count: 2274 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): My Florida-Business and Professional Regulation SCALE OF ORIGINAL SOURCE MAPS: VARIOUS DATE OF AUTOMATION OF SOURCE: 20060601 GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: GC_MOBILEHOMES_2006.DBF
ITEM NAME | WIDTH | TYPE |
FID
|
4 | OID |
Shape
|
0 | Geometry |
Status
|
1 | String |
Score
|
4 | Number |
Side
|
1 | String |
COUNTY
|
15 | String |
OWNER_NUMB
|
15 | String |
OWNER_NAME
|
70 | String |
ROUTING_IN
|
50 | String |
OWNER_STRE
|
65 | String |
OWNER_CITY
|
30 | String |
OWNER_STAT
|
15 | String |
OWNER_ZIP
|
15 | Number |
PRJ_NUMBER
|
15 | String |
PRJ_NAME
|
70 | String |
PRJ_STREET
|
50 | String |
PRJ_CITY
|
25 | String |
PRJ_STATE
|
15 | String |
PRJ_ZIP
|
15 | Number |
PRJ_DESC
|
10 | String |
INIT_AP_DA
|
8 | Date |
NUMBER_TO_
|
15 | Number |
1STATUS_CO
|
15 | String |
2STATUS_CO
|
15 | String |
DESCRIPT
|
70 | String |
FGDLAQDATE
|
8 | Date |
AUTOID
|
4 | Number |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
FID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
Status |
Data attribute inherent to the ESRI shapefile format, (whether it was matched or not). |
|
Score |
ESRI item which denotes the score with which the address was matched to a feature in the reference data. |
|
Side |
ESRI item which denotes the side of the street to which the address was matched (for geocoding service styles that can match an address to a particular side of a street). |
|
COUNTY |
Name of county. |
|
OWNER_NUMB |
License number given to the owner by the State of Florida. |
|
OWNER_NAME |
Name of owner. |
|
ROUTING_IN |
Co-owners or other associated names. |
|
OWNER_STRE |
Owners street of residence. |
|
OWNER_CITY |
City where owner lives. |
|
OWNER_STAT |
State of owner. |
|
OWNER_ZIP |
Zip Code of owner. |
|
PRJ_NUMBER |
Project number of MHP. |
|
PRJ_NAME |
Name of MHP |
|
PRJ_STREET |
Street of MHP. |
|
PRJ_CITY |
City of MHP. |
|
PRJ_STATE |
State of MHP. |
|
PRJ_ZIP |
Zip Code of MHP. |
|
PRJ_DESC |
The project description. |
|
INIT_AP_DA |
Intial appropriation date. |
|
NUMBER_TO_ |
Internal feature number. |
|
1STATUS_CO |
Status condition |
|
2STATUS_CO |
Other Status Conditions |
|
DESCRIPT |
Based on PRJ_NAME. |
|
FGDLAQDATE |
The date FGDL acquired the data from the Source. |
|
AUTOID |
GeoPlan Center Feature Number. |
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology |
This data is provided 'as is' by GeoPlan and is complete to our knowledge. |
GeoPlan relied on the integrity of the attribute information within the original data. |
What is Geocoding? Geocoding is term used to describe the act of address matching. Geocoding is the process of finding a geographic location (x, y point) for an address (such as street number and name, city, state, and ZIP Code) on a map. Geocoding is based off the typical address scheme for the US, in which one side of the street contains even house numbers while the other side of the street contains odd house numbers. |
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan |
|
|
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan |
|
|
A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:250000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html |
My Florida http://www.state.fl.us/dbpr/sto/file_download/download_files.shtml |
Mobile home locations and information were obtained from the online MyFlorida site in 2006 www.state.fl.us/dbpr/sto/file_download/download_files.shtml. GeoPlan downloaded this data in EXCEL format and converted it to a dbf. The dbf was then geocoded against ARC Logistics Route GDT Roads and converted into a shapefile with the FGDL Albers HPGN map projection. (See "Map Projection Parameters" below). -Added Descript field based on PRJ_NAME. -Added FGDLAQDATE based on the date FGDL acquired the data from the Source. Process Date: 20060601 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
MY FLORIDA-BUSINESS AND PROFESSIONAL REGUALTION MyFlorida 1940 North Monroe Street Tallahassee, TX 32399-1027 850.922.8981 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html