Hugo Ledoux
Hugo Ledoux
they point to the "github-pages" branch, while it should be "master"
Like percentile used for diff classes, date, etc.
then we can have a schema for the validation, way easier then writing and updating the code. Reading JSON is also simpler in C++, ie the dependency is less of...
tried to have top of trees only by keeping first return only and creating a TIN, but that looks plain weird in cities: https://dl.dropboxusercontent.com/s/e4p52a24rqpe557/2016-02-04%20at%2009.27.png Perhaps solution is to do this...
following that structure: http://keepachangelog.com/en/1.0.0/
I mean this: https://github.com/tudelft3d/val3dity/commit/1706433bc337266a42446a9d55860c9654418151
@arruga asked for this in #134 but better to have it separate to not forget
With specific attributes, and document them, or just new surfaces, not just `"+ThermalSurface"` eg ```json { "type": "RoofSurface", "slope": 16.4, "children": [2, 37], "solar-potential": 5 } ```
One of the main criticism/discussion-point/question is that CityJSON uses, for the geometries and textures, an "indexed scheme" instead of a "feature-based approach". An indexed scheme means that the coordinates (x,y,z)...