Many aerodromes with the same ICAO-code are mapped in OSM

Help and support
1

By coincidence I found and airport that was mapped twice (See Aerodrome VIJR exists twice).

I decided to analyse the situation globally and found that there are actually a lot of aerodromes that are mapped multiple times.

Does anybody have a suggestion how to fix this hopefully without having to touch all of them individually?

ICAO OSM elements
HUEN node 26608719, way 669659157
NFNM node 240485015, way 829463446
VEJP node 245652501, way 790037803
VEMN node 245759577, way 97945321
LTBL node 254396985, way 308553267
LTAB node 254413530, relation 8796772
MUMG node 259849773, way 844417236
CYXX node 275639689, way 929827772
YBHM node 301682474, way 481995428
OIAD node 343702015, relation 10660866
LGSY node 353289451, way 228788343
EFUT node 365622709, relation 7777022
KSXL node 368381091, way 949187829
KHSA node 368385985, way 730035233
KELK node 368390278, way 1052140493
None node 368395585, node 1042023943, node 1042028359, node 1498837932, way 690081823
KAHH node 368885451, way 798560362
KVIQ node 368887570, way 779379193
KMDZ node 368887801, way 657418493
KPKF node 368888441, relation 10928390
KLLU node 368932640, way 864851192
KHLX node 368946897, way 1126238281
KJYG node 369004955, way 946198448
KBDN node 369014048, way 1054008033
F87 node 369015735, way 777780887
KHTL node 369022858, way 660469348
KCIU node 369023518, way 730036282
KOSC node 369023622, way 936387155
KSAW node 369023758, way 763017817
KHSB node 369054029, way 909905818
KSPS node 369120432, way 505598862, way 696266113
KLLN node 369121701, way 1132757931
KOZA node 369122140, way 1134637596
KGYI node 369122726, way 713185583
KRIW node 369132255, way 1068356163
PALH node 369144119, way 760255362
PAKY node 369144263, way 648854890
PAMD node 369144495, way 665637233
PAWN node 369144558, node 369145195
PAMB node 369144710, way 694715362
PAPC node 369145025, way 826543873
PADL node 369146379, way 714475952
KLAM node 369158762, way 769503494
KAJZ node 369163684, way 887911780
KALS node 369165192, way 730028560
KCFO node 369165609, relation 9583882
KSVE node 369171265, way 864304198
KBKF node 369179652, relation 1753900
KGRF node 388484490, way 989806949
KXTA node 389726285, relation 14657286
VCCN node 408503714, way 897676017
CYOC node 409290033, node 1042019709
MPSA node 410625383, way 841137937
RJSF node 410805375, way 1037339151
YWIS node 415436410, way 818834035
KVPS node 416793368, way 547153940
DRZF node 469806272, way 939762446
YHLC node 677811767, way 902166406
SCSF node 703320042, way 149925601
VECA node 746952719, way 123935434
SSMH node 832642707, way 290462935
none node 974605798, node 8833363579, way 1074354951
HKMY node 974605863, way 1004373695
VTPL node 997259131, node 1042092424
VTSH node 998541906, way 988784908
OESH node 1014372092, relation 13740136
CYOO node 1041997421, way 764398387
HKBM node 1042023405, way 1004373665
CJX4 node 1042026529, way 1107815891
CSM5 node 1042029629, way 646437395
CYDF node 1042031002, way 798633690
CYQQ node 1042031479, way 1093480929
CYTN node 1042031520, way 652931276
EERU node 1042032420, way 1080692722
ENEG node 1042033493, way 963610633
FAHC node 1042035306, way 717280050
FAZQ node 1042036353, node 2311449761
FDBS node 1042036647, way 384653767
FDMH node 1042036663, way 871854720
FDTS node 1042036680, way 874120616
FZRL node 1042040481, node 1042040642
HKEW node 1042043237, node 10048804730
KCRX node 1042045631, node 9463358503
KNLC node 1042045858, way 324125679
LEOA node 1042046415, node 5537398059
LHBA node 1042046889, way 997176974
LHSS node 1042046942, way 1051319271
SPRM node 1042048663, node 1042081215
NFKD node 1042049672, way 829461424
NFMO node 1042049680, way 813581577
NFNH node 1042049685, way 829464351
NFNO node 1042049690, way 241754822
NFNW node 1042049698, way 829460672
OJ38 node 1042052242, way 1098681992
RJSH node 1042056016, way 245451491
RKJM node 1042056349, way 902512928
RKRO node 1042056465, node 10159069510
RKTI node 1042056519, way 355208312
RP17 node 1042056627, way 1126523137
USMQ node 1042057084, way 136398566
SAWM node 1042059492, node 7703815842
SCIA node 1042060828, way 1072354130
SCAD node 1042061097, node 10591613678
SCLM node 1042062151, node 1042062853
SCVN node 1042063130, way 775234456
SDCD node 1042063581, way 433834849
SDDV node 1042063771, way 1117685828
SDFF node 1042063923, way 1014373583
SILI node 1042068448, way 653761017
SKTI node 1042075811, node 1042075946
SNEE node 1042077743, way 290293740
SNLD node 1042078860, way 975404194
SPLP node 1042080996, way 28746824
SSFO node 1042081900, node 8664370947
SSOW node 1042082840, relation 8335878
SSAO node 1042086748, way 955456740
VGCM node 1042092140, way 624089964
VGSH node 1042092144, way 623242795
WASK node 1042092742, way 504033057
YAMB node 1042093139, way 902155670
YBCH node 1042093193, way 820424979
YEUA node 1042093785, way 765606375
YGLI node 1042093860, way 1025745532
YIFL node 1042093934, way 666916108
YMAR node 1042096089, way 453949960
YOOM node 1042097226, way 857391068
YSRD node 1042098674, way 1047725644
YTEE node 1042098782, way 621845536
YVVA node 1042099509, way 675738678
KBWI node 1042101112, relation 12805078
FZGV node 1080896537, way 866345089
GCLP node 1118731515, way 578958832
CYPQ node 1860910040, way 1093471509
YHBA node 1932121141, relation 10381362
YBTL node 2119119847, way 372778463, way 847890824
FDSM node 2316652208, way 871906081
EDNR node 2790124340, way 384591175
FEFZ node 3392528897, way 254037446
UESU node 4326877639, relation 7449677
RJNK node 4380614852, relation 13514757
SVLR node 4585335555, way 785982685
SMTA node 4588931160, way 513117962
VYCI node 4818300976, way 793162672
CYVR node 4853395421, relation 11680231
SIYO node 4986487447, way 509352806
MPMF node 5371512333, way 527428522
DTTD node 5601593034, way 247545861
FDST node 5695502467, way 871906079
FDNS node 5696597256, way 871906077
TFFF node 6274363436, way 366729029
VIDX node 6436473949, way 265984430
KPHD node 6975525755, way 424690072
SJNA node 7746921268, way 425176505
AYYZ node 7816989018, way 837546601
KOKC node 7862780110, way 224385248
SBSP node 7936165260, way 96494371
RKTN node 8192515622, relation 11750367
HHHB node 8234358649, way 870451421
HHKT node 8234452526, way 918833903
HHMF node 8234887877, way 885579191
HHOH node 8234919874, way 881325541
HHMG node 8234935828, way 885583729
HHTS node 8234998119, way 421569614
PHLU node 8394709100, way 232277908
SJZA node 8495396600, way 290462923
SSMX node 8576498302, way 227090692
DRRL node 8863349546, way 1036298119
YBTR node 8975947931, way 969961965
YBCK node 8994788948, way 238175176
TFFC node 9276586218, way 51203849
RJGG node 9502157358, way 54717812
SARM node 9525537934, way 956532708
SARO node 9525537938, way 397729817
SARL node 9525537951, way 311672805
SARC node 9525537954, way 954496233
KLWC node 9583887507, way 890761606
YCTN node 9630663746, way 191306772
SNDV node 9930359846, way 957772384
SNOB node 9997273424, way 240829555
WAPF node 10013516002, way 150718677
CYEY node 10014293053, way 189629235
WADY node 10287618667, way 896377208
WARR node 10288593415, way 312366913
SBBH node 10579026756, relation 5653549
NZPN way 33532923, way 176131209
YMND way 39934890, way 551406304
LFBD way 40841881, way 327966676
LFXA way 42019330, way 237585191
RJSM way 57008923, relation 6723874
LELN way 64042602, way 544737843
UHMW way 75208120, way 969756133
LRCK way 84575399, relation 14671198
CYHZ way 100034801, way 1016694773
RKJJ way 105569841, way 444717696
RPVP way 106045775, way 306989574
MMSM way 136142100, way 1073670135
CYRO way 136325762, way 1093494057
KLCI way 149629957, way 1085225969
KMOB way 152993599, relation 2230082
YCDW way 156760664, way 666916119
WSSL way 175010903, way 381760619
RCLY way 178351999, way 239183338
BGAA way 181362579, way 1036378333
ZSOF way 182657362, way 372448194
YPLM way 187114230, way 847901800
VBAT way 194473869, way 429867187
YPDN way 216110357, way 833764002
FEFE way 222742820, way 1092030270, way 1092030271, way 1092030292
RPLP way 230068618, way 245018563
KPKV way 231600459, way 519707123
VIJO way 239937935, way 239937938
CYDA way 244858643, way 1093461313
FKYS way 255110880, way 1083220442, way 1083229347, way 1101729139, way 1101739969
FACB way 256494501, relation 3437621
CYDM way 261330406, way 1093462293
WALB way 262501824, relation 9048561
CYJN way 264345572, way 1093465483
LTAW way 290826222, way 902229739
N/A way 316395408, way 910289482
SLVM way 322254273, way 775181233
KGUY way 334899311, way 355832730
LPPT way 336112741, way 336146807
KVAD way 341018077, relation 7384858
KELD way 342776964, way 1004817628, way 1004817629
KBJC way 368683795, relation 9104553
FNUB way 369009671, way 767895452
ZSLG way 395981227, way 874071145
CYQT way 416178294, way 1093486045
CYQA way 430197882, way 1093475443
HLLM way 452104533, way 1104971995, way 1104971996
CYQB way 464846018, way 1093475659
VVPQ way 486311356, way 1135316110
LGPA way 606845672, way 1051391904
AYBP way 630470147, way 801369636
EKYT way 645002278, way 665995354
NTAA way 662380667, way 734616444
LPSC way 682009930, way 740424312
GMAG way 689392870, way 689392894
CYPW way 752836765, way 1093472123
CYDB way 753531377, way 1093460950
HELX way 765905189, way 1046451463
SSAZ way 803355873, relation 11761088
AYHX way 804890581, way 841772439
AYIU way 835042085, way 1134925858
KTOI way 884864604, way 1008919572
GAKL way 885091778, relation 12290932
WMKJ way 911199108, way 943848684
WBGN way 913837696, way 1016534636
KGRK way 1009986807, relation 13526712
CYPT way 1093471825, relation 14442127
KBLV relation 122949, relation 8911707
LELC relation 2614519, relation 2614520
YWLM relation 4145466, relation 6263052
VIJR relation 12990105, relation 12990107
KNKX relation 13902660, relation 14514162
5 Likes
2

I’m aware that the list also contains values of the icao-tag that are not real ICAO-codes (e.g. None, F87, RP17, …) but I wanted the list to be as complete as possible to raise awareness of this data issue.

1 Like
3

I believe it can be discouraged to use this tag at ways.
I can prepare MapRoulette quest to quickly fix it if community agree on solution.

1 Like
4

which tag?

5

I think map roulette is a good idea! :+1:

But I do believe that we should discourage the use of aeroway=aerodrome on a node if the same ICAO-code already exists on an area enclosing the node.

But let’s discuss the best approach. This was just a first idea.

1 Like
6

Big problem here is that the wiki itself is confused in what it asks for: Tag:aeroway=aerodrome - OpenStreetMap Wiki

" Preferably this is the airport’s ARP, but it can also be associated with the area around the perimeter of the aerodrome."

" How to map

  • Either create a closed way … around the extent of the airport land.
  • Or draw a node in the centre of the airport and add [aeroway]"

Looking at a few of those examples you provided, in some cases, the same mapper has mapped the area of the airport, & also placed a node in the centre of it, on the same day!

2 Likes
7

One would definitely have to go through that list manually and fix it as needed, as the problems are different:
e.g.

  • HUEN seem to have both a node and closed way, which should be merged to closed way (node contains extra info which should be merged before deleting it)
  • FEFE or FKYS seems someone has broken closed way into 4 separate ways. combining in one closed way needed.
  • LTAW seems to have two diferent pistes. That should be merge into one closed way, or creating a relation and moving tags to it.
  • SLVM seem to be military=airfield sharing ICAO with aerodrome:type=public. Have no idea if that is correct or not, and what a solution should be.
  • N/A is not an ICAO code, so tag should be cleared and a note added why it doesn’t have one.
  • HLLM seems to be two duplicated ways (?) in addition to one correct closed way. probably should delete the erronous dupes.

etc, etc. No way fixing such mess could be automated without causing more damage than good. Interested parties should go and fix them one by one.

Maybe make a MapRoulette task for it to make it easier and distributed across different mappers?

1 Like
8

I’ve had a look at the Australian ones & a similar mix, with some having issues, while others are fine, but just tagged twice - area & node.

So which should it be - area or node?

9

aeroway=aerodrome wiki says:

The aeroway=aerodrome key is used to hold all the main details for an aerodrome. Preferably this is the airport’s ARP, but it can also be associated with the area around the perimeter of the aerodrome.

So, if you know exact ARP node, than that is preferred. If not, it should be mapped on an area.

10

But as I said ^, the wiki also goes on to say

" How to map

Either create a closed way … around the extent of the airport land.
Or draw a node in the centre of the airport and add [aeroway]"

So in two places a paragraph apart, it says a node is best or use an area, but then says draw an area or use a node?

Happy to do either (or both!) but which should it be?

11

Huh, I though I just answered that? Let’s try again.
In the order of preference walk this list. First match wins and stops processing the list:

  • do you know exact ARP (airport reference point) node? If yes, map aeroway=aerodrome+icao=* on that ARP node.
  • if you don’t know ARP but know area around the perimeter of the aerodrome, map aeroway=aerodrome+icao=* on that area.
  • if you don’t know ARP nor area around the perimeter of the aerodrome (e.g. no or bad aerial imagery), as a fallback, pick an approximate center of airport and add aeroway=aerodrome+icao=* on that node (preferably with a note=approximate guessed location).
  • if you don’t have any idea where the airport is, do not map it at all (obviously :smiley:)
1 Like