Closed JohnTigue closed 9 years ago
I'll commit the TopoJSON files to this project Tuesday or Wednesday. I think I want to move some files around in the repo first. Need to noodle that for a wee bit.
Cool!
Noted Great, I'm working on using leaflet with Angular.js. I hope to see you both at the code for Seattle meetup tomorrow.
I'm not going to make that, physically. Is there a IRC/chat/slack/smoke-signals way to join remotely?
Do you have a Skype account? I'm more than willing to keep you updated that way.
John -- Yes, there is a #codeforseattle channel on freenode.
Thanks both. I'll be on #codeforseattle during the meetup
Another M-Lab data client project that Ritzo, M-Lab PM, pointed to for non hex shapes:
http://hyperiontest.gr/
See also #9
The TopoJSON has landed: https://github.com/codeforseattle/seanetmap/blob/master/static/geojson/seattle-districts.json
There is code coming from M-Lab, probably this week that has something to do with clustering by polygon. From a Ritzo-Tigue email:
- M-Lab developers are adding support to the example map for binning data by a polygon file
Excellent! Please point me at that and I will merge it with the TopoJSON files I generated of the Seattle City Council Districts as per issue #1: https://github.com/codeforseattle/seanetmap/issues/1
This will also get moving early next week on our end. I'm cc'ing Nathan Kinkade and Georgia Bullen on this, since they're leading the effort on that here. Nathan may have started on this today, but I'm not certain. At the very least we'll have it rolled in next week.
So, the above two together should make for seeing test results by Seattle City Council District.
Can @nkinkade @georgiamoon get added to the collaborators group?
I've already written the initial code to allow bq2geojson to accept arbitrary polygon files (in GeoJSON format) rather than using the default of creating hexagons. I haven't committed the changes yet, but will do so today after cleaning it all up a little and then integrating the changes into the prototype front-end.
Another feature I intend to implement in bq2geoson is that the Node.js script will output TopoJSON instead of GeoJSON, which should reduce the file sizes by >50%, greatly helping the speed at which a browser can load the files (especially when animating the map). It will then be converted back to GeoJSON on the client side using leaflet-omnivoire. This is based on the assumption (perhaps false) that the processing cost of converting the file type client-side will be less than the network cost of a larger polygon file, in terms of UX.
@critzo Just tried to add @nkinkade @georgiamoon. Seems I do not not have that privilege.
@willscott I'm assigning this to you as a "sub-issue." When the folks are added kick this issue back to me, please.
FYI, #25 seems to be becoming the bq2geojson hub issue.
Collaborators added
Currently the test results are being aggregated by City Council District maps. Census tracks to come.
Moving forward this is being tracked as #40 CityReq3 (User views the broadband map), which states:
Map shows an overlay of census tracts over the City, with each tract color-coded by the state of broadband experience in the tract as defined in the summary section.
Also see #37 CityReq2 (Data is summarized by census tract)
In the prototype from M-Lab, the test results are clustered into hexes tiling the city.
There are requirements (CityReq2 and CityReq3.1 call for Census block and/or Census track) to aggregate test results according to political boundaries.
Another layer (not in the requirements) could be aggregated results by Seattle City Council District (which was actually the first political boundary the work was preformed on).
First step was (well, actually GeoJSON should have been first, but, hey) to get TopoJSON files for the council districts. Closest that we found were shapefiles. Converting them to TopoJSON turned out to be a bit of a hassle but it's done now. See my write up:
https://github.com/JohnTigue/nodeio/tree/master/data/generating-topojson