cityjson
MultiPoint of address requires "lod" property
The "location" property of a building "address" is defined to be a "MultiPoint" geometry. As per definition in the v0.3 schema, a "MultiPoint" requires an "lod" property.
Whereas "lod" is important for spatial properies of features, having different LoDs for the location of an address does not make too much sense.
Imho, the "lod" property should remain mandatory for feature geometries. Hence I suggest adding a new "LoD-less" multi point geometry for addresses.
I agree. I can fix this easily.
But is there a need to have a "lod" for a "MultiPoint" at all actually? I could imagine for terrains, if only the points are stored... but I didn't include this in CityJSON, only TINs. Other uses you can think of?
