You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @MurrayData , Jeni remembers that one of the common-ETL sources of data you selected was sufficient to build a street name reference table, too, to go together with the postcode, city and locality reference tables.
I remember discussing this subject over the phone with you last Weds, but I also understood then that, differently from the other address elements, we always need some degree of inference to produce street names.
Am I wrong? This issue in GitHub is just a reminder so that we talk about it when you are here on Thu. Thanks.
G.
The text was updated successfully, but these errors were encountered:
No the OS locator (documented) contains this hierarchy but it is based on administrative localities rather than physical/vernacular. Last week we discussed additional sources including ONS named places and an additional dataset from Strategi. I wrote the script for Strategi and it is on Github. I didn't have time to finish the documentation before I went away.
Hi @MurrayData , Jeni remembers that one of the common-ETL sources of data you selected was sufficient to build a street name reference table, too, to go together with the postcode, city and locality reference tables.
I remember discussing this subject over the phone with you last Weds, but I also understood then that, differently from the other address elements, we always need some degree of inference to produce street names.
Am I wrong? This issue in GitHub is just a reminder so that we talk about it when you are here on Thu. Thanks.
G.
The text was updated successfully, but these errors were encountered: