Have released my housing fill template to create houses where there are no housing footprints in OSM. The script is run separately from my other template which will continue to be developed. This means you will need to insert references to the 2 TOC files into your airport TSC file as indicated in the Honolulu (PHNL) TSC below.
The template uses residential roads to decide where to place the houses. This has some limitations. For instance it is not possible to have it align the houses with the photo imagery of the houses, and you will find some small areas with no houses. Houses will not appear on other road types as these proved difficult to use successfully. The script is also limited to only houses, no larger buildings are generated .
This template is designed so it won't create overlaps of buildings, or plants generated by my other template and has no impact on street lighting. The template is not 100% perfect so you may find the odd house where it shouldn't be, but houses are filtered out of most areas where they shouldn't be.
As the template uses residential roads, and these sometimes appear in rural areas in OSM, I found you can often get lines of houses on a single street in the middle of a rural area. To combat this problem, I create an include polygon using Google Earth to define the urban areas of my cities and towns. You can run the script without an include but you will need to comment out a few lines of the template. The lines to comment out are documented in the script itself. The script makes no allowances for exclude polygons, as it is a lot easier to define an urban area to include than it is to define a rural area surrounding an urban area to exclude.
You can have multiple polygons in your google earth include.kml file. And I also create the polygons for my whole city area, then use the same include for each level 10 area I am generating cultivation for, so there is no need to try and align the size of your include with the size of the OSM data area. When creating your include polygons in Google Earth it is best to set opacity to 40% so you can see the underlying urban areas as you create the polygon. This appears on the "style color" tab on the popup window that appears when creating or editing Google Earth polygons.
Its a pretty quick process once you get the hang of it. Anyone wanting to know how to create Google Earth Polygons should look at the original "learning cultivation" video. The same method is used to create include polygons required here, as detailed in the video to create exclude polygons. https://www.aerofly.com/dokuwiki/doku.php/sdk:scenerydev4. Larger city areas may not require the use of an include polygon.
Unlike my original template which is always attached to the first post in this thread, this one is attached to this post. Just rename it as .spc, create your include polygon (or comment out the noted lines) and you're good to go. As with my other template this one also works best when you are using a level 10 sized area from OSM. Run time was 5 minutes for my level 10 sized area in Honolulu and 40 minutes for my level 10 area for New Orleans which is mostly houses. The resulting TOC files are not large but it does require a lot of calculations to create them. My other similar sized test areas took 5 to 10 minutes. CPU usage peaks at 90%+ for some parts of the script but varies from step to step to as low as 15%.
Example of a Google Earth include polygon. Not separate polygons for the satellite towns to the north and north east of the main city area.
Example of houses created for Honolulu, before on the left and after on the right.
Example of what can happen when you don't use an include polygon to define your urban areas.