You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2024. It is now read-only.
We might be able to use use similar logic as nysdec datasets. We would need to determine what the appropriate ID field would be. Perhaps a concatenation of requestid and applicationid, such as {requestid}/{applicationid}.
Additionally, there are several address columns in the dep_cats_permits input data. Rather than a single address, we use house, street, and borough for geocoding. Would corrections happen before or after our initial cleaning and parsing?
The text was updated successfully, but these errors were encountered:
We might be able to use use similar logic as nysdec datasets. We would need to determine what the appropriate ID field would be. Perhaps a concatenation of requestid and applicationid, such as
{requestid}/{applicationid}
.Additionally, there are several address columns in the dep_cats_permits input data. Rather than a single address, we use
house
,street
, andborough
for geocoding. Would corrections happen before or after our initial cleaning and parsing?The text was updated successfully, but these errors were encountered: