Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MultiPoint of address requires "lod" property #9

Closed
clausnagel opened this issue Oct 12, 2017 · 1 comment
Closed

MultiPoint of address requires "lod" property #9

clausnagel opened this issue Oct 12, 2017 · 1 comment

Comments

@clausnagel
Copy link
Contributor

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.

@hugoledoux
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants