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
It looks like something may have gone wrong with CSV parsing? All of these entries do have a region (or an Unknown region). But in your table, they’re appearing at the end of the content columns.
Taking a look at some of these entries on my computer, they seem to share something in common—the final character of the content text is a backslash. So it seems your CSV parser is treating \, as an escape code for a comma. But the flavor of the CSV used by the dataset doesn’t use backslash escape codes; instead, that combination should be parsed as a textual backslash followed by a , column separator.
There are a handful of tweets that are missing a region and have the following columns shifted to the left:
The text was updated successfully, but these errors were encountered: