The type of the "location" member

[balazsdukai]

Does the location property in a CityObject require a specific value type (e.g. a MultiPoint geometry), or it can have any type of value?

The source of my confusion is that the specs define that the Building and Bridge CityObject types can have an address member, which can contain a location, and this location must be a MultiPoint geometry. This is clear.
However, the second example of the CityObjectGroup contains a location under attributes (not address), and this location is a regular string.

This suggests that if location is a member of the address then it must be a MultiPoint, but location can also be added anywhere else, in which case it is a regular attribute, or it can also be a geometry, or ... ?

Should we set the schema for the location property? For example, enforce it to be a Geometry, regardless where is it. If it is a member of address, then it must be a MultiPoint.
This would be a breaking change too, I think.

Any thoughts? @hugoledoux ?

[hugoledoux]

If it's a child of "attributes" then everything goes: CityJSON doesn't prescribe or enforce any specific attributes (unlike CityGML; this one of the few major differences).

If it's the child of an "address" then yes it must be a MultiPoint.

Agreed that it could lead to confusion, so better to rename the "location" in the CityObjectGroup snippet to "municipality"