Dear Ewen, thank You!!! :)

Hello Andy,

According to Bing aerial imagery, OS OpenMap Local (October 2022) and a state of this way (way/284473684) which connect to Trawlers Farmhouse service road, I was reclassify road segment from track to service because the higher road classification "service" persist inside this road network (way/1037358902).

Regards,
Aleksandar

Hello Andy,

According to Bing aerial imagery, Mapillary and a state of this way (way/399443425), I was reclassify road segment from track to service because the higher road classification "service" persist inside this road network (way/502064102,w954234146). Also, added barrier=gate tag which is visible from aerial imagery.

Regards,
Aleksandar

Hello Guido,

I fixed road geometry issues.

Thanks and regards,
Aleksandar

Hello Elliott,

I restored previous tag.

Thanks,
Aleksandar

Hello あんこ, I removed tag natural=coastline and added area=yes. If there is a part of river promenade and is for pedestrians, there can be added additional tag highway=footway.

Regards, Aleksandar

I would agree that OSM has some undefined tagging guidelines and options for MIL/CIV airports. OSM has a significant number of approaches in polygonization globaly for these type of aerodrome. If You have suggestion for better mapping solutions here in OpenStreetMap community, be free and share proposal at OSM Wiki pages in section for aeroway.
Local community has mapped these aerodromes as separated entities and that is dataset which we have. In these case IATA code refer to Aalborg Airport, not to Aalborg Air Base.

ICAO code is referent for both.

Your mention, AMDB standard is not related to OSM. Is not official implemented in OpenStreetMap to present airport data models which refer to different type of presenting data.

Please provide source where is explicit explained to not divide airfields into two parts. As OSM Wiki related articles about tagging and mapping there no defined to avoid these situations. In many cases depend on country, the aerodrome spatial area shares same runway or have separated runways for military/civilian purpose. The host/owner may be military or civilian. Also, issues can produces different information starting with name, contact information and Wikipedia articles, etc.
Above all, issue is routing to proper location on civilian/terminal part. If there is one entity, they refer to aerodrome name and find short route to location. There is no separation between civilian or military part, they route to shorter route instead of finding a correct result. Resulting problem can be arrival to entrance at military airbase instead civilian airport.

The IATA code purpose is not for military using or airstrip attributes. A quote from Wikipedia explains: IATA airline designators are used to identify an airline for commercial purposes in reservations, timetables, tickets, tariffs, air waybills and in telecommunications.

The OSM Wiki for military=airfield (military=airfield) has wrong tagging guideline where is IATA code included in instruction.

Please provide source where is explicit explained to not divide airfields into two parts. As OSM Wiki related articles about tagging and mapping there no defined to avoid these situations. In many cases depend on country, the aerodrome spatial area shares same runway or have separated runways for military/civilian purpose. The host/owner may be military or civilian. Also, issues can produces different information starting with name, contact information and Wikipedia articles, etc.
Above all, issue is routing to proper location on civilian/terminal part. If there is one entity, they refer to aerodrome name and find short route to location. There is no separation between civilian or military part, they route to shorter route instead of finding a correct result. Resulting problem can be arrival to entrance at military airbase instead civilian airport.

The IATA code purpose is not for military using or airstrip attributes. A quote from Wikipedia explains: IATA airline designators are used to identify an airline for commercial purposes in reservations, timetables, tickets, tariffs, air waybills and in telecommunications.

The OSM Wiki for military=airfield (military=airfield) has wrong tagging guideline where is IATA code included in instruction.

Hello olehz,

As a military part of aerodrome, IATA code is not valid and useful. The civilian part of aerodrome (way/665995354) has IATA code and may serves the purpose. Please, remove duplicate IATA code from military feature.

Regards,
Aleksandar

Hello olehz,

As a military part of aerodrome, IATA code is not valid and useful. The civilian part of aerodrome "Aéroport de Guelmim" has IATA code and may serves the purpose. Please, remove duplicate IATA code from military feature.

Regards,
Aleksandar

Hello muralito,

From changeset history and imagery, there no more "Aerodromo de Dom Pedrito" at this location. The terminal tag is used for marking building at an airport where passengers transfer between ground transportation and the facilities. In this case, the building was change purpose.

Regards,
Aleksandar

Hello tomhukins,

I added second part of way (way/83250677) according to OS OpenMap Local (October 2022) map rendering geometry of road and inherit a name which already added by other user. My changeset comment was generalised as: "Adding missing roads and names in UK", which don`t include notice about what exactly was changed and how it`s changed. I agree that the changeset comment should have been different.

Regards,
Aleksandar

Hello TreeTracks

This is probably result of some kind of import for Goulburn River and attributes from vicroads database (http://data.vicroads.vic.gov.au/metadata/Attribute_Table_Viewlist_6dbc974a.asp.html).
You may contact Australia OSM community for removing unnecessary tags which is not related for OSM tagging.

The origin way id before splitting riverbank, which result new id was way/503331935.

Regards,
Aleksandar

Hello harahu,

I just resolve issue resulted from Keep Rigt QA tool where road and water surface intersect each other. According to Maxar Premium Imagery, Bing aerial imagery and Esri World Imagery and Your dataset import for water surface, the flooded road segment is not usable for any type of vehicle.

If you have some tagging suggestion for this case, be free to add.

Regards,
Aleksandar

Hi Larmax,

I’ve added names according to this thread and opinions stated here https://community.openstreetmap.org/t/datasets-in-josm/7320/4 .
I can verify and add name:sv and name:fi for Kimito/Kemiönsaari, but wanted to verify with you: if both name:fi and name:sv are present, name=* should refer to Swedish name?
Also if you find that there are any other places in Finland that need to prioritize Swedish names as name values, please send the list to community channel here https://community.openstreetmap.org/t/datasets-in-josm/7320/4 ), so we can be aware of it as well.

Regards,
Aleksandar 

Hello Qitay,

According to IATA identifier, the ANA code refer to Maasai Mara national park area, Angama Mara safari lodge.
The Wikipedia article: https://en.wikipedia.org/wiki/Angama_Mara_Airport
OSM link: way/884013049

Regards,
Aleksandar

Hello MJames,

I have noticed that are added ICAO code "YMND" for airfield which is identical with Maitland Airport (way/39934890). Please, can you ivestigate this issue because this is categorised as airstrip and maybie have only local code indetifier ?

Thanks,
Aleksandar

Hello,

I have noticed that are added ICAO code "YCDW" for airfield which is identical with Dallachy (Cardwell) Aerodrome (way/666916119). Please, can you confirm which code is correct because it is on separated location?

Thanks,
Aleksandar

Hello AndersAndersson,

I see that some unnamed road segments have a name by my side. That is fixed now, my mistake.

Thanks,
Aleksandar