Skip lines, not lunch

Version 2.0 offers the following updates, bug fixes, and features:

• Map can be re-centered based on Search Box = search for address or establishment name
• Restaurants provided in the "Report Wait Times" feature are the five closest to the center of the map
• 12,000 test data reports over 20 restaurants generated for demonstration purposes
• NomNow2.0 integrates with Tropo API. This calls a restaurant, records a response, transcribes the response, parses the wait time integer, and stores the information as a new report in the database.
• User can view a popup graph of historical wait times for any given hour for an individual restaurant. An algorithm parses when past wait times were reported and averages the reported times for each hour. Highcharts was used to generate the graph based on these results.

Adam Guerra [Adam's Github profile] (https://github.com/adamlg)

Karen Lewis Karen's Github profile

Josh Benson Josh's Github profile

Stephanie Foskitt Stephanie's Github profile

View the deployed app

Built by Phil Dornfeld, Pat Dalberg, Vishal Atmakuri, and Ben Johnson

1. Concept
2. Stack
3. Ideas for Extension

NomNow2.0 is a web application for crowdsourcing wait times at restaurants. When at a restaurant, anyone can submit a wait time, and all the reported wait times are pooled and used to create a map which shows the average reported wait time for each restaurant.

Our schema has two tables: restaurants and reports. They look like this:

The server is comprised of two files.

This is where the express server is created. It serves up static files at '/' and accepts GET and POST requests at '/wait'.

This is where the functions that have the SQL queries live (we are not using an ORM). These functions are called from app.js.

Angular is taking care of the routes. When someone tries to report a wait, the client asks them for their location, and then it uses that to find restaurants where they may be.

We used the angular-bootstrap library to create the modal.

We used the Google Maps API to generate the map and the markers, and we used the Google Places libary to get the info about the places.

Write a cron job that prunes stale data. The data will be relevant only for an hour or two.

Make the client auto-refresh when someone else submits data.

Ideas: OpenTable, Yelp, FourSquare

Right now by default we serve up every report in the database when we create a map. Use the GPS of the client asking and dynamically serve up a map of only that city.

Not for the faint of heart.