The Residential Schools Locations Dataset in Geodatabase format (IRS_Locations.gbd) contains a feature layer "IRS_Locations" that contains the locations (latitude and longitude) of Residential Schools and student hostels operated by the federal government in Canada. All the residential schools and hostels that are listed in the Residential Schools Settlement Agreement are included in this dataset, as well as several Industrial schools and residential schools that were not part of the IRRSA. This version of the dataset doesn’t include the five schools under the Newfoundland and Labrador Residential Schools Settlement Agreement. The original school location data was created by the Truth and Reconciliation Commission, and was provided to the researcher (Rosa Orlandini) by the National Centre for Truth and Reconciliation in April 2017. The dataset was created by Rosa Orlandini, and builds upon and enhances the previous work of the Truth and Reconcilation Commission, Morgan Hite (creator of the Atlas of Indian Residential Schools in Canada that was produced for the Tk'emlups First Nation and Justice for Day Scholar's Initiative, and Stephanie Pyne (project lead for the Residential Schools Interactive Map). Each individual school location in this dataset is attributed either to RSIM, Morgan Hite, NCTR or Rosa Orlandini. Many schools/hostels had several locations throughout the history of the institution. If the school/hostel moved from its’ original location to another property, then the school is considered to have two unique locations in this dataset,the original location and the new location. For example, Lejac Indian Residential School had two locations while it was operating, Stuart Lake and Fraser Lake. If a new school building was constructed on the same property as the original school building, it isn't considered to be a new location, as is the case of Girouard Indian Residential School.When the precise location is known, the coordinates of the main building are provided, and when the precise location of the building isn’t known, an approximate location is provided. For each residential school institution location, the following information is provided: official names, alternative name, dates of operation, religious affiliation, latitude and longitude coordinates, community location, Indigenous community name, contributor (of the location coordinates), school/institution photo (when available), location point precision, type of school (hostel or residential school) and list of references used to determine the location of the main buildings or sites. Access Instructions: there are 47 files in this data package. Please download the entire data package by selecting all the 47 files and click on download. Two files will be downloaded, IRS_Locations.gbd.zip and IRS_LocFields.csv. Uncompress the IRS_Locations.gbd.zip. Use QGIS, ArcGIS Pro, and ArcMap to open the feature layer IRS_Locations that is contained within the IRS_Locations.gbd data package. The feature layer is in WGS 1984 coordinate system. There is also detailed file level metadata included in this feature layer file. The IRS_locations.csv provides the full description of the fields and codes used in this dataset.

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...

Updated July 2nd 2020 to adopt Pro 2.6 release and create Pro locators.This sample contains an ArcGIS Pro 2.6 Toolbox file containing five Spatial ETL Tools:ImportPSV2 - imports pipe separated source text files into a new (or existing, optionally to be overwritten) File Geodatabase.ImportStatePSV2 - the same as ImportPSV2 except includes a filter for a target state.MakeAllLocalityAliases - makes a city or locality alias table used in locator creation.MakeAddress2 - makes a point feature class ADDRESS with the schema similar to the ADDRESS_VIEW example in the PSMA documentation.MakeReferenceAddress - creates a point feature class REFERENCEADDRESS from the ADDRESS features, having expanded house number ranges and house number and subaddress details in suitable fields. This is the primary role data for the locator.The download also includes FME workbench FMW files (2020) for use in that product and ArcGIS Pro.You must re-source the Spatial ETL tools in the download toolbox to point to the FMW files in the download and you must re-path the data sources in each Spatial ETL tool to suit your project workspace.A model CreateGNAFLocator is in the download toolbox, use this to create your locator. A sample locator for the ACT is included.The sample locator and ones you create will support subaddress inputs, like flats and units.ImportPSV2 takes 19 hours to process 104M features on my machine. You might like to process a state at a time.If you add intermediate data to a map or leave an output geodatabase expanded in the Catalog pane you may get an error when writing output because of file locking. It is recommended you do not open an output workspace in Pro until app processing is complete.MakeAddress2 and MakeReferenceAddress take 4 hours to run for all Australia.The schema expected is as per February 2021, it may change each release, read the source documentation for change notices, this sample may not be maintained. The primary and foreign key fields according to PSMA's data model are indexed.G-NAF download site is: https://data.gov.au/dataset/geocoded-national-address-file-g-naf

This is a collection of maps, layers, apps and dashboards that show population access to essential retail locations, such as grocery stores. Data sourcesPopulation data is from the 2010 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer.Grocery store locations are from SafeGraph, reflecting what was in the data as of October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters.The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Alternative versions of these layers are available. These pairs use different colors but are otherwise identical in content.Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis.The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer's block figures can be summarized further, to tract, county and state levels.The SafeGraph grocery store locations were created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 records. In this map, this layer is included as a vector tile layer.MethodologyEvery census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway.A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle's access to all types of roads was factored in.The results for each analysis were captured in the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle).The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step.Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool uses a 200 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect.Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person's commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point.Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes