Inquiry
The field names in the E-desginations API (https://data.cityofnewyork.us/Environment/E-Designations-CSV-file/hxm3-23vy) are incorrect.
The correct fields show up when downloading the CSV file:
CSV header from downloaded file:
ENumber,E Effective Date,BOROCODE,TAXBLOCK,TAXLOT,HazMat Code,Air Code,Noise Code,HazMat Date,Air Date,Noise Date,CEQR_NUM,ULURP_NUM
However, when accessing the data through the API, the CSV headers // or JSON keys are nonsensical:
CSV header from API endpoint:
"e_1","_4_28_1983_0_00","_3","_319","_1","_0","_0_1","_1_1","column_8","column_9","column_10","_82_252k","_830178_zmk"
JSON example from API endpoint:
[{"e_1":"E-1","_4_28_1983_0_00":"1983-04-28T00:00:00.000","_3":"3","_319":"319","_1":"1","_0":"0","_0_1":"0","_1_1":"1","_82_252k":"82-252K","_830178_zmk":"830178 ZMK"}
,{"e_1":"E-1","_4_28_1983_0_00":"1983-04-28T00:00:00.000","_3":"3","_319":"319","_1":"10","_0":"0","_0_1":"0","_1_1":"1","_82_252k":"82-252K","_830178_zmk":"830178 ZMK"}
,{"e_1":"E-1","_4_28_1983_0_00":"1983-04-28T00:00:00.000","_3":"3","_319":"319","_1":"11","_0":"0","_0_1":"0","_1_1":"1","_82_252k":"82-252K","_830178_zmk":"830178 ZMK"}
Assigned Agencys Response
Hi Yarin Kessler #4,
Hello thank you for pointing out the discrepancy in the data sets metadata. We contacted DCP for approval and have updated API field names usable.
https://data.cityofnewyork.us/Environment/E-Designations-CSV-file/hxm3-23vy
Thank you,
- NYC Open Data Team