Correction: Source used was Bing aerial imagery (-4.70; 7.77); Strava

Correction: Source used was Esri World Imagery, Mapillary

Correction: Source used was Bing aerial imagery (-4.77; 1.46); Strava

My decision to not exclude the parking area (way/240341905) from the aerodrome was based on its vicinity to the military feature (way/772045900). Reviewing Mapillary (https://www.mapillary.com/app/?pKey=272903452003597), I find that your suggestion of excluding this parking area from the aerodrome is a good choice. I have gone ahead and adjusted the aerodrome.

Happy Mapping!

Hello 5m4u9! Similar to the airport in changeset/143085148, I have not included the airport entrance and parking area in the aerodrome, considering the OSM wiki states that an aerodrome is “A place from which flight operations take place. Term includes airports, aerodromes, airfields, and landing strips whether international, private, military or otherwise” (osm.wiki/Aeroways). I have adjusted the aerodrome to follow the clear separation of the airport access roads and the controlled flight operations area, indicated by fence lines that can be seen in satellite imagery, such as way/1218082843 and way/1218082845.

Thank you!

Hello 5m4u9, thank you for your contribution and input regarding the boundary of the aerodrome! While there is a fence line shared by the public airport and nearby military area, the OSM wiki states that an aerodrome is, “A place from which flight operations take place. Term includes airports, aerodromes, airfields, and landing strips whether international, private, military, or otherwise” (osm.wiki/Aeroways). The roads accessing the airport terminal are not a part of where flight operations are occurring, therefore, I have not included them in the aerodrome boundary.

Thank you, and happy mapping!

Correction: Source used was Esri World Imagery, Mapillary

Correction: Source used was Mapbox Satellite, Strava

Correction: Source used was Esri World Imagery

Correction: Source used was Maxar SecureWatch Imagery 2023-05-05.

Hello felipeeugenio, upon returning to the area and inspecting Mapillary further, I can now see that construction may still be ongoing. I have gone ahead and re-added the segment that was removed. Thanks for reaching out and happy mapping!

Correction: Source used was Bing aerial imagery.

Hello! The highway in question way/1102991848 appears to be temporarily unusable after a presumable flooding incident of the nearby river. I saw evidence of this in a Maxar SecureWatch image from 2022-09-28. I chose the "abandoned" prefix instead of "destroyed," because this situation is hopefully temporary. According to the lifecycle prefix page (osm.wiki/Lifecycle_prefix#Stages_of_decay), "abandoned" is defined as requiring ‘considerable effort’ to make the highway functional again, which seems the most appropriate at this time.

Correction: Source used was Esri World Imagery.