The ArcGIS World Geocoding Service finds addresses and places in all supported countries around the world in a single geocoding service. The service can find point locations of addresses, cities, landmarks, business names, and other places. The output points can be visualized on a map, inserted as stops for a route, or loaded as input for a spatial analysis.The service is available as both a geosearch and geocoding service:Geosearch Services – The primary purpose of geosearch services is to locate a feature or point of interest and then have the map zoom to that location. The result might be displayed on the map, but the result is not stored in any way for later use. Requests of this type do not require a subscription or a credit fee. Geocoding Services – The primary purpose of geocoding services is to convert an address to an x,y coordinate and append the result to an existing record in a database. Mapping is not always involved, but placing the results on a map may be part of a workflow. Batch geocoding falls into this category. Geocoding requires a subscription. An ArcGIS Online Subscription, or ArcGIS Location Platform Subscription, will provide you access to the ArcGIS World Geocoding service for batch geocoding.The service can be used to find address and places for many countries around the world. For detailed information on this service, including a data coverage map, visit the ArcGIS World Geocoding service documentation.

This Africa Geocoding locator is a view of the World Geocoding Service constrained to search for places in the countries of Africa. The World Geocoding Service finds addresses and places in all supported countries around the world in a single geocoding service. The service can find point locations of addresses, cities, landmarks, business names, and other places. The output points can be visualized on a map, inserted as stops for a route, or loaded as input for a spatial analysis.The service is available as both a geosearch and geocoding service:Geosearch Services – The primary purpose of geosearch services is to locate a feature or point of interest and then have the map zoom to that location. The result might be displayed on the map, but the result is not stored in any way for later use. Requests of this type do not require a subscription or a credit fee. Geocoding Services – The primary purpose of geocoding services is to convert an address to an x,y coordinate and append the result to an existing record in a database. Mapping is not always involved, but placing the results on a map may be part of a workflow. Batch geocoding falls into this category. Geocoding requires a subscription. An ArcGIS Online subscription will provide you access to the World Geocoding service for batch geocoding.The service can be used to find address and places for many countries around the world. For detailed information on this service, including a data coverage map, visit the World Geocoding service documentation.

VT E911 Composite geocoder - uses ESITE, RDSNAME, and RDSRANGE. REFRESHED WEEKLY. VCGI, in collaboration with the VT E911 Board, has created a suite of geocoding services that can be used to batch geocode addresses using ArcGIS Desktop 10.x. This service can also be integrated into ESRI ArcGIS web-based mapping applications.Input Address Requirements Must use valid E911 addresses (street style addressing...no P.O. box addresses!) and E911 town names. Limitations Don't attempt to geocode more than 50000 records or so. You must have an Internet connection to use the services. A DSL, cable, or other high bandwidth connection is the best option. Addresses other than E911 addresses are not supported. ArcGIS Pro - How To:Startup ArcGIS ProUnder the "Insert" ribbon select Connections --> New ArcGIS Server. Server URL = https://maps.vcgi.vermont.gov/arcgis/servicesBrowse to the ./EGC_services folder and select GEOCODE_COMPOSITE (or GEOCODE_ESITE).Add the table you want to geocode to project, then right-click and select "Geocode Table". Choose the “Go to Tool” option at the bottom of the dialogue box.Make selections and run geocoder.ArcGIS Desktop (ArcMap) - How To: Startup ArcMap 10+ Add a table containing VT addresses to geocode. ?Click the "Add Data" button.Navigate to your table, choose to add your tableRight-click on the table in the table of contentsSelect "Geocode Addresses...".Select "Add" in the dialog box.Browse to the "GIS Servers" icon in your catalog, then double click "Add ArcGIS Server".Select "Use GIS Services", then Next.ServerURL = https://maps.vcgi.vermont.gov/arcgis/services then click finish.Browse to "arcgis on maps.vcgi.org (user)". Browse to .\EGC_services folder.Select GECODE_ESITE (or GEOCODE_COMPOSITE). Click OK.Select whatever options you want in the geocode dialog box, including output, then click ok.The output will be automatically added to your ArcMap session.

The World Geocoding Service finds addresses and places in all supported countries around the world in a single geocoding service. The service can find point locations of addresses, cities, landmarks, business names, and other places. The output points can be visualized on a map, inserted as stops for a route, or loaded as input for a spatial analysis.The service is available as both a geosearch and geocoding service:Geosearch Services – The primary purpose of geosearch services is to locate a feature or point of interest and then have the map zoom to that location. The
result might be displayed on the map, but the result is not stored in
any way for later use. Requests of this type do not require a subscription or a credit fee. Geocoding Services – The primary purpose of geocoding services is to convert an address to an x,y coordinate and append the result to an existing record in a
database. Mapping is not always involved, but placing the results on a
map may be part of a workflow. Batch geocoding falls into this
category. Geocoding requires a subscription. An ArcGIS Online subscription will provide you access to the World Geocoding service for batch geocoding.The service can be used to find address and places for many countries around the world. For detailed information on this service, including a data coverage map, visit the World Geocoding service documentation.

Vermont composite geocoding service built with VT E911 data. This service can be used by ArcGIS Pro 2.8.x+ to batch geocode addresses stored in a table. It also can be used as a geocoder with most ArcGIS Online apps, as well as QGIS. [How To Use The Vermont Geocoding Service]This ArcGIS Online item utilizes the ArcGIS Server geocoding service at this REST Endpoint: https://maps.vcgi.vermont.gov/arcgis/rest/services/EGC_services/GCS_E911_COMPOSITE_SP_v2/GeocodeServer

The Street_and_Address_Composite will return a geographic coordinate when a street address is entered. A user can enter an address either manually or by bulk input from a database or other source.The geocoder returns a coordinate pair and standardized address for each input address it is able to match. The NYS ITS Geospatial Services geocoder uses a series of combinations of reference data and configuration parameters to optimize both the likelihood of a match and the quality of the results. The reference data supporting the geocoder is stored in Federal Geographic Data Committee (FGDC) standard.The first composite locator (Street_and_Address_Composite) is made up of the following set of locators which are most likely to return a high quality hit. The locators are listed in the order in which they will be accessed along with a brief description of the locator's source data. These six locators will generate the majority of the results when geocoding addresses.Locator NameSource DataDescription1A_SAM_AP_ZipNameSAM Address PointsSAM address points using the postal zip code name for the city name in the locator.1B_SAM_AP_CTNameSAM Address PointsSAM address points. The city or town name is used for the city name in the locator.1C_SAM_AP_PlaceNameSAM Address PointsSAM address points. The city name is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These names do not exist everywhere so there will be a limited number of points in this locator.3A_SS_ZipNameNYS Street SegmentsNYS Street Segments dataset using the postal zip code name for the city name in the locator. The location is interpolated from an address range on the street segment. The city name can be different for the left and right sides of the streets.3B_SS_CTNameNYS Street SegmentsNYS Street Segments using the city or town name for the city name in the locator. The location is interpolated from an address range on the street segment.3C_SS_PlaceNameNYS Street SegmentsNYS Street Segments using an alternate place name for the city field. This field is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These areas do not exist everywhere so there will be a limited number of segments with this attribute. The location is interpolated from an address range on the street segment.For more information about the geocoding service, please visit: https://gis.ny.gov/address-geocoder.For documentation on how to add these locators to ArcGIS, please reference Adding the Statewide Geocoding Web Service. If you would like these locators to be your default locators in ArcGIS, copy DefaultLocators.xml to C:\Users<username>\AppData\Roaming\ESRI\Desktop10.X\Locators, where

Context

This dataset contains the locations found in the Kiva datasets included in an administrative or geographical region. You can also find poverty data about this region. This facilitates answering some of the tough questions about a region's poverty.

Content

In the interest of preserving the original names and spelling for the locations/countries/regions all the data is in Excel format and has no preview (I think only the Kaggle recommended file types have preview - if anyone can show me how to do this for an xlsx file, it will be greatly appreciated)

The Tables datasets contain the most recent analysis of the MPI on countries and regions. These datasets are updated regularly. In unique regions_names_from_google_api you will find 3 levels of inclusion for every geocode provided in Kiva datasets. (village/town, administrative region, sub-national region - which can be administrative or geographical). These are the results from the Google API Geocoding process.

Files:

• all_kiva_loans.csv

Dropped multiple columns, kept all the rows from loans.csv with names, tags, descriptions and got a csv file of 390MB instead of 2.13 GB. Basically is a simplified version of loans.csv (originally included in the analysis by beluga)

• country_stats.csv

1. population source: https://en.wikipedia.org/wiki/List_of_countries_by_population_(United_Nations)
2. population_below_poverty_line: Percentage
3. hdi: Human Development Index
4. life_expectancy: Life expectancy at birth
5. expected_years_of_schooling: Expected years of schooling
6. mean_years_of_schooling: Mean years of schooling
7. gni: Gross national income (GNI) per capita This dataset was originally created by beluga.

• all_loan_theme_merged_with_geo_mpi_regions.xlsx

This is the loan_themes_by_region left joined with Tables_5.3_Contribution_of_Deprivations. (all the original entries from loan_themes and only the entries that match from Tables_5; for the regions that lack MPI data, you will find Nan)

These are the columns in the database:

1. Partner ID
2. Field Partner
3. Name
4. sector
5. Loan Theme ID
6. Loan Theme Type
7. Country
8. forkiva
9. number
10. amount
11. geo
12. rural_pct
13. City
14. Administrative region
15. Sub-national region
16. ISO
17. World region
18. Population Share of the Region (%)
19. region MPI
20. Education (%)
21. Health (%)
22. Living standards (%)
23. Schooling (%)
24. Child school attendance (%)
25. Child Mortality (%)
26. Nutrition (%)
27. Electricity (%)
28. Improved sanitation (%)
29. Drinking water (%)
30. Floor (%)
31. Cooking fuel (%)
32. Asset ownership (%)

• mpi_on_regions.xlsx

Matched the loans in loan_themes_by_region with the regions that have info regarding MPI. This dataset brings together the amount invested in a region and the biggest problems the said region has to deal with. It is a join between the loan_themes_by_region provided by Kiva and Tables 5.3 Contribution_of_Deprivations.

It is a subset of the all_loan_theme_merged_with_geo_mpi_regions.xlsx, which contains only the entries that I could match with poverty decomposition data. It has the same columns.

• Tables_5_SubNational_Decomposition_MPI_2017-18.xlsx

Multidimensional poverty index decomposition for over 1000 regions part of 79 countries.

Table 5.3: Contribution of deprivations to the MPI, by sub-national regions
This table shows which dimensions and indicators contribute most to a region's MPI, which is useful for understanding the major source(s) of deprivation in a sub-national region.

Source: http://ophi.org.uk/multidimensional-poverty-index/global-mpi-2016/

• Tables_7_MPI_estimations_country_levels.xlsx

MPI decomposition for 120 countries.

Table 7 All Published MPI Results since 2010
The table presents an archive of all MPI estimations published over the past 5 years, together with MPI, H, A and censored headcount ratios. For comparisons over time please use Table 6, which is strictly harmonised. The full set of data tables for each year published (Column A), is found on the 'data tables' page under 'Archive'.

The data in this file is shown in interactive plots on Oxford Poverty and Human Development Initiative website. http://www.dataforall.org/dashboard/ophi/index.php/

• unique_regions_from_kiva_loan_themes.xlsx

These are all the regions corresponding to the geocodes found in Kiva's loan_themes_by_region. There are 718 unique entries, that you can join with any database from Kiva that has either a coordinates or region column.
Columns:

• geo: pair of Lat, Lon (from loan_themes_by_region)

• City: name of the city (has the most NaN's)

• Administrative region: first level of administrative inclusion for the city/location; (the equivalent of county for US)

• Sub-national region: second level of administrative inclusion for the geo pair. (like state for US)

• Country: name of the country

Acknowledgements

Thanks to Shane Lynn for the batch geocoding and to Joseph Deferio for reverse geocoding:

https://www.shanelynn.ie/batch-geocoding-in-python-with-google-geocoding-api/

https://github.com/jdeferio/Reverse_Geocode

The MPI datasets you can find on the Oxford website (http://ophi.org.uk/) under Research.

"Citation: Alkire, S. and Kanagaratnam, U. (2018)

“Multidimensional Poverty Index Winter 2017-18: Brief methodological note and results.” Oxford Poverty and Human Development Initiative, University of Oxford, OPHI Methodological Notes 45."

This repository contains data and codes that support the findings of the study.- PPD-EPC open dataset with the enriched spatial analyses scores and UPRN.- Batch Geocoding Notebook of PPD-EPC dataset with GeoPy - Here API- PyQGIS codes for proximity, terrain, and visibility spatial analyses.- Jupyter Notebook of Machine Learning algorithms for mass property valuation.

Access to these data files and dissemination of data retrieved from them is restricted to current faculty, staff or students employed by, or studying at UBC. Users must also abide by the DMTI License Agreement. This product is designed to be installed on a Windows based computer system. To install, download GeoPinpoint.zip and package.zip to a temporary directory. Uncompress package.zip using WinZip or a similar utility. Run TMSetup.exe to complete the installation. If you require data only, they are contained in GeoPinpoint.zip. A list of all the files is contained in the file FileList (below). Features Graphic User Interface that includes user friendly menus and geocoding options Geocode large databases in a single pass quickly and accurately (interactive and batch mode) Flexible input and output options to standardize address data Interactive geocoding process that allows user input for difficult matches Ability to generate a summary report containing intuitive description of geocoding results Supports ODBC connection (Oracle 8 and Microsoft Access 97 and 2000) Geo-reference Database Coverage: National

Location of TxDot properties generated from TxDot files to point layer files batch geocoding.

Street_NoNum_and_ZipCode_Composite uses the NYS Streets and Zipcode boundaries to return a match within the street segment. Any address that does not successfully geocode to the first composite can then be run through the second composite locator (Street_NoNum_and_ZipCode_Composite). Recognizing that hits from this locator will not be spatially accurate. This composite locator is made up of the following locators.Locator NameSource DataDescription4A_SS_NoNum_ZipNameNYS Street SegmentsNYS Street Segments dataset using the postal zip code name for the City name in the locator. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.4B_SS_NoNum_CTNameNYS Street SegmentsNYS Street Segments dataset using the city or town name is used for the city name in the locator. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.4C_SS_NoNum_PlaceNameNYS Street SegmentsNYS Street Segments dataset using the alternate place name is used for the city name in the locator. This field is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These areas do not exist everywhere so there will be a limited number of segments with this attribute. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.5_ZipCodePtsZip Code boundariesPoint placed at the centroid of the Zip Code boundaries. Currently, the geocoding service will return all of the results when using the Find Tool within ArcGIS. The user will then be responsible for choosing which of the results they want to keep. The SAM Address Points are the most accurate data available and should be picked anytime a result is returned from one of the SAM address point locators. If the geocoding service is used in the ESRI batch tool, the locator will return a Match from the first locator it comes to in the cascading order. If there are multiple locators with the same score or within the same locator the first result is returned and it is coded as a Tie.The locators will output a field named 'User_fld' which should be used in conjunction with the Loc_Name field. When the Loc_Name field contains one of the Address Point locators (1A, 1B or 1C) this field will contain either a 1,2,3,4 or a 5. When the Loc_Name field contains anything other than the Address Point locators, the 'User_fld' will either be NULL or "0". The numeric values correspond with the type of Address Point that was located:RooftopPrimary Structure EntranceDrivewayParcel CentroidMiscellaneous

A table of Bike305 Calendar Evetns. This table is populated through the Calendar Wiz api. It populates a view VW_TblCalendarWizEvent. It is used by batch job J716140 which creates a point layer from geocoding events addresses from the view.Updated: Not Planned

Description: All current, active business licensesProcess: Data is queried from TRMS, processed to clean up common addressing issues (change "FT LOWELL" to "FORT LOWELL" - street name "1" become "1ST", funny "ÿ" characters are removed etc) and geocoded. Geocoding is a 3 step process: 1 - whole table is geocoded to adparcel with a 9.3.1 geocoder (scores of 69 and higher become seperate layer)2 - anything with a score of 68 or below is joined to adparcel based on street #, street direction and street name - those that have a match have their address recalculated based on the full address in adparcel and are geocoded again with the 9.3.1 geocoder (become seperate layer)3 - those from step 2 that do not have a match in adparcel are goecoded to stnetall and everything with a score of 80 or above are exported out as a seperate layerLayers from steps 2 and 3 are appended into layer in step 1 and the original buslic FC has records deleted and the new data appended.Attributes: ACC_NUM: account numberACC_NAME: account nameOWN_CODE: ownership codeOWN_DESC: ownership descriptionTYPE_CODE: business type code (RRP is RENTAL REAL PROPERTY is a license for renting a building)TYPE_DESC: business type descriptionNAIC_CODE: NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM number codesNAIC_DESC: NAICS descriptionLIC_TYPE: SVL (Service License - professional and service businesses, may collect use tax) or PLL (Privilige LicenseLicense, businesses that collect sales tax)DT_START: start date of businessDT_ISSUED: issued date of current business license CITY: Tucson or several astericks with numbers in between indicates multiple addressesSTATE: AZZIP_CODE: zipcode from TRMSADD_ORIG: original address from TRMS, including suite/unit numberADD_MATCH: address account matched to (this will not necessary match the ADD_ORIG field)MT: match type, number indicates which geocoding step was used (1 = highest quality match, 3 = lowest quality match)---------------------------------------------------------------------------------------------------------------------------------------------------------------Who: Original TRMS (TAX MANTRA) data query and geoprocessing done by Johanna Kraus - March 2011Maintinance/Update Schedule: Data and geoprocessing are a batch job done weekly.-----------------------------------------------------------------------------------------------------------------------------------------------------------------Known Errors:All locations are approximate. Most data is mapped to existing address points (which are not precise locations),those records that don't have an equivilant address match are approximated along the address range of street. SeeMT field for more details.Fields for NAICS codes, business types and owner types may be missing data or incorrect.Data layer should not be considered a complete listing of all active businesses in Tucson. Please send spatial errors to GIS_IT@tucsonaz.govPlease send data errors to Tax-License@tucsonaz.gov