Closed santheo closed 11 years ago
How about passing a ward_2015
parameter, same as ward_2013
, and that returns all transitions that are moving to the given 2015 ward?
For /wards/transitions.json
, the only parameter is ward
. That should be enough to return the transitions leaving as well as the ones entering. Just please split them up into different sections of the response.
My bad, confused params with db columns.
Do you still need the ability to return all transition areas at once? It will simplify this change if I can omit that.
In other words: I want to make "ward" a required parameter.
I'm not using the all-transitions-at-once view, so you can kill it.
The only place I would need all Transitions at once that is on the TTC endpoint, for that theoretical Transitions page, which DXO said we could postpone.
Re-opening and assigning to me. Still need to write code to add the shapes to the map.
To be clear, I definitely said that we could postpone. I consider this to be a "we ran out of time and decided to be lame" kind of feature delay.
It is what it is-- no biggie. I just want to be clear that if anyone gets any midnight magic, it would be nice to launch this...
Incoming blobs are now visible. See any ward page. http://chicagoworksforyou.com/ward/47/#/
Does the color scheme work for you?
@danxoneil wrote:
This wouldn't be hard for me to add to the map, but it's up to @cgansen if he can add it to the API. (Preferably at the same endpoint.) Chris?