Accuracy Issues for Release 0.3 - Githubissues

thinkingmachines / linksight-2018

LinkSight is a web app for applying the Philippine Standard Geographic Code to messy and misspelled barangay, municipality, city, and province names.

https://linksight.thinkingmachin.es

GNU General Public License v3.0

11 stars 1 forks source link

Accuracy Issues for Release 0.3 #151

Closed piafaustino closed 6 years ago

piafaustino commented 6 years ago

[x] Sometimes, LinkSight gives the same accuracy scores to two possible matches, of which one is clearly more correct. Examples:

Poblacion and Santo Niño have the same score for Santo Niño (Jabonga), even though the latter should clearly have a higher score:

screen shot 2018-08-21 at 1 24 56 pm

Poblacion 1 and Poblacion 10 have the same score for Poblacion 10 (Buenavista) although the latter should clearly have a higher score:

screen shot 2018-08-21 at 1 23 48 pm

[x] Bislig City and Mauing City were not identified correctly yet classified as "Exact Matches" in this test dataset.
[x] The following barangays were misidentified as "Exact Matches" when processing happy-path-test-file yet the final exported file had totally incorrect matches.

screen shot 2018-08-22 at 4 25 36 pm

Osmena (La Paz), La Paz, Agusan del Sur
Chanarian, Basco, Batanes
Pila, San Pascual, Batangas
Poblacion 1, Taal, Batangas

Matched Dataset -NCR Listahanan

Exact matches that should not have been:

[x] Cembo and South Cembo are different barangays
[x] Tanza and Tanza 1 are different barangays

Matched Dataset -PSA Education

[x] No match found for Cotabato City when dataset put Maguindanao as the province. But in the PSGC Reference, Cotabato City does not have a province.

piafaustino commented 6 years ago

Most of these are addressed by updated matching algorithm. Closing for now