add from_open_street_map() Methods to Model Class

[AntoineDao]

Open Street Map is a strongly formatted and rich data format to host building information. I reckon adding this as a method might be a bit of a stretch as it would involve writing an XML parser for OSM etc... But might as well drop the issue here in case it gains traction.

[chriswmackey]

This is a good idea. I would just note a few things:
Getting openstreetmap solids into building typologies might involve some math that is pretty hard to do. Doing intersections of solids with planes is a pretty tough and it's something that I plan on relying on Rhino for for current building solids workflows.
I think openstreetmap also has polygon information, which would be a lot easier to process (just like geojson).

One thing I would also note is that, if we add a method for this, we should write out from_open_street_map() because this can get very confusing with the .osm file type that is used to represent OpenStudio models.

[AntoineDao]

Ah my thinking was to use the following information from Open Street Map:

• footprint geometry
• building height
• building type
• building age

The idea was that OSM is a strongly typed semantic map (more so than GeoJson which can hold the same information but name of the key values is likely to vary more).

Agreed about using from_open_street_map()! Ideally this method would also be able to do it using just latitude and longitude to download osm data from a fixed server.

Is this something you reckon I can start working on or should I put it on hold like the from_geojson() stuff?