code-for-syracuse / without81 Goto Github PK

Mark,

I noticed two typos while reviewing the site.

On the About page, in The arguments, in the Dig row, in the Against column, there's an instance of "disrutive" that should probably read "disruptive."

On the Contact page, there's an instance of "wwant" that should probably be "want."

Cool site; this is a classic Mark Headd project. I'm looking forward to seeing more work from the Upstate Data Project.

Dan

Change the default route to make the destination address in Downtown Syracuse.

Might be nice to have the option to let users route their travels using public transit to see if this option is favorable to them.

Make difference in time / distance (fuel?) more prominent. Add to top of page?

When a user calculates travel directions that avoid 81 through Syracuse, provide the option to email the map and route narrative to the user for later use.

Clicking either the 'Home' link or the site name in the top menu bar should refresh the maps and remove any existing routes.

Need about page describing goal of the app and discussion it in context of broader 81 overhaul project.

Need contact details for questions, inquiries.

Might make it easier for users if the address entry fields used an autocomplete service, to ensure proper address entry for route calculation.

A segment of 81 S just pass the 690 interchange is not being avoided in calculated routes.

When doing multiple route lookups, the route narrative and duration inforamtion is not cleared prior to the new route details being appended to the content div.

This site uses the MapQuest Directions API and a set of LinkIds for I-81 through Downtown Syracuse to generate directions that both use and avoid the highway when traveling through the city. The process of identifying the correct linkIds is somewhat tedious and admittedly imperfect.

Manually identifying roadway segments and using the MapQuest API to determine the correct LinkIds to include in the app is the method that has been used to date.

If there are issues reported with certain directions not working properly, it may just require an update to the LinkIds.

One of the fields returned with the route information is fuel used (in gallons I think). Is displaying this field useful if the difference between routes is just a few minutes?

To support further analysis down the road, need to log the origin and destination locations and the calculate routes, distances, etc.

Need to add a statement about data collection and privacy to about page?

When rendering the route narrative and duration, avoid writing out the raw HTML and use a precompiled template. Handlebars, yo.

I-81 would be replaced between about the SU exits and the 690 interchange. When I search directions from within Syracuse, many still put me onto I-81, which I think is in error.