Dominik Leutnant

@gaoxiangying This is rather a network (behind a proxy?) or access issue and most probably not related to {swmmr}. Please check if you can generally install a package from github.

Hi @hsonne! That's cool, looking forward to your contributions! Well, there isn't an official dev branch anymore. I use the main branch as the one with the latest developments, which...

Well, I'm about to go on vacation. So things may take a while.

Could you share .txt, .shp and .dat files so that I could try to reproduce this issue?

I reckon this relates to the dictionary of colnames (`compare_to_dictionary`). I am going to write a unit test to catch this error. @DoeringA The column name tested is e.g. "FromNode"...

Thanks for reporting this! If you need a quick solution, I would suggest to check out the fantastic lubridate package and simply override the time zone. The next option would...

I get the the same results like PCSWMM... ``` r library(swmmr) model [,1] #> 2019-06-08 03:00:00 61.44199 #> 2019-06-08 03:01:00 59.80343 #> 2019-06-08 03:02:00 61.03724 #> 2019-06-08 03:03:00 59.52657 #>...

Could you test SWMM 5.1.014? (which would be highly surprising, if the error would still occur...)

Are you using R 32 or 64 bit?

Your .out file seems to be ok?! Could you eventually restart R and your system? ``` r library(swmmr) flows Warning: timezone of object (GMT) is different than current timezone ()....