Closed nickballen closed 4 years ago
Hey, thanks for the bug report. It looks like the issue is the value for ZONING
on these three parcels is blank
which is causing it to crash on lookup in the zoning dictionary
Never a dull moment with the parcel data!
On 18 Feb 2020, at 2:54 PM, Jimmy McBroom notifications@github.com wrote:
Hey, thanks for the bug report. It looks like the issue is the value for ZONING on these three parcels is blank which is causing it to crash on lookup in the zoning dictionary
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CityOfDetroit/parcel-viewer/issues/11?email_source=notifications&email_token=ABO4K2SMSHFGC32FYWHI33DRDQ4HZA5CNFSM4KXIYWJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMEEJ3Q#issuecomment-587744494, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABO4K2V5LHFU3YSPIA5W463RDQ4HZANCNFSM4KXIYWJQ.
Searching or interacting with certain parcels cause the application to crash. This behavior happens across browsers (Firefox/Chrome/Safari) Some examples:
https://cityofdetroit.github.io/parcel-viewer/05004190.001 https://cityofdetroit.github.io/parcel-viewer/15003802.002L/ https://cityofdetroit.github.io/parcel-viewer/15009498-515/
One hunch is it might be related to overlay parcels: where a land parcel also has overlying, but separate, improvement parcels (i.e. special acts parcels). But I can't find a consistent pattern in parcel attributes that would cause this.