-
Notifications
You must be signed in to change notification settings - Fork 56
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
Recalculate bbox when LoD filter is used for CityGML exports #239
Conversation
@@ -184,6 +190,11 @@ private void doWork(DBSplittingResult work) { | |||
AbstractGML object = exporter.exportObject(work.getId(), work.getObjectType()); | |||
if (object instanceof AbstractFeature) { | |||
feature = (AbstractFeature) object; | |||
|
|||
if (useLodFilter && feature.isSetBoundedBy()) { | |||
feature.setBoundedBy(feature.calcBoundedBy(bboxOptions)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The feature here is top-level. How about sub-features, should their bbox also be recalculated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is an option |
Well, this option controls whether a Or did you mean something else? |
Yes, that is what I mean. OK, it sounds impossible to reccalculate the CityModel envelope based on the LOD filter. |
Well, not impossible in general. But this would require changing the dataset after it has been written. This cannot be done if we write to a stream though. In such cases, we would need some temporary export dataset which is only sent to the stream once it has been adapted. Thus, the stream would have to wait long for a response... Anyway, at least no easy and nice solution in any case. |
yes, we could improve this in future in a separate PR once we find a better solution. |
This PR addresses #104.