urbanopt-rnm-us 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: bfd1fdcbaf0908d6ec884147fd9a26c78429181063cadb15fd5210e89bacd83e
+  data.tar.gz: d8ca20d16669801961c405b8609f6a8adf21bfc2c5862e604e74f90732cece6d
+SHA512:
+  metadata.gz: 9364a3a2cd150e57ee2dff2e1f070065fdc83b35dc519361e9c076393e7f3ee9b290899fef8952b26eae42abc8872989fe5ad8a7ef00b7a1a35397273578a3c7
+  data.tar.gz: 0fcaf071315fac36a51abace8a64f3278d80c854fd6d85bbb7a63affa774cd0a09e7c4196e2aa0e71ee446d7e8f9cd8349e3c068b67d4ae7c235b82f03433a79

data/.gitignore

@@ -0,0 +1,32 @@
+.bundle/
+.DS_Store
+/.yardoc
+/.ruby-version
+Gemfile.lock
+/gems
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/spec/test/
+/spec/test_reopt/
+/tmp/
+/test/
+/lib/measures/test_results
+/lib/measures/*/tests/output
+*.gem
+
+.rubocop*s3*
+
+# rspec failure tracking
+.rspec_status
+
+# Ignore IDE files
+/.idea
+runner.conf
+
+# ignore template files for now
+/template_inputs/*
+test_opendss_catalog.json
+*.sql

data/.rubocop.yml

@@ -0,0 +1,9 @@
+AllCops:
+  Exclude:
+    - gems/**/*
+    - measures/**/*
+    - spec/files/**/measures/**/*
+require: rubocop-performance
+
+inherit_from:
+  - http://s3.amazonaws.com/openstudio-resources/styles/rubocop_v4.yml

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## Version 0.1.0
+
+Initial version of the RNM-US gem.

data/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# URBANopt Contribution Policy
+
+## Version 1.0
+
+The URBANopt team welcomes your contribution to the project. You can contribute to the URBANopt project in several ways: by using the software, reporting issues, contributing documentation, or contributing code back to the project. The GitHub [Contributing to Open Source](https://opensource.guide/how-to-contribute/) guide provides a good overview. If you contribute code, you agree that your contribution may be incorporated into the URBANopt Software Development Kit (SDK) and made available under the URBANopt SDK license.
+
+The contribution process for URBANopt is composed of three steps:
+
+## 1. Send consent email
+
+In order for us to distribute your code as part of URBANopt under the URBANopt SDK [license](https://github.com/urbanopt/urbanopt-scenario-gem/blob/develop/LICENSE.md), we’ll need your consent. An email acknowledging your understanding of these terms and agreeing to them is all that will be asked of any contributor. Send an email to the URBANopt project manager ([see below](#documentation) for the address) including the following text and a list of co-contributors (if any):
+
+*I agree to contribute to the URBANopt SDK. I agree to the following terms and conditions for my contributions: First, I agree that I am licensing the copyright to my contributions under the terms of the current URBANopt SDK license. Second, I hereby grant to Alliance for Sustainable Energy, LLC, to any successor manager and distributor of URBANopt SDK appointed by the U.S. Department of Energy, and to all recipients of a version of URBANopt SDK that includes my contributions, a non-exclusive, worldwide, royalty-free, irrevocable patent license under any patent claims owned by me, or owned by my employer and known to me, that are or will be,necessarily infringed upon by my contributions alone, or by combination of my contributions with the version of URBANopt SDK to which they are contributed, to make, have made, use, offer to sell, sell, import, and otherwise transfer any version of URBANopt SDK that includes my contributions, in source code and object code form. Third, I represent and warrant that I am authorized to make the contributions and grant the foregoing license(s). Additionally, if, to my knowledge, my employer has rights to intellectual property that covers my contributions, I represent and warrant that I have received permission to make these contributions and grant the foregoing license(s) on behalf of my employer.*
+
+Once we have your consent on file, you’ll only need to redo it if conditions change (e.g. a change of employer).
+
+## 2. Scope agreement and timeline commitment
+
+If your contribution is small (e.g. a bug fix), simply submit your contribution via GitHub. If you find a bug, first make sure it is not an already known issue, then report it in the GitHub [issue tracker](https://github.com/urbanopt/urbanopt-scenario-gem/issues) for this repository. If your contribution is larger (e.g. a new feature or new functionality/capability), we’ll need to evaluate your proposed contribution first. We may ask you to revise your materials and make changes to it, which we will then re-review.
+
+## 3. Technical contribution process
+
+We want URBANopt to adhere to our established quality standards. Smaller, non-code contributions may not require as much review as code contributions, but all contributions will be reviewed. Code contributions will initially be in a source control branch, and then will be merged into the official URBANopt repository after review and approval. Any bugs, either discovered by you, us, or any users will be tracked in our issue tracker. We request that you take full responsibility for correcting bugs. Be aware that, unless notified otherwise, the correction of bugs takes precedence over the submission or creation of new code.
+
+### Release Schedule
+
+Contributions should be aligned with the URBANopt release schedule. The URBANopt SDK is currently released publicly two times each year (approximately on the last workday of March and October). There are cutoff dates for when new contributions are allowed for the upcoming release (approximately two weeks before release date). If your contribution is incomplete or comes in past the cutoff date for a release, we reserve the right to hold your code for a later release.
+
+### Coding Standards
+
+Make sure you read and follow the coding standards when writing URBANopt SDK code. Although these standards are not complete or very detailed, they should give you an idea of the style that we would like you to adopt. New additions to the URBANopt SDK must be written using object-oriented programming techniques and practices. Please also look at the URBANopt SDK code itself as an example of the preferred coding style.
+
+### Code Reviews
+
+You will be working and testing your code in a source control branch. When a piece of functionality is complete, tested and working, let us know and we will review your code. If the functionality that you contributed is complex, we may ask you for a written design document as well. We want your code to follow coding standards, be clear, readable, and maintainable, and of course it should do what it is supposed to do. We will look for errors, style issues, comments (or lack thereof), and any other issues in your code. We will inform you of our comments and we expect you to make the recommended changes. New re-reviews may be expected until the code complies with our required processes.
+
+### Unit Tests
+
+We ask that you supply unit tests along with the code that you have written. A unit test is a program that exercises your code in isolation to verify that it does what it is supposed to do. Your unit tests are very important to us. First, they give an indication that your code works according to its intended functionality. Second, we execute your unit tests automatically along with our unit tests to verify that the overall URBANopt SDK code continues to work.
+
+### Code Coverage
+
+We require that your unit tests provide an adequate coverage of the source code you are submitting. You will need to design your unit tests in such a way that all critical parts of the code (at least) are tested and verified.
+
+### Documentation
+
+Proper documentation is crucial for our users, without it users will not know how to use your contribution. We require that you create user documentation so that end users know how to use your new functionality.
+
+For further questions or information:
+
+- Ben Polly\
+URBANopt Project Management\
+ben.polly@nrel.gov\
+(303) 384-7429
+
+URBANopt is funded by the U.S. Department of Energy (DOE) and managed by the National Renewable Energy Laboratory (NREL).
+
+URBANopt is developed in collaboration with NREL, LBNL, and private firms.

data/Gemfile

@@ -0,0 +1,10 @@
+source 'http://rubygems.org'
+
+# Specify your gem's dependencies in urbanopt-scenario-gem.gemspec
+gemspec
+
+# if you want to use local gems during development, use this environment variable to enable them
+allow_local = ENV['FAVOR_LOCAL_GEMS']
+
+# Below is an example of how to configure the gemfile for developing with local gems
+# modify as appropriate

data/LICENSE.md

@@ -0,0 +1,38 @@
+URBANopt (tm), Copyright (c) 2019-2021, Alliance for Sustainable Energy, LLC, and other
+contributors. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list
+of conditions and the following disclaimer.
+
+Redistributions in binary form must reproduce the above copyright notice, this
+list of conditions and the following disclaimer in the documentation and/or other
+materials provided with the distribution.
+
+Neither the name of the copyright holder nor the names of its contributors may be
+used to endorse or promote products derived from this software without specific
+prior written permission.
+
+Redistribution of this software, without modification, must refer to the software
+by the same designation. Redistribution of a modified version of this software
+(i) may not refer to the modified version by the same designation, or by any
+confusingly similar designation, and (ii) must refer to the underlying software
+originally provided by Alliance as "URBANopt". Except to comply with the foregoing,
+the term "URBANopt", or any confusingly similar designation may not be used to
+refer to any modified version of this software or any modified version of the
+underlying software originally provided by Alliance without the prior written
+consent of Alliance.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+OF THE POSSIBILITY OF SUCH DAMAGE.
+*********************************************************************************

data/README.md

@@ -0,0 +1,49 @@
+# URBANopt RNM-US Gem
+
+The URBANopt<sup>&trade;</sup> RNM-US Gem includes functionalities to interface the URBANopt SDK to the RNM-US Gem for the development of a synthetic optimum distribution network in the considered district, given data related to the buildings energy consumption/DER energy generation and location, modeled by the other URBANopt modules. 
+The RNM-US Gem is used to collect required data for the execution of RNM-US, which has been modeled in the other URBANopt modules, translating information provided
+in .json and .csv format into .txt files
+
+## Usage
+
+The URBANopt RNM-US Gem extracts output values from the other URBANopt Gems, to create required input files for the execution of the RNM-US software for the development of a synthetic distribution grid.
+
+RNM-US provides output results in GIS, JSON and OpenDSS format. The results in GIS format outline the graphical representation of the synthetic distribution network modeled, including a visual outline of the street map of the considered district, the location of the consumers, transformers and substations, including the power lines layout.
+The JSON format output provides a set of results regarding size, costs and measures of the synthetic network modelled.
+The OpenDSS format presents results for power system analysis and simulations.
+
+The current functionalities of the RNM-US Gem include the creation of a streetmap text file, the substation txt file and multiple txt files related to the consumers peak loads and profiles and DERs peak generation and profiles.
+The streetmap text file is developed from coordinates information provided by geoJSON feature file input. The customers and generators text files, which define all the network consumers and DG included in the project, are created from their peak electricity demand/generation, and building location, provided by csv and json feature_report files modeled by the URBANopt Scenario Gem.
+The profiles txt files are divided among the consumers hourly profiles of active and reactive power and the DG hourly profiles of active and reactive power for the 2 most "extreme" days of maximum net demand and maximum net generation for the district .
+Finally, the extended profiles txt files provide the active and reactive profiles for each consumer/DG for the whole year. 
+
+
+## Generate input files
+
+The `create_inputs` rake command can be used to generate the RNM-US inputs for an arbitrary command.  You will need to specify the path to the scenario results directory and the path to the GeoJSON feature file:
+
+```bash
+  bundle exec rake create_inputs[/path/to/example_project/run/scenario_name,/path/to/feature_file.json]
+```
+
+### Options
+
+Several options can be set when creating the input files and running the RNM-US process.
+
+1. REopt: Set the `reopt` argument to `true` when initializing the runner to use REopt results in the RNM-US inputs.
+1. Underground cables ratio:  Set the `underground_cables_ratio` field at the project level in the JSON Feature File to specify the ratio of underground cables to overhead cables.  If this field is not set, the default value of 0.9 will be used.
+1. Low-Voltage Only: Set the boolean `only_lv_consumers` field at the project level in the JSON Feature File.  If set to `true`, only low voltage consumers will be considered in the RNM analysis. If this field is not set, the default value of `true` will be used.
+
+## Generating OpenDSS catalog
+
+An OpenDSS-formatted catalog can be generated from the extended catalog with the following command:
+
+```bash
+bundle exec rake create_opendss_catalog[/desired/path/to/opendss_catalog.json]
+```
+
+## Testing
+
+```bash
+bundle exec rspec
+```

data/Rakefile

@@ -0,0 +1,166 @@
+# *********************************************************************************
+# URBANopt (tm), Copyright (c) 2019-2021, Alliance for Sustainable Energy, LLC, and other
+# contributors. All rights reserved.
+
+# Redistribution and use in source and binary forms, with or without modification,
+# are permitted provided that the following conditions are met:
+
+# Redistributions of source code must retain the above copyright notice, this list
+# of conditions and the following disclaimer.
+
+# Redistributions in binary form must reproduce the above copyright notice, this
+# list of conditions and the following disclaimer in the documentation and/or other
+# materials provided with the distribution.
+
+# Neither the name of the copyright holder nor the names of its contributors may be
+# used to endorse or promote products derived from this software without specific
+# prior written permission.
+
+# Redistribution of this software, without modification, must refer to the software
+# by the same designation. Redistribution of a modified version of this software
+# (i) may not refer to the modified version by the same designation, or by any
+# confusingly similar designation, and (ii) must refer to the underlying software
+# originally provided by Alliance as "URBANopt". Except to comply with the foregoing,
+# the term "URBANopt", or any confusingly similar designation may not be used to
+# refer to any modified version of this software or any modified version of the
+# underlying software originally provided by Alliance without the prior written
+# consent of Alliance.
+
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+# IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+# INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+# LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+# OF THE POSSIBILITY OF SUCH DAMAGE.
+# *********************************************************************************
+
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+
+# Load in the rake tasks from the base extension gem
+require 'urbanopt/rnm'
+
+require 'rubocop/rake_task'
+RuboCop::RakeTask.new
+
+task default: :spec
+
+# example rake task
+desc 'Return gem version number'
+task :version_number do
+  puts "Version is: #{URBANopt::RNM::VERSION}"
+end
+
+# create input files for a project
+# pass in the path to the scenario csv, the path to the json feature file, and whether this a reopt analysis (true/false)
+desc 'Create input files'
+task :create_inputs, [:scenario_csv_path, :feature_file_path, :reopt, :opendss_catalog] do |t, args|
+  puts 'Creating input files'
+  # if no path passed in, use default:
+  scenario_csv_path = args[:scenario_csv_path] || 'spec/test/example_project/baseline_scenario.csv'
+  root_dir, scenario_file_name = File.split(File.expand_path(scenario_csv_path))
+  scenario_name = File.basename(scenario_file_name, File.extname(scenario_file_name))
+  run_dir = File.join(root_dir, 'run', scenario_name.downcase)
+  puts "SCENARIO NAME: #{scenario_name}"
+
+  # set up variables
+  feature_file_path = args[:feature_file_path] || File.join(root_dir, 'example_project_with_network_and_streets.json')
+  reopt = args[:reopt] || false
+  reopt = reopt == 'true'
+  opendss_catalog = args[:opendss_catalog] || false
+  opendss_catalog = opendss_catalog == 'true'
+
+  extended_catalog_path = File.join(File.dirname(__FILE__), 'catalogs',  'extended_catalog.json')
+  average_peak_catalog_path = File.join(File.dirname(__FILE__), 'catalogs', 'average_peak_per_building_type.json')
+
+  if !File.exist?(File.join(File.dirname(__FILE__), '..', 'test'))
+    FileUtils.mkdir_p(File.join(File.dirname(__FILE__), '..', 'test'))
+  end
+
+  # generate inputs
+  runner = URBANopt::RNM::Runner.new(scenario_name, run_dir, scenario_csv_path, feature_file_path, extended_catalog_path: extended_catalog_path, average_peak_catalog_path: average_peak_catalog_path, reopt: reopt, opendss_catalog: opendss_catalog)
+  runner.create_simulation_files
+  puts '....done!'
+end
+
+# create input files for a project using defaults
+# pass in the path to the scenario csv, the path to the json feature file, and whether this a reopt analysis (true/false)
+desc 'Create input files with defaults'
+task :create_inputs_default, [:scenario_csv_path, :feature_file_path] do |t, args|
+  puts 'Creating input files with defaulted settings'
+ # if no path passed in, use default:
+  scenario_csv_path = args[:scenario_csv_path] || 'spec/test/example_project/baseline_scenario.csv'
+  root_dir, scenario_file_name = File.split(File.expand_path(scenario_csv_path))
+  scenario_name = File.basename(scenario_file_name, File.extname(scenario_file_name))
+  run_dir = File.join(root_dir, 'run', scenario_name.downcase)
+  puts "SCENARIO NAME: #{scenario_name}"
+
+  # set up variables
+  feature_file_path = args[:feature_file_path] || File.join(root_dir, 'example_project_with_network_and_streets.json')
+
+  if !File.exist?(File.join(File.dirname(__FILE__), '..', 'test'))
+    FileUtils.mkdir_p(File.join(File.dirname(__FILE__), '..', 'test'))
+  end
+
+  # generate inputs
+  runner = URBANopt::RNM::Runner.new(scenario_name, run_dir, scenario_csv_path, feature_file_path)
+  runner.create_simulation_files
+  puts '....done!'
+end
+
+# run simulation and retrieve results
+# pass in the path to the scenario csv, whether this is a reopt analysis (true/false), and whether to use localhost RNM API (true/false)
+desc 'Run Simulation'
+task :run_simulation, [:scenario_csv_path, :reopt, :use_localhost] do |t, args|
+  puts 'Running simulation'
+  # if no path passed in, use default:
+  scenario_csv = args[:scenario_csv_path] || 'spec/test/example_project/run/baseline_scenario'
+  root_dir, scenario_file_name = File.split(File.expand_path(scenario_csv))
+  scenario_name = File.basename(scenario_file_name, File.extname(scenario_file_name))
+  run_dir = File.join(root_dir, 'run', scenario_name.downcase)
+
+  rnm_dir = File.join(run_dir, 'rnm-us')
+  reopt = args[:reopt] || false
+  reopt = reopt == 'true'
+
+  use_localhost = args[:use_localhost] || false
+  use_localhost = use_localhost == 'true'
+
+  if !File.exist?(rnm_dir)
+    raise 'No rnm-us directory found for this scenario...run the create_inputs rake task first.'
+  end
+
+  puts "scenario dir path: #{run_dir}"
+  puts "reopt: #{reopt}"
+  puts "use_localhost: #{use_localhost}"
+  api_client = URBANopt::RNM::ApiClient.new(scenario_name, rnm_dir, use_localhost = use_localhost, reopt = reopt)
+  # zip inputs
+  api_client.zip_input_files
+  api_client.submit_simulation
+  api_client.get_results
+
+  puts '...done!'
+end
+
+# Create opendss catalog from extended catalog
+# pass in the path and filename where the OpenDSS catalog should be saved
+desc 'Create OpenDSS catalog'
+task :create_opendss_catalog, [:save_path] do |t, args|
+  puts 'Creating OpenDSS catalog'
+  # if no path passed in, use default (current dir):
+  save_path = args[:save_path] || './opendss_catalog.json'
+
+  extended_catalog_path = File.join(File.dirname(__FILE__), 'catalogs', 'extended_catalog.json')
+  opendss_catalog = URBANopt::RNM::ConversionToOpendssCatalog.new(extended_catalog_path)
+  # create catalog and save to specified path
+  opendss_catalog.create_catalog(save_path)
+
+  puts "Catalog saved to #{save_path}"
+  puts '....done!'
+end

data/catalogs/average_peak_per_building_type.json

@@ -0,0 +1,94 @@
+[
+  {
+    "building type": "Office",
+    "sub-type": "SmallOffice",
+    "average peak demand (kW/ft2)": 0.0032,
+    "floor_area (ft2)": 5500
+  },
+  {
+    "building type": "Office",
+    "sub-type": "MediumOffice",
+    "average peak demand (kW/ft2)": 0.0058,
+    "floor_area (ft2)": 53628
+  },
+  {
+    "building type": "Office",
+    "sub-type": "LargeOffice",
+    "average peak demand (kW/ft2)": 0.0033,
+    "floor_area (ft2)": 498588
+  },
+  {
+    "building type": "School",
+    "sub-type": "PrimarySchool",
+    "average peak demand (kW/ft2)": 0.0043,
+    "floor_area (ft2)": 73960
+  },
+  {
+    "building type": "School",
+    "sub-type": "SecondarySchool",
+    "average peak demand (kW/ft2)": 0.0056,
+    "floor_area (ft2)": 210887
+  },
+  {
+    "building type": "Retail",
+    "sub-type": "Stand-aloneRetail",
+    "average peak demand (kW/ft2)": 0.0037,
+    "floor_area (ft2)": 24962
+  },
+  {
+    "building type": "Mall",
+    "sub-type": "StripMall",
+    "average peak demand (kW/ft2)": 0.0037,
+    "floor_area (ft2)": 22500
+  },
+  {
+    "building type": "SuperMarket",
+    "average peak demand (kW/ft2)": 0.0077,
+    "floor_area (ft2)": 45000
+  },
+  {
+    "building type": "Restaurant",
+    "sub-type": "QuickServiceRestaurant",
+    "average peak demand (kW/ft2)": 0.0144,
+    "floor_area (ft2)": 2500
+  },
+  {
+    "building type": "Restaurant",
+    "sub-type": "FullServiceRestaurant",
+    "average peak demand (kW/ft2)": 0.0115,
+    "floor_area (ft2)": 5500
+  },
+  {
+    "building type": "Hotel",
+    "sub-type": "SmallHotel",
+    "average peak demand (kW/ft2)": 0.0029,
+    "floor_area (ft2)": 43200
+  },
+  {
+    "building type": "Hotel",
+    "sub-type": "LargeHotel",
+    "average peak demand (kW/ft2)": 0.0038,
+    "floor_area (ft2)": 122120
+  },
+  {
+    "building type": "Hospital",
+    "average peak demand (kW/ft2)": 0.0064,
+    "floor_area (ft2)": 241351
+  },
+  {
+    "building type": "Outpatient",
+    "average peak demand (kW/ft2)": 0.0071,
+    "floor_area (ft2)": 40946
+  },
+  {
+    "building type": "Warehouse",
+    "average peak demand (kW/ft2)": 0.0017,
+    "floor_area (ft2)": 52045
+  },
+  {
+    "building type": "Apartment",
+    "sub-type": "MidriseApartment",
+    "average peak demand (kW/ft2)": 0.0017,
+    "floor_area (ft2)": 33740
+  }
+]