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

Define Dataset: Address Points (Geospatial) #35

Open
emily878 opened this issue Mar 6, 2015 · 5 comments
Open

Define Dataset: Address Points (Geospatial) #35

emily878 opened this issue Mar 6, 2015 · 5 comments

Comments

@emily878
Copy link
Contributor

emily878 commented Mar 6, 2015

Define the essential substantive elements of the core Address Points dataset. What are the components that it must minimally include? Do we have a dataset that we could hold up as a model?

@waldoj
Copy link
Contributor

waldoj commented Mar 7, 2015

@iandees, is OpenAddress' list of attribute tags a good reference for the minimal components of an address points dataset?

@iandees
Copy link

iandees commented Mar 7, 2015

Yep, bare minimum is house number and street name. Adding city and postcode makes it more useful. Even better would be to have street name split into prefix, road name, suffix, and road type.

@waldoj
Copy link
Contributor

waldoj commented Mar 7, 2015

I hadn't realized that the minimum could be so minimal. Thanks, Ian!

@iandees
Copy link

iandees commented Mar 7, 2015

The other fields can be backfilled/estimated from other datasets, so it's a whole lot more work, but still useful.

@waldoj
Copy link
Contributor

waldoj commented Mar 23, 2015

So, to be explicit, here's our minimum viable dataset:

  • address: numeric component
  • address: street name
  • coordinates

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

3 participants