The IBM Envizi- Emissions API is a comprehensive solution for organizations to calculate, track, and report greenhouse gas (GHG) emissions across their operations and value chains. This API provides standardized methodologies for emissions calculations aligned with the Greenhouse Gas Protocol, enabling businesses to meet regulatory requirements and sustainability goals.
To get started with the Emissions API follow these steps:
- Sign up at the IBMid sign up page.
- You will be sent an invite email to join to create an account.
- Login, explore, calculate!
- sphinx-build/: Contains the Sphinx documentation source files and build configuration
- docs/: Contains the built HTML documentation for GitHub Pages
- notebooks/: Contains Jupyter notebooks demonstrating API usage and examples
- tutorials/: Step-by-step guides for using the API
- samples/: Real-world application examples
The documentation is built using Sphinx with nbsphinx for integrating Jupyter notebooks. The main documentation is organized into:
- Overview: General information about the API
- Tutorials: Step-by-step guides for using different API features
- Samples: Real-world examples demonstrating API applications
- Python ≥3.8 and ≤3.11
- Sphinx
- nbsphinx
- Jupyter
- Other dependencies listed in requirements.txt
Removes all build artifacts and temporary files.
cd sphinx-build
make cleanCopies notebooks from the notebooks directory to the Sphinx source directory for inclusion in the documentation.
cd sphinx-build
make notebooksBuilds the HTML documentation.
cd sphinx-build
make htmlRuns clean, notebooks, and html targets in sequence to perform a complete documentation rebuild.
cd sphinx-build
make allBuilds the documentation and copies the output to the docs directory for GitHub Pages publishing.
cd sphinx-build
make pagesAfter building the documentation, you can view it locally using:
# Open the locally built documentation
open sphinx-build/build/html/index.html
# Or view the GitHub Pages version
open docs/index.html- Update the repository content, could be documentation and/or notebooks
- Build the documentation with
make all - Test the documentation locally
- When ready to publish, run
make pages - Commit and push changes
Note: Don't commit the /notebooks that gets copied over within the /sphinx-build directory on running the make all target