Well.. that.

SketchUp, EnergyPlus, Radiance and other tools use different conventions for the sign in Latitude and Longitude. We need to choose one for Emp and make it very clear. Also, we need to check for the consistency when reading EPW, WEA and SKP files.

EPW files use: - for South, - for West, GMT for TimeZone (i.e. timezone = 15std_meridian)
WEA files use: - for South, + for West, -GMT for TimeZone (i.e. timezone = -15std_meridian)
Gendaylit and Gensky use: - for South, + for West, and uses std_meridian as input (in + West)
SKP use: - for South, - for West, GMT for TimeZone

As for now, EMP_CORE's LOCATION object has the following definitions:

float latitude; //!< The latitude in degrees North (use negative for South)
float longitude; //!< The longitude in degrees West (use negative for East)
float timeZone; //!< in GMT units

Which means that it is using WEA file standards. Need to make sure this is consistent in other functions.

On a model with one workplane and two tasks, an error occurred when trying to calculate

Error: #<JSON::ParserError: 776: unexpected token at 'null'>

I just rewrote it in Rust, and I had to change it quite a bit... worth revising.

Windows within components are Bulked into the definition instead of being treated as Windows.

Expected behaviour

1. Their vertices should be transformed into global coordinates
2. The transformed polygon should be added to the "Windows" section in the EmpModel.
3. We need to deal with names.... the same will happen with workplanes.

Workaround

Explode the model.

Workplanes in SketchUp models are now stored in an array of objects, not in an object itself. This allows for more information about the workplanes.

That is, from:

{
    workplaneName : [ 'task1',  'task2' ],
    anotherWorkplane : [ 'task2' ]                                  
}

to

[
    { name: 'workplaneName', tasks : [ 'task1',  'task2' ], pixel_size: 0.25 },
    { name: 'anotherWorkplane', tasks : [ 'task2' ] , pixel_size: 0.25  }                               
]