Laatste update: 10 maart 2025Gebruikers die graag met Microsoft Excel werken kunnen met de ArcGIS for Excel Add-in hun feature layers aanmaken en bewerken vanuit Excel. Ook voor gebruikers die minder vaak met Excel werken kunnen met deze Add-In gebruik maken van nieuwe functionaliteiten. In dit artikel wordt besproken hoe de Add-in kan worden toegevoegd, hoe vanuit Excel een feature layer aangemaakt kan worden, hoe een bestaande feature layer bewerkt kan worden vanuit Excel en hoe aan de hand van functies coördinaten en adressen van punten berekend kunnen worden.

With this add in it is possible to create map templates from GIS files in KML format, and create choropleths with them. Providing you have access to KML format map boundary files, it is possible to create your own quick and easy choropleth maps in Excel. The KML format files can be converted from 'shape' files. Many shape files are available to download for free from the web, including from Ordnance Survey and the London Datastore. Standard mapping packages such as QGIS (free to download) and ArcGIS can convert the files to KML format. A sample of a KML file (London wards) can be downloaded from this page, so that users can easily test the tool out. Macros must be enabled for the tool to function. When creating the map using the Excel tool, the 'unique ID' should normally be the area code, the 'Name' should be the area name and then if required and there is additional data in the KML file, further 'data' fields can be added. These columns will appear below and to the right of the map. If not, data can be added later on next to the codes and names. In the add-in version of the tool the final control, 'Scale (% window)' should not normally be changed. With the default value 0.5, the height of the map is set to be half the total size of the user's Excel window. To run a choropleth, select the menu option 'Run Choropleth' to get this form. To specify the colour ramp for the choropleth, the user needs to enter the number of boxes into which the range is to be divided, and the colours for the high and low ends of the range, which is done by selecting coloured option boxes as appropriate. If wished, hit the 'Swap' button to change which colours are for the different ends of the range. Then hit the 'Choropleth' button. The default options for the colours of the ends of the choropleth colour range are saved in the add in, but different values can be selected but setting up a column range of up to twelve cells, anywhere in Excel, filled with the option colours wanted. Then use the 'Colour range' control to select this range, and hit apply, having selected high or low values as wished. The button 'Copy' sets up a sheet 'ColourRamp' in the active workbook with the default colours, which can just be extended or deleted with just a few cells, so saving the user time. The add-in was developed entirely within the Excel VBA IDE by Tim Lund. He is kindly distributing the tool for free on the Datastore but suggests that users who find the tool useful make a donation to the Shelter charity. It is not intended to keep the actively maintained, but if any users or developers would like to add more features, email the author. Acknowledgments Calculation of Excel freeform shapes from latitudes and longitudes is done using calculations from the Ordnance Survey.

The ArcGIS Monitor Excel report task summarizes statistics for a specified time range (eg. last 7 days). The user can edit the config.json parameters to determine what timeframe, report path, and modules (tabs) to be included. Long-running reports over 7 days are best scheduled as a task and may avoid web time-out conditions in some environments.For more information on configuring the extension, see the PDF included in the download.

The Spinel Count dataset comprises counts, grouped by sample number, of spinel group end-members including chromite, magnesiochromite, spinel (sensu stricto), hercynite, magnetite, ulvospinel, and other species. In addition, the Creighton’s Excel add-in was used to classify spinel group minerals as basaltic, kimberlite groundmass, ultramafic, or diamond inclusion. Counts were derived from the Microprobe Analyses and Mineral Interpretation dataset with the objective to facilitate the evaluation of mineralogy, quantity and spatial distribution of KIMs with a GIS software. Counts are based on the interpreted detailed mineral data field [Det_Min] and only included those grains with analyses with total oxides [Total_Calc] between 98.5 and 101 wt.%.

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Water_Type/MapServer/4For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.It is intended that these data be only a first step in determining whether or not wetland issues have been or need to be addressed in an area. The DNR Forest Practices Division and the Department of Ecology strongly supports the additional use of hydric soils (from the GIS soils layer) to add weight to the call of 'wetland'. Reports from the Department of Ecology indicate that these data may substantially underestimate the extent of forested wetlands. Various studies show the NWI data is 25-80% accurate in forested areas. Most of these data were collected from stereopaired aerial photos at a scale of 1:58,000. The stated accuracy is that of a 1:24,000 map, or plus or minus 40 feet. In addition, some parts of the state have data that are 30 years old and only a small percentage have been field checked. Thus, for regulatory purposes, the user should not rely solely on these data. On-the-ground checking must accompany any regulatory call based on these data.The reclassification is based on the USFWS FWS_CODE. The FWS_CODE is a concatenation of three subcomponents: Wetland system, class, and water regime. Forest Practices further divided the components into system, subsystem, class, subclass, water regime, special modifiers, xclass, subxclass, and xsystem. The last three items (xsomething) are for wetland areas which do not easily lend themselves to one class alone. The resulting classification system uses two fields: WLND_CLASS and WLND_TYPE. WLND_CLASS indicates whether the polygon is a forested wetland (F), open water (O), or a vegetated wetland (W). WLND_TYPE, indicates whether the wetland is a type A (1), type B (2), or a generic wetland (3) that doesn't fit the categories for A or B type wetlands. WLND_TYPE = 0 (zero) is used where WLND_CLASS = O (letter "O").

The wetland polygon is classified as F, forested wetland; O, open water; or W, vegetated wetland depending on the following FWS_CODE categories: F O W --------------------------------------------------- Forested Open Vegetated Wetland Water Wetland --------------------------------------------PFO* POW PUB5 E2FO PRB* PML2 PUB1-4 PEM* PAB* L2US5 PUS1-4 L2EM2 PFL* PSS* L1RB* PML1 L1UB*
L1AB* L1OW L2RB* L2UB* L2AB* L2RS* L2US1-4 L2OW

• indicates inclusion of the subcategory (ie. PEM* includes PEM1F, PEM1FB, etc.).

DNR FOREST PRACTICES WETLANDS DATASET ON FPARS Internet Mapping Website: The FPARS Resource Map and Water Type Map display Forested, Type A, Type B, and "other" wetlands. Open water polygons are not displayed on the FPARS Resource Map and Water Type Map in an attempt to minimize clutter. The following code combinations are found in the DNR Forest Practices wetlands dataset:

WLND_CLASS WLND_TYPE wetland polygon classification F 3 Forested wetland as defined in WAC 222-16-035 O 0 *NWI open water (not displayed on FPARS Resource or Water Type Maps) W 1 Type A Wetland as defined in WAC 222-16-035 W 2 Type B Wetland as defined in WAC 222-16-035 W 3 other wetland

• NWI open water polygons are indicated by WLND_CLASS = O and WLND_TYPE = 0. Open water is used in the USFWS and WAC 222-16-035 classification system. These open water polygons are not included in the FPARS Resource Map and Water Type Map views of this dataset in an attempt to minimize clutter on the FPARS maps.

This Garnet Class Counts comprises counts, grouped by sample number, of garnet grains by garnet class. Garnets were classified by using Creighton’s Excel add-in to determine garnet class (G0, G1, G3, G3D, G4, G4D, G5, G5D, G9, G10, G10D, G11, or G12). Counts were derived from the Microprobe Analyses and Mineral Interpretation dataset with the objective to facilitate the evaluation of mineralogy, quantity and spatial distribution of KIMs with a GIS software. Counts are based on the garnet class data field [G-class] and only included those grains with analyses with total oxides [Total_Calc] between 98.5 and 101 wt.%.

The Arizona Local Government Safety Project Model is a tool that can be used to facilitate the selection of hazardous roadway locations in local jurisdictions, to prioritize those locations by rational means, and to aid in the evaluation of potential spot treatments of safety hazards. However, the model is not intended to automate the entire decision-making process, and can not substitute for the analysis and judgment of a traffic engineer. While Arizona LGSP Model should prove to be a useful tool, particularly for jurisdictions with limited research budgets or capabilities, use of the model is not mandatory, and is subject to the preference of each jurisdiction. The Arizona Local Government Safety Project Implementation Model (LGSP model) was created in MS Access 97. The model consists of a self-contained query and reporting database, and a supplemental database of crash records on CDROM. Running the model requires the following hardware and software: Microsoft Office 97 or newer: Access, Word and Excel programs, MS Access must be loaded with the “Linked Table Manager” add-in, CDROM drive or network access, and Approximately 32Mb RAM and 100Mb hard disk space The model is computation-intensive, and will require a significant amount of time to run on machines with slower processors. On slower processors, it is particularly important that additional programs be closed while the update is being run. The amount of time required for a complete update of the model will vary with the power of the machine used, the speed of CDROM or network data transfer, and the size of the jurisdiction(s) being analyzed. It is recommended that smaller units of analysis (e.g. a single city rather than an entire county) be examined separately whenever possible.

The community profiles contain data from 2016 Census and long form program. The 2016 census data is considered to be of good quality and general comparisons can be made with similar data from previous years. Direct comparisons cannot be made between Statistics Canada’s 2016 Long Form data and the 2011 National Household Survey (NHS).The figures shown in the tables and charts have been subjected to a confidentiality procedure known as random rounding to prevent the possibility of associating statistical data with any identifiable individual. Under this method, all figures, including totals and margins, are randomly rounded either up or down to a multiple of "5", and in some cases "10". While providing strong protection against disclosure, this technique does not add significant error to the data. The user should be aware that totals and margins are rounded independently of the cell data so that some differences between these and the sum of rounded cell data may exist. Also, minor differences can be expected in corresponding totals and cell values among various census tabulations.Statistics Canada is committed to protect the privacy of all Canadians and the confidentiality of the data they provide. As part of this commitment, some population counts of geographic areas are adjusted in order to ensure confidentiality.For more information about Kingston's Community & Neighbourhood Profiles, as well as links to exciting new tools, please visit our website: https://www.cityofkingston.ca/explore/neighbourhood-profilesA detailed Glossary of Terms is also available (Adobe PDF format): https://drive.google.com/file/d/1KAbrqmARXjzy1yBcVlVYf2Xz-KidOfXM/view?usp=sharingNOTE: The data delivered by Statistics Canada for Kingston has been altered and "category totals" removed in the languages section. This was necessary in order to ensure compatibility when downloading the data with third party applications (e.g., MS Excel, ESRI Shapefile).