wagnertimo / emarketcrawlr Goto Github PK

Hi @wagnertimo,

Appreciate you no longer work on this project but still hoping you might be able to guide me on how you found the original JSON url used for getPHELIXDEFuturesForADate

I have been able to bruteforce myself to the Spanish futures, but am hoping to be able to extract Phelix DE, French, Italian, Spanish etc.

Do you have any recollection? Perhaps we could extend this package to other markets.

This is not an issue but rather an enhancement request.

Hey!

I was trying to fetch some data with the package in RStudio but got the following error.

`

setLogging(TRUE)
[1] "Outputs/logs will be displayed!"
[1] "Outputs/logs will be displayed!"
prices <- getIntradayContinuousEPEXSPOT("2019-12-10", "2019-12-24")
| | 0%2020-01-02 16:43:52 INFO::getIntradayContinuousEPEXSPOT - Call for: 2019-12-24 and 2019-12-23 | REMEBER 2 dates on site!
2020-01-02 16:43:53 INFO::parseICEPEXSPOT - Parsing Continuous Intraday EPEX website with 2 dates
Error in as.Date.default(xpathSApply(htmlDoc, "id('content')/div/table/tbody/tr[1]/th[contains(@Class, 'date')]/text()", :
c("do not know how to convert 'xpathSApply(htmlDoc, "id('content')/div/table/tbody/tr[1]/th[contains(@Class, 'date')]/text()", ' to class “Date”", "do not know how to convert ' saveXML)' to class “Date”")
`

Maybe website code changed and parser is outdated? Or minor issue?

Thanks,
Adrian

Reason: The URL https://www.epexspot.com/en/market-data/intradayauction/quarter-auction-table/2017-05-26/DE does not work anymore.

Hey Timo,

great work! But to raise an issue: the function getPHELIXDEFuturesEEX, (more specifically getPHELIXDEFuturesForADate) is a bit broken.
You can only ask for Tuesdays to Fridays (at least for some sample weeks in 2018 and 2019), as it otherwise tries to get data from the day before which would be a weekend and not available. Again no expectation that this is fixed. I might try it myself.

Cheers
Jörn

PS: My first diagnosis was wrong, so I updated the issue.

There is a bug regarding the daylight saving time e.g. in Sun, 30/10/2016 (https://www.epexspot.com/en/market-data/dayaheadauction/auction-table/2016-11-04/DE).

The extra two hours are labeled as 02a - 02b and 02b - 03. This leads to an addtitional observation row (7 days on one webpage) which explains the error message:

Error in data.frame(..., check.names = FALSE) : 
  arguments imply differing number of rows: 168, 175

Hi Timo,
are there any plans on updating? As this is not working anymore in present state.
Kind regards!

Dear Timo,

Thank you for this great job, however, I can not reproduce your first example using the function "getIntradayContinuousEPEXSPOT"

Here is the error message:
04-28 16:03:04 INFO::getIntradayContinuousEPEXSPOT - Call for: 2017-05-26 and 2017-05-25 | REMEBER 2 dates on site!
2018-04-28 16:03:05 INFO::parseICEPEXSPOT - Parsing Continuous Intraday EPEX website with 2 dates
Error in data.frame(..., check.names = FALSE) :
arguments imply differing number of rows: 96, 108
De plus : Warning message:
In parseICEPEXSPOT(parsedHtml, product, country) :

Have you any ideas how to fix that ?
Kind regards,
Tristan

I am running a code provided in the readme file and it's giving me this error.

prices <- getIntradayContinuousEPEXSPOT("2020-01-01", "2023-08-18", "60", "CH")

Error:

Error in seq.default(1, length(times_list) - 1, 7) :
wrong sign in 'by' argument