DOCSLIB.ORG

Smart Points of Interest (SPOI) Data Model

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Smart Points of Interest (SPOI) Data Model Smart Points of Interest (SPOI) Data Model Otakar Čerba 13. 8. 2018 Namespaces • dc (http://purl.org/dc/elements/1.1/) – Dublin Core • dcterms (http://purl.org/dc/terms/1.1/) – Dublin Core terms • foaf (http://xmlns.com/foaf/0.1/) – Friend of a Friend (FOAF) • geos (http://www.opengis.net/ont/geosparql#) – GeoSPARQL • gn (http://www.geonames.org/ontology#) – GeoNames Ontology • locn (http://www.w3.org/ns/locn) – ISA Programme Location Core Vo- cabulary • poi (http://www.openvoc.eu/poi#) – Specific URI of SPOI data resource1 • rdf (http://www.w3.org/1999/02/22-rdf-syntax-ns#) – Resource Descrip- tion Framework • rdfs (http://www.w3.org/2000/01/rdf-schema#) – Resource Description Framework Schema • skos (http://www.w3.org/2004/02/skos/core#) – Simple Knowledge Or- ganization System • xml (http://www.w3.org/XML/1998/namespace) – Extensible Markup Language Identifier Unique identifier of each POI is adopted from original data source (if it is possible) or generated as the combination of URI (http://www.sdi4apps.eu/poi/), data resource prefix (e.g. OSM) and number. Changes: • 2015-09-02 With respect to need of keeping a persistent URI (which is not kept with xsl:generate-id usage during data updating = new data 1The initial version was http://gis.zcu.cz/poi#. The new was established 2015-06-03. 1 transformation) the new ID is generated as the combination of ISO 3166- 1 alpha-2 country code, acronym of category of POI according Waze navigation data and both coordinates. • 2015-06-18: The original ID (URI+code) was changed to the more under- standable and readable form composed of URI (http://www.sdi4apps.eu/poi), ISO 3166-1 alpha-2 country code, category of POI according Waze naviga- tion data and unique code (generated randomly by the XSLT script). All items were separated by _ (underscore character). Example of generated identifier: <rdf:Description rdf:about="http://www.sdi4apps.eu/poi/#Adv_23"> Core • rdfs:label [1..*] • geos:asWKT [1] • rdf:type [1..*] • geos:sfWithin [1..*] rdfs:label • Description: Name of the POI. One POI can contain more names in different languages (language versions are distinguished by xml:lang attribute and values from ISO 639-1 Language Codes2). • Data type: string (xsd:string) • Multiplicity: 1..* • Comment: In case of more labels in one language there will be necessary to add property skos:prefLabel (or something similar). • Changes: – 2015-09-02 Cardinality was changed from 0..* to 1..* (attribute is mandatory). geos:asWKT • Description: Coordinates according to GeoSPARQL standard (WKT seri- alization) – longitude latitude. • Data type: literal • Multiplicity: 1 • Changes: 2If it is possible, the xml:lang attribute is added to other properties such as rdfs:comment or dc:title. 2 – 2015-09-10 Due to compatibility with Virtuso was the original form (poi:hasExactGeometry linked to sf:Point) changed to the propo- erty geos:asWKT (without any datatypes etc.). rdf:type • Description: Category of POI based on SPOI Ontology. This property replaces all previous classification attributes. It uses ontological hierarchical structures. Particular categories were adopted from Waze and OSM, but any other class can be created. • Data type: URI (xsd:anyURI). The types of POIs are in the SPOI Ontol- ogy described by standardized attributes rdfs:label, rdfs:comment and rdfs:isDefinedBy (the last two attributes are optional). • Multiplicity: 1 geos:sfWithin • Description: Topological relation (Simple Features Topological Relations) to appropriate countries expressed in DBpedia and GeoNames.org. This property is also used to express any topological relation repsenting the one feature is inside other feature (for example “the church is in the village). • Data type: URI (xsd:anyURI) • Multiplicity: 1..* • Changes: – 2015-05-21: The name of property was corrected from sf-within to sfWithin to keep conformity with GeoSPARQL. Also the namespace was changed to GeoSPARQL. Feature Metadata • dc:identifier [1] • dc:publisher [1] • dc:title [1] • dc:rights [1] • dc:source [1..*] • dcterms:created [1] dc:identifier • Description: Copy of the unique identifier of the object. • Data type: URI (xsd:anyURI) 3 • Multiplicity: 1 • Changes: – 2015-11-12: New attribute was added. dc:publisher • Description: Publisher of data. • Data type: value “SPOI (hhtp://sdi4apps.eu/spoi)” • Multiplicity: 1 • Changes: – 2015-11-12: New attribute was added. dc:title • Description: First or the main label of the feature. • Data type: string (xsd:string) • Multiplicity: 1 • Changes: – 2015-11-12: New attribute was added. dc:rights • Description: Link to the original license of point of interest. Processed data resources are open and compliant with ODbL. • Data type: URI (xsd:anyURI) • Multiplicity: 1 • Changes: – 2015-11-12: New attribute was added. dc:source • Description: Link to the original data resource (or text string). • Data type: URI (xsd:anyURI) • Multiplicity: 1..* • Changes: – 2015-11-12: New attribute was added. dcterms:created • Description: Date of adding data to the database. • Data type: date (xsd:date) 4 • Multiplicity: 1 • Changes: – 2015-11-12: New attribute was added. Extended Description • rdfs:comment [0..*] rdfs:comment • Description: Textual description of POI. The property uses xml:lang attribute to distinguish language versions. • Data type: string (xsd:string) • Multiplicity: 0..* Localization • poi:secondaryGeometry [0..*] • locn:fullAddress [0..1] • locn:poBox [0..1] • locn:thoroughfare [0..1] • locn:locatorDesignator [0..*] • locn:locatorName [0..1] • locn:addressArea [0..1] • locn:postName [0..1] • locn:adminUnitL2 [0..1] • locn:adminUnitL1 [0..1] • locn:postCode [0..1] • locn:addressId [0..1] poi:secondaryGeometry • Description: Secondary geometry (including polygons or lines) according to GeoSPARQL standard (WKT serialization). • Data type: literal • Multiplicity: 0..* • Changes: – 2015-11-11: The property was added. 5 locn:fullAddress • Description: The complete address written as a string, with or without formatting. The address contains this property or it composed of following components. Description of full address and address components is adopted from ISA Programme Location Core Vocabulary. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:poBox • Description: The Post Office Box number. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:thoroughfare • Description: An address component that represents the name of a passage or way through from one location to another. A thoroughfare is not necessarily a road, it might be a waterway or some other feature. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:locatorDesignator • Description: A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s). The full identification of the locator could include one or more locator designators. • Data type: literal • Multiplicity: 0..* • Changes: – 2016-03-21 – The property was added. 6 locn:locatorName • Description: Proper noun(s) applied to the real world entity identified by the locator. The locator name could be the name of the property or complex, of the building or part of the building, or it could be the name of a room inside a building. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:addressArea • Description: The name or names of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit. This would typically be part of a city, a neighbourhood or village. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:postName • Description: The key postal division of the address, usually the city. (INSPIRE’s definition is “One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.”). • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:adminUnitL2 • Description: The region of the address, usually a county, state or other such area that typically encompasses several localities. The domain of locn:adminUnitL2 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. 7 locn:adminUnitL1 • Description: The uppermost administrative unit for the address, almost always a country. The domain of locn:adminUnitL1 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type. Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, country names should be provided in a consistent manner to reduce ambiguity. For example, either write ‘United Kingdom’ or ‘UK’ consistently throughout the data set and avoid mixing the two. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:postCode • Description: The post code (a.k.a postal code, zip code etc.). Post codes are common elements in many countries’ postal address systems. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The property was added. locn:addressId • Description: The concept of adding a globally unique identifier for each instance of an address is a crucial part of the INSPIRE data spec. • Data type: literal • Multiplicity: 0..1 • Changes: – 2016-03-21 – The
Load more

Recommended publications
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • Natural Area Coding Based Postcode Scheme
    International Journal of Computer and Communication Engineering Natural Area Coding Based Postcode Scheme Valentin Rwerekane1*, Maurice Ndashimye2 1 Department of Computer Science, University of Rwanda, Huye, Rwanda. 2 iThemba Labs, University of South Africa, Cape Town, South Africa. * Corresponding author. Tel.: +250 788 873 955; email: [email protected] Manuscript submitted March 7th, 2017; accepted June 23, 2017. doi: 10.177606/ijcce.6.3.161-172 Abstract: Traditionally, addresses were used to direct people and helped in social activities; nowadays addresses are used in a wide range of applications, such as automated mail processing, vehicles navigation, urban planning and maintenance, emergency response, statistical analyses, marketing, and others, to ensure necessities induced by new information technologies and facility developments. On top of addresses primary use, postcodes systems were developed to comprehensively provide a variety of public and commercial services. Postcode being an integral part of an addressing system, if well-established, a postcode system brings further social-economic development benefits to a country. This paper aims at designing a postcode based on the Natural Area Coding (NAC). The design focuses on designing a standardized postcode that can fit into any addressing scheme and be used for towns and cities of any shapes from structured cities to slums. Design considerations of a fine-grained postcode (easy for humans, efficient for computerized systems and requiring less or no maintenance over time to improve its efficiency) have proven to be difficult to realize. Therefore, in this paper a new logic is illustrated whereby these considerations are rationally handled while simultaneously allowing the postcode to give a sense of directions and distance.
    [Show full text]
  • 6. Part 6: Reference Standards and Specifications Note: Each Citation Indicates Whether the Cited Work Is Normative Or Informative Within This Standard
    Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard 6. Part 6: Reference Standards and Specifications Note: Each citation indicates whether the cited work is normative or informative within this standard. All references and URLs were current as of September 4, 2010. 6.1 Standards and Specifications Cited 1. EPSG - European Petroleum Survey Group (now defunct; superseded by Geodetic Subcommittee of the International Association of Oil and Gas Producers (OGP)) - see International Association of Oil and Gas Producers (OGP). 2. International Association of Oil and Gas Producers (OGP) Geodetic Subcommittee. "EPSG Geodetic Parameter Dataset." (currently at version 7.5), augmented by accompanying guidance notes, especially EPSG Guidance Note Number 7, part 1, "Using the EPSG Geodetic Parameter Dataset." Version 5.0, November 2009. Posted at: http://www.epsg.org and at: http://info.ogp.org.uk/geodesy/ (Informative) Cited in: Content (Address Coordinate Reference System ID and Address Coordinate Reference System Authority). 3. International Standards Organization. "ISO 3166-1: Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes.” As posted on the ISO webpage captioned "ISO 3166-1: English country names and code elements." ISO Note: "This list states the country names (official short names in English) in alphabetical order as given in ISO 3166-1 and the corresponding ISO 3166- 1-alpha-2 code elements. This list is updated whenever a change to the official code list in ISO 3166-1 is effected by the ISO 3166/MA. It lists 248 official short names and code elements." Note: ISO 3166-1 is protected by ISO copyright.
    [Show full text]
  • ISO 3166-1 NEWSLETTER VI-2 Date: 2008-03-31
    ,621HZVOHWWHU9, ISO 3166-1 NEWSLETTER VI-2 Date: 2008-03-31 Name changes for Moldova, Montenegro and other minor corrections ISO 3166-1 Newsletters are issued by the secretariat of the ISO 3166/MA when changes in the code lists of ISO 3166-1 have been decided upon by the ISO 3166/MA. ISO 3166-1 Newsletters are identified by a two-component number, stating the currently valid edition of ISO 3166-1 in Roman numerals (e.g. "V") and a consecutive order number (in Latin numerals) starting with "1" for each new edition of ISO 3166-1. All the changes indicated in this Newsletter refer to changes to be made to ISO 3166-1:2006 as corrected by its Technical Corrigendum 1, ISO 3166-1:2006/Cor 1:2007 (published 2007-07-15). The ISO 3166 Maintenance Agency has agreed to the following change(s) to ISO 3166-1:2006, Codes for the representation of names of countries and their subdivisions — Part 1: Country codes. For all countries affected, a complete new entry is given in this Newsletter. A new entry replaces an old one in its entirety. The changes take effect on the date of publication of this Newsletter. The modified entries are listed from page 2 onwards. For reasons of user-friendliness, changes to be added are presented in red colour and those deleted in blue colour. The table below gives a short overview of the changes made. Changes to Alpha Country name/ Short description of change ISO 3166-1:2006 2-code/ Nom de pays Code alpha 2 Clause 9, p.
    [Show full text]
  • ISO 3166-2 NEWSLETTER Changes in the List of Subdivision Names And
    ISO 3166-2 NEWSLETTER Date: 2010-06-30 No II-2 Changes in the list of subdivision names and code elements The ISO 3166 Maintenance Agency1) has agreed to effect changes to the header information, the list of subdivision names or the code elements of various countries listed in ISO 3166-2:2007 Codes for the representation of names of countries and their subdivisions — Part 2: Country subdivision code. The changes are based on information obtained from either national sources of the countries concerned or on information gathered by the Panel of Experts for the Maintenance of ISO 3166-2. ISO 3166-2 Newsletters are issued by the secretariat of the ISO 3166/MA when changes in the code lists of ISO 3166-2 have been decided upon by the ISO 3166/MA. ISO 3166-2 Newsletters are identified by a two-component number, stating the currently valid edition of ISO 3166-2 in Roman numerals (starting with "I" for the first edition) followed by an Arabic numeral in consecutive order starting with "1" for each new newsletter of the current edition (e.g. "Newsletter II-1" for the first newsletter of the second edition, ISO 3166-2:2007). All the changes indicated in this Newsletter refer to changes to be made to ISO 3166-2:2007 as corrected by Newsletter II-1. For all countries affected a complete new entry is given in this Newsletter. A new entry replaces an old one in its entirety. The changes take effect on the date of publication of this Newsletter. The modified entries are listed from page 4 onwards.
    [Show full text]
  • Country Codes in ISO 3166 Page 1 of 10 Country Codes in ISO 3166
    Country codes in ISO 3166 Page 1 of 10 Country codes in ISO 3166 Page last modified: 2003-07-25 Data last modified: 2003-07-25 This file lists the codes for each country provided in ISO 3166. There are two tables: existing codes and withdrawn codes (codes can be withdrawn because the country no longer exists, the name has significantly changed, or one or more codes has altered). Each country or territory has three codes: l a two letter code l a three letter code l a three digit code The numeric code identifies a physical territory, and the letters a country name. Thus when Germany reunified, it kept DE/DEU but changed from 280 to 276, while when Southern Rhodesia was renamed Zimbabwe it stayed 716 but changed from RH/RHO to ZW/ZWE. There is also a numeric version of the two letter code not given here, calculated as 1070+30a+b, where a and b are the two letters of the code converted by A=1, B=2, etc. So AA=1101, AB=1102, BA=1131, and ZZ=1876. Changes to ISO 3166 are managed by the ISO 3166 Maintenance Agency (ISO3166/MA). Codes withdrawn from use may not be reused for five years. The two letter codes AA, QM to QZ, XA to XZ, and ZZ, all three letter codes beginning with those pairs, and numeric codes beginning 9, are available for individual use and will not be allocated to countries. The codes OO, OOO, and 000 are designated for use as "escape codes" to indicate that additional codes are being used.
    [Show full text]
  • Global Geocoding SDK V2.1.0 Developer Guide
    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.
    [Show full text]
  • The UN/EDIFACT PAXLST Implementation Guide
    ANNEX III to ADVANCED PASSENGER INFORMATION GUIDELINES WCO/IATA PASSENGER LIST MESSAGE (PAXLST) IMPLEMENTATION GUIDE 28 June 2010 Version 3.0 As this Guide is considered to be a living document, potential developers and users of the PAXLST message are recommended to confirm with the WCO or IATA that they are in possession of the latest version. WCO/IATA PAXLST IMPLEMENTATION GUIDE PASSENGER LIST MESSAGE (PAXLST) IMPLEMENTATION GUIDE TABLE OF CONTENTS 1.0 INTRODUCTION ........................................................................................................... 1 2.0 MESSAGE RELATIONSHIPS...................................................................................... 2 3.0 MESSAGE STRUCTURE FOR THE PAXLST MESSAGE ...................................... 4 3.1 APPLICATION SEGMENTS USED IN THE WCO/IATA PAXLST MESSAGE ..........5 3.2 UNITED NATIONS SERVICE SEGMENTS ...................................................................5 4.0 SEGMENT DETAILS FOR USE IN THE PAXLST MESSAGE .............................. 6 4.1 UNA: SERVICE STRING ADVICE .................................................................................7 4.2 UNB: INTERCHANGE HEADER ....................................................................................8 4.3 UNG: FUNCTIONAL GROUP HEADER .....................................................................10 4.4 UNH: MESSAGE HEADER ...........................................................................................12 4.5 BGM: BEGINNING OF MESSAGE ...............................................................................14
    [Show full text]
  • Note on Definition of Regions for Statistical Analysis
    Committee for the Coordination of Statistical Activities SA/2006/15 Eighth Session Montreal, 4-5 September 2006 30 August 2006 Item 6 of the provisional agenda ================================================================== Note on definition of regions for statistical analysis Prepared by UNSD 1. Background The need to define regional aggregations that would allow a meaningful statistical analysis has long been a concern of the international statistical community. This has become more evident with the new monitoring requirements and with the increasing demand for consistency in the analysis, presentation and reporting across the UN-system and other international agencies, on development issues. A large number of official reports are produced every year by specialized agencies and other UN entities, which present country data according to a regional/geographical classification and often regional and sub-regional aggregates (based on average or other aggregation methods). Regional aggregates are a convenient way to show trends and assess progress over time and differences across the various areas of the world. However, practices vary among the various international agencies and regional groupings and classification of countries are based on different criteria. With the increasing use of statistics and statistical analysis by a large audience, including country delegations, policy makers, the media and the general public, a consistent use of nomenclature for geographical and other country groupings has become a real necessity. This brief
    [Show full text]