Mandatory data_revision on all obs-readers, disable last-file check in caching

[heikoklein]

Is your feature request related to a problem? Please describe.
Caching of ungridded data relies on both data_revision and newest_file_in_read_dir, see #1242 . The newest_file_in_read_dir test is error prone since a touch or another minor filesystem operation will invalidate the cache, in addition it can be very slow, e.g. for the EEA-reader. If observation-readers deliver their own mandatory data_revision, the too general test can be removed.

Describe the solution you would like to see

• All observation readers must have a data_revision. This is already addressed in pyaro in Mandatory data-revision for reader-sources pyaro#37, the readers in pyaerocom must be checked
• newst_file_in_read_dir and newest_file_date_in_read_dir are removed from the ungridded-cache as well as the test-code:

  pyaerocom/pyaerocom/io/cachehandler_ungridded.py

  Line 163 in 300de5a

  newestp = max(glob.iglob(os.path.join(self.src_data_dir, "*")), key=os.path.getctime)

[Ovewh]

What about updating the cache between versions of pyaerocom? From a user standpoint there the should be warning if the cached ungridded data where generated with a different version of pyaerocom. I encountered issues due to changes in pyaerocom made my cached file incompatible and causing some not obvious errors...

[heikoklein]

@Ovewh When did you encounter such problems? The cache is independent of the pyaerocom-version, and pyaerocom-versions change often. The cache is dependent on the ungriddeddata-version, which is checked. The cache might also be dependent on external libraries, but those are partly unchecked.

[Ovewh]

I couldn't rerun my analysis due to some station names including / that resulted in an error that I did get before. Due Pyaerocom reading the cache, (which i did not realize at first) the error persisted even if I changed the problematic station name by replacing / with _ . I thought that this error was due to some additional checks introduced by updates to pyaerocom?