Add link to download CB boundary shapefile (or similar) directly from Community District Profiles Page

[mtreg]

This is a great platform with so much useful information.

One thing that would be useful for desktop GIS users is a link to the Bytes of the Big Apple with the source shapefile for Community District boundaries, or even just having a link to directly download the original zipped shapefile from the Bytes of the Big Apple page in the 'Downloads' section. This would just saves the effort of finding the boundary dataset for new users and such.

Alternatively, given the indicators for all Community Districts can be downloaded from the 'Download the Data' portion of the page, perhaps have an option to download as geojson/shapefile/similar in which the result would have both the geometry and indicator data.

Thanks!

[allthesignals]

There are some shapefile downloads here: https://communityprofiles.planning.nyc.gov/queens/1#resources

Is this what you mean?

[mtreg]

Thanks @allthesignals for following up on this. I'm not seeing any option to download the shapefiles of the CD boundaries at that link, or even a link to that dataset on Bytes of the Big Apple or NYC Open Data. But let me know if I'm missing it. (The only shapefiles I'm seeing are for FacDB and PLUTO)

I could envision a few options:

• A link to download the CD boundaries directly from section previously linked - this would be something that could easily be joined to the Indicators Data;
• A link to the Bytes of the Big Apple or NYC Open Data page with the spatial data for CD boundaries;
• The best option in my opinion - An option to download the Indicators data in a spatial format, rather than just a CSV, such that it's a file with the geometries and the indicators all in one.
  • Shapefile probably wouldn't do well with the long column names for some indicators, but geojson, gpkg, or similar would work.

In my work I sometimes fetch the spatial data, and then the indicators csv data, and join them for analyses or maps, so it would be nice to just reduce the steps folks need to go through to get a more GIS-ready product

[allthesignals]

@mtreg got it, thank you for clarifying, i really appreciate it.

Next time we have room for improvements, we'll know exactly how to address this :) I think the last option would be very easy to implement. Let me see what I can do.