Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
The core validation stayed exactly the same, no changes. Only these were modified:
- the report is slightly changed: the CityObjects/Primitives subdivision in the report is replaced by Features having Primitives, where Features are the top-level objects, containing one or many Primitives. This is done to allow other data model to be used as input, eg IndoorGML is coming soon!
- pytest allows to specify the binary to use if not under 'build/'
- with Windows binaries, finally!
- fixed bug where inner rings of gml:Polygon wasn't read properly when that polygon is referenced by an XLink.
Each surface are now triangulated with a constrained Delaunay triangulation (CDT) instead of a non-Delaunay one. That improves stability, especially when there are nearly collinear vertices in a surfaces: slivers are avoided, which means less errors 204, and less wrong errors caused by numerical stability.
Explained here what is going on: CGAL/cgal#2733
This releases fixes it with a hack, but I think this is solid (touch wood).
Almost a complete re-write, with:
- support for all 3D primitives in ISO19107
- support for new formats: CityJSON, OFF
- completely new reports: in JSON and HTML (browsable version)
- complete unit test suite (with pytest)
Validation can now consider CityGML Buildings when validating, ie only the primitives used to represent Buildings are validated, and the report contains the Building ID for each primitive.
Plus, the summary shows how many Buildings are valid/invalid; keep in mind that one Building can be represented with both multiple Solids and/or MultiSurfaces.
prevents collapsed triangles given as input from crashing return error 104 instead, as it should.