Data gap before reshaping market region from DE-AT-LU to DE-LU #29
Description
While I'm recognizing a data issue in an older version of the database (epex day ahead is similar for 2018 and 2019) I'm watching for the new version and there just the data rows for the new market region which Germany belongs to (recently DE-LU) are included. So even if i konwo its hard to keep the consistency of the data collection and not to overengineer the crawling script, it would be nice also to incorporate the values from the former market region until middle of 2018.
Best,
martin