This script will prompt the user for a path to a file geodatabase or a sde geodatabase connection file. Then the script will loop through the feature classes\tables and document details about the attribute rules. All of the data gathered is written to a csv file. This is a Jupyter Notebook written using arcpy.Sources used to develop this notebook:Iterate through SDE to find and export FCs with Attribute Rules with python?Attribute Rule propertiesA Python script to Automate Attribute Rules Deployment

The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

*This dataset is authored by ESRI and is being shared as a direct link to the feature service by Pend Oreille County. NHD is a primary hydrologic reference used by our organization.The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesCoordinate System: Web Mercator Auxiliary Sphere Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American Samoa Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not.Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this Feature Layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.

The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution. Dataset Summary Phenomenon Mapped: Surface waters and related features of the United States and associated territories Geographic Extent: Shared Drainage Basins- Canada and the U.S. Projection: Web Mercator Auxiliary Sphere  Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000 Source: USGS Update Frequency: Annual Publication Date: July 2022 This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema. Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values. What can you do with this layer? Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro. ArcGIS Online Add this layer to a map in the map viewer. The layer or a map containing it can be used in an application.  Change the layer’s transparency and set its visibility range Open the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table. Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbology Add labels and set their properties Customize the pop-up Use as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data. ArcGIS Pro Add this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the data Open table and make interactive selections with the map Modify the pop-ups Apply Definition Queries to create sub-sets of the layer This layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.

User guide for the ArcGIS Online Statewide Traffic Count AppThe guide covers essential aspects, including:Map Functions Overview: This section details the basic interactive functions of the map, including zooming, panning, and identifying features. It will explain how to navigate the map interface effectively, find specific locations, and understand the map's overall layout and controls. Turn Layers On and Off: This portion of the guide will teach users how to control the visibility of different data layers within the map. Users will learn how to toggle layers on and off to customize the map display, focusing on specific traffic count data or related information. This allows for a more focused analysis of the data. Attribute Table and Export Data: This section explains how to access and utilize the attribute table associated with the traffic count data. Users will learn how to view detailed information about each traffic count location, including specific count values, dates, and other relevant attributes. Furthermore, this section will instruct how to export the attribute table data into formats like CSV or Excel for further analysis outside of the online application. Downloading Data: This portion of the guide will explain how to download the traffic count data. It will explain what file types are available for download, and any restrictions that are placed on the data.

(Link to Metadata) EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. https://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfmField Descriptions:OBJECTID: Internal feature number, automatically generated by Esri software.SEGMENTID: Unique segment ID.ARCID: Arc identifier, unique statewide. The ARCID is a unique identifier for every ARC in the EmergencyE911_RDS data layer.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East, etc.GEONAMEID: Unique ID for each road name.PRIMARYNAME: Primary name.ALIAS1: Alternate road name 1.ALIAS2: Alternate road name 2.ALIAS3: Alternate road name 3.ALIAS4: Alternate road name 4.ALIAS5: Alternate road name 5.COMMENTS: Free text field for miscellaneous comments.ONEWAY: One-way street. Uses the Oneway domain*.NO_MSAG:MCODE: Municipal code.LESN: Left side of road Emergency Service Number.RESN: Right side of road Emergency Service Number.LTWN: Left side of road town.RTWN: Right side of road town.LLO_A: Low address for left side of road.RLO_A: Low address for right side of road.LHI_A: High address for left side of road.RHI_A: High address for right side of road.LZIP: Left side of road zip code.RZIP: Right side of road zip code.LLO_TRLO_TLHI_TRHI_TRTNAME: Route name.RTNUMBER: Route number.HWYSIGN: Highway sign.RPCCLASSAOTCLASS: Agency of Transportation class. Uses AOTClass domain**.ARCMILES: ESRI ArcGIS miles.AOTMILES: Agency of Transportation miles.AOTMILES_CALC:UPDACT:SCENICHWY: Scenic highway.SCENICBYWAY: Scenic byway.FORMER_RTNAME: Former route name.PROVISIONALYEAR: Provisional year.ANCIENTROADYEAR: Ancient road year.TRUCKROUTE: Truck route.CERTYEAR:MAPYEAR:UPDATEDATE: Update date.GPSUPDATE: Uses GPSUpdate domain***.GlobalID: GlobalID.STATE: State.GAP: Gap.GAPMILES: Gap miles.GAPSTREETID: Gap street ID.FIPS8:FAID_S:RTNUMBER_N:LCOUNTY:RCOUNTY:PRIMARYNAME1:SOURCEOFDATA: Source of data.COUNTRY: Country.PARITYLEFT:PARITYRIGHT:LFIPS:RFIPS:LSTATE:RSTATE:LESZ:RESZ:SPEED_SOURCE: Speed source.SPEEDLIMIT: Speed limit.MILES: Miles.MINUTES: Minutes.Shape: Feature geometry.Shape_Length: Length of feature in internal units. Automatically computed by Esri software.*Oneway Domain:N: NoY: Yes - Direction of arcX: Yes - Opposite direction of arc**AOTClass Domain:1: Town Highway Class 1 - undivided2: Town Highway Class 2 - undivided3: Town Highway Class 3 - undivided4: Town Highway Class 4 - undivided5: State Forest Highway6: National Forest Highway7: Legal Trail. Legal Trail Mileage Approved by Selectboard after the enactment of Act 178 (July 1, 2006). Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trail versus trails that had traditionally been shown on the maps. Towns have until 2015 to map all Class 1-4 and Legal Trails, based on new changes in VSA Title 19.8: Private Road - No Show. Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes.9: Private road, for display on local maps10: Driveway (put in driveway)11: Town Highway Class 1 - North Bound12: Town Highway Class 1 - South Bound13: Town Highway Class 1 - East Bound14: Town Highway Class 1 - West Bound15: Town Highway Class 1 - On/Off Ramp16: Town Highway Class 1 - Emergency U-Turn20: County Highway21: Town Highway Class 2 - North Bound22: Town Highway Class 2 - South Bound23: Town Highway Class 2 - East Bound24: Town Highway Class 2 - West Bound25: Town Highway Class 2 - On/Off Ramp30: State Highway31: State Highway - North Bound32: State Highway - South Bound33: State Highway - East Bound34: State Highway - West Bound35: State Highway - On/Off Ramp40: US Highway41: US Highway - North Bound42: US Highway - South Bound43: US Highway - East Bound44: US Highway - West Bound45: US Highway - On/Off Ramp46: US Highway - Emergency U-Turn47: US Highway - Rest Area50: Interstate Highway51: Interstate Highway - North Bound52: Interstate Highway - South Bound53: Interstate Highway - East Bound54: Interstate Highway - West Bound55: Interstate Highway - On/Off Ramp56: Interstate Highway - Emergency U-Turn57: Interstate Highway - Rest Area59: Interstate Highway - Other65: Ferry70: Unconfirmed Legal Trail71: Unidentified Corridor80: Proposed Highway Unknown Class81: Proposed Town Highway Class 182: Proposed Town Highway Class 283: Proposed Town Highway Class 384: Proposed State Highway85: Proposed US Highway86: Proposed Interstate Highway87: Proposed Interstate Highway - Ramp88: Proposed Non-Interstate Highway - Ramp89: Proposed Private Road91: New - Class Unknown92: Military - no public access93: Public - Class Unknown95: Class Under Review96: Discontinued Road97: Discontinued Now Private98: Not a Road99: Unknown***GPSUpdate Domain:Y: Yes - Needs GPS UpdateN: No - Does not need GPS UpdateG: GPS Update CompleteV: GPS Update Complete - New RoadX: Unresolved Segment

In late September 2017, intense precipitation associated with Hurricane Maria caused extensive landsliding across Puerto Rico. Much of the Las Marias municipality in central-western Puerto Rico was severely impacted by landslides., Landslide density in this region was mapped as greater than 25 landslides/km2 (Bessette-Kirton et al., 2019). In order to better understand the controlling variables of landslide occurrence and runout in this region, two 2.5-km2 study areas were selected and all landslides within were manually mapped in detail using remote-sensing data. Included in the data release are five separate shapefiles: geographic areas representing the mapping extent of the four distinct areas (map areas, filename: map_areas), initiation location polygons (source areas, filename: SourceArea), polygons of the entire impacted area consisting of source, transport, and deposition (affected areas, filename: AffectArea), points on the furthest upslope extent of the landslide source areas (headscarp point, filename: HSPoint), and lines reflecting the approximate travel paths from the furthest upslope extent to the furthest downslope extent of the landslides (runout lines, filename: RunoutLine). These shapefiles contain qualitative attributes interpreted from the aerial imagery (such as geomorphic setting and impact of human activity) and qualitative attributes extracted from the geospatial data (such as source area length, width, and depth), as well as attributes extracted from other sources (such as geology and soil properties). A table detailing each attribute, attribute abbreviations, the possible choices for each attribute, and a short description of each attribute is provided as a table in the file labeled AttributeDescription.docx. The headscarp point shapefile attribute tables contain closest distance between headscarp and paved road (road_d_m; road data from U.S. Census Bureau, 2015). The runout line shapefile attribute table reflects if the landslide was considered independently unmappable past a road or river (term_drain), the horizontal length of the runout (length_m), the fall height from the headscarp to termination (h_m), the ratio of fall height to runout length (hlratio), distance to nearest paved road (road_d_m), and the watershed area upslope from the upper end of the runout line (wtrshd_m2). All quantitative metrics were calculated using tools available in ESRI ArcMap v. 10.6. The source area shapefile attribute table reflects general source area vegetation (vegetat) and land use (land_use), whether the slide significantly disaggregated during movement (flow), the failure mode (failmode), if the slide was a reactivation of a previous one (reactivate), if the landslide directly impacted the occurrence of another slide (ls_complex), the proportion of source material that left the source area (sourc_evac), the state of the remaining material (remaining), the curvature of the source area (sourc_curv), potential human impact on landslide occurrence (human_caus), potential landslide impact on human society (human_effc), if a building exists within 10 meters of the source area (buildng10m), if a road exists within 50 meters of the source area (road50m), the planimetric area of the source area (area_m2), the dimension of the source area perpendicular to the direction of motion (width_m), the dimension of the source area parallel to the direction of motion (length_m), the geologic formation of the source area (FMATN; from Bawiec, W.J., 1998), the soil type of the source area (MUNAME; from Acevido, G., 2020), the root-zone (0-100 cm deep) soil moisture estimated by the NASA SMAP mission for 9:30 am Atlantic Standard Time on 21 September 2017 (the day after Hurricane MarÃa) (smap; NASA, 2017), the average precipitation amount in the source area for the duration of the hurricane (pptn_mm; from Ramos-Scharrón, C.E., and Arima, E., 2019), the source area mean slope (mn_slp_d), the source area median slope (mdn_slp_d), the average depth change of material from the source area after the landslide (mn_dpth_m), the median depth change of material from the source area after the landslide (mdn_dpt_m), the sum of the volumetric change of material in the source area after the landslide (ldr_sm_m3), the major geomorphic landform of the source (maj_ldfrm), and the landcover of the source area (PRGAP_CL; from Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004). The affected area shapefile attribute table reflects the general affected area vegetation type (vegetat), the major geomorphic landform on which the landslide occurred (maj_ldfrm), whether the slide disaggregated during movement (flow), the general land use (land_use), the planimetric area of the affected area (area_m2), the dominant geologic formation of the affected area (FMATN; from Bawiec, W.J., 1998), the dominant soil type of the affected area (MUNAME; from Acevido, G., 2020), the sum of the volumetric change of material in all the contributing source areas for the affected area (Sum_ldr_sm), the average volumetric change of material in all the contributing source areas for the affected area (Avg_ldr_sm), if the landslide was considered independently unmappable past a road or river (term_drain), the number of contributing source areas to the affected area (num_srce), and the dominant landcover of the affected area (PRGAP_CL; from Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004). Mapping was conducted using aerial imagery collected between 9-15 October 2017 at 25-cm resolution (Quantum Spatial, Inc., 2017), a 1-m-resolution pre-event lidar digital elevation model (DEM) (U.S. Geological Survey, 2018), and a 1-m-resolution post-event lidar DEM (U.S. Geological Survey, 2020). In order to accurately determine the extent of the mapped landslides and to verify the georeferencing of the aerial imagery, aerial photographs were overlain with each DEM as well as a pre- and post-event lidar difference (2016-2018), and corrections were made as needed. Additional data sources described in the AttributeDescription document and metadata were used to extract spatial data once mapping was complete and results were appended to the shapefile attribute tables. Data in this release are provided as ArcGIS point (HSPoint), line (RunoutLine), and polygon (AffectArea and SourceArea) feature class files. Bessette-Kirton, E.K., Cerovski-Darriau, C., Schulz, W.H., Coe, J.A., Kean, J.W., Godt, J.W, Thomas, M.A., and Hughes, K. Stephen, 2019, Landslides Triggered by Hurricane Maria: Assessment of an Extreme Event in Puerto Rico: GSA Today, v. 29, doi:10.1130/GSATG383A.1 U.S. Census Bureau, 2015, 2015 TIGER/Line Shapefiles, State, Puerto Rico, primary and secondary roads State-based Shapefile: United States Census Bureau, accessed September 12, 2019, at http://www2.census.gov/geo/tiger/TIGER2015/ PRISECROADS/tl_2015_72_prisecroads.zip. Bawiec, W.J., 1998, Geology, geochemistry, geophysics, mineral occurrences and mineral resource assessment for the Commonwealth of Puerto Rico: U.S. Geological Survey Open-File Report 98-38, https://pubs.usgs.gov/of/1998/of98-038/ (accessed May 2020). Acevido, G., 2020, Soil Survey of Arecibo Area of Norther Puerto Rico: United States Department of Agriculture, Soil Conservation Service. National Aeronautics and Space Administration [NASA], 2017, SMAP L4 Global 3-hourly 9 km EASE-Grid Surface and Root Zone Soil Moisture Analysis Update, Version 4: National Snow & Ice Data Center web page, accessed September 12, 2019, at https://nsidc.org/data/SPL4SMAU/versions/4. Ramos-Scharrón, C.E., and Arima, E., 2019, Hurricane MarÃa’s precipitation signature in Puerto Rico—A conceivable presage of rains to come: Scientific Reports, v. 9, no. 1, article no. 15612, accessed February 28, 2020, at https://doi.org/10.1038/ s41598-019-52198-2. Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004, Development of a 2001 National Landcover Database for the United States: Photogrammetric Engineering and Remote Sensing, Vol. 70, No. 7, July 2004, pp. 829-840. Quantum Spatial, Inc., 2017, FEMA PR Imagery: https://s3.amazonaws.com/fema-cap-imagery/Others/Maria (accessed October 2017). U.S. Geological Survey, 2018, USGS NED Original Product Resolution PR Puerto Rico 2015: http://nationalmap.gov/elevation.html (accessed October 2018). U.S. Geological Survey, 2020, USGS NED Original Product Resolution PR Puerto Rico 2018: http://nationalmap.gov/elevation.html (accessed June 2020). Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government

The U.S. Defense Department oversees the USA"s armed forces and manages over 30 million acres of land. With over 2.8 million service members and civilian employees the department is the world"s largest employer.Dataset SummaryPhenomenon Mapped: Lands managed by the U.S. Department of DefenseGeographic Extent: United States, Guam, Puerto RicoData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: DOD Military Installations Ranges and Training Areas layer. Publication Date: May 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Department of Defense lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "department of defense" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "department of defense" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

The US National Park Service manages 84.4 million acres that include the United States" 63 national parks, many national monuments, and other conservation and historical properties. These lands range from the 13 million acre Wrangell-St. Elias National Park and Preserve in Alaska to the 0.02 acre Thaddeus Kosciuszko National Memorial in Pennsylvania.Dataset SummaryPhenomenon Mapped: Administrative boundaries of U.S. National Park Service landsGeographic Extent: 50 United States, District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana IslandsData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: NPS Administrative Boundaries of National Park System Units layerPublication Date: April, 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Park Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "national park service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "national park service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

The US Fish and Wildlife Service manages the United States" 573 National Wildlife Refuges and thousands of small wetlands and other special management areas. These lands cover more than 150 million acres that protect fish, wildlife, plants, and their habitats.Dataset SummaryPhenomenon Mapped: United States lands managed by the US Fish and Wildlife ServiceGeographic Extent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, and the Northern Mariana Islands. The layer also includes Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Data Coordinate System: WGS 1984Visible Scale: The data is visible at all scales.Source: USFWS Interest Simplified layerPublication Date: January 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Fish and Wildlife Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "fish and wildlife service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "fish and wildlife service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

One-eighth of the United States (247.3 million acres) is managed by the Bureau of Land Management. As part of the Department of the Interior, the agency oversees the 30 million acre National Landscape Conservation System, a collection of lands that includes 221 wilderness areas, 23 national monuments and 636 other protected areas. Bureau of Land Management Lands contain over 63,000 oil and gas wells and provide forage for over 18,000 grazing permit holders on 155 million acres of land. Dataset SummaryPhenomenon Mapped: United States lands managed by the Bureau of Land ManagementGeographic Extent: Contiguous United States and AlaskaData Coordinate System: WGS 1984Visible Scale: The data is visible at all scales but draws best at scales larger than 1:2,000,000.Source: BLM Surface Management Agency layer, Rasterized by Esri from features May 2025.Publication Date: December 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Bureau of Land Management lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "bureau of land management" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "bureau of land management" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

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)

In late September 2017, intense precipitation associated with Hurricane Maria caused extensive landsliding across Puerto Rico. Much of the Utuado municipality was characterized as a severely impacted area, or having landslides at a density of greater than 25 landslides/km2 (Bessette-Kirton et al., 2019). In order to better understand the controlling variables of landslide occurrence and runout in this region, four 3.0-km2 study areas were selected and all landslides within were mapped in detail using remote-sensing data. Four separate shapefiles were produced: initiation location polygons (source areas), polygons of the entire impacted area consisting of source, transport, and deposition (affected areas), points on the furthest upslope extent of the landslide source areas (headscarp point), and lines reflecting the approximate travel paths from the furthest upslope extent to the furthest downslope extent of the landslides (runout lines). These shapefiles contain a number of attributes, some subjective (including general geomorphic setting and impact of human activity), some geometric (including length, width, and depth), and others involving the underlying geology and soil of the landslides. A table detailing each attribute, attribute abbreviations, the possible choices for each attribute, and a short description of each attribute is provided as a table in the file labeled AttributeDescription.docx. The headscarp point shapefile attribute tables contain closest distance between headscarp and paved road (road_d_m; road data from U.S. Census Bureau, 2015). The runout line shapefile attribute table reflects if the landslide was considered independently unmappable past a road or river (term_drain), the horizontal length of the runout (length_m), the fall height from the headscarp to termination (h_m), the ratio of fall height to runout length (hlratio), distance to nearest paved road (road_d_m), and the watershed area upslope from the upper end of the runout line (wtrshd_m2). All quantitative metrics were calculated using tools available in ESRI ArcMap v. 10.6. The source area shapefile attribute table reflects general source area vegetation (vegetat) and land use (land_use), whether the slide significantly disaggregated during movement (flow), the failure mode (failmode), if the slide was a reactivation of a previous one (reactivate), if the landslide directly impacted the occurrence of another slide (ls_complex), the proportion of source material that left the source area (sourc_evac), the state of the remaining material (remaining), the curvature of the source area (sourc_curv), potential human impact on landslide occurrence (human_caus), potential landslide impact on human society (human_effc), if a building exists within 10 meters of the source area (buildng10m), if a road exists within 50 meters of the source area (road50m), the planimetric area of the source area (area_m2), the dimension of the source area perpendicular to the direction of motion (width_m), the dimension of the source area parallel to the direction of motion (length_m), the geologic formation of the source area (FMATN; from Bawiec, W.J., 1998), the soil type of the source area (MUNAME; from Acevido, G., 2020), the root-zone (0-100 cm deep) soil moisture estimated by the NASA SMAP mission for 9:30 am Atlantic Standard Time on 21 September 2017 (the day after Hurricane María) (smap; NASA, 2017), the average precipitation amount in the source area for the duration of the hurricane (pptn_mm; from Ramos-Scharrón, C.E., and Arima, E., 2019), the source area mean slope (mn_slp_d), the source area median slope (mdn_slp_d), the average depth change of material from the source area after the landslide (mn_dpth_m), the median depth change of material from the source area after the landslide (mdn_dpt_m), the sum of the volumetric change of material in the source area after the landslide (ldr_sm_m3), the major geomorphic landform of the source (maj_ldfrm), and the landcover of the source area (PRGAP_CL; from Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004). The affected area shapefile attribute table reflects the general affected area vegetation type (vegetat), the major geomorphic landform on which the landslide occurred (maj_ldfrm), whether the slide disaggregated during movement (flow), the general land use (land_use), the planimetric area of the affected area (area_m2), the dominant geologic formation of the affected area (FMATN; from Bawiec, W.J., 1998), the dominant soil type of the affected area (MUNAME; from Acevido, G., 2020), the sum of the volumetric change of material in all the contributing source areas for the affected area (Sum_ldr_sm), the average volumetric change of material in all the contributing source areas for the affected area (Avg_ldr_sm), if the landslide was considered independently unmappable past a road or river (term_drain), the number of contributing source areas to the affected area (num_srce), and the dominant landcover of the affected area (PRGAP_CL; from Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004). Mapping was conducted using mostly 15-cm-resolution aerial imagery collected between 9-15 October 2017 (Quantum Spatial, Inc., 2017), a 1-m-resolution pre-event lidar DEM (U.S. Geological Survey, 2018), and a 1-m-resolution post-event lidar DEM (U.S. Geological Survey, 2020). In order to accurately determine the extent of the mapped landslides and to verify the georeferencing of the aerial imagery, aerial photographs were overlain with the DEMs and a generated lidar difference (2016-2018), and corrections were made as needed. Due to cloud cover, shadowed photographs, variable clarity, and the occasional lack of available overlapping aerial imagery, some qualitatively determined attributes were difficult to interpret and the data reflects a certain margin of error. Additional data sources were used to extract spatial data once mapping was complete and results were appended to the shapefile attribute tables. Data in this release are provided as ArcGIS point (HSPoint), line (RunoutLine), and polygon (AffectArea and SourceArea) feature class files. Bessette-Kirton, E.K., Cerovski-Darriau, C., Schulz, W.H., Coe, J.A., Kean, J.W., Godt, J.W, Thomas, M.A., and Hughes, K. Stephen, 2019, Landslides Triggered by Hurricane Maria: Assessment of an Extreme Event in Puerto Rico: GSA Today, v. 29, doi:10.1130/GSATG383A.1 U.S. Census Bureau, 2015, 2015 TIGER/Line Shapefiles, State, Puerto Rico, primary and secondary roads State-based Shapefile: United States Census Bureau, accessed September 12, 2019, at http://www2.census.gov/geo/tiger/TIGER2015/ PRISECROADS/tl_2015_72_prisecroads.zip. Bawiec, W.J., 1998, Geology, geochemistry, geophysics, mineral occurrences and mineral resource assessment for the Commonwealth of Puerto Rico: U.S. Geological Survey Open-File Report 98-38, https://pubs.usgs.gov/of/1998/of98-038/ (accessed May 2020). Acevido, G., 2020, Soil Survey of Arecibo Area of Norther Puerto Rico: United States Department of Agriculture, Soil Conservation Service. National Aeronautics and Space Administration [NASA], 2017, SMAP L4 Global 3-hourly 9 km EASE-Grid Surface and Root Zone Soil Moisture Analysis Update, Version 4: National Snow & Ice Data Center web page, accessed September 12, 2019, at https://nsidc.org/data/SPL4SMAU/versions/4. Ramos-Scharrón, C.E., and Arima, E., 2019, Hurricane María’s precipitation signature in Puerto Rico—A conceivable presage of rains to come: Scientific Reports, v. 9, no. 1, article no. 15612, accessed February 28, 2020, at https://doi.org/10.1038/ s41598-019-52198-2. Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004, Development of a 2001 National Landcover Database for the United States: Photogrammetric Engineering and Remote Sensing, Vol. 70, No. 7, July 2004, pp. 829-840. Quantum Spatial, Inc., 2017, FEMA PR Imagery: https://s3.amazonaws.com/fema-cap-imagery/Others/Maria (accessed October 2017). U.S. Geological Survey, 2018, USGS NED Original Product Resolution PR Puerto Rico 2015: http://nationalmap.gov/elevation.html (accessed October 2018). U.S. Geological Survey, 2020, USGS NED Original Product Resolution PR Puerto Rico 2018: http://nationalmap.gov/elevation.html (accessed June 2020). Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.

The map package files (merged.mpk) were prepared and can be opened by Arc Gis 10.8.2 and above versions. The map package data files include the SAR data (RISAT-1 from ISRO-Bhoonidhi) in HH,HV- polarizations, DEM ( USGS ) and IRS LISS III (Bhuvan-NRSC) data with the 30m spatial resolution were downloaded from the respective websites. Geology data in 1:50,000 scale is downloaded from GSI Bhukosh. The resolution merged data of Optical and SAR data has been prepared using Brovey transform in ERDAS 2015 software. The output file have advantages of both optical and microwave features. Extracted the Lineaments(.shp) from the coupled data of merged SAR and improved and verified with the DEM, Optical, SAR and Geology data sets. All these data generation and Statistical calculation done with the help of ArcGIS software. ArcGIS guide will help to create shape files, Attribute table calculations of length, classification. Azumutal trend calculations of each lineaments done using Split lines and other geometric calculations giving the trend of each lineament and finally export the map (All .jpg files). Rose diagrams was prepared based on the trend of lineaments with the help of Rockworks 17 software. The generated Azimuthal trend data in lineament shape file can be import to linears - utilites - Rose diagram. I was prepared Rose diagram of different class of lineaments using frequency calculation method. Lineaments are the linear geological features can extend from few meters to hundreds of kms. Geologically lineaments are either structural or stratigraphical, typically it will comprise fault, fold axis, bedding contacts, dyke intrusions, shear zone or a straight coast line. Mapping lineaments using remote sensing is economical, faster can act as a preliminary study. Generally lineaments have been mapped using the optical remote sensing data such as Landsat, Resourcesat etc. For India, Lineaments were mapped using the LISS III and LISS IV of Resourcesat-1 & 2 at a scale of 1:50k. However in tropical region like India, limited exposure of ground due to vegetation cover, lineaments may go unnoticed in optical remote sensing data. This problem can be overcome by Synthetic Aperture Radar (SAR) data, which can penetrate ground significantly. With the launch of RISAT-1satelite, data availability of SAR data is immense for Indian region. Aim of this study to explore the SAR data and merged SAR and optical data for lineament mapping.

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)

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)

In the United States, the federal government manages lands in significant parts of the country. These lands include 193 million acres managed by the US Forest Service in the nation's 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources.The agencies included in this layer are:Bureau of Land ManagementBureau of ReclamationDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States lands managed by six federal agencies Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DoD, USFS, USFWS, NPS, PADUS 2.1Publication Date: Various - Esri compiled and published this layer in May 2022. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Bureau of Reclamation LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

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)

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)