The pull request with the feature you mention has been merged (https://github.com/anitagraser/TimeManager/pull/295) but there hasn't been a new release of the plugin yet. Therefore, if you want to use this feature already, you need to download the plugin from Github (https://github.com/anitagraser/TimeManager/archive/master.zip) and install it manually (i.e. ...
By using this expression :
color_hsv(0, scale_exp( day( age( "END" , animation_datetime() )),0,365,10,100,2),100)
In the data defined override for your polygon fill color you get the effect from red to pale red as the time goes.
This work like this color_hsv set the color with H set at 0 (for
red), S set as a scale_exp fonction to change over time and V ...
It might be that the plugin is interpreting your timestamp as %m.%d.%Y and raises an error when the day (which is being treated as the month) is greater than 12.
Try using one of the timestamp formats listed in the documentation:
Integer timestamp in seconds after or before the epoch (1970-1-1)
You can use an expression like this to convert the month to a season name.
when month("datefield") in (12,01,02) then 'Winter'
when month("datefield") in (03,04,05) then 'Spring'
when month("datefield") in (06,07,08) then 'Summer'
when month("datefield") in (09,10,11) then 'Autumn'
Adjust months and season names to match your ...
You are not properly adding the layer, you have to add it through "Add Layer > Comma delimited" in your case you use "custom delimiter" and check "semicolon" (;), uncheck everything else; choose lon and lat as X and Y and finally uncheck "DMS" coordinates. If you do it right you'll see a little "point" to the left of the layer on the layers panel
Make a duplicate of each polygon for each month.
Fill the "date" field with the dates for Jan 2019 to Dec 2019, so there's one copy of each polygon for every month.
Style the polygons with a graduated style using the "date" attribute. Use a custom color gradient from dark red for Jan 2019 to light red for Dec 2019.
A little late on this, but I had the same issue and thought this might be of use to others. My time field was a Python Datetime type, in the '%Y-%m-%d %H %M' format. QGIS recognizes this as a datetime format, but TimeManager didn't like it. After reading bschiltz's answer I tried converting my datetime format to epoch time, and found that TimeManager likes ...
Late answer, but better than never...
First of all I think you need one graduated style that matches all of your columns, i.e. if an attribute value ranges from 0 to 30 at the beginning and from 20 to 50 some periods later your style should cover values from 0 to 50 to make things comparable (and otherwise my approach does not work).
I have created a small ...