Hi guys,
I lost a thousand records from my database, regarding November and first 8 days of December, so the statistics show inaccurate totals for rain and increased temperatures. Now I'm trying to import csv data from the Weatherlink page using the Data Import utility, but, unfortunately, the file don't seem to work in any possible way... Every time i get the error
"There seems to be a problem with the date and time. Either it has not been parsed correctly or it is a date/time in the future! Check the format you specified and also the actual values."
The file is the below one:
https://we.tl/t-xHzl4INYII
I have spent a lot of hours without success.
Any idea?
Data import
-
Don Voni
- Newbie

- Posts: 2
- Joined: Fri Aug 25, 2017 9:38 am
- Station model: Davis Vantage Vue
- Software: Meteobridge
Re: Data import
Already tried it but no luck...iatros wrote: ↑Sun Dec 13, 2020 1:15 pm Hi Don Voni
see this post:
viewtopic.php?f=51&t=1975&p=9548#p9548
hth!
Cheers, Martin
- MonyMony
- Forecaster

- Posts: 192
- Joined: Sun Aug 20, 2017 12:54 pm
- Location: Elkton, Maryland, US
- Station model: Davis Pro 2
- Software: WeatherCat/Meteobridge
- Contact:
Re: Data import
Hi Don,
Initial view of your source did not reveal anything unusual. Difficult without headers to know exactly what each field it doing. The one thing I have to wonder about is that your date field is not qualified with quotes but every other field is. I suppose it is possible this might be part of the issue as the import is expecting everything either be qualified or not be qualified with quotes. Total guess with this one.
I looked at a sample import I have done in the past (no quote qualifiers in my case) and my data looks like this:
The first thing I make sure if is the data field is set to the proper format AND is set to field 0.
Then my other settings look like this:
The main points for me was to use the options first to SHOW FIELD NUMBERS to make sure my variables were properly aligned and then do the test import to make sure everything was going to work.
So this all said I was going to do some more screenshots but I have discovered that in doing this that my web hosting provider has enacted some new security options as the import option is not currently working for me (403 FORBIDDEN Error). Looks like I get to dig to figure out why this might be happening and if this is unique issue for me or a more broad issue for others. Not sure if any of this is useful or not. Good luck!
Initial view of your source did not reveal anything unusual. Difficult without headers to know exactly what each field it doing. The one thing I have to wonder about is that your date field is not qualified with quotes but every other field is. I suppose it is possible this might be part of the issue as the import is expecting everything either be qualified or not be qualified with quotes. Total guess with this one.
I looked at a sample import I have done in the past (no quote qualifiers in my case) and my data looks like this:
Code: Select all
2018-06-15 18:14:00,N/A,73.1,52.8,73.1,29.978,0.0,180,0.00,0.00,49,34.0,89.4,0.0,76,0.7,0,2.63,24.92,0.23,10.77,21.32,
2018-06-15 18:19:00,N/A,73.6,55.4,73.6,29.977,0.0,180,0.00,0.00,53,34.0,89.4,0.0,305,1.0,0,2.63,24.92,0.23,10.77,21.32,
2018-06-15 18:24:00,N/A,74.5,54.6,74.5,29.977,0.0,248,0.00,0.00,50,34.0,89.4,2.0,358,0.8,0,2.63,24.92,0.23,10.77,21.32,
2018-06-15 18:29:00,N/A,74.4,55.6,74.4,29.977,0.0,248,0.00,0.00,52,34.0,89.4,1.0,274,0.8,0,2.63,24.92,0.23,10.77,21.32,So this all said I was going to do some more screenshots but I have discovered that in doing this that my web hosting provider has enacted some new security options as the import option is not currently working for me (403 FORBIDDEN Error). Looks like I get to dig to figure out why this might be happening and if this is unique issue for me or a more broad issue for others. Not sure if any of this is useful or not. Good luck!
-
marcelh
- Newbie

- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Data import
Hi Don,
I am following your post since I have also problems importing data.
My previous import using template version 17 worked fine but with the same data it's not working on template version 18. So there may be a change in the import module.
I am following your post since I have also problems importing data.
My previous import using template version 17 worked fine but with the same data it's not working on template version 18. So there may be a change in the import module.
