E.g. a layer of CPS attendance boundaries for elementary or high schools. This was suggested by Val Michelman during an informal "Show and Tell" with a few Consortium folks.

Specifically, under "Intro", the quotes around Jump To are directed (i.e. left and right) double quotes, and around Run are up-and-down double quotes.

Tasks are:

1. remove SE from PARCC input file (since we have a population measure, and SE = 0);
2. for NA values in PARCC, replace n and w and r with 0s (to work with existing calculation types)
3. fit violent crime calculations into the standard framework, e.g. witl n, w and r field columns

Add logic to display only estimate if the lower bound and upper bound range are the same

Review content of methodology section

Prevent wrap around on display of estimates

I.e., if the calculated range is -10 to 20, should make it 0 to 20 instead.

Per Dave McQuown, in an e-mail sent to Nick and Paul on 6/12/2017:

Yes, this is definitely a very obnoxious problem that I have had to deal with many times before. The summary is that we need to find some kind of shapefile that has a better shoreline (the community areas shapefile from the City of Chicago data portal would be a good candidate) and use this as a means of cutting the census tract geometry. Last time I actually did this was a few years ago and in ArcGIS. This could be done using open source tools using database tables instead of ArcGIS shapefiles as well, and we ought to do so, but I don’t know exactly how off the top of my head at the moment (but it is going to be essentially the same as the steps below, but functions might have different names or need to be run as SQL statements instead of through a GUI). In ArcGIS desktop I have done this generally as follows, but there would inevitably be some fine details to work out through trial and error.

1. Load the Chicago community area shapefile into ArcGIS.
2. Use the union function to combine the Census Tracts layer and Community area layer. The union function takes two or more layers and returns a layer containing all boundaries from the input layers. So for all the tracts that stick out further than the community area boundary, they would get split into two shapes, one inside the CCA boundary and one outside.
3. Editing the resulting shape manually, delete all the bits of tracts that stick out past the CCA boundary.
4. Dissolve the resulting layer on the Census Tract FIPs field. When you do the union above, you will also get some undesirable results, like the tracts out by OHare will get all crazy since the Census Tracts and legal city border are much different out there. Dissolving on Tract FIPS basically gets you back to the original tract shape, but without the bits of tracts in the lake you deleted in the previous step.

Let me know if you would like more explanation of some of the geoprocessing functions like union or dissolve I mention above. And I’m happy to help do this as a “clean” tract file is something we need to have on hand here regardless – I’m working on making a database of shapes that we can all share and would like to include something like this.

D