Russia (RUS)
| Country Information | Description |
| ISO2 | RU |
| ISO3 | RUS |
| Address Format | Organization PostBox Building Thoroughfare Premise SubBuilding DependentThoroughfare DoubleDependentLocality DependentLocality Locality AdministrativeArea PostalCode |
| PDH | YES |
| PDH completed date | 2020Q2.0 |
| New Source |
|
|
Pre-PDH |
Post-PDH |
|
Reference Data |
rd_RU_geo.lfs |
rd_RU_ggg.lfs
|
Russia: When comparing to 2020Q1.1, there is an overall uplift of ~15% to 19%
|
2020Q1.1 |
2020Q2.0 |
|
2020Q1.1 – District is at Locality level.
|
2020Q2.0 – District is re-aligned to SubAdministrativeArea level.
|
|
2020Q1.1 – Thoroughfare incorrectly parsed to Locality.
|
2020Q2.0 – Thoroughfare correctly parsed.
|
|
2020Q1.1 – Incorrectly verified to other thoroughfare
|
2020Q2.0 – Thoroughfare correctly verified. (More thoroughfare aliases covered)
|
With the 2020Q2.0 release, Russia performance has increased by ~14%. Overall, around 80% of the addresses data has changed due to the re-alignment of Locality and DependentLocality (to SubAdministrativeArea).
Below are additional changes to Russia processing, based on Loqate test data:
The status match and status parse refer to whether the address has been Verified, Corrected, Parsed or Not Matched. The rescode value references if a search was successful.
Russia (Native) changes:
- The match to thoroughfare level increased by ~12%
- The match to locality level decreased by ~3%. These changes are due to re-alignment.
- The status match increased by ~14%.
- The status parse increased by ~3%
Additional improvements to Russia data:
- Improvements have been made to the primary name selection in the data field.
- Improvements on Saint Petersburg data where incomplete city district level is now corrected and complete at DependentLocality level.
- Alignment corrections have been made at SubAdministrativeArea level (Districts).