Updated and staged version of Wardens

Building Footprints Deleted. The dataset contains polygons representing planimetric deleted buildings , created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO). These features were originally captured in 1999 and updated in 2005, 2008, 2010, and 2013. The following planimetric layers were updated: Building Polygons (BldgPly)- Bridge and Tunnel Polygons (BrgTunPly)Grate (GratePly)Horizontal and Vertical Control Points (GeoControlPt)Obscured Area Polygons (ObsAreaPly)Railroad Lines (RailRdLn)Road, Parking, and Driveway Polygons (RoadPly)Sidewalk Polygons (SidewalkPly)Stairs (StairPly)Swimming Pools (SwmPoolPly)Wooded Areas (WoodPly) METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

Updated and staged version of migratoryBird

CDFW BIOS GIS Dataset, Contact: Nick Santos, Description: Species range layer for Clear Lake roach, showing HUC12s with presence types for Extant Range - Expert Opinion

Potential stewardship for Residential parcels in Baltimore City summarized by block group. Residential parcels was defined as only those parcels with a land use code of residential (LU_CODE = "R") based on the 2003 Maryland Property View A&T database. PRIZM 5, 15, and 62 classes are also present. PRIZM is the Potential Rating Index by Zip code Markets produced by the Claritas Corporation - > http://www.clusterbigip1.claritas.com/claritas/Default.jsp>. Total Potential stewardship is that land within a parcels not occupied by buildings, that is land that could potentially support vegetation, regardless of whether or not any vegetation is present. Realized Potential Stewardship is land that is currently occupied by vegetation. Not Realized Potential Stewardship is the land not occupied by buildings or existing vegetation, and is thus the land that is potentially available for "greening" initiatives. Normalization for realized and not realized potential stewardship is carried out by dividing by the total potential stewardship. The potential stewardship was calculated using parcel data, building footprints, and GDT census block groups. Building footprints were erased from the parcel area, resulting in a layer indicating the potential stewardship for each parcel. The potential stewardship layer was then unioned MD DNR's 2001 SUFA vegetation layer. All polygons corresponding to water features were deleted since water features cannot undergo "greening." All polygons that did fall in the potential stewardship area were deleted. This resulted in a layer in which the polygons represented the potential stewardship land along with the potential stewardship land occupied by either grass or trees. This layer was then intersected with the census block group layer resulting in a layer that had the potential stewardship land, potential stewardship vegetation, and block group IDs. All attributes were then summarized at the block group level. A cursory analysis of the parcel data indicated that parcel data was outdated for the following block groups: 245102503031, 245102503032, and 245102503033. Certain block groups with very high Normalized Total Potential Stewardship values may be indicative of the fact that building footprint data was missing, although the extent of this problem is unknown. Note: transportation networks are not part of the parcel data, and thus were appropriately not part of this analysis.

AT_2004_HOWA

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, A&T, Database, Assessors, Taxation




   Summary


   Serves as a basis for performing various analyses based on parcel data.


   Description


   Assessments & Taxation (A&T) Database from MD Property View 2004 for Howard County. The A&T Database contains parcel data from the State Department of Assessments and Taxation; it incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given parcel. These data form the basis for the 2004 Database, which also includes selected Computer Assisted Mass Appraisal (CAMA) characteristics, text descriptions to make parcel code field data more readily accessible and logical True/False fields which identify parcels with certain characteristics. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab.


   It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields).


   A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 1160 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords."


   Credits


   Maryland Department of Planning


   Use limitations


   BES use only.


   Extent



   West -77.186932  East -76.699458 

   North 39.373967  South 39.099693 




   Scale Range

   There is no scale range for this item.

Activities meeting the Monarch Butterfly Habitat Restoration initiative are a subset of activities that benefit native plants, and in doing so, benefit pollinators. Activities such as thinning, prescribed fire and other methods of fuel removal, treating invasive species and acres of native plantings can benefit Monarchs. Activities are self-reported by Forest Service Units and are reported when completed. This layer does not contain all activities that benefit Monarchs because this is a relatively new requirement for the program. The quality and comprehensiveness of this data will increase over time. Metadata

This provides a polygon coastline and islands layer which is based on the Topo50 products. It is a combination of the following layers:

• NZ Coastlines (Topo 1:50k)
• NZ Island Polygons (Topo 1:50k)
• NZ Auckland Is Island Polygons (Topo, 1:50k)
• NZ Campbell Is / Motu Ihupuku Island Polygons (Topo, 1:50k)
• NZ Antipodes Is Island Polygons (Topo, 1:25k)
• NZ Kermadec Is Island Polygons (Topo, 1:25k)
• NZ Bounty Is Island Polygons (Topo, 1:25k)
• NZ Snares Is / Tini Heke Island Polygons (Topo, 1:25k)
• NZ Chatham Is island polygons (Topo, 1:50k)

This topographic coastline is the line forming the boundary between the land and sea, defined by mean high water.

Islands from the NZ Island Polygons layer that lie within the NZ Coastline and Chatham Islands areas (i.e. islands in lakes, rivers and estuaries) have been removed.

The GIS workflow to create the layer is:

1. NZ Coastlines were converted from a polyline to a polygon using a polyline to polygon tool.
2. The resulting coastal polygon was then used as an input into an erase tool and run against the NZ Island Polygon layer to remove all islands lying within the NZ Mainland and Stewart Island.
3. This was then merged with the NZ Chatham Is island polygons (Topo, 1:50k) that have had the islands within the main island polygon removed, NZ Auckland Is Island Polygons (Topo, 1:50k), NZ Campbell Is / Motu Ihupuku Island, NZ Antipodes Is Island Polygons (Topo, 1:25k), NZ Kermadec Is Island Polygons (Topo, 1:25k), NZ Bounty Is Island Polygons (Topo, 1:25k) and NZ Snares Is / Tini Heke Island Polygons (Topo, 1:25k) layers using a merge tool.

For more detailed description of each layer refer to the layer urls above.

APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services ArcGIS REST API

This ArcGIS Online hosted feature service displays perimeters from the National Incident Feature Service (NIFS) that meet ALL of the following criteria:

This layer is the official state-maintained street transportation dataset available from MassGIS and represents all the public and a good portion of the private roadways in Massachusetts, including designations for Interstate, U.S. and State highways. Formerly known as the Massachusetts Highway Department (MHD) Roads, then the Executive Office of Transportation - Office of Transportation Planning (EOT-OTP) Roads, The MassDOT roads layer includes linework from the 1:5,000 road and rail centerlines data that were interpreted as part of the Black and White Digital Orthophoto project. The Massachusetts Department of Transportation - Office of Transportation Planning, which maintains this layer, continues to add linework from municipal and other sources and update existing linework using the most recent color orthophoto imagery as a base. In addition to the new linework, the attribute table includes all "road inventory" items maintained in MassDOT's linear referencing system.The layer is up-to-date through April 3, 2012.In ArcSDE this layer is named EOTROADS_ARC.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Potential stewardship for Baltimore City summarized by block group. PRIZM 5, 15, and 62 classes are also present. PRIZM is the Potential Rating Index by Zip code Markets produced by the Claritas corportation - (http://www.clusterbigip1.claritas.com/claritas/Default.jsp). Potential stewardship is that land within a parcels not occupied by buildings, that is land that could potentially undergo "greening." Not Realized Potential Stewardship is the land not occupied by buildings or existing vegetation, and is thus the land that is potentially available for "greening" initiatives. This dataset provides several summarizations at the block group level: 1) total potential stewardship area, 2) not realized potential stewardship, 3) normalized potential stewardship (potential stewardship area / block group area), 4) normalized not realized potential stewardship (not realized potential stewardship area / block group area), and 5) tree potential stewardship area.

   The potential stewardship was calculated using parcel data, building footprints, and GDT census block groups. Building footprints were erased from the parcel area, resulting in a layer indicating the potential stewardship for each parcel. The potential stewardship layer was then unioned MD DNR's SUFA vegetation layer. All polygons corresponding to water features were deleted since water features cannot undergo "greening."  All polygons that did fall in the potential stewardship area were deleted. This resulted in a layer in which the polygons represented the potential stewardship land along with the potential stewardship land occupied by either grass or trees. This layer was then intersected with the census block group layer resulting in a layer that had the potential stewardship land, potential stewardship vegetation, and block group IDs. All attributes were then summarized at the block group level.


   Total Potential Stewardship (Tot_PotStew) is the area of parcel land in a block group that is not occupied by buildings or water. Not Realized Potential Stewardship (NotReal_PotStew) is the area of parcel land in a block group that is not occupied by buildings, water, or vegetation, and is thus the land that is actually available for greening. Normalized Potential Stewardship (Norm_PotStew) is the Potential Stewardship area � Block Group area. Normalized Not Realized Potential Stewardship (Norm_NotReal_PotStew) is the Not Realized Potential Stewardship area � Block Group area. Summations of grass (Grass), tree (Trees), and vegetation (Tot_Veg) area within the potential steward zone are also presented.

   Tree potential stewardship (Tree_PotStew) was calculated by identifying the land that is available for plating trees, i.e. not building, water, or existing trees. Normalized tree potential stewardship (Norm_Tree_Pot_Stew) was calculated by dividing by the area of the block group. Standardized tree potential stewardship (Std_Tree_PotStew) was calculated from the normalized tree potential stewardship: ((value - min) / range) * 100.


   A cursory analysis of the parcel data indicated that parcel data was outdated for the following block groups: 245102503031, 245102503032, and 245102503033.


   Note: transportation networks are not part of the parcel data, and thus were appropriately not part of this analysis.

FEMA provides access to the National Flood Hazards Layer (NFHL) through web mapping services. The maps depict effective flood hazard information and supporting data. The primary flood hazard classification is indicated in the Flood Hazard Zones layer.The NFHL layers include:Flood hazard zones and labelsRiver Miles MarkersCross-sections and coastal transects and their labelsLetter of Map Revision (LOMR) boundaries and case numbersFlood Insurance Rate Map (FIRM) boundaries, labels and effective datesCoastal Barrier Resources System (CBRS) and Otherwise Protected Area (OPA) unitsCommunity boundaries and namesLeveesHydraulic and flood control structuresProfile and coastal transect baselinesLimit of Moderate Wave Action(LiMWA)Not all effective Flood Insurance Rate Maps (FIRM) have GIS data available. To view a list of available county and single-jurisdiction flood study data in GIS format and check the status of the NFHL GIS services, please visit the NFHL Status Page.Preliminary & Pending National Flood Hazard LayersThe Preliminary and Pending NFHL dataset represents the current pre-effective flood data for the country. These layers are updated as new preliminary and pending data becomes available, and data is removed from these layers as it becomes effective.For more information, please visit FEMA's website.To download map panels or GIS Data, go to: NFHL on FEMA GeoPlatform.Preliminary & Pending DataPreliminary data are for review and guidance purposes only. By viewing preliminary data and maps, the user acknowledges that the information provided is preliminary and subject to change. Preliminary data are not final and are presented in this national layer as the best information available at this time. Additionally, preliminary data cannot be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove preliminary data once pending data are available.Pending data are for early awareness of upcoming changes to regulatory flood map information. Until the data becomes effective, when it will appear in FEMA's National Flood Hazard Layer (NFHL), the data should not be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove pending data once effective data are available.To better understand Preliminary data please see the View Your Community's Preliminary Flood Hazard Data webpage.FEMA GeoPlatformFEMA's GIS flood map services are available through FEMAs GeoPlatform, an ArcGIS Online portal containing a variety of FEMA-related data.To view the NFHL on the FEMA GeoPlatform go to NFHL on FEMA GeoPlatform.To view the Preliminary and Pending national layers on the FEMA Geoplatform go to FEMA's Preliminary & Pending National Flood Hazard Layer.Technical InformationFlood hazard and supporting data are developed using specifications for horizontal control consistent with 1:12,000–scale mapping. If you plan to display maps from the NFHL with other map data for official purposes, ensure that the other information meets FEMA’s standards for map accuracy.The minimum horizontal positional accuracy for base map hydrographic and transportation features used with the NFHL is the NSSDA radial accuracy of 38 feet. United States Geological Survey (USGS) imagery and map services that meet this standard can be found by visiting the Knowledge Sharing Site (KSS) for Base Map Standards (420). Other base map standards can be found at https://riskmapportal.msc.fema.gov/kss/MapChanges/default.aspx. You will need a username and password to access this information.The NFHL data are from FEMA’s FIRM databases. New data are added continually. The NFHL also contains map changes to FIRM data made by LOMRs.The NFHL is stored in North American Datum of 1983, Geodetic Reference System 80 coordinate system, though many of the NFHL GIS web services support the Web Mercator Sphere projection commonly used in web mapping applications.Organization & DisplayThe NFHL is organized into many data layers. The layers display information at map scales appropriate for the data. A layer indicating the availability of NFHL data is displayed at map scales smaller than 1:250,000, regional overviews at map scales between 1:250,000 and 1:50,000, and detailed flood hazard maps at map scales of 1:50,000 and larger. The "Scalehint" item in the Capabilities file for the Web Map Service encodes the scale range for a layer.In addition, there are non-NFHL datasets provided in the GIS web services, such as information about the availability of flood data and maps, the national map panel scheme, and point locations for LOMA and LOMR-Fs. The LOMA are positioned less accurately than are the NFHL data.Layers in the public NFHL GIS services:Use the numbers shown below when referencing layers by number.0. NFHL Availability1. LOMRs2. LOMAs3. FIRM Panels4. Base Index5. PLSS6. Toplogical Low Confidence Areas7. River Mile Markers8. Datum Conversion Points9. Coastal Gages10. Gages11. Nodes12. High Water Marks13. Station Start Points14. Cross-Sections15. Coastal Transects16. Base Flood Elevations17. Profile Baselines18. Transect Baselines19. Limit of Moderate Wave Action20. Water Lines21. Coastal Barrier Resources System Area22. Political Jurisdictions23. Levees24. General Structures25. Primary Frontal Dunes26. Hydrologic Reaches27. Flood Hazard Boundaries28. Flood Hazard Zones29. Submittal Information30. Alluvial Fans31. Subbasins32. Water Areas

Data in this feature class shows the current zoning for all parcels in Sandy Springs. This dataset is used to create the Official Zoning Map for the City of Sandy Springs, GA. Details regarding the Zoning regulations and Development code for the city can be found on the city's website. Layers used for the Community Development GIS viewer. Caution! This layer is used in the Community Development public application. Do not delete this unless the Zoning Layers in that application has been re-mapped to another source.

This hosted feature layer-view aggregates Damage Inspections (DINS) and debris removal information from Environmental Protection Agency (EPA), US Army Corps of Engineers (USACE), and the consultant TetraTech at the parcel level. ROE (right-of-entry) means property owners opted-in. EPA info has been finalized.On this layer, TetraTech and USACE info is currently updated Mon-Fri by around 9:00am.The parcels with DINS are used as a base:https://lacounty.maps.arcgis.com/home/item.html?id=a27b7a1aab2d411b9e389b241f1df95bThe EPA parcels were also referenced:https://lacounty.maps.arcgis.com/home/item.html?id=f1843b0f89dc4c3bb2034ebde76876baUsed in their AGOL site:https://storymaps.arcgis.com/collections/13a8b227ac104bb1b1fa9592c92debe3The TetraTech attributes came from a GIS source from their dashboard:https://tt-emi.maps.arcgis.com/apps/dashboards/874a690d69694d2685d83d07a320e6ddThe USACE attributes came from their GIS dashboard:https://jecop-public.usace.army.mil/portal/apps/experiencebuilder/experience/?id=efbee5617ffa4d17b572d5f312004806

These data provide an accurate high-resolution shoreline compiled from imagery of Galveston Bay, Clear Lake to La Porte, TX . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://www.fisheries.noaa.gov/inport/item/39808

CAMA_2004_HOWA

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, CAMA, Database, Structure, Appraisal




   Summary


   Detailed structural information for parcels.


   Description


   The CAMA (Computer Assisted Mass Appraisal) Database is created on a yearly basis using data obtained from the State Department of Assessments and Taxation (SDAT). Each yearly download contains additional residential housing characteristics as available for parcels included in the CAMA Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab.


   It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields).


   A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 897 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords."


   Credits


   Maryland Department of Planning


   Use limitations


   BES use only.


   Extent



   West -77.186932  East -76.699484 

   North 39.373967  South 39.100772 




   Scale Range

   There is no scale range for this item.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

CAMA_2004_BACI File Geodatabase Feature Class Thumbnail Not Available Tags Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, CAMA, Database, Structure, Appraisal Summary Detailed structural information for parcels. Description The CAMA (Computer Assisted Mass Appraisal) Database is created on a yearly basis using data obtained from the State Department of Assessments and Taxation (SDAT). Each yearly download contains additional residential housing characteristics as available for parcels included in the CAMA Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 235 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." Credits Maryland Department of Planning Use limitations BES use only. Extent West -76.713415 East -76.526101 North 39.374324 South 39.200707 Scale Range There is no scale range for this item.