hi,
I saw the app approximate by defect and not to near integer the second of degree.
This results in errors of 31 meters of airspaces.
For example Alzate Brianza Acro
`official ENR5-2-2 data by enav.it are:
Alzate Brianza Acro AD
AH 4000FT AMSL
AL 2000FT AMSL
45:46:54 N 009:08:55 E
45:46:36 N 009:10:06 E
45:45:46 N 009:09:32 E
45:46:06 N 009:08:26 E
45:46:54 N 009:08:55 E
OpenAirSpace raw .aip XML data are:
45.7816666667 9.1486111111 #45° 46' 54“ 9° 8' 55
45.7766666667 9.1683333333 #45° 46' 36“ 9° 10' 6
45.7627777778 9.1588888889 #45° 45' 46“ 9° 9' 32
45.7683333333 9.1405555556 #45° 46' 6“ 9° 8' 26
45.7816666667 9.1486111111 #45° 46' 54“ 9° 8' 55
that are exactly equivalent to ENR enav.it official values
but airspace-converter results:
AC R
AN Alzate Brianza(Acro)
AH 4000F MSL
AL 2000F MSL
DP 45:46:54 N 009:08:54 E
DP 45:46:36 N 009:10:05 E
DP 45:45:46 N 009:09:32 E
DP 45:46:05 N 009:08:26 E
DP 45:46:54 N 009:08:54 E
`
As you can see, there are some one unit of degree's seconds difference, about 31 meters.
The formula to calculate the degree's seconds require ROUND(x,0) and not INT(x) function.
INT() is OK for degree and degree's prime
Valerio