<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="other" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">VeriXiv</journal-id>
            <journal-title-group>
                <journal-title>VeriXiv</journal-title>
            </journal-title-group>
            <issn pub-type="epub">3029-0988</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/verixiv.989.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Software Tool Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>traveltime: an R package to calculate travel time across a landscape from user-specified locations</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 1 approved, 2 approved with reservations]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Ryan</surname>
                        <given-names>Gerard E.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-0183-7630</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Tierney</surname>
                        <given-names>Nicholas</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Golding</surname>
                        <given-names>Nick</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Funding Acquisition</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a4">4</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Weiss</surname>
                        <given-names>Daniel J.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>The Kids Research Institute Australia, Nedlands, WA, 6009, Australia</aff>
                <aff id="a2">
                    <label>2</label>The University of Melbourne School of Population and Global Health, Melbourne, Victoria, 3010, Australia</aff>
                <aff id="a3">
                    <label>3</label>Curtin University, Bentley, WA, Australia</aff>
                <aff id="a4">
                    <label>4</label>The University of Western Australia Department of Mathematics and Statistics, Perth, Western Australia, Australia</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:gerry.ryan@thekids.org.au">gerry.ryan@thekids.org.au</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>21</day>
                <month>5</month>
                <year>2025</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2025</year>
            </pub-date>
            <volume>2</volume>
            <elocation-id>99</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>15</day>
                    <month>5</month>
                    <year>2025</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Ryan GE et al.</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://verixiv.org/articles/2-99/pdf"/>
            <abstract>
                <p>Understanding and mapping the time to travel among locations is useful for many activities from urban planning to public health and myriad others. Here we present a software package &#x2014; 
                    <monospace>traveltime</monospace> &#x2014; written in and for the language R. 
                    <monospace>traveltime</monospace> enables a user to create a raster map of the travel time over an area of interest from a user-specified set of locations defined by geographic coordinates. The result is a raster of the area of interest where the value in each cell is the lowest travel time in minutes to the nearest of the supplied locations. We envisage this software having diverse applications including: estimating sampling bias, allocating defibrillators, setting health districts, or mapping access to vehicle chargers and agricultural facilities. The work-flow requires two key steps: preparing a friction surface for the area of interest, and then calculating travel time over that surface for the points of interest. 
                    <monospace>traveltime</monospace> is available from 
                    <uri xlink:href="https://idem-lab.r-universe.dev/traveltime">R-Universe</uri> and 
                    <uri xlink:href="https://github.com/idem-lab/traveltime">GitHub</uri>, and documented at 
                    <uri xlink:href="https://idem-lab.github.io/traveltime/">https://idem-lab.github.io/traveltime/</uri>.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>R</kwd>
                <kwd>geographic information systems</kwd>
                <kwd>spatial analysis</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1" xlink:href="https://doi.org/10.13039/100000865">
                    <funding-source>Gates Foundation</funding-source>
                    <award-id>INV-021972</award-id>
                </award-group>
                <funding-statement>This work was supported, in whole or in part, by the Gates Foundation [INV-021972]. </funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec1" sec-type="intro">
            <title>Introduction</title>
            <p>Understanding and mapping the time to travel among locations is useful for many activities from urban planning (
                <xref ref-type="bibr" rid="ref20">Zahavi 1974</xref>) to public health (
                <xref ref-type="bibr" rid="ref6">Hulland et al. 2019</xref>; 
                <xref ref-type="bibr" rid="ref19">Weiss et al. 2020</xref>) and myriad others (
                <xref ref-type="bibr" rid="ref9">Nelson et al. 2019</xref>). Global maps of travel time to cities (
                <xref ref-type="bibr" rid="ref18">Weiss et al. 2018</xref>; 
                <xref ref-type="bibr" rid="ref9">Nelson et al. 2019</xref>) and health care (
                <xref ref-type="bibr" rid="ref6">Hulland et al. 2019</xref>; 
                <xref ref-type="bibr" rid="ref19">Weiss et al. 2020</xref>) have generated much interest and use
                <xref ref-type="fn" rid="fn1">
                    <sup>1</sup>
                </xref>, and the city data set of 
                <xref ref-type="bibr" rid="ref9">Nelson et al. (2019)</xref> is available to R users through the widely-used 
                <monospace>geodata</monospace> package (
                <xref ref-type="bibr" rid="ref5">Hijmans et al. 2024</xref>). Here we extend that work to enable travel time calculations from any arbitrary set of locations and friction surface.</p>
            <p>We present a software package &#x2014; 
                <monospace>traveltime</monospace> &#x2014; written in and for the language R (
                <xref ref-type="bibr" rid="ref12">R Core Team 2024</xref>). 
                <monospace>traveltime</monospace> enables a user to create a raster map of the travel time over an area of interest from a user-specified set of locations defined by geographic coordinates. The result is a raster of the area of interest where the value in each cell is the lowest travel time in minutes to the nearest of the supplied locations.</p>
            <p>A gaggle of R packages provide superficially similar though fundamentally different functionality via the 
                <ext-link ext-link-type="uri" xlink:href="https://www.TravelTime.com">TravelTime.com</ext-link> API (
                <xref ref-type="bibr" rid="ref14 ref15">TravelTime 2024a, 2024b</xref>; 
                <xref ref-type="bibr" rid="ref17">von Bergmann 2024</xref>; 
                <xref ref-type="bibr" rid="ref8">Lo Russo 2024</xref>). Their &#x2018;Isochron&#x2019; polygons &#x2014; areas reachable within a given time from a given location &#x2014; are most comparable to what 
                <monospace>traveltime::calculate_travel_time()</monospace> calculates. However, each isochron is a single polygon calculated is for a single point location and specified maximum travel time, rather than a raster of temporal gradation across a landscape, jointly for an arbitrary number of points, as in 
                <monospace>traveltime</monospace>. 
                <ext-link ext-link-type="uri" xlink:href="https://TravelTime.com">TravelTime.com</ext-link> cannot provide a single result surface for time to the nearest of a group of points, and continuous time scale without extensive repeated iteration for all combinations of time and points, plus additional calculation of the minimum value for each cell from all points. Furthermore, 
                <ext-link ext-link-type="uri" xlink:href="https://TravelTime.com">TravelTime.com</ext-link> requires access keys, a paid subscription beyond a short free period, and caps queries, which add considerable friction to the use of this resource.</p>
            <p>With 
                <monospace>traveltime</monospace>, we provide free and open source software to estimate travel time from any number of user-supplied locations, across a complete area of interest, and with convenient access to motorised transport or walking friction surfaces with global coverage.</p>
        </sec>
        <sec id="sec2" sec-type="methods">
            <title>Methods</title>
            <sec id="sec3">
                <title>Implementation</title>
                <p>

                    <monospace>traveltime</monospace> is an R (
                    <xref ref-type="bibr" rid="ref12">R Core Team 2024</xref>) package and requires installation of R version 4.1 or a more recent version 
                    <monospace>traveltime</monospace> provides a spatial interface using object classes from the 
                    <monospace>terra</monospace> package (
                    <xref ref-type="bibr" rid="ref4">Hijmans 2024</xref>). Travel time is calculated as movement over a resistance &#x2018;friction surface&#x2019; (
                    <xref ref-type="bibr" rid="ref16">van Etten 2017</xref>). To provide easy access to the existing friction surfaces generated by 
                    <xref ref-type="bibr" rid="ref19">Weiss et al. (2020)</xref>, 
                    <monospace>traveltime</monospace> internally uses the R package 
                    <monospace>malariaAtlas</monospace> (
                    <xref ref-type="bibr" rid="ref11">Pfeffer et al. 2018</xref>) to download surfaces for the area of interest; though users can also supply any other friction surface raster.</p>
            </sec>
            <sec id="sec4">
                <title>Operation</title>
                <p>The work-flow requires two key steps:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>preparing a friction surface for the area of interest, and then</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>calculating travel time over that surface for the points of interest.</p>
                        </list-item>
                    </list>
                </p>
            </sec>
            <sec id="sec5">
                <title>Installation</title>
                <p>

                    <monospace>traveltime</monospace> is available from 
                    <ext-link ext-link-type="uri" xlink:href="https://idem-lab.r-universe.dev/traveltime">R-Universe
</ext-link> and 
                    <ext-link ext-link-type="uri" xlink:href="https://github.com/idem-lab/traveltime">GitHub</ext-link>, and documented at 
                    <ext-link ext-link-type="uri" xlink:href="https://idem-lab.github.io/traveltime/">https://idem-lab.github.io/traveltime/</ext-link>. It can be installed in R as follows:

                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">

                        <monospace>
                            <styled-content style="color:#4758AB">install.packages</styled-content>
                            <styled-content style="color:#003B4F">(</styled-content>
                            <styled-content style="color:#20794D">"traveltime"</styled-content>
                            <styled-content style="color:#003B4F">,</styled-content> 
                            <styled-content style="color:#657422">repos =</styled-content> 
                            <styled-content style="color:#4758AB">c</styled-content>
                            <styled-content style="color:#003B4F">(</styled-content>
                            <styled-content style="color:#20794D">"https://idem-lab.r-universe.dev"</styled-content>
                            <styled-content style="color:#003B4F">))</styled-content>
                        </monospace>
                    </preformat>
                </p>
            </sec>
            <sec id="sec6">
                <title>Example: walking from public transport in Singapore</title>
                <p>Here we provide an example to calculate and map the walking travel time from rail transport stations across Singapore. 
                    <ext-link ext-link-type="uri" xlink:href="https://idem-lab.github.io/traveltime/articles/singapore.html">Complete code for this example is available as a vignettte in package documentation</ext-link>.</p>
                <p>

                    <italic toggle="yes">Prepare data and friction surface</italic>
                </p>
                <p>We need two items of data:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>our area of interest &#x2014; Singapore, and</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>our points to calculate travel time from &#x2014; Singapore&#x2019;s Mass Rapid Transit (MRT) and Light Rail Transit (LRT) stations.</p>
                        </list-item>
                    </list>
                </p>
                <p>We download 
                    <monospace>singapore_shapefile</monospace>, a polygon boundary of Singapore from the GADM (
                    <xref ref-type="bibr" rid="ref3">GADM 2022</xref>) database using the 
                    <monospace>geodata</monospace> package (
                    <xref ref-type="bibr" rid="ref5">Hijmans et al. 2024</xref>) as our area of interest:

                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">

                        <monospace>
                            <styled-content style="color:#4758AB">library</styled-content>
                            <styled-content style="color:#003B4F">(terra)</styled-content>
                        </monospace>

                        <monospace>
                            <styled-content style="color:#4758AB">library</styled-content>
                            <styled-content style="color:#003B4F">(geodata)</styled-content>
                        </monospace>


                        <monospace>
                            <styled-content style="color:#003B4F">singapore_shapefile</styled-content> 
                            <styled-content style="color:#003B4F">&lt;-</styled-content> 
                            <styled-content style="color:#4758AB">gadm</styled-content>
                            <styled-content style="color:#003B4F">(</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#657422">country =</styled-content> 
                            <styled-content style="color:#20794D">"Singapore"</styled-content>
                            <styled-content style="color:#003B4F">,</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#657422">level =</styled-content> 
                            <styled-content style="color:#AD0000">0</styled-content>
                            <styled-content style="color:#003B4F">,</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#657422">path =</styled-content> 
                            <styled-content style="color:#4758AB">tempdir</styled-content>
                            <styled-content style="color:#003B4F">(),</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#657422">resolution =</styled-content> 
                            <styled-content style="color:#AD0000">2</styled-content>
                        </monospace>

                        <monospace>
                            <styled-content style="color:#003B4F">)</styled-content>
                        </monospace>


                        <monospace>
                            <styled-content style="color:#003B4F">singapore_shapefile</styled-content>
                        </monospace> 

 
                        <monospace>class       : SpatVector</monospace>
 
                        <monospace>geometry    : polygons</monospace>
 
                        <monospace>dimensions  : 1, 2  (geometries, attributes)</monospace>
 
                        <monospace>extent      : 103.6091, 104.0858, 1.1664, 1.4714 (xmin, xmax, ymin, ymax)</monospace>
 
                        <monospace>coord. ref. : lon/lat WGS 84 (EPSG:4326)</monospace>
 
                        <monospace>names       : GID_0   COUNTRY</monospace>
 
                        <monospace>type        : &lt;chr&gt;     &lt;chr&gt;</monospace>
 
                        <monospace>values      :   SGP Singapore</monospace>
                    </preformat>
                </p>
                <p>Next we use the function 
                    <monospace>traveltime::get_friction_surface
</monospace> to retrieve a walking friction surface for our area of interest. Alternatively, we could use 
                    <monospace>surface = "motor2020"</monospace> for motorised travel. We&#x2019;re also only interested in walking 
                    <italic toggle="yes">on land</italic> so we 
                    <monospace>mask</monospace> out areas outside of the land boundary in 
                    <monospace>singapore_shapefile</monospace>. Users supplying their own friction surfaces do not need to download one in this fashion, only ensure that it is in 
                    <monospace>SpatRaster</monospace> format.

                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">

                        <monospace>
                            <styled-content style="color:#003B4F">friction_singapore</styled-content> 
                            <styled-content style="color:#003B4F">&lt;-</styled-content> 
                            <styled-content style="color:#003B4F">traveltime</styled-content>
                            <styled-content style="color:#5E5E5E">::</styled-content>
                            <styled-content style="color:#4758AB">get_friction_surface</styled-content>
                            <styled-content style="color:#003B4F">(</styled-content>
                        </monospace>
    
                        <monospace>
                            <styled-content style="color:#657422">surface =</styled-content> 
                            <styled-content style="color:#20794D">"walk2020"</styled-content>
                            <styled-content style="color:#003B4F">,</styled-content>
                        </monospace>
    
                        <monospace>
                            <styled-content style="color:#657422">extent =</styled-content> 
                            <styled-content style="color:#003B4F">singapore_shapefile</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#003B4F">)</styled-content>
                            <styled-content style="color:#5E5E5E">|&gt;</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#003B4F">terra</styled-content>
                            <styled-content style="color:#5E5E5E">::</styled-content>
                            <styled-content style="color:#4758AB">mask</styled-content>
                            <styled-content style="color:#003B4F">(singapore_shapefile)</styled-content>
                        </monospace>


                        <monospace>&lt;GMLEnvelope&gt;</monospace>
    
                        <monospace>|-- lowerCorner: 1.1664 103.6091</monospace>
    
                        <monospace>|-- upperCorner: 1.4714 104.0858Start tag expected, '&lt;' not found</monospace>


                        <monospace>
                            <styled-content style="color:#003B4F">friction_singapore</styled-content>
                        </monospace>


                        <monospace>class       : SpatRaster</monospace>

                        <monospace>dimensions  : 37, 57, 1 (nrow, ncol, nlyr)</monospace>

                        <monospace>resolution  : 0.008333333, 0.008333333 (x, y)</monospace>

                        <monospace>extent      : 103.6083, 104.0833, 1.166667, 1.475 (xmin, xmax, ymin, ymax)</monospace>

                        <monospace>coord. ref. : lon/lat WGS 84 (EPSG:4326)</monospace>

                        <monospace>source(s)   : memory</monospace>

                        <monospace>varname     : Accessibility__202001_Global_Walking_Only_Friction_Surface_1.1664,103.6091,1.4714,104.0858</monospace>

                        <monospace>name        : friction_surface</monospace>

                        <monospace>min value   :       0.01200000</monospace>

                        <monospace>max value   :       0.06192715</monospace>
                    </preformat>
                </p>
                <p>Our points are the 
                    <monospace>traveltime::stations</monospace> data, containing coordinates of all LRT and MRT station exits in Singapore (
                    <xref ref-type="bibr" rid="ref7">Land Transport Authority 2019</xref>):

                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">

                        <monospace>
                            <styled-content style="color:#4758AB">library</styled-content>
                            <styled-content style="color:#003B4F">(traveltime)</styled-content>
                        </monospace>

                        <monospace>
                            <styled-content style="color:#4758AB">head</styled-content>
                            <styled-content style="color:#003B4F">(stations)</styled-content>
                        </monospace>


                        <monospace>            x        y</monospace>

                        <monospace>[1,] 103.9091 1.334922</monospace>

                        <monospace>[2,] 103.9335 1.336555</monospace>

                        <monospace>[3,] 103.8493 1.297699</monospace>

                        <monospace>[4,] 103.8508 1.299195</monospace>

                        <monospace>[5,] 103.9094 1.335311</monospace>

                        <monospace>[6,] 103.9389 1.344999</monospace>
                    </preformat>
                </p>
                <p>We plot these data below. 
                    <monospace>traveltime</monospace> takes resistance values of friction (
                    <xref ref-type="bibr" rid="ref16">van Etten 2017</xref>), so higher values of friction indicate more time travelling across a given cell.</p>
                <p>

                    <italic toggle="yes">Calculate and plot the travel time</italic>
                </p>
                <p>With all the data collected, the function 
                    <monospace>
calculate_travel_time()</monospace> takes the friction surface 
                    <monospace>friction_singapore</monospace> and the points of interest in 
                    <monospace>stations</monospace>, and returns a 
                    <monospace>SpatRaster</monospace> of walking time in minutes to each cell from the nearest station:

                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">

                        <monospace>
                            <styled-content style="color:#003B4F">travel_time_singapore</styled-content> 
                            <styled-content style="color:#003B4F">&lt;-</styled-content> 
                            <styled-content style="color:#4758AB">calculate_travel_time</styled-content>
                            <styled-content style="color:#003B4F">(</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#657422">friction_surface =</styled-content> 
                            <styled-content style="color:#003B4F">friction_singapore,</styled-content>
                        </monospace>
  
                        <monospace>
                            <styled-content style="color:#657422">points =</styled-content> 
                            <styled-content style="color:#003B4F">stations</styled-content>
                        </monospace>

                        <monospace>
                            <styled-content style="color:#003B4F">)</styled-content>
                        </monospace>


                        <monospace>
                            <styled-content style="color:#003B4F">travel_time_singapore</styled-content>
                        </monospace>


                        <monospace>class       : SpatRaster</monospace>

                        <monospace>dimensions  : 37, 57, 1 (nrow, ncol, nlyr)</monospace>

                        <monospace>resolution  : 0.008333333, 0.008333333 (x, y)</monospace>

                        <monospace>extent      : 103.6083, 104.0833, 1.166667, 1.475 (xmin, xmax, ymin, ymax)</monospace>

                        <monospace>coord. ref. :  </monospace>

                        <monospace>source(s)   : memory</monospace>

                        <monospace>name        : travel_time</monospace>

                        <monospace>min value   :           0</monospace>

                        <monospace>max value   :         Inf</monospace>
                    </preformat>
                </p>
                <p>We present the resulting calculated travel times in 
                    <xref ref-type="fig" rid="f2">
Figure 2</xref> where, as expected, the travel times are lowest near station exits (per 
                    <xref ref-type="fig" rid="f1">
Figure 1</xref>) and progressively higher further away. Note that the results in 
                    <monospace>
travel_time_singapore
</monospace> include infinite values (
                    <monospace>Inf</monospace> above). In 
                    <xref ref-type="fig" rid="f1">
Figure 1</xref>, the islands to the south and north-east are shown as filled cells, but unconnected with the mainland. The raster cells for these islands appear absent in 
                    <xref ref-type="fig" rid="f2">
Figure 2</xref>. Because they are not connected to any cells with a station, the calculated travel time is infinite, and so these cells do not appear in 
                    <xref ref-type="fig" rid="f2">
Figure 2</xref>.</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>
Figure 1. </label>
                    <caption>
                        <title>Friction surface raster of Singapore, showing Singapore boundary in grey, and station locations as grey points.</title>
                    </caption>
                    <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://verixiv-files.f1000.com/manuscripts/1007/0037af68-007f-467f-9a57-9620c68a90f1_figure1.gif"/>
                </fig>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>
Figure 2. </label>
                    <caption>
                        <title>Map of walking travel time in Singapore, in minutes from nearest MRT or LRT station.</title>
                    </caption>
                    <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://verixiv-files.f1000.com/manuscripts/1007/0037af68-007f-467f-9a57-9620c68a90f1_figure2.gif"/>
                </fig>
            </sec>
        </sec>
        <sec id="sec7" sec-type="discussion">
            <title>Discussion</title>
            <p>The 
                <monospace>traveltime</monospace> package is immediately suitable to be used &#x2018;out-of-the-box&#x2019; with any set of coordinates, in any part of the globe. We envisage this software having diverse applications including: estimating sampling bias (
                <xref ref-type="bibr" rid="ref1">Dennis and Thomas 2000</xref>), allocating defibrillators (
                <xref ref-type="bibr" rid="ref13">Tierney et al. 2018</xref>), setting health districts (
                <xref ref-type="bibr" rid="ref10">Padgham et al. 2019</xref>), or mapping access to vehicle chargers (
                <xref ref-type="bibr" rid="ref2">Falchetta and Noussan 2021</xref>) and agricultural facilities (
                <xref ref-type="bibr" rid="ref21">Zhao et al. 2023</xref>). Nonetheless, we see opportunities to build the package utility through:
                <list list-type="bullet">
                    <list-item>
                        <label>&#x2022;</label>
                        <p>capability to better distribute a wider range friction surfaces, and</p>
                    </list-item>
                    <list-item>
                        <label>&#x2022;</label>
                        <p>additional methods to efficiently compute results over large spatial extents.</p>
                    </list-item>
                </list>
            </p>
            <p>Firstly, 
                <monospace>traveltime</monospace> currently facilitates access to walking and motorised friction surfaces for 2020, both at 30 arc-second resolution (approximately 0.008333 decimal degrees, or just below 1 km
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msup>
                            <mml:mspace width="0em"/>
                            <mml:mn>2</mml:mn>
                        </mml:msup>
                    </mml:math>
</inline-formula> at the equator). Although the user can presently supply their own friction surface, we expect most applications will use these existing surfaces given the extensive work needed in creating new ones (
                <xref ref-type="bibr" rid="ref18 ref19">Weiss et al. 2018, 2020</xref>). As landscapes are dynamic, it may be useful to incorporate updated versions of these friction surfaces if and when they are available. Furthermore, although the resolution of these data is likely to be suitable for larger landscape foci, higher resolution data may be helpful for more locally focussed analyses. For instance, although the example here was chosen for it&#x2019;s simplicity and low computational demands, a ~1 km
                <sup>2</sup> cell size is a relatively large area to walk across, and thus actual waking times may vary significantly within each cell. We underline however that a user can provide their own higher resolution friction surface at present if desired.</p>
            <p>At the other end of the scale, as the area of interest increases, the size of the matrix of calculations necessary increases exponentially, making significant memory demands for analyses over large landscapes (e.g. analyses over Africa required ~ 72 GB RAM to run successfully). Developing methods to handle large landscapes either with less memory or via cloud resources would be helpful to make such analyses accessible to those without access to larger computing resources.</p>
            <p>Lastly, although this article is intended to be the key reference for the 
                <monospace>traveltime</monospace> package, we suggest citations of the package are accompanied by citing the underlying methodological work as well (
                <xref ref-type="bibr" rid="ref18 ref19">Weiss et al. 2018, 2020</xref>).</p>
        </sec>
        <sec id="sec8">
            <title>
Figure permissions</title>
            <p>The authors confirm ownership of the figures used in this manuscript.</p>
        </sec>
        <sec id="sec9">
            <title>Data and software availability</title>
            <p>All software described here is available from R-Universe 
                <ext-link ext-link-type="uri" xlink:href="https://idem-lab.r-universe.dev/traveltime">https://idem-lab.r-universe.dev/traveltime</ext-link> and GitHub 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/idem-lab/traveltime">https://github.com/idem-lab/traveltime</ext-link>, and documented at 
                <ext-link ext-link-type="uri" xlink:href="https://idem-lab.github.io/traveltime/">https://idem-lab.github.io/traveltime/</ext-link>. Code used in this paper is released via GitHub as 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/idem-lab/traveltime/releases/tag/v3">v4</ext-link>, and archived on Zenodo under DOI 
                <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.15347016">10.5281/zenodo.15347016</ext-link>.</p>
            <p>The package associated with this paper contains information from the dataset &#x201c;LTA MRT Station Exit (GEOJSON)&#x201d; accessed on the 10th of December 2024 from data.gov.sg, which is made available under the terms of the Singapore Open Data Licence version 1.0 
                <ext-link ext-link-type="uri" xlink:href="https://data.gov.sg/open-data-licence">https://data.gov.sg/open-data-licence</ext-link>.</p>
        </sec>
    </body>
    <back>
        <ack>
            <title>Acknowledgements</title>
            <p>An earlier version of this article has been archived on EarthArXiv 
                <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.31223/X56M74">https://doi.org/10.31223/X56M74</ext-link>.</p>
        </ack>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Dennis</surname>
                            <given-names>RLH</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Thomas</surname>
                            <given-names>CD</given-names>
                        </name>
</person-group>:
                    <article-title>Bias in Butterfly Distribution Maps: The Influence of Hot Spots and Recorder&#x2019;s Home Range.</article-title>
                    <source>

                        <italic toggle="yes">J. Insect Conserv.</italic>
</source>
                    <year>2000</year>;<volume>4</volume>:<fpage>73</fpage>&#x2013;<lpage>77</lpage>.
                    <pub-id pub-id-type="doi">10.1023/A:1009690919835</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Falchetta</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Noussan</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>Electric Vehicle Charging Network in Europe: An Accessibility and Deployment Trends Analysis.</article-title>
                    <source>

                        <italic toggle="yes">Transp. Res. Part D: Transp. Environ.</italic>
</source>
                    <year>2021</year>;<volume>94</volume>:<fpage>102813</fpage>.
                    <pub-id pub-id-type="doi">10.1016/j.trd.2021.102813</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <mixed-citation publication-type="other">
                    <collab>GADM</collab>:
                    <article-title>GADM Maps and Data.</article-title>
                    <year>2022</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://gadm.org/index.html">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hijmans</surname>
                            <given-names>RJ</given-names>
                        </name>
</person-group>:
                    <article-title>terra: Spatial Data Analysis.</article-title>
                    <year>2024</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://CRAN.R-project.org/package=terra">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hijmans</surname>
                            <given-names>RJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Barbosa</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ghosh</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>geodata: Download Geographic Data.</article-title>
                    <year>2024</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://CRAN.R-project.org/package=geodata">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref6">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hulland</surname>
                            <given-names>EN</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wiens</surname>
                            <given-names>KE</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Shirude</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Travel Time to Health Facilities in Areas of Outbreak Potential: Maps for Guiding Local Preparedness and Response.</article-title>
                    <source>

                        <italic toggle="yes">BMC Med.</italic>
</source>
                    <year>2019</year>;<volume>17</volume>:<fpage>1</fpage>&#x2013;<lpage>16</lpage>.
                    <pub-id pub-id-type="doi">10.1186/s12916-019-1459-6</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <mixed-citation publication-type="other">
                    <collab>Land Transport Authority</collab>:
                    <article-title>LTA MRT Station Exit (GEOJSON) Dataset.</article-title>
                    <year>2019</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://data.gov.sg">Reference Source</ext-link>
                    <ext-link ext-link-type="uri" xlink:href="https://data.gov.sg/datasets/d_b39d3a0871985372d7e1637193335da5/view">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref8">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lo Russo</surname>
                            <given-names>T</given-names>
                        </name>
</person-group>:
                    <article-title>traveltime - a Traveltime API Wrapper for R.</article-title>
                    <year>2024</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://github.com/tlorusso/traveltime">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Nelson</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Weiss</surname>
                            <given-names>DJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Etten</surname>
                            <given-names>J</given-names>
                            <prefix>van</prefix>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>A Suite of Global Accessibility Indicators.</article-title>
                    <source>

                        <italic toggle="yes">Scientific Data.</italic>
</source>
                    <year>2019</year>;<volume>6</volume>(<issue>1</issue>):<fpage>266</fpage>.
                    <pub-id pub-id-type="pmid">31700070</pub-id>
                    <pub-id pub-id-type="doi">10.1038/s41597-019-0265-5</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6838165</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref10">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Padgham</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Boeing</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cooley</surname>
                            <given-names>D</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>An Introduction to Software Tools, Data, and Services for Geospatial Analysis of Stroke Services.</article-title>
                    <source>

                        <italic toggle="yes">Front. Neurol.</italic>
</source>
                    <year>2019</year>;<volume>10</volume>:<fpage>743</fpage>.
                    <pub-id pub-id-type="pmid">31440197</pub-id>
                    <pub-id pub-id-type="doi">10.3389/fneur.2019.00743</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6693386</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Pfeffer</surname>
                            <given-names>DA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lucas</surname>
                            <given-names>TCD</given-names>
                        </name>

                        <name name-style="western">
                            <surname>May</surname>
                            <given-names>D</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>malariaAtlas: An R Interface to Global Malariometric Data Hosted by the Malaria Atlas Project.</article-title>
                    <source>

                        <italic toggle="yes">Malar. J.</italic>
</source>
                    <year>2018</year>;<volume>17</volume>:<fpage>1</fpage>&#x2013;<lpage>10</lpage>.</mixed-citation>
            </ref>
            <ref id="ref12">
                <mixed-citation publication-type="book">
                    <collab>R Core Team</collab>:
                    <source>

                        <italic toggle="yes">R: A Language and Environment for Statistical Computing.</italic>
</source>
                    <publisher-loc>Vienna, Austria</publisher-loc>:
                    <publisher-name>R Foundation for Statistical Computing</publisher-name>;<year>2024</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.R-project.org/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Tierney</surname>
                            <given-names>NJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Jost Reinhold</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mira</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Novel Relocation Methods for Automatic External Defibrillator Improve Out-of-Hospital Cardiac Arrest Coverage Under Limited Resources.</article-title>
                    <source>

                        <italic toggle="yes">Resuscitation.</italic>
</source>
                    <year>2018</year>;<volume>125</volume>:<fpage>83</fpage>&#x2013;<lpage>89</lpage>.
                    <pub-id pub-id-type="pmid">29414670</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.resuscitation.2018.01.055</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <mixed-citation publication-type="other">
                    <collab>TravelTime</collab>:
                    <article-title>TravelTime API.</article-title>
                    <year>2024a</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://docs.traveltime.com/api/overview/introduction">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref15">
                <mixed-citation publication-type="other">
                    <collab>TravelTime</collab>:
                    <article-title>traveltimeR: Interface to &#x2018;Travel Time&#x2019; API.</article-title>
                    <year>2024b</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://cran.r-project.org/package=traveltimeR">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Etten</surname>
                            <given-names>J</given-names>
                            <prefix>van</prefix>
                        </name>
</person-group>:
                    <article-title>R Package gdistance: Distances and Routes on Geographical Grids.</article-title>
                    <source>

                        <italic toggle="yes">J. Stat. Softw.</italic>
</source>
                    <year>2017</year>;<volume>76</volume>(<issue>13</issue>):<fpage>1</fpage>&#x2013;<lpage>21</lpage>.
                    <pub-id pub-id-type="doi">10.18637/jss.v076.i13</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref17">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Bergmann</surname>
                            <given-names>J</given-names>
                            <prefix>von</prefix>
                        </name>
</person-group>:
                    <article-title>rtraveltime.</article-title>
                    <year>2024</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://github.com/mountainMath/rtraveltime">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref18">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Weiss</surname>
                            <given-names>DJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Andy Nelson</surname>
                            <given-names>HS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Gibson</surname>
                            <given-names>WT</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>A Global Map of Travel Time to Cities to Assess Inequalities in Accessibility in 2015.</article-title>
                    <source>

                        <italic toggle="yes">Nature.</italic>
</source>
                    <year>2018</year>;<volume>553</volume>(<issue>7688</issue>):<fpage>333</fpage>&#x2013;<lpage>336</lpage>.
                    <pub-id pub-id-type="pmid">29320477</pub-id>
                    <pub-id pub-id-type="doi">10.1038/nature25181</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref19">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Weiss</surname>
                            <given-names>DJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Andy Nelson</surname>
                            <given-names>CA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Vargas-Ruiz</surname>
                            <given-names>K</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Global Maps of Travel Time to Healthcare Facilities.</article-title>
                    <source>

                        <italic toggle="yes">Nat. Med.</italic>
</source>
                    <year>2020</year>;<volume>26</volume>(<issue>12</issue>):<fpage>1835</fpage>&#x2013;<lpage>1838</lpage>.
                    <pub-id pub-id-type="pmid">32989313</pub-id>
                    <pub-id pub-id-type="doi">10.1038/s41591-020-1059-1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref20">
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zahavi</surname>
                            <given-names>Y</given-names>
                        </name>
</person-group>:
                    <source>

                        <italic toggle="yes">Traveltime Budgets and Mobility in Urban Areas.</italic>
</source>
                    <publisher-loc>United States</publisher-loc>:
                    <publisher-name>Federal Highway Administration</publisher-name>;<year>1974</year>.</mixed-citation>
            </ref>
            <ref id="ref21">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhao</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Elmore</surname>
                            <given-names>AJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>JSH</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Replanting and Yield Increase Strategies for Alleviating the Potential Decline in Palm Oil Production in Indonesia.</article-title>
                    <source>

                        <italic toggle="yes">Agric. Syst.</italic>
</source>
                    <year>2023</year>;<volume>210</volume>:<fpage>103714</fpage>.
                    <pub-id pub-id-type="doi">10.1016/j.agsy.2023.103714</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
        <fn-group content-type="footnotes">
            <fn id="fn1">
                <label>
                    <sup>1</sup>
                </label>
                <p>Collectively &gt;1600 citations per Google Scholar at the 28th of January 2025.</p>
            </fn>
        </fn-group>
    </back>
    <sub-article article-type="reviewer-report" id="report1274">
        <front-stub>
            <article-id pub-id-type="doi">10.21956/verixiv.1007.r1274</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Shi</surname>
                        <given-names>Hui</given-names>
                    </name>
                    <xref ref-type="aff" rid="r1274a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r1274a1">
                    <label>1</label>University of California Santa Barbara, Santa Barbara, California, USA</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>12</day>
                <month>7</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Shi H</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport1274" related-article-type="peer-reviewed-article" xlink:href="10.12688/verixiv.989.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>It's great to see the development of a package for estimating travel time. However, several areas could be improved to enhance its functionality and flexibility: 
                <list list-type="order">
                    <list-item>
                        <p>
                            <bold>Input/Output Description</bold>: Please include a table that clearly outlines the input parameters and expected outputs. This will help users better understand how to interact with the package.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <bold>Walking Time Metrics</bold>: Currently, the package only provides the minimum walking time. For a more comprehensive comparison, it would be beneficial to also include walking times to the nearest few stations and the average walking time. Ideally, users should be able to specify the number of nearest stations they want to include.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <bold>Adjustable Resolution</bold>: Consider allowing users to set the spatial resolution themselves. This would make the package more applicable to larger areas, where a lower resolution may be preferred for performance or scalability.</p>
                    </list-item>
                </list> In short, I would love to see a more flexible and user-configurable package.</p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Partly</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Partly</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Partly</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Spatial analysis and transportation</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report1283">
        <front-stub>
            <article-id pub-id-type="doi">10.21956/verixiv.1007.r1283</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Macharia</surname>
                        <given-names>Peter M</given-names>
                    </name>
                    <xref ref-type="aff" rid="r1283a1">1</xref>
                    <xref ref-type="aff" rid="r1283a2">2</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-3410-1881</uri>
                </contrib>
                <aff id="r1283a1">
                    <label>1</label>Department of Public Health, Institute of Tropical Medicine, Antwerp, Belgium</aff>
                <aff id="r1283a2">
                    <label>2</label>Population &amp; Health Impact Surveillance Group, KEMRI-Wellcome Trust Research Programme Nairobi (Ringgold ID: 543945), Nairobi, Kenya</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>8</day>
                <month>7</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Macharia PM</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport1283" related-article-type="peer-reviewed-article" xlink:href="10.12688/verixiv.989.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This is a useful software package and timely for many accessibility applications to different services such as healthcare, education, and banking services. I have several points to note. 
                <list list-type="order">
                    <list-item>
                        <p>In paragraph three, there is need to further contextualise other packages and tools related to traveltime developed here, for example, gdistance, AccessMod, other APIs similar to TravelTime API</p>
                    </list-item>
                    <list-item>
                        <p>While a reference has been provided, it would be useful to have a paragraph that summarizes the data and process behind the creation of the friction surface, as it&#x2019;s a major input in this package. This may include the characteristics of the data used and the approach.</p>
                    </list-item>
                    <list-item>
                        <p>A major reservation is the use of pre-existing friction surfaces. These friction surfaces were developed for global use; however, when used in a local or even country context, several key parameters determine the magnitude of travel time change. These include travel speeds; data on roads/pathways; combinations of modes of transport and sometimes differing land use; and also the output resolution.</p>
                    </list-item>
                    <list-item>
                        <p>While one solution offered here is an option for users to provide their own friction surface, If this package added a functionality such that the users can create a friction surface by controlling key input variables, it will not only ensure &#x00a0;each output is context-specific but all outputs will be updated or based on users&#x2019; time frame of interest</p>
                    </list-item>
                </list>
            </p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Yes</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>I am a spatial epidemiologist working&#x00a0;at the interface of geospatial methods and their applications to global health challenges in SSA. &#x00a0; I am particularly interested in geographic access modelling and disease mapping.</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report1195">
        <front-stub>
            <article-id pub-id-type="doi">10.21956/verixiv.1007.r1195</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Sumner</surname>
                        <given-names>Michael D</given-names>
                    </name>
                    <xref ref-type="aff" rid="r1195a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r1195a1">
                    <label>1</label>Australian Antarctic Division, Kingston, Tasmania, Australia</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>17</day>
                <month>6</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Sumner MD</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport1195" related-article-type="peer-reviewed-article" xlink:href="10.12688/verixiv.989.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This is an excellent pithy and practical paper. The authors present a toolkit for&#x00a0;determining travel time across a landscape, which is a compelling problem in human&#x00a0;health, transport logistics, and ecology to name a few. The toolkit uses modern programming practices, well-established foundations for calculating and using travel&#x00a0;time, explaining how it works, and couches the approach within the potentially&#x00a0;confusing ecosystem of software that already exists.</p>
            <p> </p>
            <p> The work is justified in terms of its need in the software niche, its accessibility&#x00a0;for immediate problem-solving, and the transparency and explanations of how it works.&#x00a0;The software behind the paper and the results within are accessible on public websites,&#x00a0;with all of its dependencies available on the public CRAN repository. The package passes a gamut of tests and documentation building that run any time a change is made. Uses can report problems and contribute software changes via an accessible mechanism.</p>
            <p> </p>
            <p> I've installed the software, checked and built it on various systems, and gave a deep read of the software itself and how it works and I can say that the package itself is also concise, does not have any glaring technical debt or complexity problems. The software navigates the available ecosystem of R software by utilizing existing packages&#x00a0;well and presenting a consistent user interface that can work with data obtained&#x00a0;by the software, or by including extra local data by users themselves.&#x00a0;</p>
            <p> This is a good piece of work and should be accepted. No changes needed.</p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Yes</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>I'm a geospatial expert with R, I have deep experience with animal tracking applications and good knowledge of how software like this works through ecosystem research.</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
        <sub-article article-type="response" id="comment21-1195">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Ryan</surname>
                            <given-names>Gerard</given-names>
                        </name>
                        <aff>The Kids Research Institue Australia, Nedlands, WA, Australia</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>17</day>
                    <month>6</month>
                    <year>2025</year>
                </pub-date>
            </front-stub>
            <body>
                <p>Thank you Michael for this thorough consideration of our&#x00a0;work and thoughtful comments.&#x00a0; Best wishes,&#x00a0; Gerry Ryan</p>
            </body>
        </sub-article>
    </sub-article>
</article>
