Technical documentation for EJMap version 1.0

A Research Polygon is a feature representing a geographic area (polygon), where some form of research observation, test, trial, measure, or monitoring activity has, or will take place. The mapped features in this layer can be derived existing feature geometry (e.g. plantation), or as generated feature geometry (e.g., 11.28 meter diameter circular plot around a centre post). This layer will also store research areas which represent formalized groupings where research occurs. There will be significant overlaps between features in this layer. This data class is one of three primitive data classes: Research Point (RESPOINT), Research Line (RESLINE), and Research Polygon (RESPOLY).

Additional DocumentationResearch Polygon - Data Description (PDF)Research Polygon - Documentation (Word) Research Plot - User Guide (Word) Research Plot - FAQ (Word)

Status

On going: data is being continually updated

Maintenance and Update Frequency

As needed: data is updated as deemed necessary

Contact

Adam Hogg, adam.hogg@ontario.ca

The data referenced here is licensed under the Ontario Geospatial Data Exchange (OGDE) Agreement and is available to members of the OGDE for professional, non-commercial use only. To find out more about the OGDE visit Land Information Ontario on Ontario.ca.

The Ontario Railway Network (ORWN) is seven data classes that represent the Ontario government’s initiative to adapt the federal GEOBASE standard for the National Railway Network (NRWN) geospatial data.

The seven data classes include:

ORWN Track (Download: Shapefile | File Geodatabase) ORWN Crossing (Download: Shapefile | File Geodatabase) ORWN Junctions (Download: Shapefile | File Geodatabase) ORWN Marker Posts (Download: Shapefile | File Geodatabase) ORWN Structure Lines (Download: Shapefile | File Geodatabase) ORWN Structure Points (Download: Shapefile | File Geodatabase) ORWN Station (Download: Shapefile | File Geodatabase)

Although mainly used as a base data features appearing on cartographic products, users will benefit from having additional railway-associated attributes available to them in the ORWN suite of data.

Additional Documentation

ORWN - User Guide (Word)

ORWN Track - Data Description (PDF)ORWN Track - Documentation (PDF)ORWN Crossing - Data Description (PDF)ORWN Crossing - Documentation (Word)

ORWN Junction - Data Description (PDF)ORWN Junction - Documentation (Word)ORWN Marker Post - Data Description (PDF)ORWN Marker Post - Documentation (Word)

ORWN Structure Line - Data Description (PDF)

ORWN Structure Line - Documentation (Word)ORWN Structure Point - Data Description (PDF)ORWN Structure Point - Documentation (Word)ORWN Station - Data Description (PDF)ORWN Station - Documentation (Word)

Status

Required: data needs to be generated or updated

Maintenance and Update Frequency

Not planned: there are no plans to update the data

Contact

Ontario Ministry of Natural Resources - Geospatial Ontario, geospatial@ontario.ca

Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the training samples were created and saved, the raster was then reclassified using the Image Classification Wizard tool in ArcGIS Pro, using the Support...

Want to keep the data in your Hosted Feature Service current? Not interested in writing a lot of code?Leverage this Python Script from the command line, Windows Scheduled Task, or from within your own code to automate the replacement of data in an existing Hosted Feature Service. It can also be leveraged by your Notebook environment and automatically managed by the MNCD Tool!See the Sampler Notebook that features the OverwriteFS tool run from Online to update a Feature Service. It leverages MNCD to cache the OverwriteFS script for import to the Notebook. A great way to jump start your Feature Service update workflow! RequirementsPython v3.xArcGIS Python APIStored Connection Profile, defined by Python API 'GIS' module. Also accepts 'pro', to specify using the active ArcGIS Pro connection. Will require ArcGIS Pro and Arcpy!Pre-Existing Hosted Feature ServiceCapabilitiesOverwrite a Feature Service, refreshing the Service Item and DataBackup and reapply Service, Layer, and Item properties - New at v2.0.0Manage Service to Service or Service to Data relationships - New at v2.0.0Repair Lost Service File Item to Service Relationships, re-enabling Service Overwrite - New at v2.0.0'Swap Layer' capability for Views, allowing two Services to support a View, acting as Active and Idle role during Updates - New at v2.0.0Data Conversion capability, able to invoke following a download and before Service update - New at v2.0.0Includes 'Rss2Json' Conversion routine, able to read a RSS or GeoRSS source and generate GeoJson for Service Update - New at v2.0.0Renamed 'Rss2Json' to 'Xml2GeoJSON' for its enhanced capabilities, 'Rss2Json' remains for compatability - Revised at v2.1.0Added 'Json2GeoJSON' Conversion routine, able to read and manipulate Json or GeoJSON data for Service Updates - New at v2.1.0Can update other File item types like PDF, Word, Excel, and so on - New at v2.1.0Supports ArcGIS Python API v2.0 - New at v2.1.2RevisionsSep 29, 2021: Long awaited update to v2.0.0!Sep 30, 2021: v2.0.1, Patch to correct Outcome Status when download or Coversion resulted in no change. Also updated documentation.Oct 7, 2021: v2.0.2, workflow Patch correcting Extent update of Views when Overwriting Service, discovered following recent ArcGIS Online update. Enhancements to 'datetimeUtil' Support script.Nov 30, 2021: v2.1.0, added new 'Json2GeoJSON' Converter, enhanced 'Xml2GeoJSON' Converter, retired 'Rss2Json' Converter, added new Option Switches 'IgnoreAge' and 'UpdateTarget' for source age control and QA/QC workflows, revised Optimization logic and CRC comparison on downloads.Dec 1, 2021: v2.1.1, Only a patch to Conversion routines: Corrected handling of null Z-values in Geometries (discovered immediately following release 2.1.0), improve error trapping while processing rows, and added deprecation message to retired 'Rss2Json' conversion routine.Feb 22, 2022: v2.1.2, Patch to detect and re-apply case-insensitive field indexes. Update to allow Swapping Layers to Service without an associated file item. Added cache refresh following updates. Patch to support Python API 2.0 service 'table' property. Patches to 'Json2GeoJSON' and 'Xml2GeoJSON' converter routines.Sep 5, 2024: v2.1.4, Patch service manager refresh failure issue. Added trace report to Convert execution on exception. Set 'ignore-DataItemCheck' property to True when 'GetTarget' action initiated. Hardened Async job status check. Update 'overwriteFeatureService' to support GeoPackage type and file item type when item.name includes a period, updated retry loop to try one final overwrite after del, fixed error stop issue on failed overwrite attempts. Removed restriction on uploading files larger than 2GB. Restores missing 'itemInfo' file on service File items. Corrected false swap success when view has no layers. Lifted restriction of Overwrite/Swap Layers for OGC. Added 'serviceDescription' to service detail backup. Added 'thumbnail' to item backup/restore logic. Added 'byLayerOrder' parameter to 'swapFeatureViewLayers'. Added 'SwapByOrder' action switch. Patch added to overwriteFeatureService 'status' check. Patch for June 2024 update made to 'managers.overwrite' API script that blocks uploads > 25MB, API v2.3.0.3. Patch 'overwriteFeatureService' to correctly identify overwrite file if service has multiple Service2Data relationships.Includes documentation updates!

The Standardized Precipitation Index (SPI) was generated for certain Environment Canada long-term climate stations in Ontario.

The SPI quantifies the precipitation deficit and surplus for multiple time scales, including:

one month three months six months nine months 12 months 24 months

You can use the SPI to study the impact of dry and wet weather conditions to create comprehensive water management approaches.

The SPI data package is distributed as a Microsoft Access Geodatabase.

This is a legacy dataset that we no longer maintain or support.

The documents referenced in this record may contain URLs (links) that were valid when published, but now link to sites or pages that no longer exist.

Additional Documentation

Standardized Precipitation Index - User Guide (PDF)

Status Completed: production of the data has been completed

Maintenance and Update Frequency
Not planned: there are no plans to update the data

Contact
Ontario Ministry of Natural Resources - Geospatial Ontario, geospatial@ontario.ca

JOBS PROXIMITY INDEXSummaryThe jobs proximity index quantifies the accessibility of a given residential neighborhood as a function of its distance to all job locations within a CBSA, with larger employment centers weighted more heavily. Specifically, a gravity model is used, where the accessibility (Ai) of a given residential block- group is a summary description of the distance to all job locations, with the distance from any single job location positively weighted by the size of employment (job opportunities) at that location and inversely weighted by the labor supply (competition) to that location. More formally, the model has the following specification: Where i indexes a given residential block-group, and j indexes all n block groups within a CBSA. Distance, d, is measured as “as the crow flies” between block-groups i and j, with distances less than 1 mile set equal to 1. E represents the number of jobs in block-group j, and L is the number of workers in block-group j. The Longitudinal Employer-Household Dynamics (LEHD) has missing jobs data in all of Puerto Rico and a concentration of missing records in Massachusetts. InterpretationValues are percentile ranked with values ranging from 0 to 100. The higher the index value, the better the access to employment opportunities for residents in a neighborhood. Data Source: Longitudinal Employer-Household Dynamics (LEHD) data, 2017. Related AFFH-T Local Government, PHA and State Tables/Maps: Table 12; Map 8. To learn more about the Jobs Proximity Index visit: https://www.hud.gov/program_offices/fair_housing_equal_opp/affh ; https://www.hud.gov/sites/dfiles/FHEO/documents/AFFH-T-Data-Documentation-AFFHT0006-July-2020.pdf, for questions about the spatial attribution of this dataset, please reach out to us at GISHelpdesk@hud.gov. Date of Coverage: 07/2020

This dataset represents estimates for single-station annual flood and low-flow frequency in the Southwestern Hudson Bay and the Nelson River watershed systems, calculated for the Water Survey of Canada’s (WSC) database called HYDAT.The flood magnitude statistics can be used for applications such as flood plain delineation and design of hydraulic structures. The drought severity statistics can be used for applications such as water abstraction and effluent dilution.

Additional Documentation

Technical Release Documentation (PDF) Status Completed: production of the data has been completed

Maintenance and Update Frequency
Not planned: there are no plans to update the data

Contact
Ontario Ministry of Natural Resources - Geospatial Ontario, geospatial@ontario.ca

A source protection area (SPA) is an area of land and water governed by a Source Protection Authority, an agency, person or body.

This dataset defines the geographic boundaries where each SPA’s terms of reference, assessment reports and source protection plans must be developed.

Additional Documentation

Source Protection Area Generalized - Data Description (PDF) Source Protection Area Generalized - Documentation (Word)

Status Completed: production of the data has been completed Maintenance and Update Frequency As needed: data is updated as deemed necessary Contact Derek Hatfield, Program Support Section, derek.hatfield@ontario.ca

This dataset represents the locations of licenced and permitted pits and quarries regulated by the Ministry of Natural Resources and Forestry (MNRF) under the Aggregate Resources Act, R.S.O. 1990.

Aggregate site data has been divided into active and inactive sites. Active sites may be further subdivided into partial surrenders. In partial surrenders, defined areas of a site are inactive while the rest of the site remains active.

The data includes:

site location and size licensee name approval type (licence or permit) operation type (pit or quarry) maximum annual tonnage limit the MNRF district responsible for the site

Use our interactive Pits and Quarries map to find active sites.

This data does not include aggregate sites regulated by the Ministry of Transportation.

Additional Documentation

Aggregate Site Authorized - User Guide (PDF)

Aggregate Site Authorized - Active - Data Description (PDF)

Aggregate Site Authorized - Active - Documentation (Word)

Status

On going: Data is continually being updated

Maintenance and Update Frequency

Continual: Data is repeatedly and frequently updated

Contact

Ryan Lenethen, Policy Analyst, ryan.lenethen@Ontario.ca

This dataset represents the locations of licenced and permitted pits and quarries regulated by the Ministry of Natural Resources and Forestry (MNRF) under the Aggregate Resources Act, R.S.O. 1990.

Aggregate site data has been divided into active and inactive sites. Active sites may be further subdivided into partial surrenders. In partial surrenders, defined areas of a site are inactive while the rest of the site remains active.

The data includes:

site location and size licensee name approval type (licence or permit) operation type (pit or quarry) maximum annual tonnage limit the MNRF district responsible for the site

Use our interactive Pits and Quarries map to find active sites.

This data does not include aggregate sites regulated by the Ministry of Transportation.

Additional Documentation

Aggregate Site Authorized - User Guide (PDF)

Aggregate Site Authorized - Inactive - Data Description (PDF)

Aggregate Site Authorized - Inactive - Documentation (Word)

Status

On going: Data is continually being updated

Maintenance and Update Frequency

Continual: Data is repeatedly and frequently updated

Contact

Ryan Lenethen, Policy Analyst, ryan.lenethen@Ontario.ca

Facilities used by MNRF’s Aviation Forest Fire and Emergency Services branch.This dataset is used to support aviation forest fire and AFFES business operations. Additional Documentation

Fire, Aviation and Emergency Facility Point - User Guide (PDF) Fire, Aviation and Emergency Facility Point - Data Description (PDF) Fire, Aviation and Emergency Facility Point - Documentation (Word)

Status On going: data is being continually updated Maintenance and Update FrequencyNot stated Contact
Aviation, Forest Fire and Emergency Services Natalie Belanger natalie.belanger@ontario.ca Darryl Pajunen darryl.pajunen@ontario.ca

The World Ocean Atlas (WOA) is a collection of objectively analyzed, quality controlled temperature, salinity, oxygen, phosphate, silicate, and nitrate means based on profile data from the World Ocean Database (WOD). It can be used to create boundary and/or initial conditions for a variety of ocean models, verify numerical simulations of the ocean, and corroborate satellite data.

This layer uses annual means for all averaged decades years. Each value represents the "objectively analyzed climatologies" - the objectively interpolated mean fields for oceanographic variables at standard depth levels for the World Ocean.

There are 8 different variables available through the World Ocean Atlas.

Temperature (°C) Sallinity (unitless) Oxygen

Dissolved Oxygen (µmol/kg) - converted from ml/l Apparent Oxygen Utilization (µmol/kg) - converted from ml/l Percent Oxygen Saturation (%)

Nitrate (µmol/kg) - converted from ml/l Phosphate (µmol/kg) - converted from ml/l Silicate (µmol/kg) - converted from ml/l

There are 102 different depths that range between 0-5,500m that can be accessed using the depth/range slider or queries/filters.

World Ocean Atlas 2013 Source Data: https://www.nodc.noaa.gov/OC5/woa13/World Ocean Atlas 2013 Product Documentation: https://data.nodc.noaa.gov/woa/WOA13/DOC/woa13documentation.pdf

ANSI's (Areas of Natural and Scientific Interest) are polygon features that represent lands and waters containing important natural landscapes or features that are important for natural heritage, protection, appreciation, scientific study or education. This class has related tables. Areas of Natural and Scientific Interest (ANSI) related tables Additional Documentation ANSI Data Description (PDF)ANSI Documentation (Word) Status On going: Data is continually being updated Maintenance and Update Frequency As needed: Data is updated as deemed necessary Contact Melissa Rose, Natural Heritage Section, Resources Planning and Development Policy Branch, Melissa.Rose@ontario.ca

Data on the locations of seed zones in Ontario.

Seed zones were developed to ensure that the variation of climatic parameters (e.g., growing season length) within each zone corresponds with the adaptive variation exhibited by major commercial tree species in the province.

We are no longer updating this data. It is best suited for historical research and analysis.

Additional Documentation

  Seed Zone - Data Description (PDF)
  Seed Zone - Documentation (Word)

Product Packages

  Seed Zone (shapefile alternative)

Status

Completed: production of the data has been completed

Maintenance and Update Frequency

As needed: data is updated as deemed necessary

Contact

Christine Kent, Integration Branch, christine.kent@ontario.ca

This data class will capture the location and some basic information on wind turbines. A wind turbine is a machine that capture the force of the wind usually used to produce electricity.Legislated or Legal Authority for Collection: None - there is no legislative requirement or authority to collect this informationAdditional Time Period Information: This data class was developed Winter 2008. It will be populated on an ongoing basis with wind turbines that are located on both crown and private land.

Additional Documentation Wind Turbine - Data Description (PDF)Wind Turbine - Documentation (Word)

Status

On going: data is being continually updated

Maintenance and Update Frequency

As needed: data is updated as deemed necessary

Contact

Emily Hill, Ministry of Natural Resources and Forestry, emily.hill@ontario.ca

The data referenced here is licensed under the Ontario Geospatial Data Exchange (OGDE) Agreement and is available to members of the OGDE for professional, non-commercial use only. To find out more about the OGDE visit Land Information Ontario on Ontario.ca.

NGO Nature Reserves are polygon features describing lands held by nature trusts and other non-government agencies for the purpose of nature conservation.

We are no longer updating this data. It is best suited for historical research and analysis.

Additional Documentation

NGO Nature Reserve - Data Description (PDF)

NGO Nature Reserve - Documentation (Word)

Product Packages

NGO Nature Reserve (shapefile alternative)

Status
Completed: Production of the data has been completed

Maintenance and Update Frequency
Not planned: there are no plans to update the data

Contact
Emily Hill, Ministry of Natural Resources and Forestry, emily.hill@ontario.ca

Map Information This nowCOAST time-enabled map service provides maps of experimental lightning strike density data from the NOAA/National Weather Service/NCEP's Ocean Prediction Center (OPC) which emulate (simulate) data from the future NOAA GOES-R Global Lightning Mapper (GLM). The purpose of this experimental product is to provide mariners and others with enhanced "awareness of developing and transitory thunderstorm activity, to give users the ability to determine whether a cloud system is producing lightning and if that activity is increasing or decreasing..." Lightning Strike Density, as opposed to display of individual strikes, highlights the location of lightning cores and trends of increasing and decreasing activity. The maps depict the density of lightning strikes during a 15 minute time period at an 8 km x 8 km spatial resolution. The lightning strike density maps cover the geographic area from 25 degrees South to 80 degrees North latitude and from 110 degrees East to 0 degrees West longitude. The map units are number of strikes per square km per minute multiplied by a scaling factor of 10^3. The strike density is color coded using a color scheme which allows the data to be easily seen when overlaid on GOES imagery and to distinguish values at low density values. The maps are updated on nowCOAST approximately every 15 minutes. The latest data depicted on the maps are approximately 12 minutes old (or older). The OPC lightning strike density product is still experimental and may not always be available. Given the spatial resolution and latency of the data, the data should NOT be used to activite your lightning safety plans. Always follow the safety rule: when you first hear thunder or see lightning in your area, activate your emergency plan. If outdoors, immediately seek shelter in a substantial building or a fully enclosed metal vehicle such as a car, truck or a van. Do not resume activities until 30 minutes after the last observed lightning or thunder. For more detailed information about the update schedule for the lightning strike density data maps on nowCOAST, please see: http://new.nowcoast.noaa.gov/help/#section=updateschedule Background Information The source for the data is OPC's gridded lightning strike density data on an 8 x 8 km grid. The gridded data emulate the spatial resolution of the future Global Lightning Mapper (GLM) instrument to be flown on the NOAA GOES-R series of geostationary satellites, with the first satellite scheduled for launch in early 2016. The gridded data is based on data from Vaisala's ground based Vaisala's U.S. National Lightning Detection Network (NLDN) and its global lightning detection network referred to as the Global Lightning Dataset (GLD360). These networks are capable of detecting cloud-to-ground strokes, cloud-to-ground flash information and survey level cloud lightning information. According to the National Lightning Safety Institute, NLDN uses radio frequency detectors in the spectrum 1.0 kHz through 400 kHz to measure energy discharges from lightning as well as approximate distance and direction. According to Vaisala, the GLD360 network is capable of a detection efficiency greater than 70% over most of the Northern Hemisphere with a median location accuracy of 5 km or better. OPC's experimental gridded data are coarser than the original source data from Vaisala's networks. The 15-minute gridded source data are updated at OPC every 15 minutes at 10 minutes past the valid time. The lightning strike density product from NWS/NCEP/OPC is considered a derived product or Level 5 product ("NOAA-generated products using lightning data as input but not displaying the contractor transmitted/provided lightning data") and is appropriate for public distribution. Time Information

This map is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

Due to software limitations, the time extent of the service and map layers displayed below does not provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time information about the service:

Issue a returnUpdates=true request for an individual layer or for the service itself, which will return the current start and end times of available data, in epoch time format (milliseconds since 00:00 January 1, 1970). To see an example, click on the "Return Updates" link at the bottom of this page under "Supported Operations". Refer to the ArcGIS REST API Map Service Documentation for more information.

Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against the proper layer corresponding with the target dataset. For raster data, this would be the "Image Footprints with Time Attributes" layer in the same group as the target "Image" layer being displayed. For vector (point, line, or polygon) data, the target layer can be queried directly. In either case, the attributes returned for the matching raster(s) or vector feature(s) will include the following:

validtime: Valid timestamp.

starttime: Display start time.

endtime: Display end time.

reftime: Reference time (sometimes reffered to as issuance time, cycle time, or initialization time).

projmins: Number of minutes from reference time to valid time.

desigreftime: Designated reference time; used as a common reference time for all items when individual reference times do not match.

desigprojmins: Number of minutes from designated reference time to valid time.

Query the nowCOAST LayerInfo web service, which has been created to provide additional information about each data layer in a service, including a list of all available "time stops" (i.e. "valid times"), individual timestamps, or the valid time of a layer's latest available data (i.e. "Product Time"). For more information about the LayerInfo web service, including examples of various types of requests, refer to the nowCOAST help documentation at: http://new.nowcoast.noaa.gov/help/#section=layerinfo

References Kithil, 2015: Overview of Lightning Detection Equipment, National Lightning Safety Institute, Louisville, CO. (Available from http://www.lightningsafety.com/nsli_ihm/detectors.html).NASA and NOAA, 2014: Geostationary Lightning Mapper (GLM). (Available at http://www.goes-r.gov/spacesegment/glm.html).NWS, 2013: Experimental Lightning Strike Density Product Description Document. NOAA/NWS/NCEP/Ocean Prediction Center, College Park, MD (Available at http://www.opc.ncep.noaa.gov/lightning/lightning_pdd.php and http://products.weather.gov/PDD/Experimental%20Lightning%20Strike%20Density%20Product%2020130913.pdf). ,li>NOAA Knows Lightning. NWS, Silver Spring, MD (Available at http://www.lightningsafety.noaa.gov/resources/lightning3_050714.pdf).) Siebers, A., 2013: Soliciting Comments until June 3, 2014 on an Experimental Lightning Strike Density product (Offshore Waters). Public Information Notice, NOAA/NWS Headquarters, Washington, DC (Available at http://www.nws.noaa.gov/om/notification/pns13lightning_strike_density.htm).

Licensed agricultural tile drainage contractors create plans for numerous agricultural tile drainage systems and install thousands of feet of agricultural drainage tile each year. As a requirement of their license, each contractor must report to the Ontario Ministry of Agriculture, Food, and Rural Affairs (OMAFRA) the location of the area where they installed drainage tile. These areas are represented as polygon features.Legislated or Legal Authority for Collection: Agricultural Tile Drainage Installation Act (Regulation 18)Additional Time Period Information: The legislation was official as of 1983 but some the data holding may contain data that was installed prior to 1983. The legislation is still in effect therefore the data holding is still currently receiving information.Additional Metadata Location: Ontario Ministry of Agriculture and Food, Ontario Ministry of Rural Affairs website This class has related tables. Tile Drainage Area related tables Additional DocumentationTile Drainage Area - Data Description (PDF)Tile Drainage Area - Documentation (Word) Status On going: data is being continually updated Maintenance and Update Frequency Irregular: data is updated in intervals that are uneven in duration Contact Ontario Ministry of Agriculture, Food and Rural Affairs, omafra.gis@ontario.ca

LOW POVERTY INDEXSummary The low poverty index captures poverty in a given neighborhood. The index is based on the poverty rate (pv). The mean and standard error are estimated over the national distribution.The poverty rate is determined at the census tract level.InterpretationValues are inverted and percentile ranked nationally. The resulting values range from 0 to 100. The higher the score, the less exposure to poverty in a neighborhood.

Data Source: American Community Survey, 2011-2015. Related AFFH-T Local Government, PHA and State Tables/Maps: Table 12; Map 12. School Proficiency Index.

To learn more about the Low Poverty Index visit: https://www.hud.gov/program_offices/fair_housing_equal_opp/affh ; https://www.hud.gov/sites/dfiles/FHEO/documents/AFFH-T-Data-Documentation-AFFHT0006-July-2020.pdf, for questions about the spatial attribution of this dataset, please reach out to us at GISHelpdesk@hud.gov. Date of Coverage: 07/2020