Date problem using import module
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Date problem using import module
Hello to you all,
I try to import data from the past into the Meteotemplate database. I succieded in the past but now I get stuck on a date error. The import file contains data from 1951 until 2017 with one data entry for eacht day.
When starting the test it shows the correct date:
>> Parsing date and time...Date and time parameters all in separate fields.
>> MySQL accepts date and time in format YYYY-MM-DD HH:MM, the parsed date and time is: 1951-01-01 01:05
But at the end of the test I get this error message:
>> Parsing line 0 finished.
>> Checking validity of data based on your limits in Main settings...
>> Checking date and time...
>> 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.
I already tried a smaller import file, but with the same result.
Maybe someone has a clue what can cause this problem .....
Many thanks,
Marcel
Meteo Helmond
I try to import data from the past into the Meteotemplate database. I succieded in the past but now I get stuck on a date error. The import file contains data from 1951 until 2017 with one data entry for eacht day.
When starting the test it shows the correct date:
>> Parsing date and time...Date and time parameters all in separate fields.
>> MySQL accepts date and time in format YYYY-MM-DD HH:MM, the parsed date and time is: 1951-01-01 01:05
But at the end of the test I get this error message:
>> Parsing line 0 finished.
>> Checking validity of data based on your limits in Main settings...
>> Checking date and time...
>> 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.
I already tried a smaller import file, but with the same result.
Maybe someone has a clue what can cause this problem .....
Many thanks,
Marcel
Meteo Helmond
- iatros
- Language Admin
- Posts: 145
- Joined: Mon Aug 21, 2017 5:56 am
- Location: Flims Waldhaus Switzerland
- Station model: Davis Pro 2 6163
- Software: Meteobridge
- Contact:
Re: Date problem using import module
Hi marcelh
I don't know if that helps: In "Data Import" section is a notice concerning php and Date/Time formats:
Date/time: 2020-11-24 16:45
Format: Y-m-d H:i
Cheers, Martin
I don't know if that helps: In "Data Import" section is a notice concerning php and Date/Time formats:
Date/time: 2020-11-24 16:45
Format: Y-m-d H:i
Cheers, Martin
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Date problem using import module
Thanks for your reply Martin, but the format is correct according to the PHP settings (as shown in the most upper quote).
So this should be OK.
Regards,
Marcel
So this should be OK.
Regards,
Marcel
-
- Observer
- Posts: 14
- Joined: Mon Sep 25, 2017 4:52 am
- Station model: Davis Vantage Pro2
- Software: Meteobridge
Re: Date problem using import module
Hi
I think you need to include seconds as well. So the format must be:
YYYY-MM-DD HH:MM:SS
That worked for me.
Gert
I think you need to include seconds as well. So the format must be:
YYYY-MM-DD HH:MM:SS
That worked for me.
Gert
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Date problem using import module
Thanks Gand
With a previous import it worked OK in the way I mentioned above, so this should be OK (don't need seconds).
Regards,
Marcel
With a previous import it worked OK in the way I mentioned above, so this should be OK (don't need seconds).
Regards,
Marcel
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Date problem using import module
So since there seems to be no sollution data import isn't possible anymore .......
Good to know
Good to know
-
- Expert
- Posts: 862
- Joined: Tue Jan 12, 2021 8:03 am
- Location: Italy
- Station model: WH2650
- Software: WH2650 (direct upload)
- Contact:
Re: Date problem using import module
Please attach the data you are trying to import ( or a part ), I can give a try
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Date problem using import module
Sorry for the late reply.
Please find attached the import file. Thanks a lot.
Please find attached the import file. Thanks a lot.
- Attachments
-
- weer70.zip
- (864.1 KiB) Downloaded 56 times
-
- Expert
- Posts: 862
- Joined: Tue Jan 12, 2021 8:03 am
- Location: Italy
- Station model: WH2650
- Software: WH2650 (direct upload)
- Contact:
Re: Date problem using import module
I have uploaded the document to google spreadsheet, lots of data present:
1) you should fill the first and second row ( only for the fields to import in the main table )
2) there are several '#WAARDE!' ( 125 ) across the spreadsheet, we should decide what to do with these cells, only for columns to be imported ( simple solution is to remove these warning or substitute with some data, a quick and dirty solution is remove these data and in a second time 'fill in the blanks' )
3) the table contains data from 1970 Jan 1 to 2019 Jan 22 ( I mean it does not contain data from 1951 to 1969 )
P.S.
The 'main' table ( alldata ) on meteotemplate contains only these fields ( and we should import all these fields if available ):
Date Time, T ,Tmin, Tmax, H, D, W, G, B, RR, R, P, S, A ( metric units )
P.P.S.
Other data may be imported in a 'second pass' to the extra table ( alldataExtra )
1) you should fill the first and second row ( only for the fields to import in the main table )
2) there are several '#WAARDE!' ( 125 ) across the spreadsheet, we should decide what to do with these cells, only for columns to be imported ( simple solution is to remove these warning or substitute with some data, a quick and dirty solution is remove these data and in a second time 'fill in the blanks' )
3) the table contains data from 1970 Jan 1 to 2019 Jan 22 ( I mean it does not contain data from 1951 to 1969 )
P.S.
The 'main' table ( alldata ) on meteotemplate contains only these fields ( and we should import all these fields if available ):
Date Time, T ,Tmin, Tmax, H, D, W, G, B, RR, R, P, S, A ( metric units )
P.P.S.
Other data may be imported in a 'second pass' to the extra table ( alldataExtra )
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Date problem using import module
Thanks for the reply.
I'll remove all rows which are not used and give it another try.
I'll remove all rows which are not used and give it another try.
-
- Newbie
- Posts: 8
- Joined: Thu Aug 08, 2019 8:43 am
- Station model: Davis Vantage Peo 2
- Software: MeteoHub
Re: Date problem using import module
I removed all extra rows and empty or false values. Still no luck ......
- Attachments
-
- weer2021.zip
- (563.6 KiB) Downloaded 66 times
-
- Expert
- Posts: 862
- Joined: Tue Jan 12, 2021 8:03 am
- Location: Italy
- Station model: WH2650
- Software: WH2650 (direct upload)
- Contact:
Re: Date problem using import module
Ok, but you have to add a couple of heading rows:
- first row is the column name
- the second row is the unit of measure of the column ( I mean °C, Km/h, hPa... )
- first row is the column name
- the second row is the unit of measure of the column ( I mean °C, Km/h, hPa... )