Redistricting App Change

Quick update on the app. Because so many of you have been using the app (and it was discussed on the DailyKos front page last weekend) and because the test data for NY is so large, we’ve blown thru my bandwidth quota for the month. I’ve upped it a couple of times, and we’re over that, too. So far it seems the site still works, thanks to the grace of my host.

But, I’ve made a change so that once you load the date for a state, the app saves it on your machine in the same place as the drf.xml files. If you then refresh the browser and reload the state, it grabs the data from your machine, saving a lot of bandwidth and…bonus…making it a lot faster to load.

I’ve tested this with NY, NV and a couple of other states (and with combinations of voting districts and block groups) and it seems to work. Please let me know if you have problems.

(Also, I know about the Indiana voting district problem and will get to that soon.)

Thanks.

30 thoughts on “Redistricting App Change”

  1. I tried it with New York and California, and both work really well. It takes only a few seconds for each one to load now.

  2.  Thanks for updating the app and happy new year! I’m wondering what you plan to add or change on the app in the upcoming future and when.

  7. I’ve discovered that Silverlight (or the way I’m using it) is no longer allowing you (the user) to increase the quota. This is what gs is running into and probably others of you already or soon you will (if you play with different states). When this happens, it pretty bad, first making certain states unusable, by leaving 0 length files, and then making the entire app unusable. I spent a bunch of time yesterday on this, but then we had a party at our house last night, so I put it down for that. I’m back at it again this morning and will either get a proper fix out or back out the change I put in on Thursday.

    Thanks for your patience.

Comments are closed.