Catchments at different times

[hasanglr]

Hi,

I've been trying to run catchment for London at different times of the day, such as midnight, off-peak and weekend midday. However, the result remained the exact same for all three even though I changed the departure_datetime parameter. I am also attaching calendar.txt file. I'd be glad if you can help me with that. [Uploading calendar.txt…]()

mode <- c("WALK", "TRANSIT")

max_walk_time <- 15 # in minutes

travel_time_cutoff <- 50

departure_datetime_tr <- as.POSIXct("15-11-2023 02:30:00", format = "%d-%m-%Y %H:%M:%S")

time_window <- 50 # in minutes

percentiles <- 50

[rafapereirabr]

could you please the code you used in the analysis ?

[hasanglr]

Sure, here is the rest of the code:

access_jobs <- accessibility(r5r_core, origins = origin, destinations = job_dest, mode = mode, opportunities_colnames = c("jobs"), decay_function = "step", cutoffs = travel_time_cutoff, departure_datetime = departure_datetime_tr, max_walk_time = max_walk_time, time_window = time_window, percentiles = percentiles, progress = TRUE)

By the way, I realized that I get an warning for each record, indicating that timezone is unknown and API request times will be interpreted as GMT.

[rafapereirabr]

Hi @hasanglr , this is only part of the code. I'm sorry but I cannot help without a reproducible example . Also, the link to the calendar.txt does not work.

[rafapereirabr]

I'm closing this issue due to no response. I'm happy to reopen it if the problem persists

[hasanglr]

Hi @rafapereirabr,

Sorry for the late reply. I wasn't able to provide the code due to our organisation's policy. However, We realized that the network file we've been using was incorrect and produced walk-only result without giving any warning. We fixed the network file and now it works. Thanks for your help.

[rafapereirabr]

ah, no problem. Thanks for the feedback @hasanglr !