Write parser for TROPOMI

[pennelise]

Elise will need to ask Hannah about this, but I think it should be very similar in structure to the GOSAT one so easier for me to take this.

We should discuss whether we should incorporate filters (e.g. albedo) in our parsers since they are so important for TROPOMI.

[hannahnesser]

A few thoughts:

• We should think about the various different TROPOMI products out there--i.e., the science product, the operational product, and Nick's blended albedo product. I think there are two different format schemes across these. Do we want to write two different parsers?
• I agree it makes sense for you to at least draft the parser. I'm happy to provide any help if it's useful (including demo files, or finalizing the parser if you provide a general structure).
• The IMI uses default filtering. I'm wondering if we could figure out a way to allow a user to pass filters as a dictionary? Maybe this is too hard. But we could do like filters={'qa' : (data['qa'], "> 1"), "blended_albedo" : (data['albedo'][0,:] + 2*data['albedo'][1,:], ">0.85")}?

[pennelise]

1. Yes - I think these should have different parsers. I believe the main difference is just the names of the data fields, which should be in the config file (if that's the only difference then I guess we could use the same parser for all satellites and just pass the config file)
2. Thank you!
3. I think a dictionary (or some entries in the config file) would be a great way to pass this.