I don't believe the issue here is the delimiter itself, rather we need to get the delimiter used in the source data file to match the delimiter specified in the import config file whilst at the same time we need to get the source data field names specified in the import config file to match the field names that wee_import extracts from the source data file header row (which is of course impacted by the delimiter).
Provided the source data file is a text file I have not yet seen a delimiter that has caused a properly configured wee_import run to fail. Gary On Friday, 4 March 2022 at 18:06:57 UTC+10 [email protected] wrote: > > > On 4/03/22 20:57, gjr80 wrote: > > You also have a problem in that the delimiter in your data has now > > been changed to a period rather than a comma. You can try using a > > period as the delimiter in your import config file, I do not know how > > well that will work though. > > > > Gary > > > > On Friday, 4 March 2022 at 17:55:00 UTC+10 gjr80 wrote: > > > > The delimiter setting in in your import config file needs to be > > enclosed in single or double quotes, eg: > > > > delimiter = "," > > > > Gary, I've seen this delimiter 'comma' vs 'period' problem before. It > was not related to Weewx but to > a totally different DB. In our case the answer turned out to be the use > of a totally different delimiter. > > Can't recall the DB involved but making the delimiter '|' (pipe) fixed it. > > \Worth a try? > > cheers > john > > -- 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/d24d9ce5-4b80-4168-bc44-0ed288f203a9n%40googlegroups.com.
