Underground floors are missing in 2019 CF1R (should be on p. 7). Is there a place to report this in the schema? The underground floor (785.8 ft2) is not found in the XML report at all. The Epro7 file shows how it appeared in 2016 "slab" (p. 10).
No new section. It belongs in Section_P. Using 2016 reporting as a pattern, what was reported on the CF1R seems adequate. I'm attaching a side-by-side comparison so you can make 2019 match reporting in 2016 (or shoe-horn it in).
A. The P05 insulation elements for Section_P seem to have three choices: 1. P05a AND P05c, 2. P05b AND P05c, 3. NotApplicable ("n/a"). Can you confirm that this is the case so that the CF1R XSD and rules can include these choices?
B. Should Underground Floors also be included in Section_Mm (SLAB FLOORS - VERIFIED AND ALTERED)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A. Underground floors cannot be insulated, and no input for perimeter. Please make both P04 (if you can) and P05 "n/a" (Note: P06 and 07 are not choices). P08 can have a status (new, altered, existing) but with no ability to insulate. This means P10a should be n/a.
B. No do not include underground floors in Section Mm because there is no input for the existing construction (it's moot).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The instructions for displaying this table indicate it should be the same as the 2016 report version. In this there are either 7 or 9 columns (the additional 2 are Status and Verified used with EAA). What is confusing are the elements P10To11ColumnLabel, P10a, P10b, P10c, and P11_SlabCarpetedFraction. P10To11ColumnLabel has the text 'Existing Conditions' but the underground example is 'NewConstruction' where one row of data includes a value for P10a. This seems inconsistent with making this table layout the same as that for 2016. Some clarification would be helpful...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Diff:
There are currently no rules to export this surface type to the CF1R XML.
The properties of "Underground Floor" do not really match CF1R XSD elements in either Section_J (opaque surfaces) or Section_P (slab floors).
So, do we need a new section to report this surface type? If so, what properties of "Underground Floor" should be reported in this new section?
No new section. It belongs in Section_P. Using 2016 reporting as a pattern, what was reported on the CF1R seems adequate. I'm attaching a side-by-side comparison so you can make 2019 match reporting in 2016 (or shoe-horn it in).
More CEC input needed:
A. The P05 insulation elements for Section_P seem to have three choices: 1. P05a AND P05c, 2. P05b AND P05c, 3. NotApplicable ("n/a"). Can you confirm that this is the case so that the CF1R XSD and rules can include these choices?
B. Should Underground Floors also be included in Section_Mm (SLAB FLOORS - VERIFIED AND ALTERED)?
A. Underground floors cannot be insulated, and no input for perimeter. Please make both P04 (if you can) and P05 "n/a" (Note: P06 and 07 are not choices). P08 can have a status (new, altered, existing) but with no ability to insulate. This means P10a should be n/a.
B. No do not include underground floors in Section Mm because there is no input for the existing construction (it's moot).
r1793: Added export of Underground Floors to CF1RPRF Section_P SLAB FLOORS
Report processing modifications are required to address new CF1RPRF XSD P05a_NotApplicableMessage and P05c_NotApplicableMessage elements
The instructions for displaying this table indicate it should be the same as the 2016 report version. In this there are either 7 or 9 columns (the additional 2 are Status and Verified used with EAA). What is confusing are the elements P10To11ColumnLabel, P10a, P10b, P10c, and P11_SlabCarpetedFraction. P10To11ColumnLabel has the text 'Existing Conditions' but the underground example is 'NewConstruction' where one row of data includes a value for P10a. This seems inconsistent with making this table layout the same as that for 2016. Some clarification would be helpful...
Mods to columns to match xml and maintain layout as with the 2016 version.