DOCSLIB.ORG

Global Geocoding SDK V2.1.0 Developer Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Location Intelligence Global Geocoding SDK Version 2.1 REST and Java API Developer Guide Table of Contents Appendix C: Result Codes 147 1 - Installation Appendix D: Error Messages 181 Deploying the Global Geocoding SDK Distribution 4 2 - Using the Global Geocoding SDK Introduction to the Global Geocoding APIs 11 3 - REST Web Services Geocode Service 13 Reverse Geocode Service 35 Interactive Geocode Service 45 Key Lookup Service 53 Capabilities Service 58 Dictionaries Service 66 PBLocator REST API 70 4 - Java API Getting Started 78 Configuring 78 Javadocs 80 Chapter : Appendices Appendix A: ISO 3166-1 Country Codes 82 Appendix B: Country-Specific Custom Fields 91 1 - Installation In this section Deploying the Global Geocoding SDK Distribution 4 Installation Deploying the Global Geocoding SDK Distribution Global Geocoding SDK resources must be deployed and configured before they can be used by a geocoding engine. This section explains the necessary commands. The following topics are covered: • Geocoding CLI Utility on page 5 • deploy Command on page 6 • extract Command on page 6 • configure Command on page 7 • setting Command on page 7 Syntax Conventions The following syntax conventions apply when using these CLI commands: Values containing a space must be enclosed with quotes, for example, "Some Value" Path slash marks must be escaped with quotes around it. For example: • A Windows path "C:\path", must be written as "C:\\path" or "C:/path" • A Linux /path must be written as "/path" Global Geocoding SDK 2.1 REST and Java API Developer Guide 4 Installation Geocoding CLI Utility Geocoding CLI utility is bundled with the Global Geocoding SDK (GGS) distribution. Starting CLI The cli folder contains the files as below. • lib: Contains java library for available utility commands. • resources: Contains GGS resources including GGS Javadocs • cli.cmd: Windows batch script to start Geocoding CLI shell. • cli.sh: Linux shell script to start Geocoding CLI shell. • Logging.properties Contains properties required for logging strategy. Note: cli.cmd is for Windows users. cli.sh is for UNIX/Linus users. Ensure that the cli.sh file has execute permission. chmod 755 cli.sh Now cli.sh shell script file is executable. cli.sh Execute this shell script to start geocoding CLI shell. $ ./cli.sh CLI Batch Process How to run the cli commands as a batch process: Linux platform ./cli.sh --cmdfile ./commands.cli Windows platform ./cli.cmd --cmdfile commands.cli Global Geocoding SDK 2.1 REST and Java API Developer Guide 5 Installation deploy Command The Global Geocoding SDK distribution is deployed by using CLI's deploy command. Use the deploy command to deploy the application to a Tomcat webapps directory, creating an application ROOT directory if necessary. This example uses "Geocode" as the directory. Format of this command: deploy --c "/ggs-dist-{version}/resources" --m "WAR_EXTRACTED" --d "/tomcat/webapps/Geocode" --l "/tomcat/logs" where the deploy parameters are: --c or --config Configuration resources directory.is included at root level of as a resources directory when extracted --m or --mode Deployment mode default: WAR WAR - will configure and copy .war to destination directory WAR_EXTRACTED - will configure and extract .war file to destination directory. Destination directory must be empty JAVA_API -will configure and copy the Java API to the destination directory (must be empty). The logDirectory path param (–l or --logDirectory) is not required. --d or --destination Destination directory where application will be configured, for example tomcat/webapps/Geocode --l or --logDirectory Logging directory is required for WAR and WAR_EXTRACTED file deployments where the application will create log files. Optional for JAVA_API. extract Command Reference data for geocoding, such as streets and points, and Interactive is bundled as .spd files, which must extracted and configured before it is available for use. Format of the extract command: extract --s "/location/to/spd/files" --d "/data" where --s is the location of the source .spd file and --d is the destination folder for the extracted data. Global Geocoding SDK 2.1 REST and Java API Developer Guide 6 Installation configure Command Once the geocoding reference data has been extracted, it must be configured for use. The configuration parameters go into a JsonDataConfig.json. This file is created when you run the configure command. Format of this command: configure --s "/data" --d "/ggs-dist-{version}/resources/config" where --s is the location of the extracted .spd file and --d is the destination folder for the generated JsonDataConfig.json. Note: If a REST Service is running, the web server must be restarted whenever JsonDataConfig.json is updated. To configure the data located on multiple paths, the format is: configure --s "/data,/data2" --d "/ggs-dist-{version}/resources/config" where "/data,/data2" are two folders of data. setting Command The setting command is used to change a setting in the GGS API. To modify settings using the CLI, follow this format: setting --n [Name of setting] --v [Value for setting] --d [Path to configuration dir] --t [Type of setting] To remove a particular setting, set --v to an empty string, e.g., --v "". To define a country setting, use the country ISO 3 code with --t [Type of setting]. Examples: # Global Settings setting --n MAXIMUM_BATCH_SIZE --v 100 --d "/path/to/config/dir" # or with type specified setting --n MAXIMUM_BATCH_SIZE --v 100 --d "/path/to/config/dir" --t GLOBAL # Country level settings (use iso3 country code for country level settings) Global Geocoding SDK 2.1 REST and Java API Developer Guide 7 Installation setting --n RETURN_EXTENDED_DATA --v no --d "/path/to/config/dir" --t USA # Core settings setting --n COUNTRY_FALLBACK_MODE --v BASIC --d "/path/to/config/dir" --t CORE_SETTINGS Manually Configuring Datasets If you have data that was not installed and configured using Geocoding CLI Utility on page 5, you can manually edit a .json file to include the path, properties and other information about your data. You can include as many countries and datasets as you want in the file. JsonDataConfig.json is located in the Global Geocoding SDK (GGS) installation directory under the /resources/config directory. There are two main sections to the file: roots and countries. • roots - may contain one or more key:value pairs that define locations where several countries are installed. "root1" key can be any name you wish. • countries - a list of configurations by country where each configuration is identified by its ISO-3 country code. Each country configuration can contain properties and a list of datasets. The keys in this section are not arbitrary. { "roots" : { "root1" : "C:\\mydata" }, "countries" : [ { "country" : "USA", "properties" : null, "dataSets" : [ ] }] } The example below has been edited to include several countries, one with multiple datasets for USA (CTP, TTS). In the case of CTP, notice useRoot is true. The path to the data then is root1 plus path (c:\\myserver\\mydata\\DVDCPoints). When useRoot is false, as in the case for TTS, the path to the dataset must be defined in the path element. The rootId would be ignored. { "roots": { "root1": "c:\\myserver\\mydata" }, "countries": [ { Global Geocoding SDK 2.1 REST and Java API Developer Guide 8 Installation "country": "USA", "properties": { "RETURN_EXTENDED_DATA": "yes", "DEBUG": "no", "GEOSTAN_INSTANCE_COUNT": "5", "APN_CODE": "true", "ELV_CODE": "true", "FILE_MEMORY_LIMIT": "2000" }, "dataSets": [ { "name": "CTP", "path": "/DVDCPoints", "rootId": "root1", "useRoot": true }, { "name": "TTS", "path": "c:\\myserver2\\mydata\\TTS", "rootId": "THIS_WILL_BE_IGNORED_SINCE_useRoot_IS_FALSE", "useRoot": false } ] }, { "country": "ABW", "properties": null, "dataSets": [ { "name": "NTS", "path": "/ABW/NTS", "rootId": "root1", "useRoot": true } ] }, { "country": "ARG", "properties": null, "dataSets": [ { "name": "NTS", "path": "/ARG/NTS", "rootId": "root1", "useRoot": true } ] }, ] } Global Geocoding SDK 2.1 REST and Java API Developer Guide 9 2 - Using the Global Geocoding SDK In this section Introduction to the Global Geocoding APIs 11 Using the Global Geocoding SDK Introduction to the Global Geocoding APIs The Global Geocoding SDK allows you to develop and deploy geocoding desktop, mobile or Web applications that are capable of delivering location information for over 120 countries. This guide contains information about using the REST and Java APIs which provide: • Geocode Service - The Geocode Service service performs forward geocoding using input addresses and returning location data and other information. Reverse Geocode Service - The Reverse Geocode Service service performs reverse geocoding using input coordinates and returns address information that is the best match for that point. Interactive Geocode Service - The Interactive Geocode Service service suggests addresses and place names as you type. Key Lookup Service - The Key Lookup Service service returns geocoded candidates when given a unique key. It is a more efficient method than matching with an address, as the key is unique to that address. Global Geocoding Module supports the pbKey™ unique identifier for US data and the G-NAF key for AUS data. Each service has options that allow you to control matching and geocoding criteria, dataset resource configuration and more. Global Geocoding SDK 2.1 REST and Java API Developer Guide 11 3 - REST Web Services In this section Geocode Service 13 Reverse Geocode Service 35 Interactive Geocode Service
Recommended publications
  • ECE/TRADE/C/CEFACT/2021/20 Economic and Social Council Distr.: General 29 January 2021

    ECE/TRADE/C/CEFACT/2021/20 Economic and Social Council Distr.: General 29 January 2021

    United Nations ECE/TRADE/C/CEFACT/2021/20 Economic and Social Council Distr.: General 29 January 2021 Original: English Economic Commission for Europe Executive Committee Centre for Trade Facilitation and Electronic Business Twenty-seventh session Geneva, 19-20 April 2021 Item 9 of the provisional agenda Advisory Group on the United Nations Code for Trade and Transport Locations Report of the United Nations Code for Trade and Transport Location Advisory Group at its Fourth Annual Meeting Submitted by the secretariat Summary The United Nations Code for Trade and Transport Location (UN/LOCODE) Advisory Group held its fourth annual meeting on 27 November 2020. The secretariat prepared a conference report detailing activities undertaken by the Group and decisions made at the meeting. The participants reviewed and agreed to this report. The report provides a summary of the major activities conducted by the Group, the developments and the decisions related to UN/LOCODE, such as supporting the use of UN/LOCODE to identify the Agreement on Port State Measures (PSMA) designated ports by the Food and Agriculture Organization (FAO) to combat Illegal, Unreported and Unregulated (IUU) fishing; the publication of the revised United Nations Economic Commission for Europe (UNECE) Recommendation No. 16; the UN/LOCODE maintenance and the UN/LOCODE Re-engineering project. Document ECE/TRADE/C/CEFACT/2021/20 is submitted by the secretariat to the twenty- seventh UN/CEFACT Plenary for endorsement. ECE/TRADE/C/CEFACT/2021/20 I. Introduction and attendance 1. The UN/LOCODE Advisory Group held its fourth annual meeting on 27 November 2020. Because of the global COVID-19 pandemic, the face-to-face meeting could not be held as usual and the meeting was thus organized virtually.
  • Identifying Locations of Social Significance: Aggregating Social Media Content to Create a New Trust Model for Exploring Crowd Sourced Data and Information

    Identifying Locations of Social Significance: Aggregating Social Media Content to Create a New Trust Model for Exploring Crowd Sourced Data and Information

    Identifying Locations of Social Significance: Aggregating Social Media Content to Create a New Trust Model for Exploring Crowd Sourced Data and Information Al Di Leonardo, Scott Fairgrieve Adam Gribble, Frank Prats, Wyatt Smith, Tracy Sweat, Abe Usher, Derek Woodley, and Jeffrey B. Cozzens The HumanGeo Group, LLC Arlington, Virginia, United States {al,scott,adam,frank,wyatt,tracy,abe,derek}@thehumangeo.com Abstract. Most Internet content is no longer produced directly by corporate organizations or governments. Instead, individuals produce voluminous amounts of informal content in the form of social media updates (micro blogs, Facebook, Twitter, etc.) and other artifacts of community communication on the Web. This grassroots production of information has led to an environment where the quantity of low-quality, non-vetted information dwarfs the amount of professionally produced content. This is especially true in the geospatial domain, where this information onslaught challenges Local and National Governments and Non- Governmental Organizations seeking to make sense of what is happening on the ground. This paper proposes a new model of trust for interpreting locational data without a clear pedigree or lineage. By applying principles of aggregation and inference, it is possible to identify locations of social significance and discover “facts” that are being asserted by crowd sourced information. Keywords: geospatial, social media, aggregation, trust, location. 1 Introduction Gathering geographical data on populations has always constituted an essential element of census taking, political campaigning, assisting in humanitarian disasters/relief, law enforcement, and even in post-conflict areas where grand strategy looks beyond the combat to managing future peace. Warrior philosophers have over the millennia praised indirect approaches to warfare as the most effective means of combat—where influence and information about enemies and their supporters trumps reliance on kinetic operations to achieve military objectives.
  • Package 'Passport'

    Package 'Passport'

    Package ‘passport’ November 7, 2020 Type Package Title Travel Smoothly Between Country Name and Code Formats Version 0.3.0 Description Smooths the process of working with country names and codes via powerful parsing, standardization, and conversion utilities arranged in a simple, consistent API. Country name formats include multiple sources including the Unicode Common Locale Data Repository (CLDR, <http://cldr.unicode.org/>) common-sense standardized names in hundreds of languages. Depends R (>= 3.1.0) Imports stats, utils Suggests covr, dplyr, DT, gapminder, ggplot2, jsonlite, knitr, mockr, rmarkdown, testthat, tidyr License GPL-3 | file LICENSE URL https://github.com/alistaire47/passport, https://alistaire47.github.io/passport/ BugReports https://github.com/alistaire47/passport/issues Encoding UTF-8 LazyData true RoxygenNote 7.1.1 VignetteBuilder knitr NeedsCompilation no Author Edward Visel [aut, cre] (<https://orcid.org/0000-0002-2811-6254>) Maintainer Edward Visel <[email protected]> Repository CRAN Date/Publication 2020-11-07 07:30:03 UTC 1 2 as_country_code R topics documented: as_country_code . .2 as_country_name . .3 codes . .5 country_format . .6 nato .............................................7 order_countries . .8 parse_country . 10 Index 12 as_country_code Convert standardized country names to country codes Description as_country_code converts a vector of standardized country names or codes to country codes Usage as_country_code(x, from, to = "iso2c", factor = is.factor(x)) Arguments x A character, factor, or numeric vector of country names or codes from Format from which to convert. See Details for more options. to Code format to which to convert. Defaults to "iso2c"; see codes for more options. factor If TRUE, returns factor instead of character vector. Details as_country_code takes a character, factor, or numeric vector of country names or codes to translate into the specified code format.
  • What3words Geocoding Extensions and Applications for a University Campus

    What3words Geocoding Extensions and Applications for a University Campus

    WHAT3WORDS GEOCODING EXTENSIONS AND APPLICATIONS FOR A UNIVERSITY CAMPUS WEN JIANG August 2018 TECHNICAL REPORT NO. 315 WHAT3WORDS GEOCODING EXTENSIONS AND APPLICATIONS FOR A UNIVERSITY CAMPUS Wen Jiang Department of Geodesy and Geomatics Engineering University of New Brunswick P.O. Box 4400 Fredericton, N.B. Canada E3B 5A3 August 2018 © Wen Jiang, 2018 PREFACE This technical report is a reproduction of a thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Engineering in the Department of Geodesy and Geomatics Engineering, August 2018. The research was supervised by Dr. Emmanuel Stefanakis, and support was provided by the Natural Sciences and Engineering Research Council of Canada. As with any copyrighted material, permission to reprint or quote extensively from this report must be received from the author. The citation to this work should appear as follows: Jiang, Wen (2018). What3Words Geocoding Extensions and Applications for a University Campus. M.Sc.E. thesis, Department of Geodesy and Geomatics Engineering Technical Report No. 315, University of New Brunswick, Fredericton, New Brunswick, Canada, 116 pp. ABSTRACT Geocoded locations have become necessary in many GIS analysis, cartography and decision-making workflows. A reliable geocoding system that can effectively return any location on earth with sufficient accuracy is desired. This study is motivated by a need for a geocoding system to support university campus applications. To this end, the existing geocoding systems were examined. Address-based geocoding systems use address-matching method to retrieve geographic locations from postal addresses. They present limitations in locality coverage, input address standardization, and address database maintenance.
  • PROBLEMATIC TAXIWAY GEOMETRY STUDY OVERVIEW January 2018 6

    PROBLEMATIC TAXIWAY GEOMETRY STUDY OVERVIEW January 2018 6

    DOT/FAA/TC-18/2 Problematic Taxiway Geometry Federal Aviation Administration William J. Hughes Technical Center Study Overview Aviation Research Division Atlantic City International Airport New Jersey 08405 January 2018 Final Report This document is available to the U.S. public through the National Technical Information Services (NTIS), Springfield, Virginia 22161. U.S. Department of Transportation Federal Aviation Administration NOTICE This document is disseminated under the sponsorship of the U.S. Department of Transportation in the interest of information exchange. The United States Government assumes no liability for the contents or use thereof. The United States Government does not endorse products or manufacturers. Trade or manufacturer's names appear herein solely because they are considered essential to the objective of this report. The findings and conclusions in this report are those of the author(s) and do not necessarily represent the views of the funding agency. This document does not constitute FAA policy. Consult the FAA sponsoring organization listed on the Technical Documentation page as to its use. This report is available at the Federal Aviation Administration William J. Hughes Technical Center’s Full-Text Technical Reports page: actlibrary.act.faa.gov in Adobe Acrobat portable document format (PDF). Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. DOT/FAA/TC-18/2 4. Title and Subtitle 5. Report Date PROBLEMATIC TAXIWAY GEOMETRY STUDY OVERVIEW January 2018 6. Performing Organization Code ANG-E261 7. Author(s) 8. Performing Organization Report No. 1 2 3 Lauren Vitagliano , Garrison Canter , and Rachel Aland 9. Performing Organization Name and Address 10.
  • Geocoding and Buffering Addresses in Arcgis

    Geocoding and Buffering Addresses in Arcgis

    Spatial Structures in the Social Sciences Geocoding Geocoding and Buffering Addresses in ArcGIS INTRODUCTION Geocoding is the process of assigning location coordinates in a continuous, globlal reference system (Latitude and Longitude, for instance) to street addresses. While street addresses are an easy to understand way for us to make sense of locations in a local area there are many problems will using them for distinguishing locations in the world. Street addresses are generally considered location identifiers within a local reference system; furthermore, a street address system is often discrete, meaning it is only effective for positions that fall on the street network. For this reason the US street network has been digitized and coordinates (lat/long for instance) have been determined for the two points that specify individual line segments (smallest line segments possible). In addition to the global coordinates the street address range for each side of the street is also specified for that segment of the street network. Therefore, based on the known range of street addresses and lat/long coordinates a reasonable approximation can be made of the location of an address on a street in global coordinates. DATA and SHAPEFILES Geocodebuffer.zip can be downloaded from the S4 tutorials section of the training page (http://www.s4.brown.edu/S4/about.htm) It contains: 1) NOSchoolsaddrs.xls: Excel file of addresses of currently open schools in New Orleans 2) NOstreets.shp: a street file for all of Louisiana, the state in which you will be geocoding addresses. 3) Katrina_damage_all2.shp: a file displaying damage sustained across New Orleans from Katrina.
  • Resident Hotels Partners with What3words

    Resident Hotels Partners with What3words

    PRESS RELEASE 23rd April 2021 RESIDENT HOTELS PARTNERS WITH WHAT3WORDS ///times.solve.elaborate and ///many.wiser.hired are not lockdown scrabble attempts, they are unique three words guests can use to locate Resident Hotels via app, what3words In anticipation of a summer of city exploration, Resident Hotels has partnered with the global geocode app, what3words, to ensure that all guests can quickly and easily find each of The Resident hotels in London and Liverpool A recent study shows that over half of travellers (52%) spent more than an hour getting lost on their last trip.1 Now, The Resident’s guests will be able to pinpoint the exact location they need faster, more easily and without getting lost – leaving them stress free to enjoy a relaxing and comfortable stay. what3words, which has divided the world into 3mx3m squares, means the addresses are more precise than street addresses and more useful than dropping a pin in the centre of the building. This is a more reliable way of navigating and makes travelling in unfamiliar places easier and safer. 1 what3words Consumer Travel Survey based on 2,000 respondents in the UK and USA, aged 18+ Resident Hotels will be communicating each unique set of three words to guests on its pre- arrival communication, on TripAdvisor as well as being listed on the website pages for the four hotels in London and one in Liverpool. what3words is currently available in 40 languages. The app also works offline, which means that international travellers can use it to find each of The Resident hotels confidently.
  • General Addressing Issues

    General Addressing Issues

    Universal POST*CODE® DataBase page 1/9 Addressing Knowledge Centre General Addressing Issues 1 Which countries in the world have/do not have a postcode system? Nearly every country has a different addressing system. Most countries have a postcode system which indicates the delivery zone or office. When a letter is sent to a given country, it needs to be addressed correctly and with the postcode in the position required by that country. However, some countries do not have a postcode system or have one but do not use it. Here you can find two lists: a list of countries with a postcode system and a list of countries without a postcode system. Universal DataBase (Aug. 2021) List of countries which require postal codes: Country/territory Country/territory Country/territory Country/territory Country/territory name name name name name A-C C-I I-M M-S S-Z Saint Vincent and the Afghanistan Czech Republic Iraq Monaco Grenadines Åland Islands Denmark Isle of Man Mongolia San Marino Albania Djibouti Israel Montserrat Saudi Arabia Algeria Dominican Republic Italy Montenegro (Rep.) Senegal Andorra Ecuador Japan Morocco Serbia Argentina Egypt Jersey Mozambique Singapore Armenia El Salvador Jordan Myanmar Slovakia Australia Estonia Kazakhstan Namibia Slovenia Austria Eswatini Kenya Nauru South Africa Azerbaijan Ethiopia Kiribati Nepal Spain Bahrain Faroe Islands Korea (Rep.) Netherlands Sri Lanka Bangladesh Finland Kosovo (UNMIK) New Caledonia Sudan Barbados France Kuwait New Zealand Sweden Belarus French Guiana Kyrgyzstan Nicaragua Switzerland Lao (People’s Dem. Svalbard and Jan Belgium French Polynesia Niger Rep.) Mayen Island Federated States of Bermuda Latvia Nigeria Tajikistan Micronesia North Macedonia Bhutan Georgia Lebanon Thailand (Rep.) Timor-Leste (Dem.
  • Guide to Sentinel-1 Geocoding

    Guide to Sentinel-1 Geocoding

    Issue: 1.10 Date: 26.03.2019 Guide to S-1 Geocoding Ref: UZH-S1-GC-AD Page 1 / 42 Guide to Sentinel-1 Geocoding Supported by: à Versions up to 1.05: Sentinel-1 Mission Performance Centre (S1MPC) ESRIN Contract No. CLS-DAR-DF-13-041 à Versions 1.06 through 1.10: Subcontract from Telespazio/Vega IDEAS+ Authors: David Small & Adrian Schubert Distribution List Name Affiliation Nuno Miranda ESA-ESRIN David Small UZH-RSL Adrian Schubert UZH-RSL Peter Meadows BAE Guillaume Hajduch CLS Issue: 1.10 Date: 26.03.2019 Guide to S-1 Geocoding Ref: UZH-S1-GC-AD Page 2 / 42 Document Change Record Issue Date Page(s) Description of the Change 0.5 11.07.2017 all Initial Draft Issue 0.7 14.08.2017 Extended discussion of S-1 bistatic residual correction Replaced Figure 5 with S-1 example 0.9 25.08.2017 Corrected some corrupt equation objects; formatting fixes; clari- fied sections on azimuth bistatic corrections. Various minor clar- ifications and corrections spanning the document. 0.91 01.09.2017 Minor edits in response to comments from P. Meadows (BAE) 0.92 01.09.2017 UZH logo added; small correction to Fig. 1 0.95 01.02.2018 New section 4.6.8 added, comparing “out-of-the-box” S-1 prod- uct geolocation accuracy with UZH post-processed accuracy. 1.0 13.02.2018 Edits made to address comments from ESA. 1.01 01.03.2018 Added discussion in section 4.6.8; Final edits made to text flow; added column with ALE requirement to Table 11 and references to S-1 Product Definition and two recent technical notes on pre- cise geocoding.
  • 3Geonames (Slides)

    3Geonames (Slides)

    2/3/2019 Geocode: A Geolocation Code 3geonames dot org An open source Geocoding system for the simple communication of locations with a resolution of 1 m BRUSSELS-VOT-SHOOY 3071531887023 50.812375,4.38073 ERVIN RUCI Fosdem Université libre de Bruxelles Campus du I hit my laptop's keyboard repeatedly for fun and prot Solbosch Avenue Franklin D. Roosevelt 50 1050 Bruxelles Belgium https://3geonames.org/fosdem.html#slide=1 1/32 2/3/2019 Geocode: A Geolocation Code Location Codes From X,Y to Z M L S, Geohash, Mapcodes, Plus codes, O P C, N A C, XADDRESS, What3words, Zippr, MapTags, OkHi, Geokey, FB ... https://3geonames.org/fosdem.html#slide=1 2/32 2/3/2019 Geocode: A Geolocation Code Address Codes Alphanumeric string sets created by humans for communicating locations with other humans. https://3geonames.org/fosdem.html#slide=1 3/32 2/3/2019 Geocode: A Geolocation Code Where were we? | FRANKLIN ROOSEVELT | Brussels | | Franklin Rooseveltlaan | Brussel | | Avenue Franklin Roosevelt | Ville de Bruxelles | Permunations e.g., Avenue Franklin D. Roosevelt 50 1050 Bruxelles Belgium or Avenue Franklin Roosevelt - Franklin Rooseveltlaan 50 1050 Brussel Belgium or Avenue Franklin D. Roosevelt 50 1050 Brussels Belgium https://geocode.xyz/Avenue Franklin D. Roosevelt 50 Brussel Belgium BRUSSELS-AAX-MONTESE / BRUSSELS-NILWK / 50.81136,4.38176 https://3geonames.org/fosdem.html#slide=1 4/32 2/3/2019 Geocode: A Geolocation Code Geocode A hashing function for locations. G{Latitude,Longitude + 3 Geo Names} = Geocode. https://3geonames.org/fosdem.html#slide=1 5/32 2/3/2019 Geocode: A Geolocation Code Some Geocode use cases VOICE GEOCODING SYSTEMS POST CODE SYSTEMS INDOOR NAVIGATION The robots are coming - autonomous vehicle Better Alphanumeric string sets for the Using store names instead of geonames navigation &more unaddressed and/or ambiguously addressed world.
  • Census Bureau Public Geocoder

    Census Bureau Public Geocoder

    1. What is Geocoding? Geocoding is an attempt to provide the geographic location (latitude, longitude) of an address by matching the address to an address range. The address ranges used in the geocoder are the same address ranges that can be found in the TIGER/Line Shapefiles which are derived from the Master Address File (MAF). The address ranges are potential address ranges, not actual address ranges. Potential ranges include the full range of possible structure numbers even though the actual structures might not exist. The majority of the address ranges we have are for residential areas. There are limited address ranges available in commercial areas. Our address ranges are regularly updated with the most current information we have available to us. The hypothetical graphic below may help customers understand the concept of geocoding and Census Geography (addresses displayed in this document are factitious and shown for example only.) If we look at Block 1001 in the example below the address range in red 101-199 is the range of numbers that overlap the actual individual house numbers associated with the blue circles (e.g. 103, 117, 135 and 151 Main St) on that side of the street (i.e. the Left side, note the arrow is pointing to the right on Main Street.) Based on this logic, the from address would be 101 and the to address would be 199 for this address range. Besides providing a user with the geographic location of an address the Census Geocoder can also provide all of the additional Census geographic information associated with a location, for example a Census Block, Tract, County, and State.
  • Geo-Process Lookup Management

    Geo-Process Lookup Management

    Geo-process lookup management Andreas Hägglund Civilingenjör, Datateknik 2017 Luleå tekniska universitet Institutionen för system- och rymdteknik Geo-process Lookup Management Andreas H¨agglund Lule˚aUniversity of Technology Dept. of Computer Science and Electrical Engineering Div. of Information and Communication Technology 14th November 2016 ABSTRACT This thesis presents a method to deploy and lookup applications and devices based on a geographical location. The proposed solution is a combination of two existing technolo- gies, where the first one is a geocode system to encode latitude and longitude coordinates, and the second one is a Distributed Hash Table (DHT) where values are stored and ac- cessed with a <key,value> pair. The purpose of this work is to be able to search a specific location for the closest device that solves the user needs, such as finding an Internet of Things (IoT) device. The thesis covers a method for searching by iterating key-value pairs in the DHT and expanding the area to find the devices further away. The search is performed using two main algorithm implementations LayerExpand and SpiralBox- Expand, to scan the area around where the user started the search. LayerExpand and SpiralBoxExpand are tested and evaluated in comparison to each other. The comparison results are presented in the form of plots where both of the functions are shown together. The function analysis results show how the size of the DHT, the number of users, and size of the search area affects the performance of the searches. iii PREFACE I would like to offer thanks to my supervisors. Johan Kristiansson at Ericsson research in Lule˚afor support in my work with the project at Ericsson, and also with giving great feedback on this thesis paper improving the paper.