dsread - Windows command-line utility for SAS7BDAT files
in [SAS]
|
From: ChrisBLong on 25 Feb 2010 09:45 Hi, Readers of this group may be interested in dsread, available at http://www.oview.co.uk/dsread It's a command-line utility that understands the SAS7BDAT file format. It lets you examine the structure of datasets conveniently from the command-line, and converts SAS7BDAT data into valid CSV format for import into other software. All comments and suggestions gratefully received, Chris.
From: xlr82sas on 25 Feb 2010 13:43 On Feb 25, 6:45 am, ChrisBLong <ch...(a)oview.co.uk> wrote: > Hi, > > Readers of this group may be interested in dsread, available athttp://www..oview.co.uk/dsread > > It's a command-line utility that understands the SAS7BDAT file > format. It lets you examine the structure of datasets conveniently > from the command-line, and converts SAS7BDAT data into valid CSV > format for import into other software. > > All comments and suggestions gratefully received, > > Chris. Hi Chris, Congratulations for reading SAS datasets. WPS has powerfull capabilities. Thanks!!! Competition is great. Even though you only create csv's, I see this as a great product because you do not need SAS and with pipes users can programtically get at SAS data from other languages. Also CSVs are also very amenable to EXCEL. ============================================================================================================================== Just some thoughts: Any chance you could create a lossless output format, like SAS export datasets, but allow for longer names and character values greater than 200 bytes. This would open up SAS datasets to other languages. The format would have to be open. This could be a really big deal, if instead of a csv, you created R dataframes, if called from R. An even bigger deal would be if you created a SAS dataset from an R dataframe. XML would be another nice output. A silient ODBC would also be great. I bet you can use pipes whith yow command line interface.
From: Alan Churchill on 25 Feb 2010 14:34 Chris and I worked on the layout early on and then I split off on my own (Chris had to do other things at the time). I think Chris's app is cool and I have already downloaded, tested it, and fed him my comments. My latest reader and writer actually supports exporting SAS datasets to Excel, delimited (you pick the delimiter), and XML. OleDB is more than doable but it doesn't seem to have a lot of need outside of coding. Hence, a command-line type of interface seems to not be well-defined (mentally for me). ODBC is wrapped under OleDB so the argument is really for OleDB. If someone can articulate what an OleDB interface would like at a command line level, I am open to rolling it in. Likewise, a writer that reads in Excel, for example, needs to be well-defined. What column/row do you start at, what are the SAS dataset variables, their format, etc. SAS export datasets are well-defined so not sure how you can modify them to support v7 SAS dataset features. If a new standard for SAS datasets needs to be created outside of SAS then someone needs to form a committee and get folks to help out. Creating a command line interface whether it is Chris's or mine is trivial. Getting the layout down is the challenge here. And writing a dataset is far harder than reading one. Alan Alan Churchill Savian www.savian.net Office: (719) 687-5954 Cell: (719) 310-4870 -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of xlr82sas Sent: Thursday, February 25, 2010 11:43 AM To: SAS-L(a)LISTSERV.UGA.EDU Subject: Re: dsread - Windows command-line utility for SAS7BDAT files On Feb 25, 6:45 am, ChrisBLong <ch...(a)oview.co.uk> wrote: > Hi, > > Readers of this group may be interested in dsread, available > athttp://www.oview.co.uk/dsread > > It's a command-line utility that understands the SAS7BDAT file format. > It lets you examine the structure of datasets conveniently from the > command-line, and converts SAS7BDAT data into valid CSV format for > import into other software. > > All comments and suggestions gratefully received, > > Chris. Hi Chris, Congratulations for reading SAS datasets. WPS has powerfull capabilities. Thanks!!! Competition is great. Even though you only create csv's, I see this as a great product because you do not need SAS and with pipes users can programtically get at SAS data from other languages. Also CSVs are also very amenable to EXCEL. ============================================================================ ================================================== Just some thoughts: Any chance you could create a lossless output format, like SAS export datasets, but allow for longer names and character values greater than 200 bytes. This would open up SAS datasets to other languages. The format would have to be open. This could be a really big deal, if instead of a csv, you created R dataframes, if called from R. An even bigger deal would be if you created a SAS dataset from an R dataframe. XML would be another nice output. A silient ODBC would also be great. I bet you can use pipes whith yow command line interface.
From: xlr82sas on 25 Feb 2010 15:15 On Feb 25, 10:43 am, xlr82sas <xlr82...(a)aol.com> wrote: > On Feb 25, 6:45 am, ChrisBLong <ch...(a)oview.co.uk> wrote: > > > Hi, > > > Readers of this group may be interested in dsread, available athttp://www.oview.co.uk/dsread > > > It's a command-line utility that understands the SAS7BDAT file > > format. It lets you examine the structure of datasets conveniently > > from the command-line, and converts SAS7BDAT data into valid CSV > > format for import into other software. > > > All comments and suggestions gratefully received, > > > Chris. > > Hi Chris, > > Congratulations for reading SAS datasets. WPS has powerfull > capabilities. Thanks!!! Competition is great. > > Even though you only create csv's, I see this as a great product > because you do not need SAS and with pipes users can programtically > get at SAS data from other languages. Also CSVs are also very amenable > to EXCEL. > > ============================================================================================================================== > > Just some thoughts: > > Any chance you could create a lossless output format, like SAS > export datasets, but allow for longer names and > character values greater than 200 bytes. This would open up SAS > datasets to other languages. The format would have to be open. > > This could be a really big deal, if instead of a csv, you created R > dataframes, if called from R. An even bigger deal would be if you > created a SAS dataset from an R dataframe. > > XML would be another nice output. > > A silient ODBC would also be great. > > I bet you can use pipes whith yow command line interface. My apologies. I assumed your site was somehow affiliated with WPS. It looks like it may not be. Which makes what you have done all the more remarkable. I was hoping you honored formats because I wanted to associate hex16 with the numeric columns so I could create a lossless csv, but it did not work.
From: xlr82sas on 25 Feb 2010 21:42 Hi Alan and Chis What interests me is communications with open source products, like R, perl and MySQL. Export and import needs to be lossless. My understanding is that SAS -ODBC/OleDB... requires you to bring up SAS(ODBC server) and the server has to be closed manually. I feel this is unsatisfactory. The crux of the issue is IEEE floating point. I think HEX16. would be lossless, all I have to in R is convert the character hex16. to floating point. The nice thing about dsread is it is light, fast and you do not need SAS and it looks like it supports pipes. On Feb 25, 12:15 pm, xlr82sas <xlr82...(a)aol.com> wrote: > On Feb 25, 10:43 am, xlr82sas <xlr82...(a)aol.com> wrote: > > > > > > > On Feb 25, 6:45 am, ChrisBLong <ch...(a)oview.co.uk> wrote: > > > > Hi, > > > > Readers of this group may be interested in dsread, available athttp://www.oview.co.uk/dsread > > > > It's a command-line utility that understands the SAS7BDAT file > > > format. It lets you examine the structure of datasets conveniently > > > from the command-line, and converts SAS7BDAT data into valid CSV > > > format for import into other software. > > > > All comments and suggestions gratefully received, > > > > Chris. > > > Hi Chris, > > > Congratulations for reading SAS datasets. WPS has powerfull > > capabilities. Thanks!!! Competition is great. > > > Even though you only create csv's, I see this as a great product > > because you do not need SAS and with pipes users can programtically > > get at SAS data from other languages. Also CSVs are also very amenable > > to EXCEL. > > > ============================================================================================================================== > > > Just some thoughts: > > > Any chance you could create a lossless output format, like SAS > > export datasets, but allow for longer names and > > character values greater than 200 bytes. This would open up SAS > > datasets to other languages. The format would have to be open. > > > This could be a really big deal, if instead of a csv, you created R > > dataframes, if called from R. An even bigger deal would be if you > > created a SAS dataset from an R dataframe. > > > XML would be another nice output. > > > A silient ODBC would also be great. > > > I bet you can use pipes whith yow command line interface. > > My apologies. > > I assumed your site was somehow affiliated with WPS. > It looks like it may not be. > > Which makes what you have done all the more remarkable. > > I was hoping you honored formats because I wanted to associate hex16 > with the numeric columns so I could create a lossless csv, but it did > not work.- Hide quoted text - > > - Show quoted text -
|
Next
|
Last
Pages: 1 2 3 4 Prev: update a column based on a column in another table Next: Unstacking Data |