Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

behaviour when postcode and housenumber don't match #12

Open
Jeroen-GroeneBij opened this issue Apr 1, 2020 · 0 comments
Open

behaviour when postcode and housenumber don't match #12

Jeroen-GroeneBij opened this issue Apr 1, 2020 · 0 comments

Comments

@Jeroen-GroeneBij
Copy link

Hi,

Wonderful plugin, very useful in my line of work.

It did notice some behaviour that I consider to be unwanted.
When geoding using a csv file consisting of huisnummer, postcode and woonplaats, it does not give an error when there is a mismatch between postcode and huisnummer.
Instead, it geocodes a (random?) location within that postcode and tells me all addresses where successfully geocoded.

Use attached csv for testing.
testgeocode.zip

The postcode 3533VJ only has 30 up to 58 as huisnummer.
When using even numbers below 30, it will geocode a different location on 3533VJ.

This has two implications:
I am not informed about non-existing combinations, which otherwise would have pointed me to wrong data, which I could then adjust.
And I am getting false data in my point layer: the plugin algorithm is choosing a point on it's own, without informing me.

Is there any way to fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant