We're doing some work on this ready for our next major version.

It affected a Polish military TRA on the same day as well - as I mentioned in my FB-posting. I only have these dated screenshots where the wrong TRA is not included as it was around 50nm to the north of that screenshot area.

Anyway: That should be sufficient to illustrate the issue.

I do not know if there is a NOTAM archive in the internet, if so, check those from 09th of May this year and compare to what was displayed in SD that day, if that is reproducable.

By the way: I observe that effect frequently, so there will surely be a chance to see that effect live - if somebody should really be interested in the problem and intend to find a solution (instead of just arguing against the complaint).

Sorry, I thought we were talking about restricted areas? The ones in the screenshots are notifications of glider flying activity (I am not disputing they are inappropriately sized).

I found one of my related postings in facebook.

Again: it can not be that difficult to code something that blanks out everything behind a FIR border. As a general filter rule.

It sounds like from your posts above like you're fortunate enough to have never been exposed to the raw data that companies like us have to deal with. As I mentioned before, if you wait until you've got a specific example, we can look into it and comment.

Ok - but I do not see how correcting a dataset at the provider could in any way affect end user devices performance. All the relevant corrections should be made in SD‘s internal database. So the users only see a map with (correct) markings.