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

Locality not populated #54

Open
Donoss-zz opened this issue Mar 18, 2015 · 3 comments
Open

Locality not populated #54

Donoss-zz opened this issue Mar 18, 2015 · 3 comments

Comments

@Donoss-zz
Copy link

Hi, I've noticed that most of the addresses within my own locality do not have the locality populated. Is there a mechanism by which we can update these and resubmit in bulk?

Many thanks

Andy

@giacecco giacecco self-assigned this Mar 19, 2015
@giacecco
Copy link
Contributor

Hi Andy,
For the time being our parser is dropping the locality names where the address is unambiguous even without using it, typically when a postcode is specified. Other users like you have challenged this choice, too. What do you reckon?

@Donoss-zz
Copy link
Author

Gianfranco,

I see it as being an issue for small businesses and business where different people are doing order entry and service delivery. If I look at ‘CHURCH STREET’ in ‘DONCASTER’ I have postcodes in DN3, DN5, DN9, DN10 and DN12. For the smaller business, especially mobile who needs to find their destination e.g. plumbers, dog groomers, cleaners, carers etc., with the LOCALITY known they can start to head towards a destination, without it they will need to look it up or have satnav. I believe not having the locality will put some potential users of these data off.

Hope this helps.

Many thanks

Andy

@giacecco
Copy link
Contributor

I personally feel, too, that in later releases localities should be preserved, and not only!

With @MurrayData for example we talked often about the importance of 'vernacular' localities: localities that you won't even find in our "reference tables" but that are very meaningful to the people there.

@peterkwells you don't need a new entry in the roadmap: this is part of the work we need to do on revising the address model OpenAddressesUK/roadmap#66 . We just need to add it there as one of the requirements to address.

@giacecco giacecco removed their assignment Mar 30, 2015
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

2 participants