Can't import data to Rapidminer properly - csv

The data I'm trying to import is here: http://archive.ics.uci.edu/ml/machine-learning-databases/car/
car.data 51 K
There are no missing values in this data, yet there are lots of "?"s in the rapidminer once I imported the data. I looked at to the source and those data, which shown as "?", do exist properly in the source. What may be the problem?
by the way, if I download that file it's extension is .data. How should I import that kind of files? I import it as if it is a .csv file and it looks ok at first but there are those "?"s.

It's been sometime since I have used Rapidminer, but AFAIK, you can import .data file by using csv Import Wizard and setting the file type to All Files.
Regarding the ? values, you would have the look at the settings while importing the file and may have to adjust the datatype in Step 4 of the Import Wizard (the dropdown menu)

Use the Read CSV operator to load the file.
In the "Data import wizard - Step 2 of 4 screen, find the Column Separation group box and select the radio button Comma ",". The default separator is the semicolon and car.csv is comma-separated.
In the next step-- "Data import wizard - Step 3 of 4"-- change the annotation for row 1 from Name to - (the dash character). This tells RapidMiner that the first row contains data and not column headers.

Related

Loading data from a UTF-16 Le (.txt) file to Azure SQL Db

We have a .txt file with encoding UTF-16 LE (discussed here, as well). We need to load this file into an Azure SQL database. We are first trying to convert this file to a csv format by using Text Import Wizard of Data Excel 365 wizard. But if we use the ^|^,^|^ as a custom delimiter, the first and last columns still end up with ^|^ value.
Question: What may be possible solutions/work arounds for converting this type of file to csv?
Remarks: This is a huge file (1GB) with about 150 columns. Following is just a sample for explaining the scenario in this post.
Sample of the txt file:
^|^Col0^|^,^|^Col1^|^,^|^Col2^|^,^|^Col3^|^,^|^Col4^|^,^|^Col5^|^,^|^Col6^|^,^|^Col7^|^
^|^1234^|^,^|^4600869848^|^,^|^6000.00^|^,^|^2021-12-20 10:16:19.3600000^|^,^|^False^|^,^|^^|^,^|^^|^,^|^2^|^
^|^5431^|^,^|^3425143451^|^,^|^30000.00^|^,^|^2021-12-13 10:27:44.9030000^|^,^|^False^|^,^|^^|^,^|^^|^,^|^2^|^
.....................
............................
After using the delimiter ^|^,^|^ in Excel text import wizard
Instead of mentioning the ^|^,^|^ as custom delimiter, you can mention comma as a delimiter, that will give you a result like below:
Then you can record a macro to replace the desired characters which is ^|^ after importing is done as mentioned in below link:
Create A Macro Code To Achieve Find And Replace Text In Excel

MySQL import wizard isn't importing the COMPLETE data

I used MySQL workbench's import wizard to import data from a csv file. The import was successful but not all the data rows were imported. My csv file contains 271,117 rows but only 270,396 were imported successfully. 721 rows were not imported.
There was no error message at all but this is no good, right? How do I rectify this issue?
I had the same problem. But I converted my csv data to JSON using https://csvjson.com/
Afterwards I validated the JSON using https://jsonlint.com/.
Btw when you convert the data to JSON remember the first row needs to be the column names :)
Then inside of mySQL workbench select the table --> Table Data Import Wizard --> select the JSON file.

Why are my column headers combined when importing csv to MySQL workbench

When I try to upload my csv, my headers get combined, so it says I only have 4 whereas there are 10. When I open my csv in excel, the categories are properly in their 10 respective columns. I'm using the import wizard. Thanks!
You obviously use the wrong separator (space) while the correct one would be a comma. This can be set as option in the import wizard.

CSV file import problem in ms access

I have been trying to import a csv file to access and appending it to a table. It only imports some of the rows and stops arbitarily. All the lines in the csv file are in the same format. HAs anyone encounntred this problem? how can I fix it?
Make sure text data is quote-encapsulated. You may have some text fields containing commas that can throw off the record layout and hose the entire import.

Access97 VBA Export to CSV format issue

I have an access97 database and I am trying to write some code to export to a CSV file - (I am new to VBA).
I have this working however, there is one field that I am exporting that is a currency so in it for example is £3,456.00 - when I export to the CSV I get exactly this - however I need it to just be the number i.e 3456.00.
On a similar issue - I have the date as dd/mm/yyyy and I wonder if there is a way to convert that in VBA to yyyy-mm-dd?
Please bear in mind any solutions has to be simple due to my limited knowledge!
Sorry about the delay; seemingly easy things took longer. As I assumue from your:
DoCmd.TransferText acExportDelim, "olly_csv", "olly aorder export", "\\10.0.0.38\nw_upload\aorders.csv"
that you have an export specification "olly_csv" that determines how to export the
resultset of the SELECT query "olly aorder export" to the file "aorders.csv"
in the destination folder "\10.0.0.38\nw_upload".
The easy way to export the CURRENCY field(s) as plain Double/Float/Single number
and the DATE field(s) with a format of your choice (dd/mm/yyyy) would be to
request just that in the export specification. I found no way to do that in Access
2000 (As far as I can see, there are limited ways to pick date formats, but the features of the Import Wizard to deal with the types of columns are not implemented by the
Export Wizard).
The Docs about "TransferText" (sorry, Access 2003) state:
SpecificationName Optional Variant. A string expression that's the name of
an import or export specification you've created and saved in the current
database. For a fixed-width text file, you must either specify an argument or
use a schema.ini file, which must be stored in the same folder as the
imported, linked, or exported text file. To create a schema file, you can use
the text import/export wizard to create the file. For delimited text files
and Microsoft Word mail merge data files, you can leave this argument blank
to select the default import/export specifications.
Now there are to schools of Microsoft Docs philology: The optimists will read
that as: If you don't pass an export specification and have a suitable schema.ini
file, then the export process will adhere to the specs in the file. The pessimists
will say: Microsoft never agreed to fullfill your pipe dreams - if you don't
specify an argument for a non-fixed-width file, the TransferText command will
use some obscure default export specification (please pay a consultant to
seek and change it).
Let's be optimistic!
So create a schema.ini file with a section for "aorders.csv". For my tests I
used a table
Tabelle: OlliesOrders
Name Typ Größe
OrderId Long Integer 4
Amount Währung 8
DateDue Datum/Uhrzeit 8
(sorry about the German; Amount is Currency, DateDue Date/Time). For that table
the schema.ini section looks like:
[aorders.csv]
ColNameHeader=True
CharacterSet=1252
Format=Delimited(;)
DateTimeFormat=dd/mm/yyyy
Col1=OrderId Integer
Col2=Amount Float
Col3=DateDue Date
You'll have to adapt this example to your fields. Do you want column headers? Is the
windows codepage ok? What about field separators? I had to use ; (German locale), you
may need "Format=CSVDelimited". Look here for some background. Then call
DoCmd.TransferText acExportDelim, , "olly aorder export", "\\10.0.0.38\nw_upload\aorders.csv"
and check if optimists rule.
For pessimists:
Create a new query on the table to export (from). Change the type to Ausführung/Execute (?)
and edit the SQL until it looks like:
SELECT OlliesOrders.* INTO [aorders.csv] IN 'M:\trials\23forum\SOTrials\txt' [TEXT;] FROM OlliesOrders;
resp.:
SELECT YourFieldsList INTO [aorders.csv] IN '\\10.0.0.38\nw_upload' [TEXT;] FROM YourTable;
and execute it (from the query window or a macro/module Sub). My result:
"OrderId";"Amount";"DateDue"
1;1411,09;29/04/2011
2;123,45;13/04/2011
ADDED: Evidence for my claim, that you can't specify types in the Export Wizard:
Export
Import