Fix issue 132 #133
Draft
Fix issue 132 #133
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A partir de janvier 2026, le coefficient de chauffage passe de 2.3 à 1.9.
Cest l'objet de cette PR.
Les anciennes valeurs de conso sont stockés sur avec un suffix 2025 si le dpe à été généré avant le 01/01/2026.
https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000052134589
Maj des scripts de tests sur l'analyse des corpus.
On stocke dans le dpe la valeur initiale de la conso ep sur l'usage, l'usage au m² et la classe dpe.
Ils'agit bien ici de stocker la valeur de sortie de la lib open3cl avec l'ancien coefficient de chauffage et non la valeur originelle du DPE.
Pour les propriétés concernées, si le dpe à été généré avant le premier Janvier 2026 alors on compare avec la valeur initiale de la conso ep.