Skip to content

Services

Sabu services are focused runtime components. Each service is designed to perform a specific responsibility within the broader framework.

The naming convention for services is:

jug_domain_specifics

In this convention, jug means service.

Service list

Service Purpose Status
jug_lca_buildings Calculates building-level embodied and end-of-life carbon emissions from GeoJSON input Main implemented service
jug_gis_cities Supports city-scale geospatial data preparation workflows Planned for fuller Sabu architectural alignment
jug_gis_validation Supports validation of geospatial datasets Planned for fuller Sabu architectural alignment
jug_sim_buildings Intended for future scenario-based building simulation workflows Planned; not yet developed

Main service: jug_lca_buildings

jug_lca_buildings is the current reference implementation for the Sabu architecture.

It demonstrates the main service design principles:

  • explicit input structure,
  • API-based execution,
  • direct Python execution,
  • Docker-based execution,
  • generated artifacts,
  • reusable outputs,
  • shared infrastructure through sabu-chassis.

Geospatial services

jug_gis_cities and jug_gis_validation support the geospatial side of the Sabu workflow.

The intended future service chain is:

geospatial preparation → geospatial validation → carbon emissions calculation

In this chain:

  1. jug_gis_cities prepares geospatial data.
  2. jug_gis_validation validates processed geospatial data.
  3. jug_lca_buildings calculates building-level carbon emissions from prepared inputs.