5. During development:
You can get Census boundaries by sending GeoJSON in the
request? THAT’s going to save us time.
At the end of the session:
We spent most of our time on the UI because were able to
easily use [this functionality] to really quickly draw a custom
boundary and pull down the Census boundaries and data we
need to display on our map.
Andrew Turner: Github Followers = 200 + 1
7. It was really nice that you guys abstracted the bringing
together of geographic [boundaries] and the Census
variables. Trying to make these calls separately and then put
them together is probably not the most efficient way of doing
things... [this way] it was easy.
Daniel Fenton, ESRI
8. It was really nice that you guys abstracted the bringing together of geographic
[boundaries] and the Census variables. Trying to make these calls separately
and then put them together is probably not the most efficient way of doing
things... [this way] it was easy.
10. Daniel ?
The examples and interactive documentation really helped us get
productive quickly. Thank you for the help.
11. You can get Census boundaries by sending GeoJSON in the request?
THAT’s going to save us time. We spent most of our time on the UI
because were able to easily use [this functionality] to really quickly draw a
custom boundary and pull down the Census boundaries and data we need
to display on our map.
13. Brian Brotsos, USDA
I really like the modularity of the SDK. With the
modular architecture, in one hour, I was
successfully able to take your code and create a
module for a USDA API.
14. I really like the modularity of the SDK. With the modular
architecture, in one hour, I was successfully able to take
your code and create a module for a USDA API.
15. ● Move examples to github.io pages
● Enforce a consistent naming convention
● More aliases ACS aliases to correct (arcGis)
● List of features (consider making a list of links with teasers, but each having it's own page with examples, tutorial,
etc.) .IO Pages
● Variable search engine (still think the Search functionality would be cool here), maybe pull down the Census Reporter
functionality
● Tutorials for implementing each feature / module (consider allowing users/pull requests to add feature/modules to the
list of features)
● Query Builder
● Custom variable transformations, ala' F.R.E.D.
● Document the level of detail for the response objects as well as the documentation for the request objects
● D3 example (charts)
● Choropleth Mapping tutorial/example
● Make JSON response consistent across geographic levels (i.e., different levels currently are structured differently)
even if it means returning empty fields
● Geocoding functionality by sending in city, state and getting back a geojson boundary
● Tutorial for pulling point data by Census Boundary
REQUESTS (No particular order):
Editor's Notes
How do we do this at the Census Bureau?
http://lithespeed.com/healthcare-gov-one-year-later/
How do we do this at the Census Bureau?
http://lithespeed.com/healthcare-gov-one-year-later/
Aligned
SWAT team (of ninjas)
Highest level support (John and Nancy)
Start with Brian?
Include Jeff Press from DoC?
Move quickly
In question
initial size of SWAT team
Number of initial projects (1 or more?)
bootcamp (6 month trial period in CAT)
Weekly meetings (logistics),
Digital Services group as bureaucracy reducing team that reports to Nancy et or John directly (Explicit blessing of relationship with:
ACQ
Legal / Policy
Usability lab?
Comms
OIS (and others in IT)
ninja team
How much agile/lean in initial pitch
