by wlbragg » Thu Feb 04, 2016 11:13 pm
I guess we're talking apples and oranges, I think of OSM data as the road, rail and building data, not so much land cover, even though it does have hydro. The NLCD was just land cover and hydro although the one land class (grass I think) was incredibly accurate in outlining the roadway easements. They both in combination produced the best scenery to date (for North America) with the exception of the actual OSM and NLCD combined from source. The massaging done to the NLCD while certainly making it easier on terragear did a disservice to the water ways and smaller land class chunks that were stripped out. The morphing sometimes moved the banks to inappropriate positions and clashed with the accurate OSM roadways.
I always wanted to learn that smoothing algorithm used in grass but it was over my head at the time. A little more work on it could have made the water ways better and also the small strips of deciduous forest which was stripped out making it somewhat less desirable for my area as the actual OSM and NLCD combined from source which I use in my KS an OH custom scenery. But the original is rather heavy and requires at least average computing power and a reasonable graphics processor.
The state of flux in the whole scenery system has left me disenchanted with pursuing any meaningful help, even though I still extend the offer to help.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q