You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go from GeoJSON footprints to FloorSpaceJS models. Users can then subdivide the footprint and assign space types, then reimport the FloorSpaceJS models back into UO and use the more detailed geometry in UO analysis.
Also, as part of this effort, please review the current FloorSpaceJS UO Workflow to determine if the OSM model is still required (in addition to the floorspaceJS). Adjust as needed, adjust the documentation, and potentially relax the file extension requirements on the Detailed_OSM field)
The text was updated successfully, but these errors were encountered:
Do we want to focus on supporting this first, or a workflow to go from OpenStreet Maps to GeoJSON? There seems to be a script to do this, we could work on integrating it to the SDK? This could be useful for the prototype district workflows as well.
Go from GeoJSON footprints to FloorSpaceJS models. Users can then subdivide the footprint and assign space types, then reimport the FloorSpaceJS models back into UO and use the more detailed geometry in UO analysis.
Also, as part of this effort, please review the current FloorSpaceJS UO Workflow to determine if the OSM model is still required (in addition to the floorspaceJS). Adjust as needed, adjust the documentation, and potentially relax the file extension requirements on the Detailed_OSM field)
The text was updated successfully, but these errors were encountered: