This survey is designed to gather input from MOCA programs to help prioritize features and inform the design of a new SharePoint site that supports internal collaboration and access to resources.

NOTE: The Historic Traffic Data Dashboard & Feature Hosted Service have been retired.Network operations traffic data from Main Roads Western Australia from 2013 onwards. The data provided includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals.

The Historic Traffic Data is provided in CSV format per year. Each table has over 34 million rows and can be linked to the M-Links Road Network using the M-Links ID. A data dictionary for M-Links Road Network and the Historic Traffic Data is at the following link:https://mainroads.sharepoint.com/:w:/s/mr-opendata/EVHlw9Ils59Al4q3y7xxWxABBSOHVr4SCrxOYzJw1dReQg?e=KUhjhb

The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time.

Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes.

Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.”

Source https://nation258.sharepoint.com/:b:/s/USRSystemDocumentation/Eed65FnVKPBIns5mltwJPZgBMB3l7neUDiVPqYzyuKoq1A?e=oT5dxo

AFRAA Data Upgrade & Transition Plan for 2025 Fire Season Given the mission-critical nature of AFRAA dataset and federal mandates, the FS Enterprise Data Warehouse (EDW) and AFRAA data stewards will fully support the legacy map services throughout the 2025 fire season before retirement. The latest 2025 data, approved by Forest Service Regional Forester and GIS Coordinators, has been integrated into legacy schemas, ensuring authoritative data while maintaining backward compatibility for applications relying on legacy endpoints. What You Need to KnowWhere is the New Data Most users will use the new map image service REST endpoints: https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Aquatic_01/MapServer https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Terrestrial_01/MapServer Metadata is available in these ArcGIS items that reference the new map services: Fire_AerialFireRetardantAvoidanceAreas_Aquatic (Landing Page) Fire_AerialFireRetardantAvoidanceAreas_Terrestrial (Landing Page) Sync Enable ArcGIS Online Hosted Feature Services: Aquatic Hosted Feature Service Terrestrial Hosted Feature Service Internal FS users can make direct SDE connections (see detailed instructions on the AFRAA SharePoint ). Downloadable Data from the FS GeoData Clearinghouse: Fire_AerialFireRetardantAvoidanceAreas_Aquatic.gdb.zip Fire_AerialFireRetardantAvoidanceAreas_Terrestrial.gdb.zip When Will the Legacy Product Be Retired? March 14, 2025 – New terrestrial map service available, and a deprecation watermark is added to the legacy service. March 14, 2025 - Region 3 approved 2025 aquatic data via the legacy service endpoint. April 1, 2025 – All 2025 approved data loaded into both new and legacy services. April 1, 2025 – New aquatic service published, and a deprecation watermark is added to the legacy service. April 1, 2025 – Legacy download products removed from the Clearinghouse and replaced with the new versions. April 7, 2025 – Sync enabled Hosted Feature Services published to ArcGIS Online October 1, 2025 – Legacy services stopped. Fire personnel can contact SM.FS.afraa@usda.gov during regular business hours if unknown dependencies are discovered. The services will be restarted if needed. November 1, 2025 – Unless an extension is requested, legacy services will be deleted, and all feature classes will be removed from EDW, making the data inaccessible. What Products Are Being Deprecated? Terrestrial Map Services & Associated Feature ClassesLegacy Terrestrial: https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_01/MapServerS_USA.AerialFireRetardantAvoidance New Authoritative Terrestrial: https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Terrestrial_01/MapServerS_USA.Fire_AerialFireRetardantAvoidanceAreas_Terrestrial Aquatic Map Services & Associated Feature Classes Legacy Aquatic: https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantHydrographicAvoidanceAreas_01/MapServer S_R01.AFRAA_Hydro S_R02.AFRAA_Hydro S_R03.AFRAA_Hydro S_R04.AFRAA_Hydro S_R05.AFRAA_Hydro S_R06.AFRAA_Hydro S_R08.AFRAA_Hydro S_R09.AFRAA_Hydro S_R10.AFRAA_Hydro New Authoritative Aquatic Map Service and Feature Class: https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_AerialFireRetardantAvoidanceAreas_Aquatic_01/MapServerS_USA.Fire_AerialFireRetardantAvoidanceAreas_Aquatic

AT parking locations as found at https://at.govt.nz/driving-parking/find-parking. Parking data sourced from the sharepoint list, https://aucklandtransport.sharepoint.com/sites/projects-msd/Lists/Parking/AllItems.aspx

THIS ITEM IS PUBLIC AND READ ONLYThe Water Resources Inventory feature layer is a spatial inventory of miscellaneous point and line water related features on U.S. Fish and Wildlife Service lands. Management Actions and Maintenance related tables are included. This is a national authoritative data layer constructed by the NWRS Geospatial Advisory Committee assets sub-team based on the success of the Region 3 NWRS Water Resources Inventory dataset. This is a read-only, public AGOL View of FWS_Asset_Water_Resources_Inventory. Content can be added/edited by joining the FWS Asset Editing Group if a member of the FWS Organization. This public view only shows records that meet the following criteria:Record Status = "Valid"Public Viewable = "Yes"Data Set Contact: U.S. Fish and Wildlife Service Natural Resource Program Center, GIS Team Lead, richard_easterbrook@fws.govU.S. Fish and Wildlife Service Catalog (ServCat) Record - https://ecos.fws.gov/ServCat/Reference/Profile/154161For more information on the data that can be collected, see NWRS GAC FWS Assets sharepoint.

CREST_Historic_DischargeData: https://sooners-my.sharepoint.com/:u:/g/personal/skyan_ou_edu/EVzT4n0QsA1DlVe_CyeQD5AB7cg-E023yvzPdKHeMtOS-A?e=7EML28Unit:cubic meters per month

Fiche descriptive dans le géocatalogue de l'Apur : BESOIN THEORIQUE DE CHAUFFAGE ET TYPOLOGIE DU BATICombinaison des couches des bâtis de Paris et hors-Paris (Métropole du Grand Paris) correspondant à l'emprise au sol avec l'affectation d'informations typologiques et morphologiques ainsi que la modélisation des besoins en terme de chauffage ou de déperdition résidentiel.Cette couche de données contient plus d'1 million de bâtiments sous la forme vectorielle. Son téléchargement peut durer un certain temps ou échouer en raison du volume de données. En cas d'échec par l'outil de téléchargement, merci de suivre le lien alternatif ci-après : https://apur365-my.sharepoint.com/:f:/g/personal/opendata_apur_org/EnXO8KQGdOhHseTTjjHc29EB9fHRiRLq6O8cp7igf7cWQw?e=nb5aZdAvertissement aux utilisateurs : cette couche contient notamment des données vectorielles provenant des bâtiments issus du PCI Vecteur (source DGFiP). Elle est mise à disposition avec l'autorisation de la DGFiP. Cette couche a toutefois fait l’objet d’assemblage et de mise en cohérence topologique de la part de l’Apur dans le cadre de ses études et travaux. Si ces modifications n’ont pas altérées ou dénaturées les données sources, il ne s’agit pas des données du cadastre original de la DGFiP. La couche cadastrale ici proposée n’a pas vocation à remplacer la version de la DGFiP. Merci de vous adresser à la DGFiP pour tout usage des données officielles : https://www.cadastre.gouv.frPour plus de précision, merci de suivre le lien vers la fiche descriptive.

A Park and Ride lot point is a point in coordinate space that represents a physical location. This feature layer is based on data extracts from regional coordinators and the Park and Ride Sharepoint webpages.

The National PODs Feature Service is the official depiction of PODs approved by agency administrators. This service is hosted in the National Interagency Fire Center (NIFC) ArcGIS Online (AGOL) organization and is based on the attributes from the PODs Poly and PODs Line NWCG Data Standards. This service is managed by the USFS Washington Office Fire and Aviation Management Strategic Analytics Branch and has three components; PODs_Poly (a polygon layer), PODs_Line (a line layer), and PODs_Lines_HAVE_Polys (a many to many relationship table between lines and polygons).

PODs Poly. The PODs Poly layer represents pre-planned areas defined by potential operational delineation lines (i.e., potential control features), such as roads and ridge tops, within which relevant information can be summarized

PODs Line. The PODs Line layer represents pre-planned potential control features, such as roads and ridge tops, that may form polygon wildland fire potential operational delineations

PODs_Lines_HAVE_Polys. This is a many-to-many relationship which allows a line to be shared by many polygons or a polygon to be shared by many linesThis service is filtered to include only those features where FeatureAccess = Public. Additionally, attributes containing Personal Identifying Information (PII) have been removed from this View. No fall-off rules apply to this service. For information on how to contribute or edit data within this service, please locate the National POD Feature Service Implementation Guidance within the PODs folder on the RMA Sharepoint Site. Please contact Rick Stratton with any comments or questions.

This feature layer depicts location and other details about U.S. Fish & Wildlife Service internships that are hosted through our partners (e.g. Student Conservation Association, American Conservation Experience, Hispanic Access Foundation, etc.) in one central location so that we are able to share these opportunities with potential applicants and the public.This map is mostly auto-populated by financial assistant intake requests to NWRS Division of Realty, Budget, Performance, and Workforce (Youth Financial Assistance team) on SharePoint. However, for any internship opportunities that are not captured through that process can be added to this map via the Survey123 form on the Youth SharePoint site.Questions about this dashboard/map can be directed to Rachel_F_McCracken@fws.gov

Data is released by the US Census Bureau following a Decennial count that is used in support of compliance with Public Law 94-171 and the Voting Rights Act (VRA). Public Law (P.L.) 94-171, enacted in 1975, directs the Census Bureau to make special preparations to provide the redistricting data needed by the fifty states. Within a year following Census Day, the Census Bureau must send the data agreed upon to redraw districts for the state legislature to each state's governor and majority and minority legislative leaders and those state officials legally responsible for statewide redistricting such as commission chairs. Process Doc:pl94171_data_loading_and_processing.docx (sharepoint.com)

This feature layer was created on March 1, 2025, and is derived from the 2025 State Partners Excel sheet located in the GHS SharePoint. It is designed to present a comprehensive overview of statewide school providers, making it easy for users to identify service locations across Wisconsin. By integrating this map into our website's dashboard, we aim to improve accessibility and usability for users seeking information on available providers in key focus areas like water, waste, transportation, building health and more. The goal of this map is to connect K-12 WI schools with local providers to gain valuable regional and local resources and technical assistance.Missing Data and Known GapsThis data only includes business and organizations that have been identified by Green & Healthy Schools staff and partners as places that offer resources or assistance to schools. This data does not encompass every business and organization that offers school resources.

The National PODs Feature Service is the official depiction of PODs approved by agency administrators. This service is hosted in the National Interagency Fire Center (NIFC) ArcGIS Online (AGOL) organization and is based on the attributes from the PODs Poly and PODs Line NWCG Data Standards. This service is managed by the USFS Washington Office Fire and Aviation Management Strategic Analytics Branch and has three components; PODs_Poly (a polygon layer), PODs_Line (a line layer), and PODs_Lines_HAVE_Polys (a many to many relationship table between lines and polygons).

PODs Poly. The PODs Poly layer represents pre-planned areas defined by potential operational delineation lines (i.e., potential control features), such as roads and ridge tops, within which relevant information can be summarized

PODs Line. The PODs Line layer represents pre-planned potential control features, such as roads and ridge tops, that may form polygon wildland fire potential operational delineations

PODs_Lines_HAVE_Polys. This is a many-to-many relationship which allows a line to be shared by many polygons or a polygon to be shared by many linesThis service is filtered to include only those features where FeatureAccess = Public. Additionally, attributes containing Personal Identifying Information (PII) have been removed from this View. No fall-off rules apply to this service. For information on how to contribute or edit data within this service, please locate the National POD Feature Service Implementation Guidance within the PODs folder on the RMA Sharepoint Site. Please contact Rick Stratton with any comments or questions.

The National PODs Feature Service is the official depiction of PODs approved by agency administrators. This service is hosted in the National Interagency Fire Center (NIFC) ArcGIS Online (AGOL) organization and is based on the attributes from the PODs Poly and PODs Line NWCG Data Standards.

This service has three components, PODs_Poly (a polygon layer), PODs_Line (a line layer), and PODs_Lines_HAVE_Polys (a many to many relationship table between lines and polygons).

PODs Poly. The PODs Poly layer represents pre-planned areas defined by potential operational delineation lines (i.e., potential control features), such as roads and ridge tops, within which relevant information can be summarized

PODs Line. The PODs Line layer represents pre-planned potential control features, such as roads and ridge tops, that may form polygon wildland fire potential operational delineations

PODs_Lines_HAVE_Polys. This is a many-to-many relationship which allows a line to be shared by many polygons or a polygon to be shared by many linesFor information on how to contribute data to this service, please locate the National POD Feature Service Implementation Guidance within the PODs folder on the RMA Sharepoint Site.

The National PODs Feature Service is the official depiction of PODs approved by agency administrators. This service is hosted in the National Interagency Fire Center (NIFC) ArcGIS Online (AGOL) organization and is based on the attributes from the PODs Poly and PODs Line NWCG Data Standards.

This service has three components, PODs_Poly (a polygon layer), PODs_Line (a line layer), and PODs_Lines_HAVE_Polys (a many to many relationship table between lines and polygons).

PODs Poly. The PODs Poly layer represents pre-planned areas defined by potential operational delineation lines (i.e., potential control features), such as roads and ridge tops, within which relevant information can be summarized

PODs Line. The PODs Line layer represents pre-planned potential control features, such as roads and ridge tops, that may form polygon wildland fire potential operational delineations

PODs_Lines_HAVE_Polys. This is a many-to-many relationship which allows a line to be shared by many polygons or a polygon to be shared by many linesFor information on how to contribute data to this service, please locate the National POD Feature Service Implementation Guidance within the PODs folder on the RMA Sharepoint Site.

The National PODs Feature Service is the official depiction of PODs approved by agency administrators. This service is hosted in the National Interagency Fire Center (NIFC) ArcGIS Online (AGOL) organization and is based on the attributes from the PODs Poly and PODs Line NWCG Data Standards.

This service has three components, PODs_Poly (a polygon layer), PODs_Line (a line layer), and PODs_Lines_HAVE_Polys (a many to many relationship table between lines and polygons).

PODs Poly. The PODs Poly layer represents pre-planned areas defined by potential operational delineation lines (i.e., potential control features), such as roads and ridge tops, within which relevant information can be summarized

PODs Line. The PODs Line layer represents pre-planned potential control features, such as roads and ridge tops, that may form polygon wildland fire potential operational delineations

PODs_Lines_HAVE_Polys. This is a many-to-many relationship which allows a line to be shared by many polygons or a polygon to be shared by many linesFor information on how to contribute data to this service, please locate the National POD Feature Service Implementation Guidance within the PODs folder on the RMA Sharepoint Site.

Data is released by the US Census Bureau following a Decennial count that is used in support of compliance with Public Law 94-171 and the Voting Rights Act (VRA). Public Law (P.L.) 94-171, enacted in 1975, directs the Census Bureau to make special preparations to provide the redistricting data needed by the fifty states. Within a year following Census Day, the Census Bureau must send the data agreed upon to redraw districts for the state legislature to each state's governor and majority and minority legislative leaders and those state officials legally responsible for statewide redistricting such as commission chairs. Process Doc:pl94171_data_loading_and_processing.docx (sharepoint.com)

A tabbed StoryMap currently containing LiDAR extent and tile datasets with links to SharePoint and other public sites where Waikato Regional Council data is hosted for public consumption. The intention is to build on this in the future adding further tabs with more data freely available.LINZ LiDAR User Guides: See Elevation Aotearoa (arcgis.com) from Elevation data | Toitū Te Whenua - Land Information New Zealand (linz.govt.nz)

This dataset includes geotechnical reports available throughout Auckland Council systems. Geotechnical reports are written by suitably qualified and experienced geotechnical engineers or engineering geologists and include information on ground quality and subsurface geology. They are generally undertaken for infrastructure and building development or land use planningGeotechnical reports are received by council as part of consent applications, and are stored on the related property file. For each legacy council these records were located with the help of the document management team. Although spatial data was generated by property, the final database is not tagged to property parcels. Where feasible, detailed location polygons were generated using site maps available in the individual reports. In addition, some geotechnical reports are received by council for our own projects. These are also provided where available.This database was August 2020. All reports are available either on the Geotechnical Sharepoint or on ACCORD. Editing of this dataset can be done with the approval of Ross Roberts. geotechnical reports (i.e. tag them as Geotech and edit the GIS geometr, or a secondary process mayautomatically created property based geometry). Report data will be stored in OpenText/Accord, and will be flagged in SAPLineage: Data was extracted from legacy council databases sourced from:ACC/FDC Filenet ReportsNSCC Dataworks ReportsWCC Pathway ReportsRDC Pathway ReportsMCC Alchemy ReportsSAP Reports (2015-2019)ACGD Partner Reports (Watercare)These were evaluated to remove duplicate records, and associated with property records. Using property records a process was created for a one off load of the data (Geospatial team) using the property boundaries to create a base geometry. As one area may have several reports a separate related table was created to hold summary details of the reports. (Geotechnical Report Details)As some reports were not property based areas were manually digitised to indicate the extent of the report area.Future updates:As at this date the data is not yet updated - though it is intended that:The database will be updated whenever a new report is received. When a geotechnical report comes into council as part of a resource or building consent, the SAP team will need to follow the SAP protocol for In addition, new consent applications with geotechnical reports will be added, as will geotechnical reports undertaken for Auckland Council projects. Reports from other sources (e.g. CCOs, other crown entities) may be added where appropriate.