Version: 1.0.0
Frequency: Consistently
Severity: High
Context: 2024 Airport Package, unable to modify water
Bug description: Using an apron or polygon; or water polygon does not enable editing of any water to remove or change.
Repro steps:
Attachments:
I’ve encountered the same issue. Water polygons are pretty useless at both removing and adding bodies of water.
Would you be able to specify the locations (airport or lat/lon) where you are trying to use the feature? Even better - if you have a sample DevMode project that illustrates the issue, would you be able to send it through Private Content?
Best regards,
Eric / Asobo
@EPellissier Hello Eric,
This happens at all airports where water is present around the airport.
The one I have is KRSW. I believe it might be only photogrammetry areas but I could be wrong.
A couple other airports where it’s happening:
KORF
KTPA
KMCO
I will make a sameple DevMode project for you.
Regards,
Andrew
Wouldn’t this then just be the issue that you can’t modify terrain in PG areas?
Or has progress been made on that front?
I’ve had a bit of conundrum with that too, but editing water is a bit different I think.
There’s a thread on the main forum about the water mask bleeding through at the historic scenery of Meigs Field. Not sure if that has an exclusion that’s being ignored or if it’s related to this.
I think a big part of the problem is that water doesn’t conform to the shape of the polygon tool.
This screenshot should be water with straight edges as per my polygon tool. Instead its leaking out everywhere.
I understand the more natural look, but we need to be able to define exact shapes of water bodies.
*we also need to be able to define the exact shapes of water bodies.
The above situation works well for 95% of definitions, that the water fills in the terrain at the altitude of the water.
@EPellissier Any update on this fix?
Hello @Verticalsim
I was able to remove most of the water with a polygon with water exclusion set to “pond”.
There are still some puddles left for some reason and actual polygon boundaries are unclear. I’ll log a bug for this and see if we can have something a bit more predictable.
Regards,
Sylvain
@FlyingRaccoon Thank you for the update 
