Geocoding Data v2020.10 Release Notes · 2020. 10. 15. · POL Poland (PL1, PL2, PL4) PRT Portugal...

Geocoding DataVersion October 2020

Release NotesThis document contains information about worldwide datasetsfor use in Spectrum Technology Platform geocoding modulesand the Global Geocoding SDK.You have access only to themodules or products you have licensed. Contact your Preciselyaccount executive for a trial license key for other modules orproducts.

Contents:

What's New...............................................................................2Datasets By Country..............................................................12Bug Fixes................................................................................29Data Setup..............................................................................31Appendix A: Examples of SYNTHETIC_LDU and

CPC_BUILDING_TYPE ....................................................34Appendix B: French House Matching Examples.....................37

What's New

This release includes updated bundles, new fields for select countries, dataset improvements, andbug fixes.

Note: As data is enriched with the quarterly refreshes, the size of the datasets could growthereby increasing memory requirements. Continuous housekeeping of your databases andmanaging/deleting unused data is highly recommended for optimal performance.

Updated Datasets and Bundles

Dataset Improvements

These countries now have postal data available for geocoding.

Country NameCountry Code

(ISO3)

AlgeriaDZA

Costa Rico CRICRI

LebanonLBN

EgyptEGY

BelarusBLR

ZambiaZMB

New datasets

Two country datasets were added:

2Geocoding Data October 2020 Release Notes

Worldwide Geocoding Data

NotesLanguageProduct CodeCountry NameCountry Code

(ISO3)

Open Address Point dataset from theSwitzerland federal office of topologyKOGIS.

Note: this dataset does not includeLichtenstein (LIE).

EnglishCH7SwitzerlandCHE

Master Location Data (MLD) with thefollowing features:

• Base Address Nationale (BAN)multi-sourced dataset

• Incorporation of building footprint forimproved location (returns aPrecisionLevel 19)

• PreciselyID provides a unique andpersistent identifier to reference anaddress without storing the wholeaddress string.

For more details, see the FranceMaster Location Data section below.

FrenchFR8FranceFRA

Updated bundles

This quarter, these datasets were removed from the Beta bundle and promoted to released datasets:

Added to bundleLanguageProduct CodeCountry NameCountry Code

(ISO3)

EGM-WORLD-AP-WLDSpanishAR3ArgentinaARG

EGM-WORLD-STREET-WBLPortugueseBR2BrazilBRA

BRA-EGM--BR3PortugueseBR3BrazilBRA

EGM-WORLD-STREET-WBLEstonianEE2EstoniaEST



Added to bundleLanguageProduct CodeCountry NameCountry Code

(ISO3)

EGM-WORLD-AP-WLD

(first time points are available)

PortugueseMO4MacauMAC

MEX-EGM--MX3

(a la carte)

SpanishMX3MexicoMEX

EGM-WORLD-AP-WLD

(first time points are available)

SpanishPE4PeruPER

For a list of all available datasets, see Datasets By Country on page 12.

Canada Improvements

Synthetic Local Deliver Units (LDU) available in Master Location Data (MLD)

The "Local Delivery Unit" or "LDU" is assigned to postal addresses by Canada Post. If an addresshas not been assigned an LDU, Precisely has assigned a “Synthetic LDU”. Synthetic LDUs are notrecognized by Canada Post. However, our methodology for assigning them is geographically congruentwith LDUs assigned by Canada Post.

For Geocode and Reverse Geocode candidates, the SYNTHETIC_LDU is only returned for caseswhen it is true.The Interactive candidates will return a “t” or an “f” depending on whether the candidatehas a SYNTHETIC_LDU or not.

Building Type Indicator available in Canadian datasets (CA1, CA2, CA3, CA8, 8CA and 1CA)

A new building type indicator is for candidates with an A1 CPC_RECORD_TYPE.

• Geocode or Reverse Geocode candidates: the new field is CPC_BUILDING_TYPE• Interactive candidates: BUILDING_TYPE• Values: '1' for a residential building, '2' for a commercial building, and not returned if it is unknown.

Available as REST Responses

The new fields SYNTHETIC_LDU and CPC_BUILDING_TYPE will only be seen in REST responseswhen Return All Information is set to true. Please note that CPC fields are not present whenSYNTHETIC_LDU = true or t.



For examples of SYNTHETIC_LDU and CPC_BUILDING_TYPE responses, see Appendix A:Examples of SYNTHETIC_LDU and CPC_BUILDING_TYPE on page 34 at the end of theseRelease Notes.

France Improvements

Building Footprint in Master Location Data (FR8)

Points with precisionLevel 19 to describe the precision of the geocode as inside a building structure.

PreciselyID in Master Location Data (FR8)

PreciselyID provides a unique and persistent identifier to reference an address without storing thewhole address string. The PreciselyID is further verification an address exists, independent of DPVmatching. Additionally, to link it to other data (i.e., geoenrichment), Precisely has done the complexmatching for you. Use the PreciselyID as the gateway to the rest of the Precisely data portfolio.Contact your Sales Representative for more information, based on your specific needs.

House Matching Algorithm Improvements in all French datasets

The house number matching algorithm has been improved to handle various addressing rules inFrance. Previouly, the system returned the closest matching address number. Now with the latestrefinements, the system returns the more precise and matching house number. For more detail, seeAppendix B: French House Matching Examples on page 37

Geocoder Improvements

Switzerland and Lichtenstein

This quarter, improvements to Switzerland and Lichtenstein geocoding greatly reduced the numberof false positive results. Other changes include:

• Geographic centroid candidate returns a new additional field "POSTCODE_COUNT_IN_AREA"• Postal centroid candidates return two new additional fields "PRIMARY_AREA_FOR_POSTCODE"

and "MULTIPLE_AREAS_FOR_POSTCODE"• Street addresses in French speaking areas of Switzerland format correctly with house number at

the end• Matching against a locality will no longer be called a city match and the "C" will be replaced with

a hyphen in the Precision code• Added more Italian, French and German street types and keyword recognition• If input looks like "street name 33-35" and there is no range "33-35" in the data, the system will

first attempt to match on the first number 33 and only consider the second number if there is norange matching the first number

• In some circumstances, input words were discarded while parsing. The system no longer discardswords, although on retries, it may ignore some input tokens

Turkey



Previously, the Turkey geocoder returned false-positive street centroids when the street namematched the city name.

Now, it returns the proper geographic centroid match instead of the false-positive street match.

Example :

mainAddress = Toros Adana Cukurova

AreaName3 = Cukurova

AreaName1 = Adana

Earlier was returning:

S4-PN-SC-A

mainAddress: ÇUKUROVA OTOYOLU

AreaName3: CUKUROVA

AreaName1: ADANA

Postcode: 01170

Now it will return geographical centroid match (G3) based on city name.

Formatted Location Address: 01170 CUKUROVA

Added Arabic language support for Iraq (IRQ) and Algeria (DZA)

New Arabic language support has been added to the existing Latin language support for geocoding.

• Interactive is also supported for Arabic in Algeria (DZA).

(Iraq already had Arabic support for Interactive)

Geocoding Dataset Improvements by Country

The table below highlights countries where the quality / match of the geocode is improving, yieldingmore precise geocoding results.

Datasets with liftCountry

United Arab Emirates (AE1, AE2, AE4)ARE

Argentina (AR3)ARG

Belgium (BE3, BE4)BEL




Bulgaria (BG1)BGR

Bosnia and Herzegovina (BA4)BIH

Brazil (BR2, BR4)BRA

Canada (CA4)CAN

Chile (CL2, CL4)CHL

Colombia (CO4)COL

Cyprus (CY1)CYP

Egypt (EG4)EGY

Spain (ES1)ESP

Estonia (EE4)EST

France (FR4)FRA

Greece (GR2, GR4)GRC

Croatia (HR1)HRV

Indonesia (ID1, ID4)IDN

Ireland (IE1, IE3)IRL

Iceland (IS1, IS3)ISL

Italy (IT1, IT2, IT3, IT4)ITA

Jordan (JO1)JOR

Japan (JP7)JPN

Korea, South (KR7)KOR




Lesotho (LS1)LSO

Macau (MO1)MAC

Morocco (MA1)MAR

Moldova (MD2, MD4)MDA

Malaysia (MY1, MY2, MY4)MYS

Nigeria (NG1)NGA

Norway (NO1, NO2)NOR

Poland (PL1, PL2, PL4)POL

Portugal (PT3)PRT

Russia (RU2, RU4)RUS

Serbia (RS4)SRB

Slovakia (SK3)SVK

Sweden (SE1)SWE

Taiwan (TW1)TWN

Ukraine (UA3)UKR

Uruguay (UY1)URY

Venezuela (VE2)VEN

Vietnam (VN1, VN3, VN4)VNM

Kosovo (XK1)XKZ

Zambia (ZM1)ZMB



(USA) Geocoding Data Products Improvements

Location Accuracy Improvements

Previously, USA dataset improvements were communicated in a separate release note. As of theApril 2020 quarterly release, we are now incorporating that information into this Quarterly releaseinformation for a more complete picture of software and data changes.

Geocoding data is for use with the following software: GeoStan Geocoding Suite, SpectrumTechnology Platform, and MapMarker.

Centrus Points:

Added over 582,000 address points this quarter. The Centrus Points product now includes morethan 123,422,000 address points. States with the highest percent of change were:

% ChangeChangeState

3.780%16,557DE

3.512%10,959VT

2.181%5004ND

HERE Points:

Added over 265,000 address points.The HERE product now includes more than 125,191,000 addresspoints. States with the highest percent of change were:

% ChangeChangeState

0.58213,329SC

0.43122,551PA

0.34713,779GA

TomTom Points:



Added over 302,000 address points. The TomTom product now includes more than 123,463,000address points. States with the highest percent of change were:

% ChangeChangeState

6.87747,348ME

3.45536,034UT

2.70040,102OR

Master Location Data (MLD):

Added over 928,000 address points. The MLD data product now includes more than 208,126,000address points. States with the highest percent of change were:

% ChangeChangeState

4.6471,186GU

1.0606,340VT

1.01029,830LA

Fixes and Enhancements Summary

Master Location Data (MLD)

DescriptionTracking #

Corrected the returned location and BLOCK code associated with record 4033 Cider Mill Ct,Burlington, KY 41005.

GEOAUTO-493

Point added as a parcel centroid associated with record 2120 E 4th St, Owensboro, KY 4230.GEOAUTO-843

Points added for #A and #B as structure centroids associated with record 2713 Carnegie Ln,Redondo Beach, CA 90278.

GEOAUTO-894



https://jira.syncsort.com/browse/GEOAUTO-493https://jira.syncsort.com/browse/GEOAUTO-843https://jira.syncsort.com/browse/GEOAUTO-894

DescriptionTracking #

Point added as a structure centroid associated with record 100 Murray Drive WaynesboroGA 30830.

GEOAUTO-908

Corrected the returned location and BLOCK code associated with record 920 Dalton Cir,Foley, AL 36535.

GEOAUTO-927

Corrected and returned the location and BLOCK code of the base point and units A and Bassociated with record 1879 Williams Hwy, Grant Pass, OR, 97527.

GEOAUTO-978

Corrected the returned location and BLOCK code associated with record 279848 WoodsideDr, Comanche, OK 73529.

GEOAUTO-980

Corrected the returned location for base record and various units associated with record 150Lands End Rd, Morehead City, NC 28557.

GEOAUTO-1031



https://jira.syncsort.com/browse/GEOAUTO-908https://jira.syncsort.com/browse/GEOAUTO-927https://jira.syncsort.com/browse/GEOAUTO-978https://jira.syncsort.com/browse/GEOAUTO-980https://jira.syncsort.com/browse/GEOAUTO-1031

Datasets By Country

This table lists a number of characteristics about the country datasets provided in the October 2020data refresh, including maximum precision, availability of postal data, and supported language.

Use these datasets for geocoding. Interactive datasets are identified in the Interactive column.These are companion datasets for performing type ahead interactive geocoding with the GlobalInteractive Geocoding stage (available in Spectrum Global Geocoding beginning with version 12.0SP2 of the Spectrum Technology Platform) and from the Global Geocoding API v2.0.

Note: Occasionally a dataset may undergo a change, such as a new product code or vendor,that results in a new label for the SPD. This change will be noted in the table below for theimpacted dataset(s).

• If you had the old dataset configured in your database you will need to re-configure it in theManagement Console to pick up the new label.

• If you have previously used the old dataset in a dataflow, you must now re-align the dataflowwith the new dataset label.

• In Enterprise Designer, double-click the geocoding stage that uses the dataset. In theOptions dialog, check the Override default options, then check and uncheck the Overridein the default database search list. This will refresh the dataset list with the name of thenew dataset.

LanguagePostcodes1Maximum PrecisionInteractiveProductCode

Country NameCountryISO3

AlbanianNoStreet CentroidAL1AlbaniaALB

French

Arabic

YesStreet CentroidYesDZ1AlgeriaDZA

SpanishNoStreet InterpolatedYesES1AndorraAND

PortugueseNoStreet CentroidYesAO1AngolaAGO

SpanishYesStreet InterpolatedAR2ArgentinaARG

1 No = not available in the dataset, N/A = not available for the country





SpanishYesStreet InterpolatedYesAR1ArgentinaARG

SpanishYesAddress PointNoAR3ArgentinaARG

EnglishYesAddress PointsAR4ArgentinaARG

DutchNoStreet CentroidYesAW2ArubaABW

EnglishYesStreet InterpolatedYesAU5AustraliaAUS

EnglishYesAddress PointsYes7AUAustraliaAUS

GermanYesStreet InterpolatedYesAT1AustriaAUT

EnglishYesStreet InterpolatedAT2AustriaAUT

GermanYesAddress PointsAT3AustriaAUT



EnglishNoStreet InterpolatedYesBS2BahamasBHS

EnglishNoAddress PointsBS4BahamasBHS

Arabic,latinized Arabic

NoStreet InterpolatedYesBH1BahrainBHR


NoStreet InterpolatedBH2BahrainBHR


NoAddress PointsBH4BahrainBHR

EnglishNoStreet CentroidYesBB2BarbadosBRB






Cyrillic,latinizedCyrillic

NoStreet InterpolatedYesBY1BelarusBLR

Dutch, French,German

YesAddress PointsYesBE3BelgiumBEL


YesAddress PointsBE4BelgiumBEL


YesAddress PointsBE7BelgiumBEL


YesStreet InterpolatedYesBE1Belgium,Luxembourg

BEL

EnglishNoStreet CentroidYesBZ2BelizeBLZ

FrenchNoStreet CentroidYesBJ1BeninBEN

EnglishNoStreet CentroidYesBM2BermudaBMU

SpanishNoStreet InterpolatedYesBO2BoliviaBOL

BosnianYesStreet InterpolatedYesBA1Bosnia andHerzegovina

BIH

EnglishYesStreet InterpolatedBA2Bosnia andHerzegovina

BIH

EnglishYesAddress PointsBA4Bosnia andHerzegovina

BIH

EnglishNoStreet InterpolatedYesBW1BotswanaBWA

PortugueseYesStreet InterpolatedYesBR1BrazilBRA

PortugueseYesStreet InterpolatedNoBR2BrazilBRA






PortugueseYesAddress PointsNoBR3BrazilBRA

PortugueseYesAddress PointsBR4BrazilBRA

MalayYesStreet CentroidYesBN1Brunei DarussalamBRN

BulgarianlatinizedBulgarian

YesStreet InterpolatedYesBG1BulgariaBGR

Bulgarian,latinizedBulgarian

YesStreet InterpolatedBG2BulgariaBGR

EnglishYesAddress PointsBG4BulgariaBGR

FrenchNoStreet CentroidYesBF1Burkina FasoBFA

FrenchNoStreet CentroidYesBI1BurundiBDI

FrenchNoStreet CentroidYesCM1CameroonCMR

English,French

YesStreet InterpolatedYesCA1CanadaCAN

English,French

YesStreet InterpolatedCA2CanadaCAN

English,French

YesAddress PointsCA3CanadaCAN

English,French

YesAddress PointsCA4CanadaCAN

English,French

YesMLDYesCA8CanadaCAN

SpanishYesStreet InterpolatedYesCL1ChileCHL






SpanishYesStreet InterpolatedCL2ChileCHL

SpanishYesAddress PointsCL3ChleCHL

EnglishYesAddress PointsCL4ChileCHL

SimplifiedChinese,latinizedChinese

YesStreet CentroidYesCN6ChinaCHN

SpanishYesStreet InterpolatedYesCO1ColombiaCOL

SpanishNoAddress PointsCO4ColombiaCOL

FrenchNoStreet CentroidYesCG1Congo-BrazzavilleCOG

FrenchNoStreet CentroidYesCD1Congo-KinshasaCOD

SpanishNoStreet InterpolatedYesCR2Costa-RicaCRI

Greek,latinized Greek

YesStreet InterpolatedYesCY1CyprusCYP

CroatianYesStreet InterpolatedYesHR1CroatiaHRV

EnglishYesStreet InterpolatedHR2CroatiaHRV

EnglishYesAddress PointsHR4CroatiaHRV

SpanishNoStreet CentroidYesCU2CubaCUB


YesStreet InterpolatedYesCY1CyprusCYP

CzechYesStreet InterpolatedYesCZ1Czech RepublicCZE






CzechYesAddress PointsCZ3Czech RepublicCZE

DanishYesAddress PointsDK3DenmarkDNK

DanishYesStreet InterpolatedYesDK1DenmarkDNK

SpanishYesStreet InterpolatedYesDO2Dominican RepublicDOM

SpanishYesStreet InterpolatedYesEC2EcuadorECU


NoStreet InterpolatedYesEG1EgyptEGY

SpanishNoStreet CentroidYesSV2El SalvadorSLV

EstonianYesStreet InterpolatedYesEE1EstoniaEST

EstonianYesStreet InterpolatedEE2EstoniaEST

EnglishNoAddress PointsEE4EstoniaEST

FinnishYesStreet InterpolatedYesFI1FinlandFIN

FrenchYesStreet InterpolatedYesFR1FranceFRA

FrenchYesStreet InterpolatedFR2FranceFRA

FrenchYesAddress PointsFR4FranceFRA

FrenchYesAddress PointsFR7FranceFRA

FrenchYesMaster Location Data(MLD)

FR8FranceFRA

FrenchNoStreet CentroidYesGA1GabonGAB






GermanYesStreet InterpolatedYesDE1GermanyDEU

GermanYesAddress PointsDE3GermanyDEU

EnglishNoStreet CentroidYesGH1GhanaGHA


YesStreet InterpolatedYesGR1GreeceGRC

EnglishYesAddress PointsGR4GreeceGRC

SpanishNoStreet CentroidYesGT2GuatemalaGTM

EnglishNoStreet CentroidYesGY2GuyanaGUY

SpanishNoStreet CentroidYesHN2HondurasHND

latinizedChinese

N/AStreet InterpolatedYesHK1Hong KongHKG

latinizedChinese

N/AAddress PointsHK3Hong KongHKG

TraditionalChinese,latinizedChinese

N/AAddress PointsHK7Hong KongHKG

HungarianYesStreet InterpolatedYesHU1HungaryHUN

EnglishYesStreet InterpolatedHU2HungaryHUN

EnglishYesAddress PointsHU4HungaryHUN

IcelandicYesStreet InterpolatedYesIS1IcelandISL

EnglishYesAddress PointsIS3IcelandISL






EnglishYesStreet InterpolatedIN7IndiaIND

EnglishYesStreet InterpolatedYesIN1IndiaIND

EnglishYesAddress PointsIN3

*a la carteonly

IndiaIND

IndonesianYesStreet InterpolatedID1 2IndonesiaIDN

EnglishYesStreet InterpolatedID2IndonesiaIDN

EnglishYesAddress PointsID4IndonesiaIDN


NoStreet CentroidYesIQ1IraqIRQ

EnglishYesStreet InterpolatedYesIE1IrelandIRL

EnglishYesAddress PointsIE3IrelandIRL

latinizedHebrew

YesStreet InterpolatedYesIL2IsraelISR

latinizedHebrew

YesAddress PointsIL4IsraelISR

ItalianYesAddress PointsIT4ItalyITA

ItalianYesStreet InterpolatedYesIT1ItalyITA

ItalianYesAddress PointsIT3ItalyITA

EnglishYesStreet CentroidYesJM2JamaicaJAM

1 No = not available in the dataset, N/A = not available for the country2 Vendor change. This affects dataflows that used the previous ID1 dataset. See this note for more

information.





Japanese,latinized

YesAddress PointsYesJP7JapanJPN


NoStreet InterpolatedYesJO1JordanJOR

EnglishNoStreet CentroidYesKE1KenyaKEN

latinizedKorean

YesAddress PointsKR7Korea, SouthKOR

EnglishYesStreet CentroidYesXK1KosovoXKX


NoStreet InterpolatedYesKW1KuwaitKWT

LatvianYesStreet InterpolatedYesLV1LatviaLVA

EnglishYesAddress PointsLV4LatviaLVA


NoStreet InterpolatedYesLB1LebanonLBN

EnglishYesStreet CentroidYesLS1LesothoLSO


YesStreet InterpolatedYesCH1LiechtensteinLIE

LithuanianYesStreet InterpolatedYesLT1LithuaniaLTU

EnglishYesAddress PointsLT4LithuaniaLTU

PortugueseNoStreet InterpolatedYesMO1MacauMAC

PortugueseNoAddress PointsMO4MacauMAC

EnglishYesStreet InterpolatedYesMK1MacedoniaMKD






MalayNoStreet CentroidYesMW1MalawiMWI

MalayYesStreet InterpolatedYesMY1MalaysiaMYS

MalayYesAddress Points, POIYesMY3MalaysiaMYS

MalayNoStreet InterpolatedYesMY5MalaysiaMYS

FrenchNoStreet CentroidYesML1MaliMLI

MalteseYesStreet CentroidYesMT1MaltaMLT

FrenchNoStreet InterpolatedFR2MartiniqueMTQ

FrenchNoStreet CentroidYesMR1MauritaniaMRT

EnglishNoStreet CentroidYesMU1MauritiusMUS

SpanishYesStreet InterpolatedMX2MexicoMEX

SpanishYesAddress PointsMX3MexicoMEX

SpanishYesAddress PointsMX4MexicoMEX

SpanishYesStreet InterpolatedYesMX1MexicoMEX

EnglishNoStreet InterpolatedMD2MoldovaMDA

EnglishNoAddress PointsMD4MoldovaMDA

MontenegrinYesStreet InterpolatedYesME1MontenegroMNE

MontenegrinYesStreet InterpoliatedYesME1MontenegroMNE

FrenchYesStreet InterpolatedYesMA1MoroccoMAR






FrenchYesStreet InterpolatedMA2MoroccoMAR

EnglishYesStreet CentroidYesMZ1MozambiqueMOZ

EnglishNoStreet InterpolatedYesNA1NamibiaNAM

DutchYesStreet InterpolatedYesNL1NetherlandsNLD

DutchYesAddress PointsNL3NetherlandsNLD

EnglishYesStreet InterpolatedYesNZ1New ZealandNZL

EnglishYesStreet InterpolatedNZ5New ZealandNZL

EnglishYesAddress PointsNZ7New ZealandNZL

SpanishNoStreet CentroidYesNI2NicaraguaNIC

FrenchNoStreet CentroidYesNE1NigerNER

EnglishNoStreet CentroidYesNG1NigeriaNGA

NorwegianYesStreet InterpolatedYesNO1NorwayNOR

EnglishYesAddress PointsNO4NorwayNOR


NoStreet CentroidYesOM1OmanOMN

SpanishNoStreet InterpolatedYesPA2PanamaPAN

SpanishYesStreet InterpolatedYesPY2ParaguayPRY

SpanishYesStreet InterpolatedYesPE2PeruPER

SpanishYesAddress PointsPE4PeruPER






EnglishYesStreet InterpolatedYesPH1PhilippinesPHL

EnglishYesStreet InterpolatedPH2PhilippinesPHL

EnglishYesAddress PointsPH4PhilippinesPHL

EnglishYesStreet InterpolatedPH1PhilippinesPHL

Polish, CZEYesStreet InterpolatedYesPL1PolandPOL

Polish, CZEYesAddress PointsPL3PolandPOL

EnglishYesAddress PointsPL4PolandPOL

PortugueseYesStreet InterpolatedPT1PortugalPRT

PortugueseYesStreet InterpolatedYesPT2PortugalPRT

PortugueseYesAddress PointsPT4PortugalPRT

PortugueseYesAddress PointsPT3PortugalPRT


NoStreet InterpolatedYesQA1QatarQAT

RomanianNoStreet InterpolatedYesRO1RomaniaROU

EnglishNoAddress PointsRO4RomaniaROU

Russian,English

YesStreet InterpolatedYesRU1RussiaRUS

Russian,English

YesStreet InterpolatedRU2RussiaRUS

Russian,English

YesAddress PointsRU3RussiaRUS






Russian,English

YesAddress PointsRU4RussiaRUS

FrenchNoStreet CentroidYesRW1RwandaRWA

EnglishNoStreet CentroidYesKN2Saint Kitts and NevisKNA


YesStreet InterpolatedYesSA1Saudi ArabiaSAU

FrenchYesStreet CentroidYesSN1SenegalSEN

Serbian,English

YesStreet InterpolatedYesRS1SerbiaSRB

Serbian,latinizedSerbian

YesStreet InterpolatedRS2SerbiaSRB

Serbian,latinizedSerbian

YesAddress PointsRS4SerbiaSRB

EnglishYesStreet InterpolatedYesSG1SingaporeSGP

EnglishYesAddress PointsSG3SingaporeSGP

EnglishNoStreet InterpolatedSG6SingaporeSGP

EnglishNoAddress PointsSG7SingaporeSGP

SlovakianYesStreet InterpolatedYesSK1SlovakiaSVK

SlovakianYesAddress PointsSK3SlovakiaSVK

SlovenianYesStreet InterpolatedYesSI1SloveniaSVN






EnglishYesAddress PointsSI4SloveniaSVN

EnglishYesStreet InterpolatedYesZA1South AfricaZAF

EnglishYesAddress PointsZA4South AfricaZAF

SpanishYesStreet InterpolatedYesES1SpainESP

SpanishYesAddress PointsES4SpainESP

EnglishNoStreet InterpolatedLK2Sri LankaLKA

DutchNoStreet InterpolatedYesSR2SurinameSUR

EnglishYesStreet CentroidYesSZ1SwazilandSWZ

SwedishYesStreet InterpolatedSE2SwedenSWE

SwedishYesStreet InterpolatedYesSE1SwedenSWE

SwedishYesAddress PointsSE4SwedenSWE

French, Italian,German

YesAddress PointsCH3SwitzerlandCHE


YesStreet InterpolatedYesCH1Switzerland,Liechtenstein

CHE


YesAddress PointsCH7SwitzerlandCHE

EnglishYesStreet InterpolatedYesTW1TaiwanTWN

EnglishYesAddress PointsTW3TaiwanTWN

EnglishYesAddress PointsTW4TaiwanTWN






EnglishYesStreet CentroidYesTZ1TanzaniaTZA

Thai script,latinized Thai

YesStreet CentroidYesTH1ThailandTHA


YesAddress PointsTH3ThailandTHA


YesStreet InterpolatedTH2ThailandTHA


YesAddress PointsTH4ThailandTHA

EnglishNoStreet CentroidYesTG1TogoTGO

EnglishNoStreet CentroidYesTT2Trinidad and TobagoTTO

FrenchNoStreet InterpolatedYesTN1TunisiaTUN

TurkishYesStreet InterpolatedYesTR1TurkeyTUR

EnglishYesStreet InterpolatedTR2TurkeyTUR

EnglishYesAddress PointsTR4TurkeyTUR

TurkishYesStreet InterpolatedTR5TurkeyTUR

TurkishYesAddress PointsTR7TurkeyTUR

EnglishNoStreet CentroidYesUG1UgandaUGA

English,Ukrainian

YesStreet InterpolatedYesUA1UkraineUKR

English,Ukrainian

YesAddress PointsUA3UkraineUKR







YesStreet InterpolatedYesAE1United Arab EmiratesARE


YesStreet InterpolatedAE2United Arab EmiratesARE


YesAddress PointsAE4United Arab EmiratesARE

EnglishYesStreet InterpolatedYesGB1United KingdomGBR

EnglishYesAddress PointsGB7United KingdomGBR

EnglishYesAddress PointsYesGB8United KingdomGBR

EnglishYesStreet InterpolatedYesKGDUnited StatesUSA

EnglishYesAddress PointsKPDUnited StatesUSA

EnglishYesAddress PointsYes (8 US)KLDUnited StatesUSA

SpanishYesStreet InterpolatedUY1UruguayURY

EnglishYesAddress PointsUY4UruguayURY

SpanishNoStreet CentroidYesVE2VenezuelaVEN

VietnameseYesStreet InterpolatedYesVN1Viet NamVNM

VietnameseNoStreet InterpolatedVN2Viet NamVNM

VietnameseNoAddress PointsVN4Viet NamVNM

EnglishYesBoundary CentroidYes8XWWorldWORLD

EnglishYesBoundary CentroidXW1WorldXWG







NoStreet CentroidYesYE1YemenYEM

EnglishNoStreet CentroidYesZM1ZambiaZMB

EnglishNoStreet CentroidYesZW1ZimbabweZWE




Bug Fixes

This release includes these software and data fixes for geocoding with Spectrum Technology Platform.

Software Fixes

ResolutionCountryKey

The HouseNumberHigh and Low fields now match the input address number.AUSGN-38417

Extra comma at the end of a singleline address no longer causes an exceptionCANGN-38253

For input address British Columbia bc CA, we now return a G1 candidate of BC, CAN.CANGN-24328

Improved German geocoding handling when multiple slashes (/) are in the input address.DEUGN-37654

The customer-reported France address (with and without an apostrophe) now returns thesame street-centroid candidate.

FRAGN-37044

A France address with non-matching city and a valid postcode now returns a point-levelcandidate.

FRAGN-37043

France dataset (FR4) now returns 119 Avenue Foch.FRAGN-33670

LA PETITE ROUTE DES MIELLES now returns LA PETITE RUE DES MIELLES againstGB1 and LA PETITE ROUTE DES MIELLES against GB8 ("rue" versus "route").

GBRGN-17678

An input address with only ISO Country name 'IND' no longer causes a null point exception.INDGN-38251

Updated street matching for numeric streets with missing thoroughfare type.INDGN-29809

Hyphens in the input no longer cause null exceptionINDGN-37628

Improved matching and parsing of Italy geocoder, fixing several reported issues. (GN-35282,GN-35278, GN-35277, GN-35276, GN-35271, GN-35171)

ITAGN-35283




Interactive geocoding for Japan now autosuggests on postcodes starting with '0" (zero).

If the zero is not entered, it will not autosuggest (e.g., entering 731322 when the postcodeis 0731322).

Example

Input: 0731322

Output:

• JA formattedString: , , , 1 33, 0731322• EN formattedString: Hokkaido, Kabato-Gun Shintotsukawa-Cho, Yoshino, 1 33, 0731322

JPNGN-37587

Forward and Reverse Geocode candidate now returns "Williams Street" (street spelled out).NZLGN-38137

Improved matching of Russian addresses when thoroughfare type "Ulitsa" occurs beforemisspelled streetname.

RUSGN-35013

Postal candidates will now return administrative fields in Turkey data (TR5).TURGN-38341

Improved point-level matches for several cases in Turkey data (TR5).TURGN-38142,GN-37583

Improved search results when retrieving candidates when data has Estado but the input does not have Estado.

VENGN-37605

Data Fixes


Data now has a house number for J.E. IRAUSQUIN BOULEVARD in the town of Oranjestadand Noord

ABWGN-23459

Added additional street or house number records to Aruba data. wad - not in rel notesABWGN-23458

The addresses reported now geocode in less than a second. Example Street: 27075 GRAYRD 40 City: CLARKSBURG Prov: ON Postcode: N0H1J0

CANGN-37655,GN-36249

Input City of Copenhagen now returns a City level geographic centroid candidate.DNKGN-37030



Data Setup

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 ofthe Spectrum Technology Platform.

Spectrum version 2019.1 or greater uses Command Line Interface (CLI) commands to manage(install, extract, archive, or delete) product data. See Setting up SPD databases for Spectrum2019.1 or greater on page 32.

Spectrum versions 2018.2, 12.2 and 12.1 provide an extraction and configuration using theManagement Console. See Setting up SPD databases for Spectrum 2018.2 and v12.x on page33.

Saving Databases

Be aware that any data folders under a Spectrum installation will be removed when Spectrum isuninstalled. To retain the data for future use, consider archiving the SPD in a location outside of theSpectrum installation. To do this, set the spectrum.data.manager.archive.data property totrue located in the \server\app\conf\spectrum-container.properties.

You can also change the data repository location by providing a path inspectrum.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 the Management Console and available for usealongside any new data you installed. If you decide you don't want the legacy datasets associatedwith the database resource, in Management Console's Spectrum Database page, select thedatabase resource and click Modify. From the Edit Database page, clear the checkbox next to thedataset(s) you no longer want in the database. The legacy datasets will no longer be available.



Setting up SPD databases for Spectrum 2019.1 or greater

• You must be a Spectrum Technology Platform administrator (admin) to perform this task.• The Spectrum Technology Platform has Command Line Interface (CLI) commands to install

Spectrum data without having to download the data to the Spectrum server or having to connectyour Spectrum server to the internet. The CLI commands copy data to the Spectrum server.

Follow this procedure to extract and configure SPD datasets that have not been set up previously.

Note: We recommend setting a location for your Spectrum Product Data (SPD) that is separatefrom the Spectrum Technology Platform installation folder.

To set up and configure an SPD database:

1. Update your Spectrum installation with all product updates (patches) available for your release.2. Verify the Spectrum Technology Platform server is running before you begin.3. Download your Spectrum Product Database (SPD) files from Precisely using the link provided

in the Precisely communication or from the Precisely Data Experience (PDX).4. In the Administration Utility, open the command-line interface. If you are not familiar with this

tool, see "Getting Started with the Administration Utility".5. Connect to the Spectrum Technology Platform server by typing this command:

connect --h servername:port --u username --p password --s SSLtrueFalse

For example,

connect --h myserver:8080 --u admin --p myPassword1 --s false

6. Optionally list the locations of extracted Spectrum Product Data (SPD) files based on productname by typing:

productdata extract list

The command output shows the directory where files are located for each product.7. Install the data to the Spectrum server by typing:

productdata install --f fileOrDirectory --w waitOrReturn

For example,

productdata install --f E:/Geocoding/filename.spd --w

If you're installing multiple .spd files, then use the folder path to the files. The command installsthe data files that are in the folder and subfolders. For example:

productdata install --f E:/folderpath/Geocoding --w

8. Define a database resource for the data in the Management Console; see Creating a DatabaseResource for more information.



https://docs.precisely.com/docs/sftw/spectrum/ProductUpdateSummary/index.html#ProductUpdateSummary/source/Introduction.htmlhttps://data.precisely.com/https://docs.precisely.com/docs/sftw/spectrum/19.1/en/webhelp/AdministrationGuide-WebUI/index.html#AdministrationGuide/source/AdministrationUtility/GettingStarted.htmlhttps://docs.precisely.com/docs/sftw/spectrum/19.1/en/webhelp/InstallationGuide-Windows/index.html#InstallationGuide/source/InstallingDatabases/spd_install_create_database.htmlhttps://docs.precisely.com/docs/sftw/spectrum/19.1/en/webhelp/InstallationGuide-Windows/index.html#InstallationGuide/source/InstallingDatabases/spd_install_create_database.html

Setting up SPD databases for Spectrum 2018.2 and v12.x

Follow this procedure to extract and configure SPD datasets that have not been set up previously.This is done using the 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 bedownloaded as an SPD file, which is essentially a zip file with an .spd extension.

3. Copy the .spd into the Spectrum server's dataimport folder or a location of yourchoice.

The dataimport folder for a default installation is located in C:\Program Files\PitneyBowes\Spectrum\server\app\dataimport.. Once the .spd is in the folder, it willautomatically 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 yourcustom location.You cannot pick which datasets are extracted. This is a change from thepast when dbloader allowed you to choose.

Note: The SPD will be uninstalled from the default Spectrum location during anuninstallation of Spectrum. If you want to change the default data repository or to archivethe .spd, Spectrum provides the spectrum-container.properties file under\server\app\conf that you can edit. See the propertiesspectrum.data.manager.storage.directory andspectrum.data.manager.archive.data. Restart the server when done.

4. To configure a new database in the Management Console, choose Resources > SpectrumDatabases.

5. Click Add , provide a name for the database, and choose the appropriate module from thelist.

6. Select the dataset(s) that you would like to add to the database by checking the box next to thename. Save the database when finished.

7. To reconfigure a database resource in the Management Console, select the database from the

list. Click Modify . 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.

To reconfigure the database from the command line, see Reconfiguring a Database with theAdministration Utility.



https://docs.precisely.com/docs/sftw/spectrum/ProductUpdateSummary/index.html#ProductUpdateSummary/source/Introduction.html

Appendix A: Examples of SYNTHETIC_LDU andCPC_BUILDING_TYPE

The new fields SYNTHETIC_LDU and CPC_BUILDING_TYPE will only be seen in REST responseswhen Return All Information is set to true. Please note that CPC fields are not present whenSYNTHETIC_LDU = true or t.

SYNTHETIC_LDU

Example address: 86 CLAIRERIDGE E SHERWOOD PARK AB T8C 1H3

Geocode Candidate

{ "responses": [ { "totalPossibleCandidates": 1, "totalMatches": 1, "candidates": [ { "precisionLevel": 16, "formattedStreetAddress": "86 CLAIRERIDGE E", "formattedLocationAddress": "SHERWOOD PARK AB T8C 1H3", "identifier": "10000630", "precisionCode": "S8HPNTSCZA", "sourceDictionary": "0", "matching": { "matchOnAddressNumber": true, "matchOnPostCode1": true, "matchOnPostCode2": true, "matchOnAreaName1": true, "matchOnAreaName2": true, "matchOnAreaName3": true, "matchOnAreaName4": true, "matchOnAllStreetFields": true, "matchOnStreetName": true, "matchOnStreetType": true, "matchOnStreetDirectional": true, "matchOnPlaceName": true, "matchOnInputFields": false }, "geometry": { "type": "Point", "coordinates": [ -113.23297, 53.376 ], "crs": { "type": "name", "properties": { "name": "epsg:4326" } } }, "address": { "mainAddressLine": "86 CLAIRERIDGE E", "addressLastLine": "SHERWOOD PARK AB T8C 1H3", "placeName": "", "areaName1": "AB", "areaName2": "", "areaName3": "SHERWOOD PARK", "areaName4": "", "postCode1": "T8C", "postCode2": "1H3", "country": "CAN", "addressNumber": "86", "streetName": "CLAIRERIDGE", "unitType": "", "unitValue": "", "customFields": { "CENSUS_DA": "1690", "PB_KEY": "P0001A6UB6BB", "LANGUAGE": "en", "SEGMENT_ID": "10000630", "RESULT_CODE": "S8HPNTSCZA", "POST_DIRECTIONAL": "E", "CENSUS_CMA": "835", "CENSUS_CD": "4811", "SYNTHETIC_LDU": "true", "CENSUS_CSD": "052", "MAIN_ADDRESS": "CLAIRERIDGE", "StreetDataType": "34", "MATCH_SCORE": "100", "CENSUS_CT": "010506" } }, "ranges": [ { "lowHouse": "86", "highHouse": "86", "side": "LEFT", "oddEvenIndicator": "BOTH", "units": [], "customValues": { "AREA_NAME_3": "SHERWOOD PARK", "AREA_NAME_1": "AB", "POST_CODE_1": "T8C", "POST_CODE_2": "1H3" } } ] } ], "customValues": { "FormattedInputStreet": "86 CLAIRERIDGE E" } } ] }

Interactive Candidate

{ "totalPossibleCandidates": 1, "totalMatches": 1, "candidates": [ { "precisionLevel": 0, "formattedStreetAddress": "86 CLAIRERIDGE E", "formattedLocationAddress": "SHERWOOD PARK, AB T8C 1H3",



"formattedAddress": "86 CLAIRERIDGE E, SHERWOOD PARK, AB T8C 1H3", "identifier": "P0001A6UB6BB", "matching": { "matchOnAddressNumber": true, "matchOnPostCode1": false, "matchOnPostCode2": false, "matchOnAreaName1": false, "matchOnAreaName2": false, "matchOnAreaName3": false, "matchOnAreaName4": false, "matchOnAllStreetFields": false, "matchOnStreetName": true, "matchOnStreetType": false, "matchOnStreetDirectional": false, "matchOnPlaceName": false, "matchOnInputFields": false }, "geometry": { "type": "Point", "coordinates": [ -113.23115999999999, 53.3784 ], "crs": { "type": "name", "properties": { "name": "epsg:4326" } } }, "address": { "mainAddressLine": "", "addressLastLine": "", "areaName1": "AB", "areaName3": "SHERWOOD PARK", "postCode1": "T8C 1H3", "postCode2": "", "country": "CAN", "addressNumber": "86", "streetName": "CLAIRERIDGE E", "unitType": "", "unitValue": "", "customFields": { "FORMATTED_STRING": "86 CLAIRERIDGE E, SHERWOOD PARK, AB T8C 1H3", "DISTANCE": "-0.0", "LOCATION_CODE": "S8", "RECORD_TYPE": "2", "FEATUREID": "P0001A6UB6BB", "FROM_CUSTOM_DATASET": "false", "MATCHED_FROM_ADDRESSNUMBER": "86", "MATCHED_FROM_STREETNAME": "CLAIRERIDGE", "SYNTHETIC_LDU": "t", "ADDRESS_NUMBER_FROM": "86", "DISTANCE_UNIT": "MILES" } }, "ranges": [] } ], "customValues": {} }

CPC_BUILDING_TYPE

Example address: 12 TOWNSHIP ROAD 391 RED DEER COUNTY AB T4S 2A1

Geocode Candidate

{ "responses": [ { "totalPossibleCandidates": 1, "totalMatches": 1, "candidates": [ { "precisionLevel": 16, "formattedStreetAddress": "12 TOWNSHIP ROAD 391", "formattedLocationAddress": "RED DEER COUNTY AB T4S 2A1", "identifier": "1010989", "precisionCode": "S8HPNTS-ZA", "sourceDictionary": "0", "matching": { "matchOnAddressNumber": true, "matchOnPostCode1": true, "matchOnPostCode2": true, "matchOnAreaName1": true, "matchOnAreaName2": true, "matchOnAreaName3": false, "matchOnAreaName4": true, "matchOnAllStreetFields": true, "matchOnStreetName": true, "matchOnStreetType": true, "matchOnStreetDirectional": true, "matchOnPlaceName": true, "matchOnInputFields": false }, "geometry": { "type": "Point", "coordinates": [ -113.8205, 52.32993 ], "crs": { "type": "name", "properties": { "name": "epsg:4326" } } }, "address": { "mainAddressLine": "12 TOWNSHIP ROAD 391", "addressLastLine": "RED DEER COUNTY AB T4S 2A1", "placeName": "", "areaName1": "AB", "areaName2": "", "areaName3": "RED DEER COUNTY", "areaName4": "", "postCode1": "T4S", "postCode2": "2A1", "country": "CAN", "addressNumber": "12", "streetName": "391", "unitType": "", "unitValue": "", "customFields": { "CENSUS_DA": "0521", "PB_KEY": "P0001A6LYTGH", "LANGUAGE": "en", "SEGMENT_ID": "1010989", "RESULT_CODE": "S8HPNTS-ZA", "CENSUS_CMA": "830", "PRE_THOROUGHFARE_TYPE": "TOWNSHIP ROAD", "THOROUGHFARE_TYPE": "TOWNSHIP ROAD", "CENSUS_CD": "4808", "CENSUS_CSD": "011", "CPC_RECORD_TYPE": "A1", "MAIN_ADDRESS": "391", "StreetDataType": "34", "MATCH_SCORE": "94", "CENSUS_CT": "001601", "CPC_BUILDING_TYPE": "1" } }, "ranges": [ {



"lowHouse": "12", "highHouse": "12", "side": "LEFT", "oddEvenIndicator": "BOTH", "units": [], "customValues": { "AREA_NAME_3": "RED DEER COUNTY", "AREA_NAME_1": "AB", "POST_CODE_1": "T4S", "POST_CODE_2": "2A1" } } ] } ], "customValues": { "FormattedInputStreet": "12 TNR 391" } } ] }

Interactive Candidate

{ "totalPossibleCandidates": 1, "totalMatches": 1, "candidates": [ { "precisionLevel": 0, "formattedStreetAddress": "12 TOWNSHIP ROAD 391", "formattedLocationAddress": "RED DEER COUNTY, AB T4S 2A1", "formattedAddress": "12 TOWNSHIP ROAD 391, RED DEER COUNTY, AB T4S 2A1", "identifier": "P0001A6LYTGH", "matching": { "matchOnAddressNumber": true, "matchOnPostCode1": true, "matchOnPostCode2": false, "matchOnAreaName1": true, "matchOnAreaName2": false, "matchOnAreaName3": true, "matchOnAreaName4": false, "matchOnAllStreetFields": false, "matchOnStreetName": true, "matchOnStreetType": false, "matchOnStreetDirectional": false, "matchOnPlaceName": false, "matchOnInputFields": false }, "geometry": { "type": "Point", "coordinates": [ -113.822785, 52.330945 ], "crs": { "type": "name", "properties": { "name": "epsg:4326" } } }, "address": { "mainAddressLine": "", "addressLastLine": "", "areaName1": "AB", "areaName3": "RED DEER COUNTY", "postCode1": "T4S 2A1", "postCode2": "", "country": "CAN", "addressNumber": "12", "streetName": "TOWNSHIP ROAD 391", "unitType": "", "unitValue": "", "customFields": { "DISTANCE": "-0.0", "MATCHED_FROM_AREANAME1": "AB", "FROM_CUSTOM_DATASET": "false", "MATCHED_FROM_ADDRESSNUMBER": "12", "MATCHED_FROM_STREETNAME": "TOWNSHIP RD 391","SYNTHETIC_LDU": "f", "ADDRESS_NUMBER_FROM": "12", "FORMATTED_STRING": "12 TOWNSHIP ROAD 391, RED DEER COUNTY, AB T4S 2A1", "LOCATION_CODE": "S8", "RECORD_TYPE": "2", "MATCHED_FROM_POSTCODE": "T4S 2A1", "FEATUREID": "P0001A6LYTGH", "MATCHED_FROM_AREANAME3": "RED DEER CNTY", "DISTANCE_UNIT": "MILES", "BUILDING_TYPE": "1" } }, "ranges": [] } ], "customValues": {} }



Appendix B: French House Matching Examples

The house number matching algorithm has been improved to handle various addressing rules inFrance. Previouly, the system returned the closest matching address number. Now with the latestrefinements, the system returns the more precise and matching house number.

Rule 1: House number with building letter

Examples

1 A RUE DU BOVAGE match 1 A RUE DU BOVAGE

1 B RUE DU BOVAGE match 1 B RUE DU BOVAGE

1 C RUE DU BOVAGE match 1 C RUE DU BOVAGE

Rule 2: House number with repetition index

Examples

1 BIS RUE DU BOVAGE match 1 BIS RUE DU BOVAGE

1 TER RUE DU BOVAGE match 1 TER RUE DU BOVAGE

1 QUATER RUE DU BOVAGE match 1 QUATER RUE DU BOVAGE

1 QUINQUIES RUE DU BOVAGE match 1 QUINQUIES RUE DU BOVAGE

Rule 3: House number with repetition index abbreviation

Examples

1 B RUE DU BOVAGE match 1 BIS RUE DU BOVAGE

1 T RUE DU BOVAGE match 1 TER RUE DU BOVAGE

1 Q RUE DU BOVAGE match

• 1 QUATER RUE DU BOVAGE• OR 1 QUINQUIES RUE DU BOVAGE

So essentially, house number 1B would either match to house number 1 B or 1 Bis, and won't producea house number match on address number 1.

1B will match either to 1 BIS or 1 B

1T will match either to 1 TER or 1 T

1Q will match either to 1 QUATER or 1 QUINQUIES or 1 Q

If all the matching is done for the closest house number, house number match flag will be set tofalse. For example 1B matching to 1, will have house number flag as false, and result code will havehyphen instead of H.



2 Blue Hill Plaza, #1563

Pearl River, NY 10965

USA

www.precisely.com

© 2008, 2020 Precisely. All rights reserved.

Table of ContentsWorldwide Geocoding DataWhat's New(USA) Geocoding Data Products Improvements

Datasets By CountryBug FixesData SetupSetting up SPD databases for Spectrum 2019.1 or greaterSetting up SPD databases for Spectrum 2018.2 and v12.x

Appendix A: Examples of SYNTHETIC_LDU and CPC_BUILDING_TYPEAppendix B: French House Matching Examples

Geocoding Data v2020.10 Release Notes · 2020. 10. 15. · POL Poland (PL1, PL2, PL4) PRT Portugal...

Documents

Transcript of Geocoding Data v2020.10 Release Notes · 2020. 10. 15. · POL Poland (PL1, PL2, PL4) PRT Portugal...