Don't use date in date_of_acquisition

[bagibence]

We should use timestamp if we are inserting more than once a day.
I guess the problem is here for example:

webscraping_2018/bild_scraping.py

Line 140 in aba5809

df_daily.date_of_acquisition = df_daily.date_of_acquisition.apply(lambda x: datetime.datetime.strptime(str(x), '%Y%m%d%H').date())

webscraping_2018/daily_db.py

Line 95 in aba5809

df.date_of_acquisition = df.date_of_acquisition.apply(lambda x: datetime.datetime.strptime(x, '%Y%m%d%H').date())

We have to check where else it exists.

[vrgsdaniel]

we better agree on use timestamp always for consistency. Is the DB ok with that?

[bagibence]

It is. You use it for hourlyprediction already.

db.HourlyPrediction.select().first().date_of_acquisition returns
datetime.datetime(2018, 6, 19, 10, 0)

But only use it for the date_of_acquisition. The date_for_which_weather_is_predicted field should stay datetime.datetime.date for dailyprediction as it refers to a whole day.