r24mille / iesopublicreportbindings Goto Github PK

...for the giggles. https://travis-ci.org

See http://logging.apache.org/log4j/2.x/manual/configuration.html for details.

This document describes some of the conventions they are using and the categories which all reports fall into (eg. addition of hourly report type).

http://www.ieso.ca/Documents/ti/Market_Results/IMO_SPEC_0100.pdf

When parsing the initial two reports, JAXB2 populated objects from GenOutputCapability into the com.theimo.schema package and VGForecastSummary into ca.ieso.schema due to the fact that their .xsd documents were located at different locations.

However, now multiple shemas located at http://reports.ieso.ca/docrefs/schema/ have a base element named DocBody. The current parser would have conflicts. Figure out some reasonable way to resolve this.

The surplus baseload generation reports (http://www.ieso.ca/imoweb/marketdata/sbg.asp) are a bit of a moving target due to the fact that the report's URL changes based on date (eg. http://www.ieso.ca/weather/mkt4/sbg/PUB_SurplusBaseloadGen_20140108_v1.xml)

However, the schema is constant (http://www.ieso.ca/docrefs/schema/SBG_r1.xsd) and would be useful information since surplus wind generation is so problematic in Ontario.

DISPATCHABLE_LOAD, EMBEDDED_WIND, and EMBEDDED_SOLAR seem like relevant additions since they appear in AdequacyClient.