[x] When the input data has a city/municipality misplaced in the Barangay column, LinkSight can't find the correct result. Feedback from Reg Onglao: "I used one of my old DSWD files, and found multiple cases wherein encoders put a "city/municipality" in the "barangay" column instead (I imagine this'd be a usual error for govt agencies). I'm wondering if your algo can check these human error cases if there's a higher-accuracy match by moving one admin level up (vs a low-accuracy match within same admin level)? Here's an example below. This should have been matched to Tabaco City, Albay but had bad results since was forced to be a Barangay:" (UPDATE: Moving to Release 0.3)
[x] When the input data has the wrong province attached to a city or municipality, LinkSight fails to recommend the correct city or municipality among the options. Take for example what happens when Butuan City is misplaced
DSWD data tested by Reg Onglao reg-onglao-testfiles.zip
[x] When the input data has a city/municipality misplaced in the Barangay column, LinkSight can't find the correct result. Feedback from Reg Onglao: "I used one of my old DSWD files, and found multiple cases wherein encoders put a "city/municipality" in the "barangay" column instead (I imagine this'd be a usual error for govt agencies). I'm wondering if your algo can check these human error cases if there's a higher-accuracy match by moving one admin level up (vs a low-accuracy match within same admin level)? Here's an example below. This should have been matched to Tabaco City, Albay but had bad results since was forced to be a Barangay:" (UPDATE: Moving to Release 0.3)
[x] When the input data has the wrong province attached to a city or municipality, LinkSight fails to recommend the correct city or municipality among the options. Take for example what happens when Butuan City is misplaced