Hi Andre,
not Ian, but I can also answer this question:
The problem here is the wrong airport position in MSFS for SBMI.
In the sim you have:
Latitude: -16.433723449707
Longitude: -44.0570983886719
In real, and in our database you have, the airport reference point is:
Latitude: -22.91805556
Longitude: -42.82888889
You see, the sim point is far away from the original, real-world point.
So, why is the airport than not on the correct place with the AIRAC update, when our data are correct (as you also have figured out in the charts)? The answer is simple: we may not move existing airports in MSFS, so we must use exactly these wrong coordinates from the MSFS. Normally there are existing an “Airport Reference Point”, which is a standardized, special point on every airport. You see this point on every airport-diagram called ARP - here an example from SBGL:
But ASOBO doesn´t use this point, they take an own point somewhere on the airport. And therefore, we can use our database ARP, we must use their “ARP” point and this point is simple wrong and therefore you get a wrong result.
It´s not a database issue, we have the correct coordinates but due the internal logic of the MSFS we can´t use this ARP - we must use the MSFS ARP, which is in most cases not the same as the real-world ARP. In this case, it´s completely wrong.
So, what you can do is, that you report this to ASOBO, that they fix this … sorry.
Cheers,
Richard
PS: you haven´t done anything wrong in the installation - what I see, the data are correct installed - so it´s no issue on your end - it´s a bug in the MSFS