MultiSolid for the interior and integer storeysAboveGround

A minor release solving two bugs:

1. The interior in LOD2 is composed of multiple solids (one solid for each floor). These solids are now stored as gml:Solid of a gml:MultiSolid. Previously they were incorrectly stored as solids directly "under" with bldg:lod2solid which nevertheless worked fine with some software packages such as FME, but it did not comply to the standard.
2. The bldg:storeysAboveGround is now stored as an integer (previously it was a float, resulting in e.g. 3.0 storeys instead of 3).

Enhancement of the solid representations

This version is focused on increasing the conformance of the generated solids to the standard ISO 19107. There were some errors in the previous versions, which are now solved:

• Faces of solids of buildings (only with shed and hipped roofs) did not have an interior ring "below" the dormers. This version adds a hole below each dormer.
• Garages in solids of LOD2.2 now have a bottom surface. For some reason it was missing in the previous versions.
• Garage is a separate solid in all LODs (so there are no multisolids anymore).

Further, there was a double wall between the building and a garage, hence solids of garages had a smaller volume than it is the case.

The errors in the solids were found thanks to the validator developed at our section (http://geovalidation.bk.tudelft.nl)

Added progress bars for generating the CityGML structure and saving the files

Two progress bars are added for a real-time report on the progress of the two main processes of creating CityGML models:

• Populating the CityGML files with buildings (parallel populating of CityGMLs with one by one building) -- the longest process which can take hours in case of >5000 buildings, so it's important to report on the progress.
• Saving the CityGML files -- with all the invoked options there are almost 400 files, and if large their writing can also take hours.

These two progress bars replace the primitive reporting of every 100th processed building/file which was not reliable.

Python3 compatibility and bug fixes

This release solves the following:

• Random3Dcity is now compatible with both Python2 and Python3
• Addition of gml:upperCorner (some software packages had problems with the generated CityGMLs without gml:upperCorner)
• The CityGML realisation of the LOD3.3 had a problem with surfaces representing embrasures to be stored as multiple MultiSurfaces, which is not supported by CityGML 2.0. This version puts them in a single MultiSurface
• UTF-8 encoding of the saved XML and GMLs

Version 0.1 (initial release)

v0.1

Forced recache of the image in the readme