Your csv file does not contain a field call timestamp, which your .conf file says should be imported to dateTime. You need to combine Datum and Zeit into a field called timestamp, and then tell wee_import the format of that field.
On Monday, 13 April 2020 14:28:58 UTC+3, Meteo Oberwallis wrote: > > Hello. > > I have now worked exactly according to the instructions. Unfortunately I > always get the same error message when importing the data. I have the > relevant data as an attachment here. > > wee_import --import-config=/var/tmp/csv.conf --dry-run > Starting wee_import... > A CSV import from source file '/home/pi/Desktop/EXP09_17.csv' has been > requested. > Using database binding 'wx_binding', which is bound to database > 'weewx.sdb_new' > Destination table 'archive' unit system is '0x01' (US). > Missing derived observations will be calculated. > This is a dry run, imported data will not be saved to archive. > **** Unable to map source data. > **** Field 'timestamp' not found in source data. > **** Nothing done, exiting. > > Can someone help me please? > Thx > > > > Am Montag, 13. April 2020 01:36:35 UTC+2 schrieb gjr80: >> >> Hallo Günther, >> >> Now I have to know something else. you talk about adapting the >>> wee_import? How does that work? >>> >> >> How wee_import processes/interprets your data is controlled by the >> import config file. As Bill points out there is a template CSV import >> config file provided with WeeWX, you will find it at >> /home/weewx/util/import/csv-example.conf or >> /etc/weewx/import/csv-example.conf depending on your WeeWX install type. >> >> I also wanted to ask because I didn't quite understand it with rain. >>> WeeWX needs the cumulative amount of rain. Wouldn't it be easier if I >>> simply deleted all other rain data from the table? >>> >> >> You can certainly delete the other rain columns in your import data if >> you want but there is no need, wee_import will only import data in the >> columns included in the field map ([[FieldMap]] stanza in the import >> config file) and all other columns are ignored (there is likely a small >> processing overhead for having the extra unused columns included but I >> expect this overhead would be negligible). >> >> >>> And the last question. You wrote that (--dry-run) can be used to test >>> whether everything is ok. How should I do that? >>> >> >> When you run wee_import you can add the --dry-run option to the command >> line to run the import but any saves to your archive are skipped, so in >> effect the import runs as normal (as configured in you import config file) >> but your database is left untouched. Have a read of Option --dry-run >> <http://weewx.com/docs/utilities.htm#Option_--dry-run> in the Utilities >> Guide. >> >> >>> Sorry for the many questions. But is not quite clear ;-) >>> >> >> No problems, most of what you want to know is covered in the wee_import >> section <http://weewx.com/docs/utilities.htm#wee_import_utility> of the >> Utilities Guide. You are interested in a CSV import whereas the >> wee_import section of the Utilities Guide covers imports from other >> sources (Weatherunderground, Cumulus etc) as well. You can skip these >> sections paying attention only to the Actions and options section >> <http://weewx.com/docs/utilities.htm#Actions_and_options31> and the CSV >> specific sections here <http://weewx.com/docs/utilities.htm#General> and >> here <http://weewx.com/docs/utilities.htm#Importing_from_CSV_files>. >> >> If language is a problem or you just don't follow, let me know and I will >> put together a suitable import config file for you. >> >> Gary >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/070fe01b-4bec-42f3-bf43-30d01b8cf85a%40googlegroups.com.
