Open nicklucius opened 5 years ago
I don't understand exactly why we're testing the number of columns for #118.
In fact, I don't understand what was special about these data sets was causing what error. I see the comment from @hrect https://github.com/Chicago/RSocrata/issues/118#issuecomment-280721435 that these data sets replicate an error, but I don't know why they were causing the error.
@nicklucius do you know?
@geneorama this dataset has so many columns that including the names/types in the html header would drive the header size over their limit. So Socrata omits the names/types from the header in this case. That used to break read.socrata()
and throw an error. The development in #118 fixed the break so that it warns the user and then coerces to character
.
The test for this started failing recently.
The section of code:
The actual failing test message:
I thought this might be useful, but it didn't help me:
It looks like the URL columns are different in name only, but the other six columns are missing in the JSON. Not sure if this is related to this issue, or if this is something else?
Originally posted by @geneorama in https://github.com/Chicago/RSocrata/issues/118#issuecomment-543835796