SimCenter Forum

Thank you for using the SimCenter forum!

To help us better identify the issue, please provide us with some additional information.
1) Have you observed this issue with multiple buildings?
2) Could you please post the coordinates of the building(s) you have had this problem with?

Thank you for catching this issue!

I was able to recreate this problem. I am working on a patch and will post a fix soon.

Please stay tuned!

Thank you for using the SimCenter Forum!

I am happy to look into this issue and get it sorted out for you. For this purpose, could you please provide the bounding box coordinates, number of buildings and seed number you defined for your building inventory?

Here is the CSV file I get from BRAILS backend. It contains the building attributes required for performing earthquake damage and loss calculations for 1,569 buildings in the Mission Beach, CA area.

A few things to note about this inventory:
1) It omits 126 (1695-1569=126) buildings in Mission Beach for which street-level imagery could not be obtained.
2) The occupancy type column contains data imputed from the National Structure Inventory through BRAILS, as the current version of the software cannot obtain building occupancy classes at HAZUS-level granularity
3) This inventory contains a 13-floor hotel building. The simulation results for this building should be evaluated carefully, given that the HAZUS methodology may not be sufficiently detailed for this type of building.

I hope this helps!

There has been a slight change in the way BRAILS stores building imagery. It now saves street-level and aerial imagery in your working directory in the tmp/images/street and tmp/images/satellite folders, respectively.

I hope this helps!

Apologies for the slow response; I saw this follow-up question just now!

You are seeing this error because there are a total of 11 invalid footprint geometries (in this case, multi polygons that are not nested) in the provided GeoJSON. Anytime FootprintHandler hits one of these geometries, it throws a fatal error. Please see attached images for five randomly selected samples from these invalid footprint geometries.

I pushed an update to FootprintHandler so that it successfully bypasses such footprint issues. Please let me know if you have any problems after updating your BRAILS setup to the latest.

On a side note, I see that this GeoJSON was generated using OSM. When I look at the current footprints for the 11 problematic locations in the provided GeoJSON, I currently see valid footprints. I wonder if this issue has to do with the way the footprints were extracted from OSM. If you can share more information on the specific process used to obtain these footprints, I might be able provide suggestions that may eliminate this type of footprint extraction issues.

Thank you for using the SimCenter Forum!

I believe you are getting this error because of the way your bounding box input is defined. For bounding box entries, BRAILS expects the location parameter defined as a tuple in the format location=(lon1,lat1,lon2,lat2). Here the longitude and latitude values are the coordinates of the opposite vertices of a rectangular bounding box (at the moment, BRAILS only takes rectangular bounding box input).

For instance, one can get a random set of 100 buildings contained in the West Los Angeles bounding shown in the attachment by defining the bounding box based on the coordinates of its top left vertex (-118.4546,34.0111) and bottom right vertex (-118.3866,34.0436) via the syntax:

invGenerator = InventoryGenerator(location=(-118.4546,34.0111,-118.3866,34.0436),
                                  nbldgs=100, randomSelection=True,
                                  GoogleAPIKey="YOUR-API-KEY")

I hope this helps! Please let me know if you run into any other issues.

Hi Niko,

Thank you for using the SimCenter Forum, and apologies that this message escaped our attention until today.

Something about this image seems to trigger an error with the way FacadeParser computes the roof run. For easier troubleshooting, any chance you could share the latitude/longitude of the building location that results in this error?

Thank you