Third-party integration
LCAbyg Json guide
It's possible to use the json format as a third-party integration in LCAbyg 5. Here you'll find an overview of guides and webinars on the topic.
Webinars
- Introduction to the json format and its uses in LCAbyg 5
- Building your own library via json
- Creating EPDs from the json format
Watch the webinars onLCAbyg's YouTube channel.
Documentation
Json import guide
Includes an example project for import into LCAbyg 5.2.1.0. We recommend updating to the latest version of LCAbyg before following the guide.
Json export guide
Describes how to export projects and results as json files.
Json scenario guide
Describes the newer functionality for creating scenarios, with an example project based on a single-family home (for LCAbyg 5.2.1.0).
Testing json files
The best way to test whether a json file is valid is to import it into LCAbyg incrementally. The guide package includes a debug version (lcabyg_debug.exe) that prints error messages in the terminal. Note that LCAbyg won't work if you click into or type in the terminal — restart LCAbyg after making changes.
Common errors
- The example project won't open
- Often caused by version mismatches between the example project and LCAbyg — for example, changes to "CategoryToStage" between version 5.2.0.1 and 5.2.1.0.
- Missing constructions
- Projects that only use the gen_dk library don't export any constructions, since these are already built into LCAbyg.
- Error about missing UUID
- Search the json file with, for example, Notepad++ to check that UUIDs are correct and complete.
- Collision messages
- Occurs when the same unique ID is used multiple times — check for duplicates.
- Error about missing target/source
- When you delete a node, the associated edges must also be removed — especially those with
amount: 0.
Updating engine.yaml
Version 5.3.2.1 changed the setup of engine.yaml — see step 3.3, page 15 in the json guide for details.
We update the guides on an ongoing basis. If you have questions, write tolcabyg@build.aau.dk.