Post on 23-Jan-2020
Enterprise Geocoding Module Data Version Q3 2018
Dataset Release Notes This document contains information about the Spectrum™ Technology Platform Enterprise Geocoding Module data. You have access only to the modules you have licensed. To evaluate any other modules, contact your Pitney Bowes account executive for a trial license key.
Contents:
What's New 2 Q3 Datasets By Country 4 Enterprise Geocoding Fixes 17 Data Setup Procedures 19
Enterprise Geocoding Module Q3 2018 Data Release Notes
What's New
This release contains new and updated features.
Urgent License Code Changes for Japan and Australia Datasets
Japan: Previous JP1 has been updated in Q3 to product code JP7.
Australia: Previous AU1 Street data has been updated in Q3 to product code AU5. Previous AU2 Points (AUS GNAF) has been updated to product code AU7.
Canada: Previous CA2 has been updated in Q3 to product code CN4.
The new product codes require a new license key in order to use these datasets. Contact Technical Support for more information.
New Support Site Location for Geocoding Product Documentation
We now have a permanent location for geocoding product documentation on the PB Support site at Geocoding Support. Go here first to find user guides, developer guides, and database and software release notes for our geocoding products.
Interactive Geocoding for World Places
Now available for the Global Geocoding Module is a World Places Interactive dataset that allows you to locate world cities and postcodes with minimal typing. Called interactive geocoding or type-ahead, the World Places dataset is optimized to return potential match candidates when only a few characters are typed in. This makes this dataset ideal for use in mobile applications that need to find places easily.
This dataset bridges the gap where there is no country-level interactive dataset available. It contains world cities, administrative areas above the city level and postcodes. There is no street data. It supports names in multiple languages if they exist. Input is a string containing city name or postcode, and optional latitude/longitude coordinates and country.
Use World Places with the GGM Interactive stage to search for city names or post codes. A new search type called World Places is available for this purpose. If you want addresses and points of interest returned in addition to World Places, choose search type Address or All. The REST API parameter name is SEARCH_WORLD_PLACES under the SEARCH_TYPE. The Match Mode is Standard. The match modes Close and Relaxed will return the identical information.
To update your installation to use World Places Interactive, apply the Spectrum patch 12.2 S08. This will add a new search type to Management Console called World Places. Patches are located on the Spectrum Documentation page following installation. Choose the link that matches your version of Spectrum.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 2
https://www.pitneybowes.com/us/contact-dcs.htmlhttps://www.pitneybowes.com/us/contact-dcs.htmlhttps://www.pitneybowes.com/us/support/products/software/geocoding-support.html
Enterprise Geocoding Module Q3 2018 Data Release Notes
New Geocoder for Israel
This release includes a new geocoder for Israel (ISR). Datasets include a street dataset and equivalent interactive dataset (product code IL2), and an address point dataset (product code IL4).
The datasets contain 5-digit postcodes. In 2013 postcodes in Israel were extended to 7 digits. Input addresses with 7 digit postcodes match to records with 5 digit postcodes by default. If the Must Match to Postal Code is true, no candidates will be returned for 7-digit input addresses.
The most granular geographic information provided in the street datasets is to the city or town level (AreaName3).
Geocoding candidates in the street dataset can match to interpolated street locations (S5) and city or town centroids (G3). Address point matches return an S8 result code. Postal code matches return a postcode centroid match (Z1).
24241 is DEREKH HA'ARBA'A דארך עכו The data is provided in latinized Hebrew. For example, ACRE 24261, representing the street, city and postcode in Latin characters.
Support for Thai Script Language
The Thailand geocoder now supports data written in Thai script. This is in addition to the already supported latinized version of Thai. This street-level dataset has about 1 million records. Matching to house number is not supported due to the lack of house numbers in the datasets.
Both the Thai script and latinized datasets return the following new fields: ALT_LANG_STREET_NAME, ALT_LANG_AREA_NAME1, ALT_LANG_AREA_NAME2, ALT_LANG_AREA_NAME3, ALT_LANG_AREA_NAME4. These fields represent the other language version of the indicated field. For example if the geocoding input is in Thai script, the additional fields will contain the latinized version.
Note: In Enterprise Geocoding Module these fields contain a 3-letter country code prefix. For example, THA.ALT_LANG_STREET_NAME. When using the data in Global Geocoding Module, there is no country code prefix.
Data Updates
• New Interactive datasets: The following countries are now available as Interactive datasets for use in the Global Geocoding Module: World Places, Israel, Thailand, Montenegro and Trinidad and Tobago. The complete list of Interactive datasets is published in the table entitled Q3 Datasets By Country on page 4.
• Address Point Coverage: The number of address points for these countries in this Q3 release (October 15) has increased by the following percentages over the previous refresh of Q2 (July 15): Portugal - 113%, Italy - 47%, Spain - 28%, Malaysia - 12%, Poland - 10%.
• Turkey: New address points are available and are located in the TR7 .
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 3
Enterprise Geocoding Module Q3 2018 Data Release Notes
Q3 Datasets By Country
This table lists a number of characteristics about the country datasets provided in the Q3 2018 data refresh, including maximum precision, availability of postal data, and supported language. The refresh vintage is 201809.
Use these datasets for geocoding with Enterprise Geocoding Module. Interactive datasets are identified by a ✓ in the Interactive column. These are companion datasets for performing type ahead interactive geocoding with the Global Interactive Geocoding stage (available in the Global Geocoding Module beginning with version 12.0 SP2 of the Spectrum™ Technology Platform) and from the Global Geocoding API v2.0.
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
NoALB Albania AL1 ✓ Street Centroid Albanian
DZA Algeria DZ1 ✓ Street Centroid No French
AND Andorra ES1 ✓ Street Interpolated Yes Spanish
AGO Angola AO1 ✓ Street Centroid No Portuguese
ARG Argentina AR2 Street Interpolated Yes Spanish
ARG Argentina AR1 ✓ Street Interpolated Yes Spanish
ABW Aruba AW2 ✓ Street Centroid No Dutch
AUS Australia AU52 ✓ Street Interpolated Yes English
AUS Australia AU73 ✓ Address Points Yes English
1 No = not available in the dataset, N/A = not available for the country 2 previously AU1. Requires a new license. 3 previously AU2. Requires a new license.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 4
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
AUT Austria AT1 ✓ Street Interpolated Yes German
AUT Austria AT3 Address Points Yes German
AUT Austria AT7 Address Points Yes German
BHS Bahamas BS2 ✓ Street Centroid No English
BHR Bahrain BH1 ✓ Street Centroid No Arabic, latinized Arabic
BRB Barbados BB2 ✓ Street Centroid No English
BLR Belarus BY1 ✓ Street Centroid No Cyrillic, latinized Cyrillic
BEL Belgium BE3 ✓ Address Points Yes Dutch, French, German
BEL Belgium BE7 Address Points Yes Dutch, French, German
BEL Belgium, BE1 ✓ Street Interpolated Yes Dutch, Luxembourg French,
German
BLZ Belize BZ2 ✓ Street Centroid No English
BEN Benin BJ1 ✓ Street Centroid No French
BMU Bermuda BM2 ✓ Street Centroid No English
BOL Bolivia BO2 ✓ Street Centroid No Spanish
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 5
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
BIH Bosnia and BA1 ✓ Street Centroid No Bosnian Herzegovina
BWA Botswana BW1 ✓ Street Centroid No English
BRA Brazil BR1 ✓ Street Interpolated Yes Portuguese
BRA Brazil BR4 Address Points Yes Portuguese
BRN Brunei Darussalam BN1 ✓ Street Centroid Yes Malay
BGR Bulgaria BG1 ✓ Street Interpolated No Bulgarian latinized Bulgarian
BFA Burkina Faso BF1 ✓ Street Centroid No French
BDI Burundi BI1 ✓ Street Centroid No French
CMR Cameroon CM1 ✓ Street Centroid No French
CAN Canada CA1 ✓ Street Interpolated Yes English, French
CAN Canada CA3 Address Points Yes English, French
CAN Canada CA44 Address Points Yes English, French
CAN Canada CA8 ✓ MLD Yes English, French
CHL Chile CL1 ✓ Street Interpolated Yes Spanish
1 No = not available in the dataset, N/A = not available for the country 4 previously CA2. Requires a new license.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 6
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
CHN China CN1 Street Centroid Yes latinized Chinese
CHN China CN6 ✓ Street Centroid Yes Simplified Chinese, latinized Chinese
COL Colombia CO1 ✓ Street Interpolated No Spanish
COL Colombia CO4 Address Points No Spanish
COG Congo-Brazzaville CG1 ✓ Street Centroid No French
COD Congo-Kinshasa CD1 ✓ Street Centroid No French
CRI Costa-Rica CR2 ✓ Street Interpolated No Spanish
HRV Croatia HR1 ✓ Street Interpolated Yes Croatian
CUB Cuba CU2 ✓ Street Centroid No Spanish
CYP Cyprus CY1 ✓ Street Interpolated No Greek, latinized Greek
CZE Czech Republic CZ1 ✓ Street Interpolated Yes Czech
CZE Czech Republic CZ3 Address Points Yes Czech
DNK Denmark DK3 Address Points Yes Danish
DNK Denmark DK1 ✓ Street Interpolated Yes Danish
DOM Dominican Republic DO2 ✓ Street Centroid Yes Spanish
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 7
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
ECU Ecuador EC2 ✓ Street Interpolated No Spanish
EGY Egypt EG1 ✓ Street Interpolated No Arabic, latinized Arabic
SLV El Salvador SV2 ✓ Street Centroid No Spanish
EST Estonia EE1 ✓ Street Interpolated Yes Estonian
FIN Finland FI1 ✓ Street Interpolated Yes Finnish
FRA France FR1 ✓ Street Interpolated Yes French
FRA France FR2 Street Interpolated Yes French
FRA France FR3 Address Points Yes French
GAB Gabon GA1 ✓ Street Centroid No French
DEU Germany DE1 ✓ Street Interpolated Yes German
DEU Germany DE3 Address Points Yes German
GHA Ghana GH1 ✓ Street Centroid No English
GRC Greece GR1 ✓ Street Interpolated Yes Greek, latinized Greek
GTM Guatemala GT2 ✓ Street Centroid No Spanish
GUY Guyana GY2 ✓ Street Centroid Yes English
HND Honduras HN2 ✓ Street Centroid No Spanish
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 8
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
HKG Hong Kong HK1 ✓ Street Interpolated N/A latinized Chinese
HKG Hong Kong HK3 Address Points N/A latinized Chinese
HKG Hong Kong HK7 Address Points N/A Traditional Chinese, latinized Chinese
HUN Hungary HU1 ✓ Street Interpolated No Hungarian
ISL Iceland IS1 ✓ Street Interpolated No Icelandic
IND India IN5 Street Interpolated Yes English
IND India IN1 ✓ Street Interpolated Yes English
IND India IN3 Address Points Yes English
IDN Indonesia ID1 Street Centroid Yes Indonesian
IRQ Iraq IQ1 ✓ Street Centroid No Arabic, latinized Arabic
IRL Ireland IE1 ✓ Street Interpolated Yes English
IRL Ireland IE3 Address Points Yes English
ISR Israel IL2 ✓ Street Interpolated Yes latinized Hebrew
ISR Israel IL4 Address Points Yes latinized Hebrew
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 9
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
ITA Italy IT4 Address Points Yes Italian
ITA Italy IT1 ✓ Street Interpolated Yes Italian
ITA Italy IT3 Address Points Yes Italian
JAM Jamaica JM2 ✓ Street Centroid Yes English
JPN Japan JP75 ✓ Address Points Yes Japanese, latinized
JOR Jordan JO1 ✓ Street Centroid No Arabic, latinized Arabic
KEN Kenya KE1 ✓ Street Centroid No English
KOR Korea KR7 ✓ Address Points Yes latinized Korean
XKX Kosovo XK1 ✓ Street Centroid Yes English
KWT Kuwait KW1 ✓ Street Interpolated No Arabic, latinized Arabic
LVA Latvia LV1 ✓ Street Interpolated Yes Latvian
LBN Lebanon LB1 ✓ Street Centroid No Arabic, latinized Arabic
LSO Lesotho LS1 ✓ Street Centroid No English
1 No = not available in the dataset, N/A = not available for the country 5 previously JP1. Requires a new license.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 10
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
LIE Liechtenstein CH1 ✓ Street Interpolated Yes Dutch, French, German
LTU Lithuania LT1 ✓ Street Interpolated Yes Lithuanian
MAC Macau MO1 ✓ Street Interpolated No Portuguese
MKD Macedonia MK1 ✓ Street Centroid Yes English
MWI Malawi MW1 ✓ Street Centroid No Malay
MYS Malaysia MY1 ✓ Street Interpolated Yes Malay
MYS Malaysia MY3 ✓ Points, POI Yes Malay
MYS Malaysia MY5 ✓ Address Points Yes Malay
MYS Malaysia MY5 ✓ Street Interpolated Yes Malay
MLI Mali ML1 ✓ Street Centroid No French
MLT Malta MT1 ✓ Street Centroid No Maltese
MTQ Martinique FR2 Street Interpolated Yes French
MRT Mauritania MR1 ✓ Street Centroid No French
MUS Mauritius MU1 ✓ Street Centroid No English
MEX Mexico MX2 Street Interpolated Yes Spanish
MEX Mexico MX4 Address Points Yes Spanish
MEX Mexico MX1 ✓ Street Interpolated Yes Spanish
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 11
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
MNE Montenegro ME1 ✓ Street Interpolated No Montenegrin
MAR Morocco MA1 ✓ Street Interpolated Yes French
MAR Morocco MA2 Street Interpolated Yes French
MOZ Mozambique MZ1 ✓ Street Centroid No English
NAM Namibia NA1 ✓ Street Interpolated No English
NLD Netherlands NL1 ✓ Street Interpolated Yes Dutch
NLD Netherlands NL3 Address Points Yes Dutch
NZL New Zealand NZ1 ✓ Street Interpolated Yes English
NZL New Zealand NZ5 Street Interpolated Yes English
NZL New Zealand NZ7 Address Points Yes English
NIC Nicaragua NI2 ✓ Street Centroid No Spanish
NER Niger NE1 ✓ Street Centroid No French
NGA Nigeria NG1 ✓ Street Centroid No English
NOR Norway NO1 ✓ Street Interpolated Yes Norwegian
OMN Oman OM1 ✓ Street Centroid No Arabic, latinized Arabic
PAN Panama PA2 ✓ Street Centroid No Spanish
PRY Paraguay PY2 ✓ Street Centroid No Spanish
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 12
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
PER Peru PE2 ✓ Street Centroid Yes Spanish
PHL Philippines PH1 ✓ Street Centroid No English
POL Poland PL1 ✓ Street Interpolated Yes Polish
POL Poland PL3 Address Points Yes Polish
PRT Portugal PT1 Street Interpolated Yes Portuguese
PRT Portugal PT2 ✓ Street Interpolated Yes Portuguese
PRT Portugal PT4 Address Points Yes Portuguese
PRT Portugal PT3 Address Points Yes Portuguese
QAT Qatar QA1 ✓ Street Centroid No Arabic, latinized Arabic
ROU Romania RO1 ✓ Street Interpolated Yes Romanian
RUS Russia RU1 ✓ Street Interpolated Yes Russian, English
RWA Rwanda RW1 ✓ Street Centroid Yes French
KNA Saint Kitts and KN2 ✓ Street Centroid No English Nevis
SAU Saudi Arabia SA1 ✓ Street Centroid No Arabic, latinized Arabic
SEN Senegal SN1 ✓ Street Centroid No French
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 13
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
SRB Serbia RS1 ✓ Street Interpolated No Serbian, English
SGP Singapore SG1 ✓ Street Interpolated Yes English
SGP Singapore SG3 Address Points Yes English
SVK Slovakia SK1 ✓ Street Interpolated Yes Slovakian
SVK Slovakia SK3 Address Points Yes Slovakian
SVN Slovenia SI1 ✓ Street Centroid Yes Slovenian
ZAF South Africa ZA1 ✓ Street Interpolated Yes English
ESP Spain ES1 ✓ Street Interpolated Yes Spanish
ESP Spain ES4 Address Points Yes Spanish
SUR Suriname SR2 ✓ Street Centroid No Dutch
SWZ Swaziland SZ1 ✓ Street Centroid No English
SWE Sweden SE2 Street Interpolated Yes Swedish
SWE Sweden SE1 ✓ Street Interpolated Yes Swedish
SWE Sweden SE4 Address Points Yes Swedish
CHE Switzerland CH3 Address Points Yes French, Italian, German
CHE Switzerland, CH1 ✓ Street Interpolated Yes French, Liechtenstein Italian,
German
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 14
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
TWN Taiwan TW1 ✓ Street Interpolated Yes English
TZA Tanzania TZ1 ✓ Street Centroid No English
THA Thailand TH1 ✓ Street Centroid No Thai script, latinized Thai
TGO Togo TG1 ✓ Street Centroid No English
TTO Trinidad and TT2 ✓ Street Centroid No English Tobago
TUN Tunisia TN1 ✓ Street Centroid No French
TUR Turkey TR1 ✓ Street Interpolated Yes Turkish
TUR Turkey TR7 Address Points Yes Turkish
UGA Uganda UG1 ✓ Street Centroid No English
UKR Ukraine UA1 ✓ Street Centroid No English, Ukrainian
ARE United Arab AE1 ✓ Street Interpolated No Arabic, Emirates latinized
Arabic
GBR United Kingdom GB1 ✓ Street Interpolated Yes English
GBR United Kingdom GB7 Address Points Yes English
GBR United Kingdom GB8 ✓ Address Points Yes English
URY Uruguay UY1 Street Interpolated No Spanish
VEN Venezuela VE2 ✓ Street Centroid No Spanish
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 15
Enterprise Geocoding Module Q3 2018 Data Release Notes
Country Country Name Product Interactive Maximum Postcodes1 Language ISO3 Code Precision
VNM Viet Nam NG1 ✓ Street Centroid No English
WORLD World 8XW ✓ Boundary Centroid Yes English
XWG World XW1 Boundary Centroid Yes English
YEM Yemen YE1 ✓ Street Centroid No Arabic, latinized Arabic
ZMB Zambia ZM1 ✓ Street Centroid No English
ZWE Zimbabwe ZW1 ✓ Street Centroid No English
1 No = not available in the dataset, N/A = not available for the country
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 16
Enterprise Geocoding Module Q3 2018 Data Release Notes
Enterprise Geocoding Fixes
This release includes these fixes for Spectrum™ Technology Platform.
• (GN-27384) Argentina: The city Don Torcuato has been added to the dataset as an alias for Don Torcuato Este and Don Torcuato Oeste so that records can be geocoded by the alias.
• (GN-27532) Austria: Salzburg now returns the correct coordinates. • (GN-24447) Australia: Input address SHOP 54 1 ARBOUR AVE, ROBINA, 4226, now geocodes
correctly after a data update. • (GN-27838) Belgium: Coordinates for city centre of Brussels have been corrected. • (GN-27705) Canada: An exception is no longer thrown when matching to PO BOX 2 VAUGHAN
ON L4L 1A6 using the Relaxed match mode. • (GN-27493) Canada: An issue with single line geocoding to addresses with diacritic characters
has been resolved. • (GN-23395) Canada: Addresses along Boul De La Rive-Sud, Lévis, QC, are now matching on
house number. The street name is an alternate name to Boul Guillaume-Couture that was not provided in the MLD data. Both names have been included in the MLD for Q3.
• (GN-26748) China: An address that had returned the street candidate in Chinese (大什字街89,沈阳市, 辽宁省, 110042, CHINA) and the fallback to postcode candidate in latinized Chinese (89DÀ SHÍZÌ STREET, SHENYANG, LIAONING, 110042, CHINA) has been resolved by adding thestreet name DÀ SHÍZÌ STREET" as an alias.
• (GN-27870) Colombia: The geocoder was unable to process a specific poorly formed input address "13 N 13-0311001". This issue was resolved with performance improvements.
• (GN-24840) Finland: The street dataset has been updated with an added street block to resolve an issue with a missing street Lordin Aukio, which had been in the previous quarter's release.
• (GN-27952) Germany: Input street addresses missing ß in straße now return S8 candidates, as expected. Strae was added to the dataset as an alias.
• (GN-27521) Great Britain: NullPointerException no longer thrown when geocoding PO BOX addresses.
• (GN-27949) Great Britain: The StateProvince field in GB1 has been returning GB country names such as England, Wales, and Scotland while other GB datasets returned blank fields. To be consistent across GBR datasets, the StateProvince field has been removed from GB1.
• (GN-27904) India: The India geocoder now returns candidates with state as WEST BENGAL when the input state is WB, WESTBENGAL or WEST BENGAL.
• (GN-10763) Ireland: Beech Avenue, Naas, is now available after a dataset update. • (GN-24658) Japan: Towns that were missing from the dataset have been added back in. • (GN-26740) Japan: The issue of not returning Kanji candidate was closed due to an invalid input
address. • (GN-28206) Korea: Out of bounds exception is no longer thrown when geocoding addresses. • (GN-27703) Mexico: The geocoder has been updated to ignore NULL input fields.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 17
Enterprise Geocoding Module Q3 2018 Data Release Notes
• (GN-23456) New Zealand: An asterisk '*' in front of a street address no longer prevents a match to the house number.
• (GN-27165) Romania: County-level data is now being returned in the County field (AreaName2), as expected. Previously it was returned in the StateProvince field. County, also known as District, is the highest level administrative boundary for Romania. In addition the documentation was corrected to say that the County field is used.
• (GN-7694) Russia: Street data for the Russian state Bashkortostan is now available in the Q3 data refresh.
• (GN-26607) Russia: Added the pre-thoroughfare type 'ULITSA' in Cyrillic and latinized Cyrillic.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 18
Enterprise Geocoding Module Q3 2018 Data Release Notes
Data Setup Procedures
SPD data for EGM and Interactive is extracted to a location on your system and configured for use. There is no installation in the traditional sense. The procedure differs depending on your version of the Spectrum™ Technology Platform.
Spectrum version 12.2 and 12.1 provide an extraction and configuration using Management Console. See Setting up SPD databases for Spectrum 12.2 and 12.1 on page 20.
Versions older than v12.1 require a product update to the software to support the SPD data format. See Setting up SPD databases for Spectrum 12.0 and 11.1 on page 22.
Saving Databases
Be aware that any data folders under a Spectrum installation will be removed when Spectrum is uninstalled. To retain the data for future use, consider archiving the SPD in a location outside of the Spectrum installation. To do this, set the spectrum.data.manager.archive.data property to true located in the \server\app\conf\spectrum-container.properties.
You can also change the data repository location by providing a path in spectrum.data.manager.storage.directory.
Using Older Datasets From 12.0 and Earlier
If you upgrade to 12.1 or 12.2, you can use database resources from earlier versions of Spectrum. The legacy database resources will be visible in Management Console and available for use alongside any new data you installed. If you decide you don't want the legacy datasets associated with the database resource, in Management Console's Spectrum Database page, check the box next to the database resource and click the Modify button. From the Edit Database page, clear the checkbox next to the dataset(s) you no longer want in the database. The legacy datasets will no longer be available.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 19
Enterprise Geocoding Module Q3 2018 Data Release Notes
Setting up SPD databases for Spectrum 12.2 and 12.1
Follow this procedure to extract and configure SPD datasets that have not been set up previously.This is done using Management Console.
To set up and configure an SPD database:
1. Update your Spectrum installation with all product updates (patches) available for your release. 2. Download the database .spd to a location of your choice. The database will be
downloaded as an SPD file, which is essentially a zip file with an .spd extension. If you downloaded from g1.com/support, the .spd will be inside a .zip file. Extract it to a temporary location.
3. Copy the .spd into the Spectrum server's dataimport folder or a location of your choice. The dataimport folder for a default installation is located in C:\Program Files\Pitney Bowes\Spectrum\server\app\dataimport.. Once the .spd is in the folder, it will automatically be extracted to Spectrum's data repository at C:\Program Files\PitneyBowes\Spectrum\server\app\repository\datastorage\geocoding-all\geocoding-all.
Note: The entire contents of the SPD will be extracted to the dataimport folder or your custom location. You cannot pick which datasets are extracted. This is a change from the past when dbloader allowed you to choose.
Note: The SPD will be uninstalled from the default Spectrum location during an uninstallation of Spectrum. If you want to change the default data repository or to archive the .spd, Spectrum provides the spectrum-container.properties file under \server\app\conf that you can edit. See the properties spectrum.data.manager.storage.directory and spectrum.data.manager.archive.data. Restart the server when done.
4. To configure a new database in Management Console, choose Resources > Spectrum Databases.
5. Click the Add button and provide a name for the database and choose the appropriate module from the list.
6. Select the dataset(s) that you would like to add to the database by checking the box next to the name. Save the database when finished.
7. To reconfigure a database resource in Management Console, select the database from the list.
Click the Modify button . Change the name and select and/or unselect the datasets you want. Save the database resource when finished. You cannot rename an existing database and modify it.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 20
http://support.pb.com/help/spectrum/ProductUpdateSummary/index.html#ProductUpdateSummary/source/Introduction.html
Enterprise Geocoding Module Q3 2018 Data Release Notes
To reconfigure the database from the command line, see Reconfiguring a Database with the Administration Utility on page 24.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 21
Enterprise Geocoding Module Q3 2018 Data Release Notes
Setting up SPD databases for Spectrum 12.0 and 11.1
1. Update your Spectrum installation with all product updates (patches) available for your release version. In particular is 12.0 S12 and 11.1 S40 that contains software changes to support SPD datasets.
2. Download the database .spd from g1.com/support or the estore. Links are provided in the release announcement. The database will be downloaded as an SPD file, essentially a zip file with an .spd extension. If you downloaded from g1.com/support, the .spd will be inside a.zip file. Extract it to a temporary location.
3. Copy the .spd into the Spectrum server's dataimport folder or to the location of your choice.
The dataimport folder for a default installation is located in C:\Program Files\Pitney Bowes\Spectrum\server\app\dataimport.. Once the .spd is in the folder, it will automatically be extracted to Spectrum's data repository at C:\Program Files\PitneyBowes\Spectrum\server\app\repository\datastorage\geocoding-all\geocoding-all.
Note: The entire contents of the SPD will be extracted to the dataimport folder or your custom location. You cannot pick which datasets are extracted. This is a change from the past when dbloader allowed you to choose.
Note: The SPD will be uninstalled from the default Spectrum location during an uninstallation of Spectrum. If you want to change the default data repository or to archive the .spd, Spectrum provides the spectrum-container.properties file under \server\app\conf that you can edit. See the properties spectrum.data.manager.storage.directory and spectrum.data.manager.archive.data. Restart the server when done.
4. Navigate to the data repository or your custom location where the .spd file was extracted. Copy the filepath to the data you want to configure in Management Console.
5. In Management Console, under Resources, choose Spectrum Databases.
6. Click the Add button and provide a name for the database and choose the appropriate module from the list.
7. In the Add Dataset screen, provide a name and paste the path you copied in step 5 or navigate to the location in the data repository. Click OK to leave the screen.
8. Continue to add datasets, if appropriate, and save the database when you are done. 9. To reconfigure a database resource in Management Console, select the database from the list.
Click the Modify button . Change the name and select and/or unselect the datasets you want. Save the database resource when finished.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 22
http://support.pb.com/help/spectrum/ProductUpdateSummary/index.html#ProductUpdateSummary/source/Introduction.html
Enterprise Geocoding Module Q3 2018 Data Release Notes
You cannot rename an existing database and modify it. To reconfigure the database from the command line, see Reconfiguring a Database with the Administration Utility on page 24.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 23
Enterprise Geocoding Module Q3 2018 Data Release Notes
Reconfiguring a Database with the Administration Utility
Spectrum's Administration Utility provides commands that allow you to reconfigure an existingdatabase from the command line. For example, you may need to deploy the data to multiple placesin a clustered environment. The process involves exporting the database properties to a file, thenimporting the properties file to configure the database.
To reconfigure a previously configured SPD database:
1. At the Administration Utility command line run the egmglobaldb export command. This writes out a file that contains the properties of the database and paths for the new location. For example: egmglobaldb export --o outputpath/egmGlobalDbResource.txt.
The output file can be named anything. It will be a JSON formatted file. If an output path is not provided, the file is written to the current folder.
2. To configure the database, use the egmglobaldb import command to import the database properties and configure the database. The JSON file from the export is the input for the import operation. For example: egmglobaldb import --f egmGlobalDbResource.txt.
For more information about these commands and the Administration Utility in general, see theSpectrum™ Technology PlatformSpectrum Administration Guide.
Enterprise Geocoding Module Data Q3 2018 Dataset Release Notes 24
pitney bowes 0 3001 Summer Street
Stamford CT 06926-0700
USA
www.pitneybowes.com
© 2018 Pitney Bowes Software Inc.
All rights reserved
http:www.pitneybowes.com
Enterprise Geocoding Module Q3 2018 Data Release NotesWhat's NewQ3 Datasets By CountryEnterprise Geocoding FixesData Setup ProceduresSetting up SPD databases for Spectrum 12.2 and 12.1Setting up SPD databases for Spectrum 12.0 and 11.1Reconfiguring a Database with the Administration Utility