So when you cut the water layer back in, you technically get the same effect whether you fill it or grow the existing. So growing the land cover first is in essence the same as filling it with a cover. What I noticed when I overlay the OSM vector water and shorelines over the raster land cover, is the water/shore line is either not reaching the raster land cover shoreline, matches the raster land cover shoreline or cuts the raster land cover. Right, that is basically how Stuart does it in genVPB.py. I will try that with the raster data as well and see which method works best, growing or filling.Īnd grew the rest of the raster a couple of pixels into the empty areas So what I did with that was I filed all the water with sand or floodland (instead of growing the land) and then I cut the new source of higher resolution water into the vector data. The NLCD water for that scenery was the same as this. On the Kansas scenery I located a better source (or combinations of sources of water) that I wanted to cut into the land cover. While replying to this post I remembered how I used to do it with the vector data. But I intend to go back through the scenery and figure it out. I was not able to duplicate the steps needed to sharpen the shoreline edge the one time I tried it. I'm not using the genvpb script yet, I am executing some of the commend in that script though to build this scenery. The genvpb.py script is written to accommodate this procedure. Locate a higher resolution shoreline or river line (typically vector data) to use as a mask to cut a sharp edge into the land on the new shoreline. Then there is a procedure that you can use to cut that sharp edge into the land cover.
We can increase the resolution to a point where it is possible to get a sharp edge.