There really needs to be a convention for events list files that allows them to be created automatically. I was showing Craig R. how to use an events list to run a pngwalk, and it was tedious to describe the process. His expectation is that it knows it needs an events list, so it should be able to use the text filename to create the events list.
I've been nervous about adopting the convention of two ISO8601 columns indicating an events file, but I think it's time to accept this. Also when Craig was guessing at how to write an events file, he was using valid time range strings like "2015-03-04" and also "2015-03-04T00:00/04:00" so it would be interesting to support this as well.
So let it be:
<iso8601> <iso8601> ... <lastcolumn>
will no longer need ...?eventListColumn=lastColumn.</lastcolumn></iso8601></iso8601>
See http://autoplot.org/developer.eventsList
Chris had a .csv file that showed that it's confusing when csv doesn't do the same thing. So csv should also check for two iso8601 columns.
Last edit: Jeremy Faden 2016-05-08
I noticed that this feature makes it impossible to jump back into Autoplot. This could probably be supported by copying the list into the pngwalk so names can be dereferenced.
There are three places in the ASCII reader where it says it's going to check for an events list. This clearly needs to be reviewed. The last place ignored ?field0, preventing Sadie from plotting the first column of timetags.