43 datasets found
  1. d

    Zoning Design Review Cases

    • catalog.data.gov
    • opendata.dc.gov
    • +3more
    Updated Feb 4, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    D.C. Office of the Chief Technology Officer (2025). Zoning Design Review Cases [Dataset]. https://catalog.data.gov/dataset/zoning-design-review-cases
    Explore at:
    Dataset updated
    Feb 4, 2025
    Dataset provided by
    D.C. Office of the Chief Technology Officer
    Description

    The purpose of the design review process is to: Allow for special projects to be approved by the Zoning Commission after a public hearing and a finding of no adverse impact; Recognize that some areas of the District of Columbia warrant special attention due to particular or unique characteristics of an area or project; Permit some projects to voluntarily submit themselves for design review in exchange for flexibility because the project is superior in design but does not need extra density; Promote high-quality, contextual design; and Provide for flexibility in building bulk control, design, and site placement without an increase in density or a map amendment.

  2. d

    Chinatown Design Review Boundary

    • catalog.data.gov
    • opendata.dc.gov
    • +2more
    Updated Feb 5, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Office of Planning (2025). Chinatown Design Review Boundary [Dataset]. https://catalog.data.gov/dataset/chinatown-design-review-boundary
    Explore at:
    Dataset updated
    Feb 5, 2025
    Dataset provided by
    Office of Planning
    Description

    The Chinatown Design Review Boundary as established by DCMR Title 10 Chapter 24. The purpose of Chinatown Design Review is to ensure the contribution of proposed buildings and public space projects to the Chinese identity of Chinatown.

  3. FRAP - Public Lands Ownership

    • wifire-data.sdsc.edu
    • gis-calema.opendata.arcgis.com
    • +1more
    csv, esri rest +4
    Updated Jul 18, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    CA Governor's Office of Emergency Services (2019). FRAP - Public Lands Ownership [Dataset]. https://wifire-data.sdsc.edu/dataset/frap-public-lands-ownership
    Explore at:
    geojson, kml, zip, esri rest, csv, htmlAvailable download formats
    Dataset updated
    Jul 18, 2019
    Dataset provided by
    California Governor's Office of Emergency Services
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Description

    This ownership dataset utilizes a methodology that results in a federal ownership extent that matches the Federal Responsibility Areas (FRA) footprint from CAL FIRE's State Responsibility Areas for Fire Protection (SRA) data. FRA lands are snapped to county parcel data, thus federal ownership areas will also be snapped. Since SRA Fees were first implemented in 2011, CAL FIRE has devoted significant resources to improve the quality of SRA data. This includes comparing SRA data to data from other federal, state, and local agencies, an annual comparison to county assessor roll files, and a formal SRA review process that includes input from CAL FIRE Units. As a result, FRA lands provide a solid basis as the footprint for federal lands in California (except in the southeastern desert area). The methodology for federal lands involves:

    1) snapping federal data sources to parcels;
    2) clipping to the FRA footprint;
    3) overlaying the federal data sources and using a hierarchy when sources overlap to resolve coding issues (BIA, UFW, NPS, USF, BLM, DOD, ACE, BOR);
    4) utilizing an automated process to merge “unknown” FRA slivers with appropriate adjacent ownerships;
    5) a manual review of FRA areas not assigned a federal agency by this process.

    Non-Federal ownership information was obtained from the California Protected Areas Database (CPAD), was clipped to the non-FRA area, and an automated process was used to fill in some sliver-gaps that occurred between the federal and non-federal data. Southeastern Desert Area: CAL FIRE does not devote the same level of resources for maintaining SRA data in this region of the state, since we have no fire protection responsibility. This includes almost all of Imperial County, and the desert portions of Riverside, and San Bernardino Counties. In these areas, we used federal protection areas from the current version of the Direct Protection Areas (DPA) dataset. Due to the fact that there were draw-issues with the previous version of ownership, this version does NOT fill in the areas that are not assigned to one of the owner groups (it does not cover all lands in the state). Also unlike previous versions of the dataset, this version only defines ownership down to the agency level - it does not contain more specific property information (for example, which National Forest). The option for a more detailed future release remains, however, and due to the use of automated tools, could always be created without much additional effort.This dataset includes a representation to symbolize based on the Own_Group field using the standard color scheme utilized on DPA maps.For more details about data inputs, see the Lineage section of the metadata. For detailed notes on previous versions, see the Supplemental Information section of the metadata.

    This ownership dataset is derived from CAL FIRE's SRA dataset, and GreenInfo Network's California Protected Areas Database. CAL FIRE tracks lands owned by federal agencies as part of our efforts to maintain fire protection responsibility boundaries, captured as part of our State Responsiblity Areas (SRA) dataset. This effort draws on data provided by various federal agencies including USDA Forest Service, BLM, National Park Service, US Fish and Wildlife Service, and Bureau of Inidan Affairs. Since SRA lands are matched to county parcel data where appropriate, often federal land boundaries are also adjusted to match parcels, and may not always exactly match the source federal data. Federal lands from the SRA dataset are combined with ownership data for non-federal lands from CPAD, in order to capture lands owned by various state and local agencies, special districts, and conservation organizations. Data from CPAD are imported directly and not adjusted to match parcels or other features. However, CPAD features may be trimmed if they overlap federal lands from the SRA dataset. Areas without an ownership feature are ASSUMED to be private (but not included in the dataset as such).

    This service represents the latest release of the dataset by FRAP, and is updated twice a year when new versions are released.

  4. d

    Building Energy Performance

    • catalog.data.gov
    • cleanenergy.dc.gov
    • +6more
    Updated May 21, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2025). Building Energy Performance [Dataset]. https://catalog.data.gov/dataset/building-energy-performance-e0843
    Explore at:
    Dataset updated
    May 21, 2025
    Dataset provided by
    City of Washington, DC
    Description

    The BEPS Program was created by Title III of the Clean Energy DC Omnibus Act of 2018. The BEPS is a minimum threshold of energy performance that will be no lower than the local median ENERGY STAR score by property type (or equivalent metric). The standards were created to drive energy performance in existing buildings to help meet the energy and climate goals of the Sustainable DC plan — to reduce greenhouse gas emissions and energy consumption by 50% by 2032. DOEE established the first set of Standards on January 1, 2021. Standards will then be set every 6 years, creating BEPS Periods (BEPS Period 1, BEPS Period 2, etc.). The 2021 Building Energy Performance Standards and a Guide to the 2021 BEPS are available for viewing on DOEE’s website.To improve transparency and help building owners understand how their building performs relative to the BEPS, DOEE is publishing this BEPS Disclosure that compares a building’s benchmarking data with the BEPS and provides an estimate of the building’s distance from the standard and estimated performance requirement.Please note that this dataset is based on information currently available to DOEE using calendar year 2019 benchmarking data provided by the building owner. Some buildings are still being evaluated and therefore have been designated as “Under Review” in this dataset. Building owners that believe their 2019 calendar year data is incorrect should contact the Benchmarking Help Center (info.benchmark@dc.gov). Additionally, buildings that meet certain criteria may request a variance from the standards by submitting a variance request form on the DOEE website.

  5. Coho Range [ds534]

    • catalog.data.gov
    • data.cnra.ca.gov
    • +7more
    Updated Nov 27, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Fish and Wildlife (2024). Coho Range [ds534] [Dataset]. https://catalog.data.gov/dataset/coho-range-ds534-01900
    Explore at:
    Dataset updated
    Nov 27, 2024
    Dataset provided by
    California Department of Fish and Wildlifehttps://wildlife.ca.gov/
    Description

    June 2016 VersionData Content:This data set contains all CalWater 2.2.1 Planning Watersheds (PWS) where CDFW has documented coho salmon to be present during or after 1990. It was developed for the express purpose of assisting with Coho salmon recovery planning efforts. NOTE: Acreages are calculated for area inside California only. It is important to note that this data set does not attempt to model the entire possible distribution of the species. Rather, it only represents planning watersheds intersecting the known distribution, which is based on where the species has been observed and reported. While the distribution data may indeed represent the extent of the species, generally the upstream extent of the distribution only represents the location of positive sampling or other observations.. Therefore, this data set likely represents an underestimation of the absolute geographic distribution of the species. Data Source:This watershed level data set was derived by intersecting Calwater PWS with point and line features depicting Coho salmon distribution. These features are derived from a subset of data contained in thedevelopers file geodatabase (©Environmental Science Research Institute (ESRI) 2016). This is an ongoing project developed by CDFW Northern Region Data Management and GIS with assistance from CDFW Biogeographic Data Division and Pacific States Marine Fisheries Commission. These data are based upon confirmed observations of Coho salmon. Effort has been made to identify and correct watersheds that were erroneously selected due to inaccuracies from using data of different scales. The observation data that are the basis for the distribution were compiled from a variety of disparate sources including but not limited to CDFW, U.S. Forest Service, National Marine Fisheries Service, timber companies, and the public. Forms of documentation include CDFG administrative reports, personal communications with biologists, observation reports, and literature reviews.This derived dataset is meant to be continually updated as additional information is acquired. As such, any copy of this dataset is considered to be a snapshot of the known Coho Distribution at the time of release. It is incumbent upon the user to ensure that they have the most recent version prior to making management or planning decisions.Data Usage: Examples of appropriate uses include: Coho salmon recovery planning Evaluation of future survey sites for Coho Validating Coho distribution models Examples of inappropriate uses include: Using this data to make parcel or ground level land use management decisions. Using this data set to prove or support non-existence of coho at any spatial scale. Assuming that Coho are prevalent throughout the entire watershed. All users of this data should seek the assistance of qualified professionals such as surveyors, hydrologists, or fishery biologists as needed to ensure that such users possess complete, precise, and up to date information on Coho salmon distribution and water body location. Please refer to "Use Constraints" section below.

  6. i15 LandUse Sonoma2012

    • data.ca.gov
    • data.cnra.ca.gov
    • +6more
    Updated Feb 16, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Water Resources (2022). i15 LandUse Sonoma2012 [Dataset]. https://data.ca.gov/dataset/i15-landuse-sonoma2012
    Explore at:
    arcgis geoservices rest api, kml, zip, csv, geojson, htmlAvailable download formats
    Dataset updated
    Feb 16, 2022
    Dataset authored and provided by
    California Department of Water Resourceshttp://www.water.ca.gov/
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    This map is designated as Final.

    Land-Use Data Quality Control

    Every published digital survey is designated as either ‘Final’, or ‘Provisional’, depending upon its status in a peer review process.

    Final surveys are peer reviewed with extensive quality control methods to confirm that field attributes reflect the most detailed and specific land-use classification available, following the standard DWR Land Use Legendspecific to the survey year. Data sets are considered ‘final’ following the reconciliation of peer review comments and confirmation by the originating Regional Office. During final review, individual polygons are evaluated using a combination of aerial photointerpretation, satellite image multi-spectral data and time series analysis, comparison with other sources of land use data, and general knowledge of land use patterns at the local level.

    Provisional data sets have been reviewed for conformance with DWR’s published data record format, and for general agreement with other sources of land use trends. Comments based on peer review findings may not be reconciled, and no significant edits or changes are made to the original survey data.

    The 2012 Sonoma County land use survey data was developed by the State of California, Department of Water Resources (DWR) through its Division of Integrated Regional Water Management (DIRWM) and Division of Statewide Integrated Water Management (DSIWM). Land use boundaries were digitized and land use data was gathered by staff of DWR’s North Central Region using extensive field visits and aerial photography. Land use polygons in agricultural areas were mapped in greater detail than areas of urban or native vegetation. Quality control procedures were performed jointly by staff at DWR’s DSIWM headquarters, under the leadership of Jean Woods, and North Central Region, under the supervision of Kim Rosmaier. This data was developed to aid DWR’s ongoing efforts to monitor land use for the main purpose of determining current and projected water uses. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standards version 2.1, dated March 9, 2016. DWR makes no warranties or guarantees - either expressed or implied - as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov. This data represents a land use survey of Sonoma County conducted by the California Department of Water Resources, North Central Regional Office staff. The field work for this survey was conducted during July - September 2012 by staff visiting each field and noting what was grown. The county was divided into five survey areas using major road as centerlines and other geographic features for boundaries. The county was surveyed with two teams. The linework was heads up digitized in ArcGIS 10.0 with 2010 National Agriculture Imagery Program (NAIP) one-meter imagery as the base. Field Boundaries were reviewed with ArcGIS 10.2 and NAIP 2012 imagery when it became available. The data was recombined after it was finished. The Virtual Basic Landuse Attributor was used for the survey and to start the post survey process; after converting to ArcGIS 10.2, the domain file geodatabase structure was used to attribute and help finish facilitating the post survey process. Tables were run through a Python script to put the data in the standard landuse format. ArcGIS geoprocessing tools and topology rules were used to locate errors and for quality control and assurance. Horse pastures were designated either S2 or S6. The special condition 'G' was used to denote vineyards that had sprinklers for frost protection rather than representing a cover crop as stated in the February 2009 Standard Land Use Legend used for this survey. Field Boundaries were not drawn to represent legal parcel (ownership) boundaries, or meant to be used as parcel boundaries. Images and land use boundaries were loaded onto laptop computers that were used as the field data collection tools. GPS units connected to the laptops were used to confirm surveyor's location with respect to the fields. Staff took these laptops into the field and virtually all the areas were visited to positively identify the land use. Land use codes were digitized in the field on laptop computers using ESRI ArcMAP software, version 10.0. Before final processing, standard quality control procedures were performed jointly by staff at DWR’s North Central Region, and at DSIWM headquarters under the leadership of Jean Woods. Senior Land and Water Use Supervisor. After quality control procedures were completed, the data was finalized. The positional accuracy of the digital line work, which is based upon the orthorectified NAIP imagery, is approximately 6 meters. The land use attribute accuracy for agricultural fields is high, because almost every delineated field was visited by a surveyor. The accuracy is 95 percent because some errors may have occurred. Possible sources of attribute errors are: a) Human error in the identification of crop types, b) Data entry errors.

  7. a

    Development Reviews

    • co-cumberlandgis.opendata.arcgis.com
    • opendata.co.cumberland.nc.us
    • +2more
    Updated Nov 18, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Cumberland County, NC (2016). Development Reviews [Dataset]. https://co-cumberlandgis.opendata.arcgis.com/datasets/development-reviews-1
    Explore at:
    Dataset updated
    Nov 18, 2016
    Dataset authored and provided by
    Cumberland County, NC
    Area covered
    Description

    Reviews of small and large scale development projects within Cumberland County, NC.

  8. Review

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • hub.arcgis.com
    Updated Jul 17, 2015
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri JSAPI (2015). Review [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/jsapi::review/about
    Explore at:
    Dataset updated
    Jul 17, 2015
    Dataset provided by
    Esrihttp://esri.com/
    Authors
    Esri JSAPI
    Area covered
    Description

    This map compares any two years' per capita income for counties in the U.S.Data downloaded from GeoFred application. GeoFred provides geographical economic data from the St. Louis Fed (the Federal Reserve Bank of St. Louis)Source: U.S. Bureau of Economic Analysis, Personal Income per capita, retrieved from FRED, Federal Reserve Bank of St. Louis

  9. a

    ERP Applications - Pre-Application

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • geodata.floridagio.gov
    • +4more
    Updated Oct 31, 2011
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    South Florida Water Management District (2011). ERP Applications - Pre-Application [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/babe4c8201264f5d85443ca0a452fa1a
    Explore at:
    Dataset updated
    Oct 31, 2011
    Dataset authored and provided by
    South Florida Water Management District
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    Pre-planning application locations. This data set depicts the location of pre-applications. The regulatory review process can usually be expedited if the applicant elects to participate in a pre-application conference with District engineers and environmental scientists early in the project planning process. A meeting with District staff can help the applicant and the project designers to better understand District rules and regulations, and help District staff understand the project. The District staff can outline procedures to facilitate submittal of a complete application or explain permitting requirements, as needed. Any potential permitting problems could be identified at the meeting.

  10. a

    Coastal Area Facilities Review Act Boundary for New Jersey (polygon)

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • share-open-data-njtpa.hub.arcgis.com
    • +3more
    Updated Jul 20, 2007
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NJDEP Bureau of GIS (2007). Coastal Area Facilities Review Act Boundary for New Jersey (polygon) [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/njdep::coastal-area-facilities-review-act-boundary-for-new-jersey-polygon
    Explore at:
    Dataset updated
    Jul 20, 2007
    Dataset authored and provided by
    NJDEP Bureau of GIS
    Area covered
    Description

    This data set is a graphical representation of the Coastal Areas Facilities Review Act (CAFRA) boundary, which legislates land use within the coastal area. This boundary was dissolved from the Coastal Planning Areas in New Jersey data set.

  11. Review

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • hub.arcgis.com
    Updated Jul 14, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Urban Observatory by Esri (2017). Review [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/UrbanObservatory::review-1/geoservice
    Explore at:
    Dataset updated
    Jul 14, 2017
    Dataset provided by
    Esrihttp://esri.com/
    Authors
    Urban Observatory by Esri
    Area covered
    Description

    This layer contains Gross Domestic Product (GDP) Per Capita - the total value of goods produced and services provided, divided by the total population in each country, from 1960 to 2016, expressed in 2016 US Dollars. Expressing the GDP in "per capita" terms allows for better comparisons across countries. Total GDP is available in an accompanying layer. GDP as a measure has been largely criticized as an incomplete measure of productivity and wealth, as it does not take into account production in the informal economy, quality of life, degradation to the environment, or income distribution. However, GDP is an internationally comparable measure, used in everything from banks setting interest rates to political campaign speeches.Source: World Bank, World Development Indicators.

  12. a

    Manitoba Licensed Personal Care Homes

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • geoportal.gov.mb.ca
    Updated Dec 3, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Manitoba Maps (2020). Manitoba Licensed Personal Care Homes [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/manitoba::manitoba-licensed-personal-care-homes/about
    Explore at:
    Dataset updated
    Dec 3, 2020
    Dataset authored and provided by
    Manitoba Maps
    Area covered
    Description

    This is a feature point layer of the 124 licensed personal care homes (PCHs) in Manitoba. All licensed PCHs in Manitoba are required to comply with minimum standards of care as set out in the Personal Care Home Standards Regulation under the Health Services Insurance Act. The Licensing and Compliance Branch of Manitoba Health Seniors and Active Living monitors compliance through regular review processes. PCH operators are required to take the necessary steps to address concerns identified in the course of reviews within specified time lines and must provide status updates until concerns have been addressed. PCH licences are reviewed and renewed annually and review findings are used to inform decision-making. The dataset includes the following fields (Alias (Name): Description) Regional Health Authority (Regional_Health_Authority): The name of the Regional Health Authority in which the facility is located. Community (Community): The name of the community in which the facility is located. Facility (Facility): The name of the licensed personal care home. Facility Key (Facility_Key): Primary key used to query records in the Summary Reviews table. Facility Label (Facility_Label): An abbreviated facility name suitable for use as a label in a map. Address (Address): The street address of the facility. Postal Code (Postal_Code): The postal code for the facility. Phone Number (Phone_Number): The phone number for the facility. Proprietary Status (Proprietary_Status): Refers to the ownership of the facility, either Proprietary or Non-proprietary. Language (Language): The designated language of the facility, either English or Bilingual. Bed (Beds): The number of beds in the facility. Status of Licence (Status_of_Licence): The status of the facility’s license. Possible values are Unencumbered, Under Review, or With Conditions. Owner/Operator (Owner_Operator): The individual or company that owns the facility. Website (Website): The URL for the website of the facility. Latitude (Latitude): The latitudinal coordinate in decimal degrees. Longitude (Longitude): The longitudinal coordinate in decimal degrees.This feature point layer forms part of the data for the Manitoba Personal Care Home Reporting app.

  13. a

    Manitoba Licensed Personal Care Home Summary Reviews

    • hub.arcgis.com
    • geoportal.gov.mb.ca
    Updated Dec 3, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Manitoba Maps (2020). Manitoba Licensed Personal Care Home Summary Reviews [Dataset]. https://hub.arcgis.com/maps/manitoba::manitoba-licensed-personal-care-home-summary-reviews
    Explore at:
    Dataset updated
    Dec 3, 2020
    Dataset authored and provided by
    Manitoba Maps
    Area covered
    Description

    This table contains URL links to reports on personal care home reviews completed by the Licensing and Compliance Branch of Manitoba Health, Seniors and Active Living. All licensed personal care home facilities in Manitoba are required to comply with minimum standards of care as set out in the Personal Care Home Standards Regulation under the Health Services Insurance Act. The branch monitors compliance through regular review processes. Operators of facilities are required to take the necessary steps to address concerns identified in the course of reviews within specified time lines and must provide status updates until concerns have been addressed. Licences are reviewed and renewed annually and review findings are used to inform decision-making.The table includes the following fields (Alias (Name): Description)Regional Health Authority (Regional_Health_Authority): The name of the Regional Health Authority in which the facility is located.Community (Community): The name of the community in which the facility is located.Facility (Facility): The name of the licensed personal care home.Facility Key (Facility_Key): Primary key used to link this table with the feature point layer Licensed Personal Care Homes.Review Date (Review_Date): The date the review was conducted.Review Type (Review_Type): The type of review conducted. Possible values are Regular Standards, Unannounced, Modified, Pre-Opening, or Other.Summary Link (Summary_Link): The URL link to the report.This table forms part of the data for the Manitoba Personal Care Home Reporting app.

  14. a

    Business Licenses

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • datahub.cityofwestsacramento.org
    • +3more
    Updated Apr 25, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    West Sacramento (2018). Business Licenses [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/9aec1b340e4840c5915d7209463ac38f
    Explore at:
    Dataset updated
    Apr 25, 2018
    Dataset authored and provided by
    West Sacramento
    Area covered
    Earth
    Description

    All Business Licenses that are Active, Renewed, In Review, and/or Closed within the City of West Sacramento. Dataset is updated nightly.

  15. a

    2025 Draft Budget Explorer Datasets

    • hub.arcgis.com
    • open.ottawa.ca
    • +1more
    Updated Nov 27, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Ottawa (2024). 2025 Draft Budget Explorer Datasets [Dataset]. https://hub.arcgis.com/datasets/cd6620f68d654e88b4aa1f6e0024c3f6
    Explore at:
    Dataset updated
    Nov 27, 2024
    Dataset authored and provided by
    City of Ottawa
    Description

    The Draft Budget 2025 Explorer provides insight into how the budget is created, what elements make up the budget, user-friendly interactive charts, graphs and tables to enhance financial literacy and transparency, an update on service reviews as well as highlights from over 100 lines of services that are advancing Council’s strategic priorities. The draft budget is broken down by Committee, department and service areas as described in the Table of City Services and Standing Committee reporting structure. With direction from Council, the budget is drafted and tabled for review by each Standing Committee and adopted by Council. Aside from the draft budget considered by Committees, there are four external boards who debate their budget separately. These budgets are represented in the overviews but are not broken down by committee or included in the rates, fees and charges reports. For more information on these budgets please visit the agenda for the budget tabling meeting. • Committee of Adjustment • Ottawa Police Services • Ottawa Public Health • Ottawa Public Library For complete details on the budget visit the Budget, finance and corporate planning page.Date Created: November 19th, 2024Update Frequency: As required.Accuracy, Completeness, and Known Issues: If at any point in time the figures found in this tool differ from the draft budget books or presentations at Committee, the draft budget books will be considered the accurate data.Attributes: 1_Operating_overview_expenditure1_Operating_overview_revenueAll City programs and services are funded through the City’s operating budget, which supports the dependable delivery of services that residents rely on every day.2_Capital_program_by_committee2_Capital_program_by_funding_src2_Capital_program_by_service_categoryCity infrastructure and assets are funded through the capital budget. Most of that funding goes to maintaining and fixing existing infrastructure as described in the Comprehensive Asset Management analysis. As funding allows, the City continues to fund growth, build new infrastructure and invest in the future. 3_Reserve_fund_DiscretionaryreservesReserve funds are monies set aside to fund capital expenditures, similar to having personal savings accounts for future needs. They are also used to manage unexpected expenses and to support the City’s finances for the long-term.4_Rates_fees_and_chargesRates are utility charges dependant on usage for water consumption and sewer surcharges that are found on residents' water bills. Fees are charged to users of many City services to cover part or all of the costs of providing the service. Examples of where fees are applied include transit fares, recreation program fees, planning applications and childcare fees. Development charges are one-time fees levied by municipalities on new residential and non-residential properties to help pay for a portion of the growth-related capital infrastructure requirements.5_Exp_brkd_by_committee_OPERATING5_Exp_brkd_by_committee_CAPITALThe draft budget is broken down by Committee, department and service areas as described in the Table of City Services and Standing Committee reporting structure. Each Committee is responsible for a specific portion of the operating and capital budget. Each Committee hears from Community delegations and debates the items assigned to them. Councillors can ask for amendments to each section of the budget and then all sections of the budget are brought back to Council for final a vote on adoption.6_ How_the_city_of_ottawa_compares?See how the City’s taxation compares to other major Canadian cities from 2012-2024.Data Steward: Suzanne Schnob – Financial Services ManagerData Steward Email: fcsdposting@ottawa.caDepartment or Agency: Finance and Corporate Services DepartmentBranch/Unit: Financial Strategies, Planning and Client Services

  16. WellSTAR Underground Gas Storage: Area of Review Wells

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • data.ca.gov
    • +6more
    Updated May 3, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Conservation (2019). WellSTAR Underground Gas Storage: Area of Review Wells [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/82a645ba1ed34516b591796d1f8dc801
    Explore at:
    Dataset updated
    May 3, 2019
    Dataset authored and provided by
    California Department of Conservationhttp://www.conservation.ca.gov/
    Area covered
    Description

    This online map displays California’s active Underground Gas Storage (UGS) projects and wells associated to UGS projects. Project data and well data are provided by CalGEM’s Well Statewide Tracking and Reporting System (WellSTAR). Wells are displayed by well type and the association to a UGS project.CalGEM is the Geologic Energy Management Division of the California Department of Conservation, formerly the Division of Oil, Gas, and Geothermal Resources (as of January 1, 2020).WellSTAR homepageUpdate Frequency: As Needed

  17. a

    2023 Irrigated Lands for the Mountain Home Plateau: Machine Learning...

    • data-idwr.hub.arcgis.com
    • hub.arcgis.com
    Updated May 15, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Idaho Department of Water Resources (2024). 2023 Irrigated Lands for the Mountain Home Plateau: Machine Learning Generated [Dataset]. https://data-idwr.hub.arcgis.com/documents/b5c6474cb4ae459480bb804127c4831e
    Explore at:
    Dataset updated
    May 15, 2024
    Dataset authored and provided by
    Idaho Department of Water Resources
    Description

    This raster file represents land within the Mountain Home study boundary classified as either “irrigated” with a cell value of 1 or “non-irrigated” with a cell value of 0 at a 10-meter spatial resolution. These classifications were determined at the pixel level by use of Random Forest, a supervised machine learning algorithm. Classification models often employ Random Forest due to its accuracy and efficiency at labeling large spatial datasets. To build a Random Forest model and supervise the learning process, IDWR staff create pre-labeled data, or training points, which are used by the algorithm to construct decision trees that will be later used on unseen data. Model accuracy is determined using a subset of the training points, otherwise known as a validation dataset. Several satellite-based input datasets are made available to the Random Forest model, which aid in distinguishing characteristics of irrigated lands. These characteristics allow patterns to be established by the model, e.g., high NDVI during summer months for cultivated crops, or consistently low ET for dryland areas. Mountain Home Irrigated Lands 2023 employed the following input datasets: US Geological Survey (USGS) products, including Landsat 8/9 and 10-meter 3DEP DEM, and European Space Agency (ESA) Copernicus products, including Harmonized Sentinel-2 and Global 30m Height Above Nearest Drainage (HAND). For the creation of manually labeled training points, IDWR staff accessed the following datasets: NDVI derived from Landsat 8/9, Sentinel-2 CIR imagery, US Department of Agriculture National Agricultural Statistics Service (USDA NASS) Cropland Data Layer, Active Water Rights Place of Use data from IDWR, and USDA’s National Agriculture Imagery Program (NAIP) imagery. All datasets were available for the current year of interest (2023). The published Mountain Home Irrigated Lands 2023 land classification raster was generated after four model runs, where at each iteration, IDWR staff added or removed training points to help improve results. Early model runs showed poor results in riparian areas near the Snake River, concentrated animal feeding operations (CAFOs), and non-irrigated areas at higher elevations. These issues were resolved after several model runs in combination with post-processing masks. Masks used include Fish and Wildlife Service’s National Wetlands Inventory (FWS NWI) data. These data were amended to exclude polygons overlying irrigated areas, and to expand riparian area in specific locations. A manually created mask was primarily used to fill in areas around the Snake River that the model did not uniformly designate as irrigated. Ground-truthing and a thorough review of IDWR’s water rights database provided further insight for class assignments near the town of Mayfield. Lastly, the Majority Filter tool in ArcGIS was applied using a kernel of 8 nearest neighbors to smooth out “speckling” within irrigated fields. The masking datasets and the final iteration of training points are available on request. Information regarding Sentinel and Landsat imagery:All satellite data products used within the Random Forest model were accessed via the Google Earth Engine API. To find more information on Sentinel data used, query the Earth Engine Data Catalog https://developers.google.com/earth-engine/datasets) using “COPERNICUS/S2_SR_HARMONIZED.” Information on Landsat datasets used can be found by querying “LANDSAT/LC08/C02/T1_L2” (for Landsat 8) and “LANDSAT/LC09/C02/T1_L2” (for Landsat 9).Each satellite product has several bands of available data. For our purposes, shortwave infrared 2 (SWIR2), blue, Normalized Difference Vegetation Index (NDVI), and near infrared (NIR) were extracted from both Sentinel and Landsat images. These images were later interpolated to the following dates: 2023-04-15, 2023-05-15, 2023-06-14, 2023-07-14, 2023-08-13, 2023-09-12. Interpolated values were taken from up to 45 days before and after each interpolated date. April-June interpolated Landsat images, as well as the April interpolated Sentinel image, were not used in the model given the extent of cloud cover overlying irrigated area. For more information on the pre-processing of satellite data used in the Random Forest model, please reach out to IDWR at gisinfo@idwr.idaho.gov.

  18. a

    Record Lot Points

    • private-demo-dcdev.opendata.arcgis.com
    • opendata.dc.gov
    • +3more
    Updated Feb 27, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2015). Record Lot Points [Dataset]. https://private-demo-dcdev.opendata.arcgis.com/datasets/DCGIS::record-lot-points
    Explore at:
    Dataset updated
    Feb 27, 2015
    Dataset authored and provided by
    City of Washington, DC
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Record lots are defined by the Department of Buildings (DOB) – Office of the Surveyor (OS) - DC Surveyor. They are official, platted, recorded subdivision lots created by the D.C Surveyor’s Office in compliance with the Subdivision Ordinance of the District of Columbia (must have public street frontage etc). Typically, these lots are numbered 1 through 799 with no number being used more than once in a Square. Exceptions to this rule:When the 1-799 range has been exhausted within a square, the Surveyor’s Office assigns numbers from 1200 or may even use 8000 and aboveFor reasons unknown, 42 Squares have record lot numbers greater than 799 but less than 1200Additionally, in most case scenario’s, a piece of property must be a Record Lot before a building permit will be issued for that site in the District of Columbia, and all proposed Record Lots are carefully reviewed by Zoning Administration officials for compliance with the city’s Zoning Ordinances. Other agencies that review new record lots besides OS are Office of Zoning, Office of Planning, the Dept. of Public Works, Historic Preservation and DDOT.Record lots are defined only when requested by property owners, normally when they are seeking a building permit. Record lots are recorded in Plat Books and Subdivision Books in the Office of the Surveyor. These documents are bound volumes of historical representations of the locations of property lines, and they include record dimensions, though typically no bearings of lines. These lots are located within squares, which usually correspond to one or two city blocks. Certain record lots can also be classified as “of-lots”. An "Of-Lot" is the D.C. Surveyor’s Office term for describing “Remaining/Part of Original Lot X”In the record lot feature class, if a domain value of 1 resides in the “OF_LOT” field, you can assume that at one time the original lot was modified. Typically, any of these of-lots will also have a tax lot overlaying them since it is a piece or remainder of a Record Lot.

  19. a

    Design Review Equity Areas

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • data-seattlecitygis.opendata.arcgis.com
    Updated Apr 24, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2019). Design Review Equity Areas [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/maps/SeattleCityGIS::design-review-equity-areas
    Explore at:
    Dataset updated
    Apr 24, 2019
    Dataset authored and provided by
    City of Seattle ArcGIS Online
    Area covered
    Description

    Design Review Equity Areas are areas of Seattle where applicants for development projects going through the City’s Design Review program are required to work with staff from the Department of Neighborhoods (DON) to customize their community outreach plan to the needs of historically underrepresented communities.

    Equity Areas are identified based on local demographic and socioeconomic characteristics from the US Census Bureau. Equity Areas are census tracts having a census-tract average greater than the city-as-a-whole average for at least two of the following characteristics:

    1. Limited English proficiency, identified as percentage of households that

    are linguistically isolated households.

    2. People of Color, identified as percentage of the population that is not non-Hispanic white; and

    3. Income, identified as percentage of population with income below 200% of the federal poverty level.

    For more information please see Director’s Rule for Early Community Outreach for Design Review. Additional resources and FAQs are available on DON’s Early Community Outreach webpage.

    Data Source: US Census Bureau’s American Community Survey 2016 Five-Year Estimates.

    This map will be evaluated and updated every three years.This layer is used in the SDCI Web Map.

  20. Data from: Relative % Change

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • data.seattle.gov
    • +1more
    Updated Jun 29, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2023). Relative % Change [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/SeattleCityGIS::seattle-tree-canopy-2016-2021-50-acre-hexagons?layer=3
    Explore at:
    Dataset updated
    Jun 29, 2023
    Dataset provided by
    Authors
    City of Seattle ArcGIS Online
    Area covered
    Description

    This data layer references data from a high-resolution tree canopy change-detection layer for Seattle, Washington. Tree canopy change was mapped by using remotely sensed data from two time periods (2016 and 2021). Tree canopy was assigned to three classes: 1) no change, 2) gain, and 3) loss. No change represents tree canopy that remained the same from one time period to the next. Gain represents tree canopy that increased or was newly added, from one time period to the next. Loss represents the tree canopy that was removed from one time period to the next. Mapping was carried out using an approach that integrated automated feature extraction with manual edits. Care was taken to ensure that changes to the tree canopy were due to actual change in the land cover as opposed to differences in the remotely sensed data stemming from lighting conditions or image parallax. Direct comparison was possible because land-cover maps from both time periods were created using object-based image analysis (OBIA) and included similar source datasets (LiDAR-derived surface models, multispectral imagery, and thematic GIS inputs). OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to ensure that the end product is both accurate and cartographically pleasing. No accuracy assessment was conducted, but the dataset was subjected to manual review and correction.University of Vermont Spatial Analysis LaboratoryThis dataset consists of hexagons 50-acres in area, or several city blocks. The dataset covers the following tree canopy categories:Existing tree canopy percentPossible tree canopy - vegetation percentRelative percent changeAbsolute percent changeAverage maximum afternoon temperature (F)Tree canopy percentage & average afternoon temperature (F)For more information, please see the 2021 Tree Canopy Assessment.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
D.C. Office of the Chief Technology Officer (2025). Zoning Design Review Cases [Dataset]. https://catalog.data.gov/dataset/zoning-design-review-cases

Zoning Design Review Cases

Explore at:
Dataset updated
Feb 4, 2025
Dataset provided by
D.C. Office of the Chief Technology Officer
Description

The purpose of the design review process is to: Allow for special projects to be approved by the Zoning Commission after a public hearing and a finding of no adverse impact; Recognize that some areas of the District of Columbia warrant special attention due to particular or unique characteristics of an area or project; Permit some projects to voluntarily submit themselves for design review in exchange for flexibility because the project is superior in design but does not need extra density; Promote high-quality, contextual design; and Provide for flexibility in building bulk control, design, and site placement without an increase in density or a map amendment.

Search
Clear search
Close search
Google apps
Main menu