-
Notifications
You must be signed in to change notification settings - Fork 13
Feature request: new columns indicating lot intersection of supporting DCP layers #55
Comments
@allthesignals Flagging that Are you also computing the zoning district / commercial overlay information on the fly as well? |
I think so! |
@baolingz remove floodplain_firm2007_flag,floodplain_pfirm2015_flag,e_designations_flag from output to avoid repetition, since these flags are already in PLUTO |
@baolingz rename sql queries so that they're prefixed with zola_ |
@baolingz Move pluto_zola_export.sql into 05_export.sh |
@AmandaDoyle I just updated the scripts and output. |
Stale issue message |
Thanks everyone for working so hard on this1 :) |
Hi all, how should I use these new flags? I know there are flags for the current Pluto: edesignum, firm07_flag, pfirm15_flag. They're slightly cut off in Carto so they'll look like |
ZoLa lot detail views show users which layers the lot intersects with, including floodplain information, among other details. The app does this by performing spatial intersection queries on-the-fly. This is resource-intensive and inefficient.
It would help if PLUTO could include new columns - or include a supporting data product - that joined the spatial intersections of the following supporting tables:
Because this information changes regularly, updates to supporting layers would need to trigger a refresh of the PLUTO columns or supporting product.
The text was updated successfully, but these errors were encountered: