-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in read.dta(tmpfile) : a binary read error occurred #2
Comments
Hi @pssguy Can you try out the following code:
Also can you send the output from:
in the case where |
Hi
locale: attached base packages: other attached packages: loaded via a namespace (and not attached): |
Hm, there is some issue with either When you run
Do you get a message that looks like this:
returned in your R console? |
Yep |
Hu, then it could be with in What if you download the file manually (put http://bit.ly/1jZ3nmM into your web browswer). And then load it into R with something like:
|
That seems to work fine BTW where would I find column definitions? |
By the process of elimination, it must be something to do with where/how your computer is storing the
This is really difficult to debug without having access to your computer and file system. What do you get with:
Stata .dta files don't store variable descriptions in a column, they are stored in the binary in a way that |
Here we go library(psData) Is this relevant for read.dta Reads a file in Stata version 5–12 binary format into a data frame. Frozen: will not support Stata formats after 12. The default file format for Stata 13, format-115, is substantially different from those for Stata 5–12 |
I'm stumped. The data is definitely in pre Stata 13 format and you found it can be opened from So yeah, I'm stumped. You might want to contact the maintainers of the foreign package where |
I'm closing this issue for now as it's not exactly a psData issue. Though if anyone finds the answer, please reopen it. |
The first item should help, and the second one always solved my encoding issues, because it handles some Windows/Mac backend options that can cause issues from time to time. |
Thanks briatte |
Occurs with following command
DpiData <- DpiGet()
also there is what appears to be a typo on the main page. You refer to pdData as not yet being on CRAN
The text was updated successfully, but these errors were encountered: