sfbrigade / adopt-a-drain Goto Github PK

[] Copy legal from Oakland
[] Copy any legal I can find from SF programs
[] Send to Jean

Adopta's Things table has a city_id field, which I'm assuming is to store an external identifier. 2 fields looked like candidates, and I have hunch which one, but wanted to clarify.

From a sample record:

"DPW_Node_ID":"22337"
or
"PUC_Maximo_Asset_ID":"N-36453"

cc @jasonlally, @hackajesse

@therebelrobot if I get her to come to a hack night, are you down? She's our POC at the PUC. :)

Once the PUC has tools available for lending, create a way for adopters to know how to access the tools.

Need: on mobile, the sidebar is difficult to use. Can we redesign to make it easier on mobile?

From @hackajesse on October 21, 2015 17:5

• schedule call w/data contact at PUC
• [] document dataset
• [] update inventory for PUC
• [] Publish dataset manually
• [] Mark inventoried dataset as published

Copied from original issue: sfbrigade/adopt-a-drain.old#8

Likely in a modal w/the Ts & Cs.

Includes information on how to clean your drain, etc.

From @hackajesse on October 21, 2015 17:5

Copied from original issue: sfbrigade/adopt-a-drain.old#9

Likely needs the confirmation of a drain being cleared before implementation.
Also needs more PUC involvement / funding.

Ask Jean to ask John Seagrave

cc: @sfbrigade/website-tools-core-team

So I was chatting with @jasonlally about the API that will be released soon for the drains (soonest tomorrow, latest end of this week), and he directed me to a currently published API that has a similar structure: http://dev.socrata.com/foundry/#/data.sfgov.org/cuks-n6tp

We'll want to see where in the app the api is being consumed, and see what will be needed to tie it into the new API.

Once [the API is public], you can grab a geojson feed of the points OR grab the csv or json with lat and long as fields...

... So you can expect a coordinate pair, the weird thing is geojson flips lat and long
Otherwise it's standard among any other geojson structure

From @hackajesse on October 21, 2015 17:2

Based on the backgrounding, we need to figure out which fork is best to start from and where it will go

Copied from original issue: sfbrigade/adopt-a-drain.old#3

They're too close (green vs blue)
Related to accessibility (color blindness??)

• SF PUC
• DPW
• Mayor's office
• ask Jean for others to be included

Method: Email, SMS
Frequency: upon signup, few days before a storm, day of the storm, confirmation that things are clean(?)

From @hackajesse on October 21, 2015 17:3

Copied from original issue: sfbrigade/adopt-a-drain.old#6

Highlight those areas on the map
Emphasize the need for folks to adopt those drains first

For example, if the SFPUC or another org owns/manages a drain, that drain should be claimed (either manually or permanently or something) by that org. Convey that clearly to the public when wanting to adopt a drain.

Could be as simple as editing the modal or as complex as a landing page. Will definitely require multiple versions.

From @hackajesse on October 21, 2015 17:3

Copied from original issue: sfbrigade/adopt-a-drain.old#5

favicon is currently a fire hydrant

touch the map, keyboard appears.

for drains that they can't clear or that they see need clearing or an already flooded area.

Via SMS or the app please (no email)? :)

For clarity of data, each row should be its own drain, not as per status quo, which is each row represents a user, who can have multiple drains.

311 app.
Where to put this in the app?

• confirmation email
• expectations on homepage

[] Ask user for twitter handle
[] Tweet from the PUC handle 30 minutes after the adoption happens (so the user has time to name the drain).
[] Use this copy: TBD

From @hackajesse on October 21, 2015 17:4

Copied from original issue: sfbrigade/adopt-a-drain.old#7

• Does the data differentiate between the two types of drains? (@jasonlally @afomi )
• If it does, create issue to design different icons, legend, and write copy explaining the difference (@jasonlally)

This determines our deadline or whether we need to set up a separate announcement/PSA from the Mayor.

@jasonlally please coordinate with Jean and update this issue w/status

From Jean

I was looking at the UI scaffolding used to layout the map and sidebar and it's simple enough, but uses table and table-cell layouts in a manner that makes it hard to make this friendly on mobile.

Without knowing the exact direction yet, it's simple enough to modernize the layout so it's a bit more flexible and mobile-friendly and uses Bootstrap 3 and it's dependencies.

This is just house cleaning to clear the way for more robust UI and UX changes.

From @hackajesse on October 21, 2015 16:59

Copied from original issue: sfbrigade/adopt-a-drain.old#2

http://sfdpw.org/index.aspx?page=1229

Hi @hackajesse, this project requires 21,000+ records to be stored. Heroku's free tier maxes out at 10,000.

Is there a SF Brigade account that could host this and manage the payment? Or any other alternative 😄

V1: Thank people and say that we had X# new adoptions as a result of the app
V2 (post user confirmation they cleaned their drain): Thank people and share how many people cleaned their drains
VN (once we have data from DPW? on how much less flooding occurred during the most recent event when compared to other similar events w/out adoptadrain): Thank people, share how many people cleaned their drains, and share how much less flooding there was and cost savings as a result.

From @hackajesse on October 21, 2015 16:57

• Connect with folks who built it
• Reach out to Spike about lessons learned, share list of questions/concerns from PUC
• Review documentation

Copied from original issue: sfbrigade/adopt-a-drain.old#1

From @hackajesse on October 21, 2015 17:3

Copied from original issue: sfbrigade/adopt-a-drain.old#4

Have James Tyack go through it. Idk his github, but he's often at hacknight. I'm sure he'd be game to go through this and/or make suggestions for things we can look out for.