codeforkansascity / addressapi-website

Public website for the Address-API project, to communicate the data that is avaliable, and how to access it.

MIT License

3 stars 1 forks source link

Brainstorm solutions #5

Open zmon opened 8 years ago

zmon commented 8 years ago

Brainstorm Solutions

[ ] Using a timer, take 5 minutes to write down as many rough ideas on sticky notes as you can.
[ ] Go around as a team and put your sticky notes on a wall as you say what you wrote.
[ ] Group similar ideas together.

When you're finished, you're ready to move on to creating paper prototypes!

screen shot 2016-01-28 at 4 25 30 pm

zmon commented 8 years ago

Two sites?

Consumer Site - a site that sells the project and gets people using it. See https://github.com/codeforkansascity/address-api/issues/79
- list of data sets that are added to the Address API.
- display of where the Address API data set came from and when it was created.
- Provide a link that allows consumers to see information about datasets
- Example Sites
- Type ahead
- Address Lookup
- Map of counties
API Site - the REST endpoint

Address Storage

An interesting article on storing addresses. http://stackoverflow.com/questions/7639637/sql-database-design-best-practice-addresses

Other considerations

Do we want to handle addresses that merge into one and/or addresses that split into more than one.
How handle
- a large number of addresses being returned? Paging? CSV download only?
- Address Mergers
- identical addresses that are in two different cities like 300 main street in Kansas City and Parkville, currently we must specify the city
- indicating the source of the data, for example lat, lng comes from several sources
- freshness of the data, when was it last updated? Should this be done at the field level, ie if an address has its lat, lng changes it should be noted for the addresses changed, not by the load.