-
Notifications
You must be signed in to change notification settings - Fork 15
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
Duplicates are not picked under Issue, R12 #127
Comments
Thenk you for sending the test file. In this file both spaces and building storeys have spaces in their IDs Line 16: Spaces cause issues. See https://stackoverflow.com/questions/2277297/can-xml-attributes-have-spaces These errors seem to be preventing both the Reports panel and the Issues panels from completing successfully. We probably can get the Viewer to flag these errors more carefully. Maybe we could replace the spaces with a hyphen. But I hesitate adding this sort of slowdown unless we come across this issue fairly frequently. So far we have only seen this problem in you SAM files. Is there anyway you can prevent the SAM files from doing this? By the way, please note that the file also has CAD Object ID errors. |
thanks for catching this Line 16: Still Report panel is not working for me |
Sorry I forgot to fix adj spaces so this solution is now working. I can run Reports and Issue both in R12 and R13, |
ok.. I have file with two issues... each surface is missing top adjusency |
There are several issues with these surfaces. Exposed to Sun should be set to false not true. Interior floors should have two adjacent spaces not one. Therefore trying to fix something that is quite broken is likely to lead to issues. Best to just edit the XML text for now. In the future there should be a fix button for missing adjacent spaces. Ditto incorrect 'exposed to Sun' values. |
I found this example I mentioned before. We have two duplicates are not picked under Issue - Duplicate Surfaces
Panel 470
andPanel 381
in Space00_153
Space00_153.zip
The text was updated successfully, but these errors were encountered: