Format of returned information

[nickidlugash]

@WABA-Comms In your teams's initial project outline, you suggested that after a user draws a line to indicate where they would want a new bike lane, the tool would return information about that corridor which would allow a user to say something like:

This protected bike lane would directly connect more than 2,000 residents to 23 miles of low stress bike lanes and trails. There have been 23 pedestrian crashes and 7 bike crashes along this corridor since 2015. Four percent of the residents in this neighborhood already bike to work.

• Can you say a bit more as to what format(s) of displaying this returned information you think might be most helpful? A paragraph (similar to above)? A table of info? Visualized on the map (e.g. crashes indicated as clickable points)?

• Is it is necessary to return a text description of the corridor's location?

• Should this information be packaged in a "ready-to-use" way, and if so how? E.g. will a user want to screenshot, print, or save the view, copy and paste the text, or otherwise directly use the output in their own documentation?

[WABA-Comms]

I think a table makes the most sense. I wouldn't say it needs to be print ready or anything - a "copy table to clipboard" would probably by the most useful option. A screenshot of the line on the map and the table is would be the second most useful. Or, if there's a way to generate a link to that particular line, that would be excellent too. I don't have a great sense of how much complexity those different options add to the back end.

A text description of the street is helpful but not necessary.

Thanks!

Colin Browne Communications Coordinator Washington Area Bicyclist Association colinbrowne@waba.org (202) 518-0524 x201 waba.org

On Tue, Dec 5, 2017 at 1:14 PM, Nicki Dlugash notifications@github.com wrote:

@WABA-Comms https://github.com/waba-comms In your teams's initial project outline, you suggested that after a user draws a line to indicate where they would want a new bike lane, the tool would return information about that corridor which would allow a user to say something like:

This protected bike lane would directly connect more than 2,000 residents to 23 miles of low stress bike lanes and trails. There have been 23 pedestrian crashes and 7 bike crashes along this corridor since 2015. Four percent of the residents in this neighborhood already bike to work.

-

Can you say a bit more as to what format(s) of displaying this returned information you think might be most helpful? A paragraph (similar to above)? A table of info? Visualized on the map (e.g. crashes indicated as clickable points)?

Is it is necessary to return a text description of the corridor's location?

Should this information be packaged in a "ready-to-use" way, and if so how? E.g. will a user want to screenshot, print, or save the view, copy and paste the text, or otherwise directly use the output in their own documentation?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mapbox/waba-add-a-bike-lane/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AT0U7ewP2FgUeHeEqlz37vuuK96c-EuGks5s9YgOgaJpZM4Q2u2w .

[nickidlugash]

@WABA-Comms thanks for the written and in-person feedback on this! Capturing from our meeting:

• A table of info that can be copied to clipboard should be doable
• A permalink should be doable (we'll need to figure out the best way to save the drawn geometry – maybe as a data source, maybe as part of the URL?)

BONUS – Interact w/ each item to see a visualization on the map:

• Crashes and moving violations: incidents represented as individual dots
• Population: census block polygons
• Connected bike infrastructure: display connected network and zoom/pan to fit bounds of network