1.Validity Mistakes 

A Valid query address is:

Unambiguous, pointing to a single unique location
Real, referring to an address that exists in the real world

A query address that does not meet any of these is considered Invalid. A full comprehensive list of Valid and Invalid query address examples can be found in Guidelines. Sections 3.3 and 3.4. Please refer to the examples when you write your reasoning.

Sometimes query address might not be so obvious if it refers to a single unique location. One example of such case is when user adds a unit number to the query. Usually it is put in form “x-x”. For example 17-18, 4-8 etc. This form is unfortunately very similar to double address number of x/x (4/5, 7/9 etc.) as this kind of address can also be shown in ”x-x” form (eg. 3-5). CSGL 4.1. When you see street number like this always make sure if it is a double street number or single street number with unit number added. When we confirmed that address request is not a range we can safely assume that user gave a unit number. Unit number is not necessary in response address to validate that response address is a single unique building.

Example 1:

.

Query: Norwida 15-8, 60-867, Poznań

Response Address: Cypriana K Norwida 15, 60-867 Poznań,

Query Address: Valid

Address Accuracy: Correct

A quick check on Targeo map engine and official polish geoportal shows that only existing street number is 15 alone. Now we are sure that user gave an additional unit number. This address, with or without a unit number, points to only one location. Now we can safely confirm this address as Valid.
Additional explanation can be found in GL 7.3.2 and CSGL for Poland 5.1. 

 

2. Pin Mistakes

Please remember that in Address Verification tasks the location of the pin should reflect the query address, not a response one. This differs from the Maps Search task, where the pin is related to the result address.

Always double check if pin accurately reflects queried address.

Example 1:

.

Query: Pałucka 34, 60-604 Poznań

Response Address: Pałucka 34, 60-604 Poznań

Query Address: Valid

Address Accuracy: Correct

Pin Accuracy: Wrong (52.41841113384685, 16.911594053908665)

.

.

Query address seems to be straightforward and we can quickly check that it is recognised by Targeo map and Valid. Response address accuracy also seems fine. However, this street number is situated in dense urban area in one building divided into separate street numbers. In such case only correct rooftop would be considered correct. A closer look on street number in Targeo map shows that pin points to number 38. As per section 6.2 it is rated Wrong as there is one more number of 36 separating us from correct rooftop.

Example 2:

.

Query: Grudzieniec 92A, 60-601 Poznań

Response Address: Grudzieniec 92, 60-601 Poznań

Query Address: Valid

Address Accuracy: Incorrect (street number)

Pin Accuracy: Next Door (52.419601539400894, 16.90141182703527)

Query address is a street address with a letter suffix. Response address misses this distinction. As per Targeo maps address is Valid and 92A clearly exists. As it is not the requested street number, we rate address accuracy as incorrect. Pin points to number 92 but that’s not correct. Pin should reflect the queried address therefore it should be pointing to 92A, which is in fact the next building. In this case Pin is rated Next Door.

 

3.Address Accuracy Mistakes

Always carefully check the response address for polish special characters occurrence. This detail is often missed. All address components should be correctly formatted and grammatically proper.

Example 1:

.

Query: Swierkowki 5, 64-605

Response Address: Świerkówki 5, 64-605, Świerkowki

Query Address: Valid

Address Accuracy: Incorrect (Locality)

Pin Accuracy: Perfect (52.57936169775073, 16.833900999485035)

User looks for some rural address. Official resources check (Targeo, Geoportal) shows this is a unique and existing address therefore a Valid address. Response address seems fine at a first glance but the locality component misses the polish special character “ó”. As per GL 7.3.4 if a locality component is misspelled it is rated Incorrect – Locality.

.

.

Example 2:

.

Query: Oporówko 16, 64-120

Response Address: Oporówko 16, 64-120, Krzemieniewo

Query Address: Valid

Address Accuracy: Incorrect (Locality)

Pin Accuracy: Perfect (51.817961516064685, 16.827734749711354)

Queried address after check in Targeo map is Valid. However, the response address has some components that were not present in the query address. Response result contains a commune instead of locality. As per CSGL4.7 commune is not a part of an official address. Correct address accuracy rating is Incorrect – Locality, as it should be Oporówko.

4.Comments

Always include a comment explaining the reason for rating. In the comment, please indicate why the address query is valid or invalid. If you rated the query address as Reasonable, your comment should be specific and indicate which rules contained in the guidelines the address meets and which it violates. Leave detailed comments and links to sources if you think the reasons for your pin or response address rating may not be obvious, if the rating was difficult to determine, or if an unusual amount of research was required to make the rating.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post