Skip to main content
PLOS One logoLink to PLOS One
. 2020 Nov 13;15(11):e0234760. doi: 10.1371/journal.pone.0234760

PeskAAS: A near-real-time, open-source monitoring and analytics system for small-scale fisheries

Alexander Tilley 1,*,#, Joctan Dos Reis Lopes 1, Shaun P Wilkinson 2,3,#
Editor: Ismael Aaron Kimirei4
PMCID: PMC7665685  PMID: 33186386

Abstract

Small-scale fisheries are responsible for landing half of the world’s fish catch, yet there are very sparse data on these fishing activities and associated fisheries production in time and space. Fisheries-dependent data underpin scientific guidance of management and conservation of fisheries systems, but it is inherently difficult to generate robust and comprehensive data for small-scale fisheries, particularly given their dispersed and diverse nature. In tackling this challenge, we use open source software components including the Shiny R package to build PeskAAS; an adaptable and scalable digital application that enables the collation, classification, analysis and visualisation of small-scale fisheries catch and effort data. We piloted and refined this system in Timor-Leste; a small island developing nation. The features that make PeskAAS fit for purpose are that it is: (i) fully open-source and free to use (ii) component-based, flexible and able to integrate vessel tracking data with catch records; (iii) able to perform spatial and temporal filtering of fishing productivity by fishing method and habitat; (iv) integrated with species-specific length-weight parameters from FishBase; (v) controlled through a click-button dashboard, that was co-designed with fisheries scientists and government managers, that enables easy to read data summaries and interpretation of context-specific fisheries data. With limited training and code adaptation, the PeskAAS workflow has been used as a framework on which to build and adapt systematic, standardised data collection for small-scale fisheries in other contexts. Automated analytics of these data can provide fishers, managers and researchers with insights into a fisher’s experience of fishing efforts, fisheries status, catch rates, economic efficiency and geographic preferences and limits that can potentially guide management and livelihood investments.

Introduction

Approximately half of the global catch of fish is landed in small-scale fisheries (SSF) [1], yet the ability for science to guide the sustainable exploitation of these resources is inhibited by substantial data gaps. There are 40 million people actively fishing in inland and coastal environments worldwide, yet due to the challenges involved in collecting data in dispersed, informal and diverse fisheries, the contributions of SSF to livelihoods, and food and nutrition security, are frequently hidden and poorly accounted for [2]. As a result, fisheries solutions are underrepresented in investments and policies to address food and nutrition security [3]. Recent research has shown that the nutrient qualities and quantities of fish already caught would be sufficient to address major micronutrient deficiencies for many countries [4], and that fish-based food strategies hold untapped potential to address nutrition short falls.

Refinements to the management of fisheries towards sustainability and food and nutrition security goals can be supported, amongst other things, by higher quality and more comprehensive fisheries and value chain data. Addressing these gaps with small-scale fisheries in low-income countries requires sensitivity to the limits of resources and capacity to collect, store, analyse and respond to these data [5]. Even with adequate data, much fisheries science relies on statistical models and analytics that were developed for single species fisheries, rather than biodiverse tropical fisheries where multiple species frequently comprise the harvests from diverse and biodiverse habitats [6]. Many diagnostic and statistical tools have been developed to support fisheries decision-making or stock assessment in data-poor contexts, e.g., FishPath [7] or TropFishR [8]. However, very few solutions provide end-to-end integration from data collection at the point of fishing or landing, to visualisation of data summaries for managers and fishing communities. This leads to a situation where management and policies are built on poor government estimates or reconstructed trade and consumption statistics that are often not relevant at the local scale, and hence are highly susceptible to governance and management failures [9].

Over the past two decades, the proliferation of information and communication technologies (ICTs) has revolutionised the collection, communication and storage of data in food production sectors, including in the industrial fishing sector [10]. These ICTs innovations commonly include design and development of mobile smartphone applications and digital survey forms [11]. There are some examples of applications and tools to collect fisheries data on a small scale, the most successful of which are generally ‘high touch’, meaning they involve significant contextual development that cannot easily be scaled to other systems or geographies (see [1215]). The danger in developing scalable technologies is that they are often imposed as prescribed ‘solutions’ on low-income countries, and can merely reinforce the capacity gap, alienate managers and stakeholders, and be ill-suited to the contextual reality [16, 17]. There is an urgent need for a light touch, scalable and integrated approach to data collection and analytics, but thus far, this has been elusive in terms of getting simple, usable data in the hands of fisheries managers.

Here, we describe a new digital application called PeskAAS—a pseudo-acronym for fisheries (peskas) in the national language of Timor-Leste, Tetum, combined with Automated Analytics System. PeskAAS connects open source programs to collect, communicate, analyse and visualise SSF movement and catch data. We piloted PeskAAS to determine how scripted analytics can assist fisheries management by generating digestible, summarised information rapidly for decision-making in data-deficient and low capacity systems. We provide examples to illustrate the types of analytics and machine learning that the system can be used to carry out. Our test site of Timor-Leste was chosen due to the very limited level of fisheries development, the paucity of information, and the limited fisheries governance capacity.

PeskAAS overview

PeskAAS is an interactive web-hosted R Shiny application developed to facilitate data exploration and decision-making processes in small-scale fisheries. This application accesses the ‘peskaDAT’ database in real-time using the DBI and RMySQL R packages [18, 19], and pulls catch records collected by enumerators at landing sites into a web-based interactive R session (hosted by https://www.shinyapps.io). From this dashboard, users can apply dynamic location, gear, habitat and date-range filters to create informative plots for catch per unit effort (CPUE), total catch, species composition and total national catch estimates (Fig 1).

Fig 1. Screenshot from the interactive PeskAAS dashboard developed to visualise near-real time fish landings data in Timor-Leste.

Fig 1

https://worldfish.shinyapps.io/PeskAAS/.

The user interface incorporates tick-box widgets for dynamic selection of municipalities, fishing habitats, gear types and boat type, and a slider widget is included for users to fit cubic smoothing splines weighted by trip effort to the CPUE data with a user defined smoothing parameter that is dynamically adjustable to aid in visualization. Users also have an option to download a month-aggregated summary table in .csv format for further analysis, using a download-button widget.

The PeskAAS application is hosted remotely by shinyapps.io (https://www.shinyapps.io/) on the free pricing tier, which currently allows 25 active hours of use per month. Users can also run the application locally, by cloning the repository from GitHub and launching the application from a local R session, or by installing RStudio Shiny Server (https://www.rstudio.com/products/shiny/shiny-server/) and hosting the application on a local machine.

The PeskAAS application consists of a network of freely available components for data collection, storage, manipulation and analysis, catering to humanitarian organizations with low usage requirements (< 25 active hours per month) (Fig 2). The application is scalable for higher usage levels with modest subscription levies for KoBo toolbox, Shiny (https://www.shinyapps.io), Heliohost (https://www.heliohost.org) and Google Cloud Platform (GCP; https://cloud.google.com).

Fig 2. A diagrammatic representation of the PeskAAS application.

Fig 2

From bottom left, the catch from a fishing vessel is entered into a KoboCollect survey form on a smartphone. These data are uploaded to the KoboToolbox database (DB). The PesksPARSE.R script pulls these data along with the movement track of the fishing trip from PDS via an application-programming interface (API) every 24 hours. These data are then checked and filtered, and uploaded to the PeskaDAT database. The PeskAAS Shiny web app queries PeskaDAT and displays near-real-time graphics and analytics.

Methods

We developed and piloted PeskAAS in Timor-Leste from 2016 to 2019. In May 2019, the Timorese Government adopted and launched this technology as their official national fisheries monitoring system.

Catch documentation at landing sites

Fisheries catch data were collected on 3G-enabled android tablets using a digital survey form developed in KoBo toolbox (http://www.kobotoolbox.org/) a free suite of tools for field data collection. One data enumerator was hired in each of the 11 coastal districts to cover 25 landing sites across Timor-Leste (Fig 3). Atauro Island to the north of Dili (the national administrative centre) falls within the municipality of Dili, and is a disproportionately important area for national fisheries with a high population of fishers, so three enumerators are responsible to record landings across 12 small landing sites. Enumerators interview individual fishers (i.e., the names of fishers are collected, and their catch profile directly associated to them) when they return from fishing. Data collected include transport type (motor, canoe, on foot), gear type (gill net, seine net, beach seine, hand line, long line, spearfishing, trap, gleaning), habitat type where fishing took place (reef, fish aggregating device, deep, shore or mangrove), number of fishers (i.e., number of men, women and children engaged in that fishing trip), trip duration (rounded to nearest hour), species or species group, sizes (fork length to nearest cm) of all fish landed and number caught by species or species group, and the sale price per kg or per number of fish, if the catch was destined for market. The catch survey form evolved through time to integrate a growing list of fishers and identified species, and in response to various feedback mechanisms, such as error flagging and workshops with fisheries managers. Species of particular local importance were selected based on index of relative importance analysis on Timor-Leste fisheries [20] and these are retained at species level. All other species captured in the fishery are classified by family, or aggregated further into one of the nine groups of species constituting the Marine Fishes division of the FAO International Standard Statistical Classification of Aquatic Animals and Plants [21] (S1 Data).

Fig 3. Map of Timor-Leste illustrating landing sites where small-scale fisheries catch was recorded using smartphones or tablets.

Fig 3

All research was authorised and conducted in partnership with the Timor-Leste Ministry of Agriculture and Fisheries. All catch data collection was carried out with the verbal consent of the fisher. All participation in catch data monitoring and vessel tracking was voluntary, and fishers not willing to participate were not prejudiced against in any way.

peskaDAT database

We developed a cloud-based MySQL database of filtered landings records called ‘peskaDAT’, to host cleaned and checked fisheries landings data, geo-located boat tracks and ancillary tables such as species, boat, gear and habitat information in an easily accessible and mutable format (S2 Data). This database is hosted by Heliohost, a free hosting platform with several MySQL relational database servers. A monthly database backup is created and stored locally in.rds format (an R binary data file) in a Dropbox folder to ensure data perpetuity and backwards compatibility.

peskaPARSE.R script

To automatically access landing records from KoBo toolbox, and filter, manipulate and submit the cleaned records to the peskaDAT database on a regular (daily) basis, we developed an R script called ‘peskaPARSE.R’ (S3 Data) that is scheduled on a daily cron job (a command to a server to be executed at a specified time) run on a Google Cloud Platform virtual machine. The script first accesses the KoBo toolbox API (application programming interface that allows access to the data) and pulls the new catch records into the R environment. The catch weight for each new record is estimated using length-weight parameters obtained from FishBase (www.fishbase.org) using the rfishbase R package [22]. Several filters are applied according to thresholds including species- or group-specific length, number of individuals, weight and price boundary checks, formatting error checks, and invalid gear/habitat combination checks. Suspect entries are flagged for curation by a moderator, and their values are automatically suppressed from contributing to downstream applications (including the PeskAAS dashboard in Fig 1) until records are amended in the KoBo toolbox dashboard. This is achieved via prompt follow-up clarification with field-based observers, to ascertain whether data entry errors were made during form submission or whether the record in question is a genuine outlier.

To automatically run the peskaPARSE.R script on a daily basis, we deployed a free Ubuntu 18.04 minimal virtual machine (VM) instance on the Google Cloud Platform, transferred the script to a convenient user directory (specified by the [address] argument below), and scheduled a 24-hourly cron job by appending the following line to the /etc/crontab file:

0 0 * * * root Rscript -e 'source("[address]")'

where [address] is replaced by the web location of the R script. In our case we stored the script in a publicly available Dropbox directory and modified the public link to terminate with download = 1 to enable direct sourcing (see https://github.com/shaunpwilkinson/PeskAAS for further details). For the script to successfully import the raw trip- and landing records from the KoBo and Pelagic Data Systems APIs, and deposit the filtered records in the peskaDAT MySQL database, three authorization files must be stored in the same directory as the peskaPARSE.R file: a single-line text file named KoBo-auth.txt containing the KoBo toolbox username and password, delimited by a colon operator, and similarly-formatted files containing log-on credentials for the Pelagic Data Systems dashboard (PDS-auth.txt) and the peskaDAT MySQL database (peskaDB-auth.txt; user with SELECT privileges). The regular cleaning and filtering of new landings records ensures that the data available for analysis and visualization are timely and trustworthy.

Geospatial vessel tracking

To visualise geospatial fishing effort and extrapolate fishing effort from individual trips to community, municipal and national levels, we installed tamperproof solar-powered GPS units (PDS v1.25c) developed by Pelagic Data Systems Inc. (San Francisco, CA) on to 5–15 boats per landing site (N = 437). Tracking was voluntary and fishers bore no costs. Trackers record point location data automatically every 5 seconds and communicate those data when in range of a cellular network (Fig 4). Vessel tracks were also linked to the trip’s catch data, where available, using the unique GPS unit ID, allowing us to train a model to predict unknown variables for trips with GPS data only, such as gear and habitat type.

Fig 4. The relative effort heat map of small-scale fishing vessel tracks between August 2018 and February 2020 in Timor-Leste from the PeskAAS dashboard.

Fig 4

Red shading represents areas of highest effort (near to homeports and shore), and orange to yellow shading shows areas fished with decreasing effort further from shore. Map data © OpenStreetMap contributors. Map layer by Esri via leaflet [23].

Fisheries analytics

To quantify how catch volume varied over time and space, the catch-per-unit-effort (CPUE) is used as a metric for relative fish abundance, and to track the response of fish stocks to fishing pressure [24]. For CPUE, a standard unit of effort is required. For PeskAAS, we use raw CPUE, with effort standardized into the unit of fisher-hours on each fishing trip, calculated as the trip duration in hours multiplied by the number of people who were actively fishing on that boat during that trip. The complexity of more robust CPUE standardization (see [24]) of multiple gear types in tropical, multi-habitat, mixed species fisheries makes it impractical in a livelihoods context, so fisher hours is used as a unit applicable across all fisheries and scales.

To generate accurate regional and national catch and CPUE estimates, it is necessary to estimate the frequency and duration of fishing trips for each boat type, known as a vessel activity coefficient (VAC). To generate an accurate VAC accounting for differences in boat type, vessel tracks were used to generate monthly VAC values according to motorized and non-motorized vessels, and were used to calculate the first national scale estimates of fish production based on SSF landings in Timor-Leste (Eq 1).

The national monthly catch (in tons; C) is estimated as:

C=bCPUEb×EPTb×VACb×Nb×0.001 (1)

where b refers to the boat type (canoe or motor-powered; shore based fishing accounted for < 2% of reported landings and was hence omitted from the analysis); CPUE is the monthly catch per unit effort (averaged across all sites, in kg per fisher-hour); EPT is the median effort per trip (fisher-hours); VAC is the vessel activity coefficient (average number of trips per month); and Nb is the total number of boats of type b in the national fleet (national fisher and boat census data obtained from the Timor-Leste Ministry of Agriculture and Fisheries).

Supervised prediction of missing trip attributes

The integration of shore-based observer data with high-resolution geo-located vessel fishing tracks from on-board GPS units from Pelagic Data Systems Inc. allowed us to validate a supervised classification approach for predicting gear and habitat types in the case where only GPS data are available (i.e. trips that are tracked but catch is not recorded by enumerators). For each tracked but unobserved trip, a donor trip is selected from the subset of trips for which both GPS and observer data are available, based on spatial nearest-neighbour analysis [25]. To achieve this, ten GPS vectors from each trip spaced at even time intervals are used to generate training- and query-data matrices for input into the nn2 function in the RANN R package [26]. Donor trips are assigned based on minimum Euclidean distance and are only assigned if the distance is < 0.20 km. To validate this approach, we randomly allocated the linked trip set available as of 31 July to 80% training data and 20% query data, and tested the success rate in terms of number of gear and habitat types correctly predicted in the query set over 100 iterations. The nearest-neighbour classification approach correctly predicted 83.4% (SD = 0.023%) of gear types and 91.9% (SD = 0.021%) of habitat types based on 741 training observations and 183 query observations.

Results & discussion

At the pilot’s inception in 2016, the Timor-Leste government and fishers had very sparse quantitative data with which to characterise fisheries or determine production trends over time. PeskAAS was developed concurrently with the co-generation of a national database of SSF landings with the Timor-Leste National Fisheries Directorate. As of 31 July 2020, 59,000 fishing trips have been geotracked, representing 810,000 km travelled over 313,000 hours. Catch data was recorded for 29,251 trips, resulting in 32,872 landings records representing a total catch weight of 298.5 tonnes. PeskAAS has already been utilised to test the effectiveness of fish aggregating devices at the boosting catch rates of nearshore artisanal fishers [27] and enabled the first calculation of national fisheries production for the Timor-Leste SSF fleet [20]. The full adoption of PeskAAS as the official national fisheries monitoring system of the Timorese government in 2019 suggests legitimacy and the potential for sustainable fisheries on a national level.

PeskAAS was designed to be a free, online data exploration tool to enable rapid development of simple, near-real time fisheries monitoring systems for accurate and timely fish production data to use in adaptive, evidence-based management of fisheries resources. The tracking hardware and data service from Pelagic Data Systems (PDS) is an optional extra and represents additional costs to governments that must be considered in terms of sustainability. All the analytics of PeskAAS relating to CPUE are done without PDS data. We found effort estimations that fishers provided if asked were sufficiently accurate, and a VAC can be calculated from this by averaging all trip durations recorded from certain fishers. The specific values of the vessel tracking functionality were 1) an understanding of effort and activity distribution and, 2) the ability to calibrate effort through dynamic VAC calculation over time, and 3) in certain contexts (not tested here) may provide a safety at sea function.

If collected and managed in inclusive processes with fishers, fishing location data can be used by fishers to better argue and prove tenure and/or use rights (i.e., in line with the FAO Voluntary Guidelines on fisheries [28] and tenure [29]), for example in marine spatial planning processes that can otherwise ignore complex socio-political inequalities [30]. This value was realised in the case of the TS Taipei container ship grounding in Taiwan, where spatial and catch records from small-scale fishers were utilised to leverage fair reparations to fishers from the shipping company [14]. To date the spatial information obtained from combined vessel tracking with PeskAAS has not been used for coastal zone management, but protecting the rights of Timorese fishers to marine areas is a key commitment in the new draft National Fisheries Strategy (2018) that the PeskAAS data and team helped to inform. In other contexts, there are concerns that such data might work against fisher livelihoods, i.e. in nations and regions where exclusive no take zones and top down compliance are preferred strategies [31, 32]. The intended and unintended implications of data innovations should be considered from the outset of any such pilot and subsequent scaling out phases.

The co-design of PeskAAS with fisheries managers was crucial in building a financially and institutionally sustainable system. This same user-centred design process ensured that the PeskAAS analytical workflow was not initially too complex, and only included statistics and insights that could be readily interpreted by fisheries management users. Hence, in scaling this tool to other countries and contexts, the need to build local legitimacy and a feeling of ownership amongst government stakeholders will necessitate a process of co-design. The technical capacity in Timor-Leste for digital systems is improving, but as in most low-income country governments, the long-term maintenance of the system will still require external support. Ongoing work on PeskAAS will develop its modularity and customisation through templates for catch forms, analytics package integrations (such as TropFishR [8]) and dashboard tutorials to guide managers, to allow for more flexibility to other fish production systems, countries and capacities.

PeskAAS was developed as an open source script to make it highly adaptable to different fisheries contexts and strategic objectives. The catch form and scripted analytics require no specialised equipment and the dashboard is displayed in a web browser. However, we acknowledge that the scripted nature of PeskAAS limits its use to those with programming expertise, or implies a need to hire help that may be uncommon or unavailable in low-income countries. Rather than be an off-the-shelf solution, we envision PeskAAS to be a software framework that external NGOs or multilateral agencies can utilise to establish a highly contextualised, user-centred system for obtaining and using data from small-scale fisheries to guide decision-making. Data generated by PeskAAS were used to show how fishing technology could improve fisher incomes and fish availability in Timor-Leste [27], which substantiates government investment in interventions that are more cognisant and sensitive to SSF. Future work will focus on developing modules and templates that can be populated by local actors in new fisheries contexts to reduce the coding workload and streamline implementation, but we anticipate some level of technical assistance will continue to be required.

PeskAAS in Timor-Leste is open access and publicly available. In theory, anyone with access to a computer, tablet or smartphone, and an internet connection, are able to see the data aggregated to the municipal level. The reality is that in Timor-Leste, as in many low-income countries, there are still substantial barriers (e.g., cost of technology, digital literacy, formal identification) to digital inclusion (the access to and use of ICTs) that limit the extent to which fishers can access and benefit from such data. Addressing these limitations represents challenges for future pilots where participatory action research principles would be relevant [33] and where initiative objectives include empowering individual fishers in management decision-making, or improving their livelihoods through fisher-level business planning. This was beyond the scope of the pilot we describe here.

Further capacity building is also necessary to ensure PeskAAS outputs are being correctly interpreted to inform policy and guide extension services delivered by government actors to and for fishing communities in Timor-Leste. Better data systems can only drive informed decision-making if the information is available and understandable. Currently, this PeskAAS is suited to boat-based fisheries, compounding the unawareness and exclusion of foot fisheries often conducted by women [34]. To get a full picture of SSF and enable local legitimacy and sustainability, Timor-Leste must build on initial successes with co-management [35] as a platform on which to base a range of data collection methods and strategies. This will ensure stakeholders are included in contributing local ecological knowledge and forming shared understanding and strategies for stewardship of their aquatic resources.

In conclusion, the pilot of PeskAAS enabled system refinements, illuminated limitations and developed preliminary data for decision makers. The data have been taken into consideration in national-level fisheries governance, through the new draft National Fisheries Strategy (2018) and revised Fisheries Decree Law (2019). The application has potential for government and non-government managers, researchers and students looking for a low cost solution to address SSF data gaps.

Supporting information

S1 Data. List of species, species groups and family categories used for recording catch along with a and b parameters used to calculate weight from length measurements.

(DOCX)

S2 Data. MySQL relational database schema with cascading foreign keys shown by dashed arrows.

Figure generated in MySQL Workbench (Oracle Corp.).

(DOCX)

S3 Data. PeskaPARSE.R’ script file.

The PeskaPARS.R script scheduled on a daily cron job, run on a Google Cloud Platform virtual machine.

(R)

Acknowledgments

We are very grateful to the Timorese fishers and community members who collaborated with us and Timor-Leste’s Ministry of Agriculture and Fisheries in this project. Particular thanks go to: Joctan Dos Reis Lopes for leading the PeskAAS team on the ground; to the WorldFish Timor-Leste team members Dave Mills, Mario Gomes, Mario Pereira and Agustinha Duarte for providing important local insights throughout the co-design process; to Pedro Rodrigues, Lucas Fernandes and the Fisheries Directorate staff for helping us to build from the ground up; and to Pip Cohen for insight and comments on this manuscript.

Data Availability

The peskAAS catch questionnaire, R script and data used to test the application in this study are archived in Dataverse https://doi.org/10.7910/DVN/TVGIJJ. The peskAAS code and documentation are hosted at https://github.com/shaunpwilkinson/peskAAS.

Funding Statement

This work was undertaken as part of the CGIAR Research Program on Fish Agri-Food Systems (FISH) led by WorldFish, and the CGIAR Big Data Platform Inspire Challenge 2018 led by CIAT and IFPRI. These programs are supported by contributors to the CGIAR Trust Fund. PeskAAS was established under the Fisheries Sector Support Program funded by the Royal Norwegian Embassy in Jakarta. The funders provided support in the form of salary for authors [A.T.] and field costs, but did not have any additional role in the study design, data collection and analysis, decision to publish, or preparation of the manuscript. Wilderlab is a recent, unassociated affiliation for S.P.W. and did not contribute funding towards the study. The specific roles of these authors are articulated in the ‘author contributions’ section.

References

  • 1.Kelleher K, Westlund L, Hoshino E, Mills D, Willmann R, de Graaf G, et al. Hidden harvest: The global contribution of capture fisheries. Worldbank; WorldFish; 2012. https://play.google.com/store/books/details?id=AQktDgAAQBAJ
  • 2.Mills DJ, Westlund L, de Graaf G, Kura Y, Willman R, Kelleher K. Under-reported and undervalued: small-scale fisheries in the developing world In: Pomeroy RS, Andrew NL, editors. Small-scale fisheries management: frameworks and approaches for the developing world. Wallingford: CABI; 2011. pp. 1–15. 10.1079/9781845936075.0001 [DOI] [Google Scholar]
  • 3.FAO. The State of World Fisheries and Aquaculture 2018—Meeting the sustainable development goals. Rome: The Food and Agriculture Organisation of the UN (FAO); 2018. p. 227. 978-92-5-130562-1 [Google Scholar]
  • 4.Hicks CC, Cohen PJ, Graham NAJ, Nash KL, Allison EH, D’Lima C, et al. Harnessing global fisheries to tackle micronutrient deficiencies. Nature. 2019;574: 95–98. 10.1038/s41586-019-1592-6 [DOI] [PubMed] [Google Scholar]
  • 5.Kolding J, Béné C, Bavinck M. Small-scale fisheries: Importance, vulnerability and deficient knowledge. Governance of Marine Fisheries and Biodiversity Conservation: Interaction and Co-evolution. 2014; 317–331. 10.1002/9781118392607.ch22 [DOI] [Google Scholar]
  • 6.Kolding J, Van Zwieten PAMM. The Tragedy of Our Legacy: How do Global Management Discourses Affect Small Scale Fisheries in the South? Forum Dev Stud. 2011;38: 267–297. 10.1080/08039410.2011.577798 [DOI] [Google Scholar]
  • 7.Dowling NA, Wilson JR, Rudd MB, Babcock EA, Caillaux M, Cope J, et al. FishPath: a decision support system for assessing and managing data- and capacity-limited fisheries In: Quinn TJ II, Armstrong JL, Baker MR, Heifetz J, Witherell D, editors. Assessing and Managing Data-Limited Fish Stocks. Alaska Sea Grant, University of Alaska Fairbanks; 2016. 10.4027/amdlfs.2016.03 [DOI] [Google Scholar]
  • 8.Mildenberger TK, Taylor MH, Wolff M. TropFishR: an R package for fisheries analysis with length-frequency data. Price S, editor. Methods Ecol Evol. 2017;8: 1520–1527. 10.1111/2041-210X.12791 [DOI] [Google Scholar]
  • 9.Gutiérrez NL, Hilborn R, Defeo O. Leadership, social capital and incentives promote successful fisheries. Nature. 2011;470: 386–389. 10.1038/nature09689 [DOI] [PubMed] [Google Scholar]
  • 10.FAO, ITU. E-Agriculture in Action. FAO and ITU; 2017. [Google Scholar]
  • 11.FAO. Information and communication technologies benefit fishing communities. Policies to support improved communications for development. New Directions in Fisheries. A Series of Policy Briefs on Development Issues. Rome: FAO; 2007. Report No.: 7. http://www.fao.org/3/a-a0991e.pdf
  • 12.Jeffers VF, Humber F, Nohasiarivelo T, Botosoamananto R, Anderson LG. Trialling the use of smartphones as a tool to address gaps in small-scale fisheries catch data in southwest Madagascar. Mar Policy. 2019;99: 267–274. 10.1016/j.marpol.2018.10.040 [DOI] [Google Scholar]
  • 13.Petrik M, Raemaekers DRS. The case for supporting small-scale fisheries governance through ICT. SAIIA; 2018. Report No.: 177. https://www.africaportal.org/publications/case-supporting-small-scale-fisheries-governance-through-ict/
  • 14.FAO and WorldFish. Information and communication technologies for small-scale fisheries (ICT4SSF)—A handbook for fisheries stakeholders In support of the implementation of the Voluntary Guidelines for Securing Sustainable Small-Scale Fisheries in the Context of Food Security and Poverty Eradication. Bangkok: 2020 [Google Scholar]
  • 15.James M, Mendo T, Jones EL, Orr K, McKnight A, Thompson J. AIS data to inform small scale fisheries management and marine spatial planning. Mar Policy. 2018;91: 113–121. 10.1016/j.marpol.2018.02.012 [DOI] [Google Scholar]
  • 16.Mallalieu KI, Rocke S. Selecting Sustainable ICT Solutions for Pro-Poor Intervention Digital Poverty. Practical Action Publishing; 2007. pp. 119–140. 10.3362/9781780441115.006 [DOI] [Google Scholar]
  • 17.Donnelly M. Implementing ICTs in Indonesia’s Small-Scale Fisheries: Identifying Common Implementation Challenges and the Development Paradigms that Shape Them. Masters Communication for Development, Malmö universitet. 2018. http://muep.mau.se/handle/2043/24803
  • 18.R Special Interest Group on Databases (R-SIG-DB), Wickham H, Müller K. DBI: R Database Interface. 2018. https://CRAN.R-project.org/package=DBI
  • 19.Ooms J, James D, DebRoy S, Wickham H, Horner J. RMySQL: Database Interface and “MySQL” Driver for R. 2019. https://CRAN.R-project.org/package=RMySQL
  • 20.López-Angarita J, Hunnam KJ, Pereira M, Mills DJ, Pant J, Teoh SJ, et al. Fisheries and aquaculture of Timor-Leste in 2019: Current knowledge and opportunities Penang, Malaysia: WorldFish; 2019. [Google Scholar]
  • 21.Food, Agriculture Organization of the United Nations (FAO-UN). FAO Fisheries & Aquaculture ASFIS List of Species for Fishery Statistics Purposes, Overview. 2 Nov 2006 [cited 27 Aug 2020]. http://www.fao.org/fishery/collection/asfis/en
  • 22.Boettiger C, Lang DT, Wainwright PC. rfishbase: exploring, manipulating and visualizing FishBase data from R. J Fish Biol. 2012;81: 2030–2039. 10.1111/j.1095-8649.2012.03464.x [DOI] [PubMed] [Google Scholar]
  • 23.Cheng J, Karambelkar B, Xie Y. Leaflet: Create interactive web maps with the javascript ‘leaflet’ library. 2019. Available: https://CRAN.R-project.org/package=leaflet [Google Scholar]
  • 24.Maunder MN, Punt AE. Standardizing catch and effort data: a review of recent approaches. Fish Res. 2004;70: 141–159. 10.1016/j.fishres.2004.08.002 [DOI] [Google Scholar]
  • 25.Cover T, Hart P. Nearest neighbor pattern classification. IEEE Trans Inf Theory. 1967;13: 21–27. 10.1109/TIT.1967.1053964 [DOI] [Google Scholar]
  • 26.Arya S, Mount D, Kemp SE, Jefferis G. RANN: Fast Nearest Neighbour Search (Wraps ANN Library) Using L2 Metric. 2019. Available: https://CRAN.R-project.org/package=RANN [Google Scholar]
  • 27.Tilley A, Wilkinson SP, Kolding J, López-Angarita J, Pereira M, Mills DJ. Nearshore Fish Aggregating Devices Show Positive Outcomes for Sustainable Fisheries Development in Timor-Leste. Frontiers in Marine Science. 2019;6: 487 10.3389/fmars.2019.00487 [DOI] [Google Scholar]
  • 28.Food and Agriculture Organization of the United Nations. Voluntary Guidelines for Securing Sustainable Small-Scale Fisheries in the Context of Food Security and Poverty Eradication. Food & Agriculture Org; 2018. https://play.google.com/store/books/details?id=zGl6DwAAQBAJ [Google Scholar]
  • 29.FOOD AND AGRICULTURE ORGANIZATION OF THE UNITED NATIONS. Voluntary guidelines on the responsible governance of tenure of land fisheries and forests in the context of national food security. FAO; 2014. http://www.fao.org/3/i2801e/i2801e.pdf [Google Scholar]
  • 30.Flannery W, Healy N, Luna M. Exclusion and non-participation in Marine Spatial Planning. Mar Policy. 2018;88: 32–40. 10.1016/j.marpol.2017.11.001 [DOI] [Google Scholar]
  • 31.Garcia SM, Boncoeur J, Gascuel D. Les aires marines protégées et la pêche Bioécologie, socioéconomie et gouvernance. hal.archives-ouvertes.fr; 2013. https://hal.archives-ouvertes.fr/hal-01904070/
  • 32.Stacey N, Acciaioli G, Clifton J, Steenbergen DJ. Impacts of marine protected areas on livelihoods and food security of the Bajau as an indigenous migratory people in maritime Southeast Asia. Marine protected areas: Interactions with fishery livelihoods and food security. 2017; 113–126. https://books.google.co.uk/books?hl=en&lr=&id=ckV3DwAAQBAJ&oi=fnd&pg=PA113&dq=Impacts+of+marine+protected+areas+on+livelihoods+and+food+security+of+the+Bajau+as+an+indigenous+migratory+people+in+maritime+Southeast+Asia&ots=3wXpvo9cMm&sig=bHIyW7VC4SL9sGkAZmKRI8lYAjI
  • 33.Apgar JM, Cohen PJ, Ratner BD, de Silva S, Buisson M-C, Longley C, et al. Identifying opportunities to improve governance of aquatic agricultural systems through participatory action research. Ecol Soc. 2017;22 Available: http://www.jstor.org/stable/26270053 [Google Scholar]
  • 34.Tilley A, Burgos A, Duarte A, Dos Reis Lopes J, Eriksson H, Mills D. Contribution of women’s fisheries substantial, but overlooked, in Timor-Leste. Ambio. 2020. 10.1007/s13280-020-01335-7 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 35.Tilley A, Hunnam K, Mills D, Steenbergen D, Govan H, Alonso-Poblacion E, et al. Evaluating the fit of co-management for small-scale fisheries governance in Timor-Leste. Frontiers in Marine Science. 2019;6: 392 10.3389/fmars.2019.00392 [DOI] [Google Scholar]

Decision Letter 0

Ismael Aaron Kimirei

15 Jul 2020

PONE-D-20-16520

PeskAAS: A near-real-time, open-source monitoring and analytics system for small-scale fisheries

PLOS ONE

Dear Dr. Tilley,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

==============================

ACADEMIC EDITOR: I read this MS with interest as it addresses an important gap in small-scale fisheries which require precision and reliability to address sustainable management of the fisheries. I am sure that the reviews it has received will greatly improve its quality. And, so, please address all the queries, especially of data flow as indicated by Reviewer #2.

==============================

Please submit your revised manuscript by Aug 29 2020 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.

  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.

  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols

We look forward to receiving your revised manuscript.

Kind regards,

Ismael Aaron Kimirei, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. We note that [Figure(s) 3 and 4] in your submission contain [map/satellite] images which may be copyrighted. All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For these reasons, we cannot publish previously copyrighted maps or satellite images created using proprietary data, such as Google software (Google Maps, Street View, and Earth). For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright.

We require you to either (1) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (2) remove the figures from your submission:

1.    You may seek permission from the original copyright holder of Figure(s) [3 and 4] to publish the content specifically under the CC BY 4.0 license. 

We recommend that you contact the original copyright holder with the Content Permission Form (http://journals.plos.org/plosone/s/file?id=7c09/content-permission-form.pdf) and the following text:

“I request permission for the open-access journal PLOS ONE to publish XXX under the Creative Commons Attribution License (CCAL) CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). Please be aware that this license allows unrestricted use and distribution, even commercially, by third parties. Please reply and provide explicit written permission to publish XXX under a CC BY license and complete the attached form.”

Please upload the completed Content Permission Form or other proof of granted permissions as an "Other" file with your submission.

In the figure caption of the copyrighted figure, please include the following text: “Reprinted from [ref] under a CC BY license, with permission from [name of publisher], original copyright [original copyright year].”

2.    If you are unable to obtain permission from the original copyright holder to publish these figures under the CC BY 4.0 license or if the copyright holder’s requirements are incompatible with the CC BY 4.0 license, please either i) remove the figure or ii) supply a replacement figure that complies with the CC BY 4.0 license. Please check copyright information on all replacement figures and update the figure caption with source information. If applicable, please specify in the figure caption text when a figure is similar but not identical to the original image and is therefore for illustrative purposes only.

The following resources for replacing copyrighted map figures may be helpful:

USGS National Map Viewer (public domain): http://viewer.nationalmap.gov/viewer/

The Gateway to Astronaut Photography of Earth (public domain): http://eol.jsc.nasa.gov/sseop/clickmap/

Maps at the CIA (public domain): https://www.cia.gov/library/publications/the-world-factbook/index.html and https://www.cia.gov/library/publications/cia-maps-publications/index.html

NASA Earth Observatory (public domain): http://earthobservatory.nasa.gov/

Landsat: http://landsat.visibleearth.nasa.gov/

USGS EROS (Earth Resources Observatory and Science (EROS) Center) (public domain): http://eros.usgs.gov/#

Natural Earth (public domain): http://www.naturalearthdata.com/

3. In your Methods section, please provide additional location information of the study sites, including geographic coordinates for the data set if available.

4. In your Methods section, please provide additional information regarding the permits you obtained for the work. Please ensure you have included the full name of the authority that approved the study sites access and, if no permits were required, a brief statement explaining why.

5. Please provide additional details regarding participant consent. In the ethics statement in the Methods and online submission information, please ensure that you have specified (1) whether consent was informed and (2) what type you obtained (for instance, written or verbal, and if verbal, how it was documented and witnessed).

6.Thank you for stating the following in the Competing Interests section:

[The authors have declared that no competing interests exist.].   

We note that one or more of the authors are employed by a commercial company: Wilderlab, Wellington

  1. Please provide an amended Funding Statement declaring this commercial affiliation, as well as a statement regarding the Role of Funders in your study. If the funding organization did not play a role in the study design, data collection and analysis, decision to publish, or preparation of the manuscript and only provided financial support in the form of authors' salaries and/or research materials, please review your statements relating to the author contributions, and ensure you have specifically and accurately indicated the role(s) that these authors had in your study. You can update author roles in the Author Contributions section of the online submission form.

Please also include the following statement within your amended Funding Statement.

“The funder provided support in the form of salaries for authors [insert relevant initials], but did not have any additional role in the study design, data collection and analysis, decision to publish, or preparation of the manuscript. The specific roles of these authors are articulated in the ‘author contributions’ section.”

If your commercial affiliation did play a role in your study, please state and explain this role within your updated Funding Statement.

2. Please also provide an updated Competing Interests Statement declaring this commercial affiliation along with any other relevant declarations relating to employment, consultancy, patents, products in development, or marketed products, etc.  

Within your Competing Interests Statement, please confirm that this commercial affiliation does not alter your adherence to all PLOS ONE policies on sharing data and materials by including the following statement: "This does not alter our adherence to  PLOS ONE policies on sharing data and materials.” (as detailed online in our guide for authors http://journals.plos.org/plosone/s/competing-interests) . If this adherence statement is not accurate and  there are restrictions on sharing of data and/or materials, please state these. Please note that we cannot proceed with consideration of your article until this information has been declared.

Please include both an updated Funding Statement and Competing Interests Statement in your cover letter. We will change the online submission form on your behalf.

Please know it is PLOS ONE policy for corresponding authors to declare, on behalf of all authors, all potential competing interests for the purposes of transparency. PLOS defines a competing interest as anything that interferes with, or could reasonably be perceived as interfering with, the full and objective presentation, peer review, editorial decision-making, or publication of research or non-research articles submitted to one of the journals. Competing interests can be financial or non-financial, professional, or personal. Competing interests can arise in relationship to an organization or another person. Please follow this link to our website for more details on competing interests: http://journals.plos.org/plosone/s/competing-interests

7. Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

3. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

4. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: Review notes:

The manuscript introduces a new tool for small-scale fisheries data collation and analysis using an Rshiny platform. The manuscript is well written and the introduction does a good job of describing the many issues with monitoring small-scale fisheries. The tool itself is sophisticated and is now being used by the Timor-Leste government in monitoring their fisheries. This is a fantastic example of an operational fisheries tool and will make a great addition to the literature.

The tool appears to primarily be used in monitoring catch and effort, rather than providing analytical assessments for fisheries managers (i.e. stock assessment). This is of course fine (and much needed in the case of small scale fisheries), but I think perhaps this specific scope of the tool needs to be stated clearly somewhere, perhaps in the abstract. Or perhaps a paragraph in the discussion could envision the next steps for this tool/data in fisheries management? I.e. what comes next after appropriate monitoring?

Much of the manuscript focused on describing the tool pipeline, from shore-based observers to the final Rshiny interface. The description of this pipeline was logical and detailed, but I did have a few line-specific comments below that request more information in some sections to help improve potential reproducibility. Particularly, for Ln 171 – 184 this seems to be the biggest analytical component of the tool but the details and results are limited (see broader comment below).

Finally, the introduction makes the case for a ‘light touch’ tool for data collection and analytics. While I agree with their logic in the introduction, I don’t quite agree that peskAAS is ‘light touch’. For example, the peskAAS application in Timor-Leste involved observers with tablet computers, gps trackers on boats, sophisticated coding in R, plus multiple software subscription services (e.g. Rshiny and Kobo toolbox). The authors do detail some of the limitations in the discussion, but I think more could be done to address the scalability and ‘light touch’ effectiveness of this tool.

Abstract

- Would be useful to indicate what type of data is needed to operate peskAAS?

- Needs to explain that the peskAAS was developed and implemented for small scale fisheries in Timor-Leste

- Growth parameters doesn’t seem like the correct term to me (see comment below). Suggest using ‘length-weight’.

Introduction

- Ln 41: can you list some other tools that are used in management? E.g. fishpath (https://www.fishpath.org/the-tool), stock synthesis etc.

- Ln 41: there is no closing parenthesis

- Reference 15 – title is incorrect here. Also, is this peer-reviewed? If not then I suggest not using it as a reference

- Ln 52: need a closing parenthesis

-

peskAAS

- Ln 76: more information needed on spline type here

- Ln 89: is this the figure caption? More text is needed here to better explain the pipeline, and all the acronyms and terms. E.g. PDS, DB, API,

- Ln 91: list tablet model

- Ln 92: can you add a sentence describing what Kobotool box is?

- Ln 97: what are the gear type options?

- Ln 99: what size was measured (fork length, standard length, total length) and what units?

- Ln 99: units for trip duration?

- Ln 114: I couldn’t find this supp file 2

- Ln 118: I’m not sure if this is an error, or perhaps I don’t have the right supp file. But the VBGF is typically used to get size-at-age, using parameters k, t, and l-infinite. The parameters in table supplementary information 2 are for a and b, and are described as being used to convert length-to-weight. Suggest not using the VBGF term but rather simply saying ‘length-to-weight’ conversion.

- Ln 124: does the italics of ‘via’ have special meaning here? It’s not clear what it is

- Ln 135: I didn’t know what

- Ln 143-144: roughly how many trips to the shore-based data collectors sample?

- Ln 145: insert model number of the gps units (as per typical scientific notation)

- Ln 146: was it only voluntary boats that had gps installed? Or is this mandated at a local/state/national level?

- Ln 147-148: great figure. Is the concentration of effort near ports a function of effort or the range of cellular towers?

- Ln 157: wouldn’t it make more sense to divide by the number of fishers?

- Ln 167: isn’t cpue kg per hour per fisher? Or is the per fisher component handled in the EPT? Some clarification needed here.

- Equation 1: why multiply by 0.001?

- Ln 171 – 184: this seems to be the biggest analytical component of the tool but the details and results are sparse. Suggest adding more methods details and a results figure/table of the cross-validation test. Specifically: (1) clarify if this analysis is done as part of the peskAAS pipeline, or if this is a secondary analysis for validation; (2) can you add references to justify that this was an appropriate method to fill in missing attributes?; (3) what temporal spacing did you use? (ln 177); (4) was the 80%/20% cross validation only performed once? If so this is not adequate. Typically, this random split is repeated multiple times (e.g. 10 times) and the performance validated each time. Or you could use k-folds validation.

Ln 198-200: this is really great to see it is operational.

Reviewer #2: General comments:

This manuscript nicely lays out the development of an online or desktop tool to visualize fisheries-dependent data for use in management and decision making. This tool is already being incorporated into fisheries management in Timor-Leste, indicating its utility and need for supporting small scale fisheries. This manuscript is well done but I would encourage the authors to consider a couple aspects to help highlight where this tool could be useful and to clarify how it functions.

1. Framing: I would encourage the authors to consider how they contextualize where this tool would be useful. The abstract highlights the near real-time production data being aggregated through this tool, indicating an ability to use it for adaptative management. However, the introduction highlights its utility in gaining an understanding of food-security (based on production) while the discussion highlights utility in marine spatial planning. This tool could help in all three of these contexts and they rightly deserve to be highlighted. However, I would encourage the authors to provide more connection on these points being made between sections.

For instance: fish as a base for food security requires effective management for lasting security. Small scale fisheries afford the opportunity to provide food security but are difficult to manage because of a lack of data collection and dispersed nature of the fishery. And in order to sustain food security through development it is necessary to understand where fishing effort predominately takes place.

2. Data collection and flow: I had trouble understanding the data flow for this tool. It is not very clear if the spatial and temporal aspects of the data are because of the VMS data or if the shore side sampling provides a spatial component depending on which port the data were collected, it seems only the VMS data provide the spatial component. The VMS data appear to be a critical aspect of the functioning and ultimate use of this tool. However, this feature is called an “optional extra” on line 204. The authors do point out how this would change the function of the tool, however, the abstract and discussion highlight the data gaps around spatial fisheries data. Therefore, it seems that the VMS component is critical for the use of this tool. I understand it will function without the VMS data, so it is important to understand all the data incorporated and how it fits the potential uses outlined in point 1 above.

I would note that the description of data collection and flow is highlighted in the Figure 2 caption (lines 90 – 101 after the references). This information should be in the main text as well. Additionally, Figure 2 doesn’t appear to be referenced in the manuscript.

Specific Comments

Line 27: Missing citation for “small scale fisheries are responsible for half of the global fish catch”

Line 69: Where do the landings records come from?

Lines 73-74. The resolution for Figure 1 is too low to be able to read the screen shot of what the app can do. As a side note about the app: upon taking a look at the shinyapp, I wonder if it would be more intuitive to have none of the satellite boxes checked upon opening the app and allowing the user to specify which data they want to see instead of having to deselect everything and then select.

Lines 75-78: There is not enough detail about the smoothing spline or how a user should decide whether to use this function. Equation 1 at line 163 does not include the smoothing spline either, therefore it is not possible to decipher how this aspect of the tool functions.

Line 114: It looks like supplementary information 2 is a species list with growth parameters, am I missing supplementary file 2 to support ‘peskaPARSE.R’?

Line 143: Are shore-based data collectors how catch data are normally collected for these fisheries? The information provided under the Figure 2 Caption titled Catch document at landing sites is very helpful context. I would recommend this being added to the methods to help readers understand data collection a little more clearly. I also am not seeing Figure 2 (or Figure 3) referenced in the text, I see Figure 1 at line 73 and then Figure 4 at line 148.

Line 146: were the GPS/VMS units that were placed on the 5-15 boats per landing site placed on both power and canoe vessels?

L

ine 147: Is it costly to the harvesters to upload VMS data via cell phone? For people interested in implementing this system it could be helpful to get an idea of the overall cost to harvesters. Is there also a logbook on the cellphone that harvesters can record catch that then gets associated with the location data or that only comes from the shore side data?

Line 154: what does relative fishing success mean? I would recommend rephrasing this for clarity.

Line 188: are there a minimum number of observations that are needed to be able to use the data? For instance, US federal fisheries require a minimum of 3 observations to be able to aggregate data otherwise it can’t be shown. This would mean some data are left out, is this the case for Timor-Leste? It would be good to know if not all data are shown.

Lines 198 – 200: I personally would like to have a bit more detail about how this tool is being utilized by the Timorese government than what is provided.

Line 204: the spatial data from VMS seems critical, unless the port samples are also considered to be part of the spatial data (doesn’t seem like it). Are there area closures or other types of management that make this spatial data critical to adaptive management.

Lines 205-207 indicate the fishery footprint data are most useful for coastal zone planning, are they not used in the

current fisheries management practices?

Figures 2 and 3 are not cited in the text from what I can tell.

It is not clear what Supplementary Information 2 is supporting

Reviewer #3: Dear Authors,

Thank you very much for an interesting paper describing this new system for an open-source monitoring and analytics system. I agree that especially for small-scale fisheries it is a great problem to have reliable landings and catch data as a very important first step to establish some kind of fisheries management.

I think your system well developed and you present the results in an appropriate fashion supported by the data. The results show that this could be a very useful tool for collecting data for fisheries managers. I have, however, some doubts how this system could be established in practice in low income countries. For the development of your system and to show how it works you have selected Timor-Leste as an example. For this trial you have organised the data collection by hiring data collectors (at least that how it is described) and I am asking myself how this should work in the long run. Should the fishers report the data themselves (what I assume from your descriptions)? What will be the incentives of the fishers to participate in such a system? Misreporting is a problem in all fisheries management systems around the world.

Therefore, could you describe a bit better how you foresee that this system will be used afterwards, who need to participate in the system and what the authorities can do with this information. As I am not a fisheries biologist, I am also not sure about the fishbase database. Is the catch weight (average of all fishes in the catch, the single fish weights?) really the only parameter you need to judge the conditions of the fish stocks in mixed fisheries?

I have a few additional more detailed comments regarding your paper:

Line 36 ff.: I agree that it is a problem in low income countries to collect data on catch/landings but the question is if those data alone would help to overcome the malnutrition in many countries due to the ability to establish a management system. I think we are still far away from introducing a fisheries management system with catch and/or landings data alone. Especially for mixed fisheries I believe that another approach could work. Many coastal communities have established some kind of management strategies as they have usually a substantial knowledge about the resources and have established some kind of self-management (e.g. in a community-based-management system). Is there information on self-management in the fishing communities in Timor-Leste?

Lines 154 ff.: How does e.g. the number of fishers on a vessel influence the input data (fisher-hours)? The CPUE is very much depending on vessels size, fishing gear employed, number of fishers on board, etc. In small-scale fisheries often the owner alone is fishing or only a small number of fishers fish together.

Lines 166 ff.: I cannot judge how good those estimated numbers are. My guess is, however, that there are so many factors influencing catch levels that this may squeeze everything too much into a certain routine calculation. However, I am aware that this may be the best methodology available in this case.

Lines 183-185: Looks good but still I have doubts about the overall effort necessary to get all this detailed information and if there are no other possibilities.

**********

6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

Reviewer #3: No

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step.

PLoS One. 2020 Nov 13;15(11):e0234760. doi: 10.1371/journal.pone.0234760.r002

Author response to Decision Letter 0


19 Sep 2020

(This has also been provided in the form of the "Response to reviewers" file)

Thank you very much for taking the time to carefully review our manuscript. Your comments have been extremely helpful in improving and clarifying the paper. Please find our responses to each of your comments below (in blue) with further clarification where appropriate, and the line numbers of any subsequent changes made to the ms.

PONE-D-20-16520

PeskAAS: A near-real-time, open-source monitoring and analytics system for small-scale fisheries

ACADEMIC EDITOR: I read this MS with interest as it addresses an important gap in small-scale fisheries which require precision and reliability to address sustainable management of the fisheries. I am sure that the reviews it has received will greatly improve its quality. And, so, please address all the queries, especially of data flow as indicated by Reviewer #2.

Thank you. We have addressed all of the reviewers’ helpful comments, stating below

2. We note that [Figure(s) 3 and 4] in your submission contain [map/satellite] images which may be copyrighted. We require you to either (1) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (2) remove the figures from your submission:

Fig 3 was drawn as a vector image by AT so does not require copyright information. Copyright information has been added to the caption of figure 4.

3. In your Methods section, please provide additional location information of the study sites, including geographic coordinates for the data set if available.

Given the national scale of the study, Figure 3 has been amended to include lat/long grid coordinates instead of providing coordinates for each of the landing sites.

4. In your Methods section, please provide additional information regarding the permits you obtained for the work. Please ensure you have included the full name of the authority that approved the study sites access and, if no permits were required, a brief statement explaining why.

5. Please provide additional details regarding participant consent. In the ethics statement in the Methods and online submission information, please ensure that you have specified (1) whether consent was informed and (2) what type you obtained (for instance, written or verbal, and if verbal, how it was documented and witnessed).

We have added the following statement from line 137. ”All research was authorised and conducted in partnership with the Timor-Leste Ministry of Agriculture and Fisheries. All catch data collection was carried out with the verbal consent of the fisher. All participation in catch data monitoring and vessel tracking was voluntary, and fishers not willing to participate were not prejudiced against in any way.”

6.Competing Interests section:

We note that one or more of the authors are employed by a commercial company: Wilderlab, Wellington

1. Please provide an amended Funding Statement declaring this commercial affiliation, as well as a statement regarding the Role of Funders in your study. If the funding organization did not play a role in the study design, data collection and analysis, decision to publish, or preparation of the manuscript and only provided financial support in the form of authors' salaries and/or research materials, please review your statements relating to the author contributions, and ensure you have specifically and accurately indicated the role(s) that these authors had in your study. You can update author roles in the Author Contributions section of the online submission form.

Please also include the following statement within your amended Funding Statement. “The funder provided support in the form of salaries for authors [insert relevant initials], but did not have any additional role in the study design, data collection and analysis, decision to publish, or preparation of the manuscript. The specific roles of these authors are articulated in the ‘author contributions’ section.” If your commercial affiliation did play a role in your study, please state and explain this role within your updated Funding Statement.

Funding statement updated as required from line 326. This has been included in the cover letter along with the updated competing interests statement.

2. Please also provide an updated Competing Interests Statement declaring this commercial affiliation along with any other relevant declarations relating to employment, consultancy, patents, products in development, or marketed products, etc. Within your Competing Interests Statement, please confirm that this commercial affiliation does not alter your adherence to all PLOS ONE policies on sharing data and materials by including the following statement: "This does not alter our adherence to PLOS ONE policies on sharing data and materials.”.

Declared as required

Please include both an updated Funding Statement and Competing Interests Statement in your cover letter. We will change the online submission form on your behalf.

7. Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information.

We have amended the in-text citation and caption of supplementary information 3 and provided the associated Supplementary information 3 file (PeskaParse.R script) that was accidentally omitted when the paper was initially submitted.

Reviewer #1: Review notes:

The manuscript introduces a new tool for small-scale fisheries data collation and analysis using an Rshiny platform. The manuscript is well written and the introduction does a good job of describing the many issues with monitoring small-scale fisheries. The tool itself is sophisticated and is now being used by the Timor-Leste government in monitoring their fisheries. This is a fantastic example of an operational fisheries tool and will make a great addition to the literature.

The tool appears to primarily be used in monitoring catch and effort, rather than providing analytical assessments for fisheries managers (i.e. stock assessment). This is of course fine (and much needed in the case of small scale fisheries), but I think perhaps this specific scope of the tool needs to be stated clearly somewhere, perhaps in the abstract. Or perhaps a paragraph in the discussion could envision the next steps for this tool/data in fisheries management? I.e. what comes next after appropriate monitoring?

Thank you. Yes, complicated stock assessment analytics were not feasible for the capacity level of fisheries managers in Timor when PeskAAS was developed. However, we are currently developing new integrations of statistical tools and techniques into the analytical workflow. We have made this clearer in the abstract (lines 18-20) and throughout the discussion (lines 276-79).

Much of the manuscript focused on describing the tool pipeline, from shore-based observers to the final R shiny interface. The description of this pipeline was logical and detailed, but I did have a few line-specific comments below that request more information in some sections to help improve potential reproducibility. Particularly, for Ln 171 – 184 this seems to be the biggest analytical component of the tool but the details and results are limited (see broader comment below).

This has been clarified in the ms (lines 219-33) and all of the code of the nearest neighbor analysis is provided so can be interpreted and replicated when necessary.

Finally, the introduction makes the case for a ‘light touch’ tool for data collection and analytics. While I agree with their logic in the introduction, I don’t quite agree that peskAAS is ‘light touch’. For example, the peskAAS application in Timor-Leste involved observers with tablet computers, gps trackers on boats, sophisticated coding in R, plus multiple software subscription services (e.g. R shiny and Kobo toolbox). The authors do detail some of the limitations in the discussion, but I think more could be done to address the scalability and ‘light touch’ effectiveness of this tool.

This is certainly true and we concur that it has not been a light touch engagement to this point four years later. We have added a more thorough discussion of limitations and strengths of the tool for scaling in lines 280-290.

Abstract

- Would be useful to indicate what type of data is needed to operate peskAAS?

- Needs to explain that the peskAAS was developed and implemented for small scale fisheries in Timor-Leste

Amendments have been made to the abstract to clarify these two points (lines 13-20)

- Growth parameters doesn’t seem like the correct term to me (see comment below). Suggest using ‘length-weight’.

Changed as suggested

Introduction

- Ln 41: can you list some other tools that are used in management? E.g. fishpath (https://www.fishpath.org/the-tool), stock synthesis etc.

Added reference to specific tools (line 52)

- Ln 41: there is no closing parenthesis

- Reference 15 – title is incorrect here. Also, is this peer-reviewed? If not then I suggest not using it as a reference

This is a Master's thesis from the University of Malmo so not peer-reviewed, but we feel suitable for citation. The reference has been updated to ensure it is complete.

- Ln 52: need a closing parenthesis

Done

- Ln 76: more information needed on spline type here

We expanded the sentence to: “cubic smoothing splines weighted by trip effort to the CPUE data with a user defined smoothing parameter to aid in visualization”. Lines 91-2

- Ln 89: is this the figure caption? More text is needed here to better explain the pipeline, and all the acronyms and terms. E.g. PDS, DB, API,

Caption expanded with more details and acronyms defined

- Ln 91: list tablet model

Data can be collected on any tablet or phone running android. We used many different types so we have added that these were android tablets. We have made this clearer in the text (line 117)

- Ln 92: can you add a sentence describing what Kobotool box is?

Done

- Ln 97: what are the gear type options?

Added

- Ln 99: what size was measured (fork length, standard length, total length) and what units?

Added

- Ln 99: units for trip duration?

Added

- Ln 114: I couldn’t find this supp file 2

This should have been labelled “Supplementary information 3”, and the file was accidentally omitted. We have provided the PeskaPARSE.R script with the revision submission as Supplementary information 3.

- Ln 118: I’m not sure if this is an error, or perhaps I don’t have the right supp file. But the VBGF is typically used to get size-at-age, using parameters k, t, and l-infinite. The parameters in table supplementary information 2 are for a and b, and are described as being used to convert length-to-weight. Suggest not using the VBGF term but rather simply saying ‘length-to-weight’ conversion.

Changed as suggested

- Ln 124: does the italics of ‘via’ have special meaning here? It’s not clear what it is

Changed to non italics

- Ln 135: I didn’t know what

Comment incomplete?

- Ln 143-144: roughly how many trips to the shore-based data collectors sample?

This is stated in line 239 (= 29,251 trips up to July 2020). The average number of trips sampled per day across all enumerators is 3.

- Ln 145: insert model number of the gps units (as per typical scientific notation)

Entered

- Ln 146: was it only voluntary boats that had gps installed? Or is this mandated at a local/state/national level?

Tracking was voluntary. This has been clarified in the ms in lines 139 and 187

- Ln 147-148: great figure. Is the concentration of effort near ports a function of effort or the range of cellular towers?

No, this has nothing to do with cell range because the trackers are archival, meaning that when they are not in range of a cell tower they store location data on the device (for up to one year). The following text has been added to the caption to clarify: “Figure 4. The relative effort heat map of small-scale fishing vessel tracks between August 2018 and February 2020 in Timor-Leste from the PeskAAS dashboard. Red shading represents areas of highest effort (near to homeports and shore), and orange to yellow shading shows areas fished with decreasing effort further from shore. Basemap obtained from Esri ArcGIS via leaflet [23].”

- Ln 157: wouldn’t it make more sense to divide by the number of fishers?

Instead of multiplying? No, because if you have boat ‘A’ with 1 fisher fishing for 1 hour compared to boat ‘B’ with 2 fishers fishing for 1 hour, boat B will be fishing the same time but with double the effort. If we divided 1 hour by 2 fishers this would be 0.5, so half the effort of boat A, which would be incorrect.

- Ln 167: isn’t cpue kg per hour per fisher? Or is the per fisher component handled in the EPT? Some clarification needed here.

Clarified to show kg per fisher-hour

- Equation 1: why multiply by 0.001?

To return tonnes from kg

- Ln 171 – 184: this seems to be the biggest analytical component of the tool but the details and results are sparse. Suggest adding more methods details and a results figure/table of the cross-validation test. Specifically: (1) clarify if this analysis is done as part of the peskAAS pipeline, or if this is a secondary analysis for validation; (2) can you add references to justify that this was an appropriate method to fill in missing attributes?; (3) what temporal spacing did you use? (ln 177); (4) was the 80%/20% cross validation only performed once? If so this is not adequate. Typically, this random split is repeated multiple times (e.g. 10 times) and the performance validated each time. Or you could use k-folds validation.

Thank you for pointing out these shortcomings. We have changed the tense in the section to reflect that the nearest neighbor assignment occurs as part of the pipeline, and that we validated it on the data available up until 31 July 2020 (the code for the initial validation test is included under comment in the app.R file and the code for ongoing assignment of gear and habitat types is included in the peskaPARSE.R file (Supplementary file 3)).

The temporal spacing was distributed at even intervals over the course of the trip to allow for both spatial and temporal similarities in trip comparisons (Ms text has been updated to: ‘To achieve this, ten evenly temporally-spaced, two-dimensional GPS vectors from each trip are used to generate training- and query-data matrices’). We re-ran the analysis to iterate 100x rather than once, and we present both mean and stdev prediction success rates (thanks for pointing this out). We tried a few different classification methods and settled on NN based on predictive success and simplicity - (Cover & Hart 1967) in the text. (Lines 213-33)

Ln 198-200: this is really great to see it is operational.

Thank you

Reviewer #2: General comments:

This manuscript nicely lays out the development of an online or desktop tool to visualize fisheries-dependent data for use in management and decision-making. This tool is already being incorporated into fisheries management in Timor-Leste, indicating its utility and need for supporting small-scale fisheries. This manuscript is well done but I would encourage the authors to consider a couple aspects to help highlight where this tool could be useful and to clarify how it functions.

1. Framing: I would encourage the authors to consider how they contextualize where this tool would be useful. The abstract highlights the near real-time production data being aggregated through this tool, indicating an ability to use it for adaptive management. However, the introduction highlights its utility in gaining an understanding of food-security (based on production) while the discussion highlights utility in marine spatial planning. This tool could help in all three of these contexts and they rightly deserve to be highlighted. However, I would encourage the authors to provide more connection on these points being made between sections.

For instance: fish as a base for food security requires effective management for lasting security. Small scale fisheries afford the opportunity to provide food security but are difficult to manage because of a lack of data collection and dispersed nature of the fishery. And in order to sustain food security through development it is necessary to understand where fishing effort predominately takes place.

Thank you for this insight. We have improved consistency between sections and brought this together better throughout the discussion (lines 256-292)

2. Data collection and flow: I had trouble understanding the data flow for this tool. It is not very clear if the spatial and temporal aspects of the data are because of the VMS data or if the shore side sampling provides a spatial component depending on which port the data were collected, it seems only the VMS data provide the spatial component.

The VMS data appear to be a critical aspect of the functioning and ultimate use of this tool. However, this feature is called an “optional extra” on line 204. The authors do point out how this would change the function of the tool, however, the abstract and discussion highlight the data gaps around spatial fisheries data. Therefore, it seems that the VMS component is critical for the use of this tool. I understand it will function without the VMS data, so it is important to understand all the data incorporated and how it fits the potential uses outlined in point 1 above.

There are two levels of spatial components to the system:

1) Municipal: Enumerators are operating in different municipalities of the country, so the catch and effort can be summarised and grouped at this level to evaluate variations in fishing patterns, gears, species, habitats etc. by area of the country. For example, the north and south coasts of the country differ significantly in terms of species assemblage, habitat, bathymetry etc.

2) The movement tracks from the VMS devices provide very high resolution data of the activity space of each individual fishing vessel and hence the overall spatial extent of the national fishery. PDS tracking also enables the accurate measurement of effort in trip length (hours). However, at this point there is no integrated mechanism to detect at what time during the trip the gear was hauled or the catch was landed. Catch is only recorded when it reaches the shore and recorded by an enumerator.

The addition of VMS is not a critical aspect of the system. It works completely without vessel tracking, however, the ability to visualise fishing on a map is beneficial and popular. We have added clarification of exactly what value the PDS tracking adds to the PeskAAS system in the discussion in lines 248-268.

I would note that the description of data collection and flow is highlighted in the Figure 2 caption (lines 90 – 101 after the references). This information should be in the main text as well. Additionally, Figure 2 doesn’t appear to be referenced in the manuscript.

I think there was an error with the formatting of the original file because this section “Catch documentation at landings sites” was intended as a section in the methods, and is not a figure caption. We have added “METHODS” at the start of the section to clarify the paper structure. Figure 3 is referenced at the start of this paragraph (originally line 95). Figure 2 is referenced just before the figure itself (originally line 87).

Specific Comments

Line 27: Missing citation for “small scale fisheries are responsible for half of the global fish catch”

Inserted

Line 69: Where do the landings records come from?

Clarified in extended figure 2 caption and in lines 82-83 and 115-135

Lines 73-74. The resolution for Figure 1 is too low to be able to read the screenshot of what the app can do. As a side note about the app: upon taking a look at the shinyapp, I wonder if it would be more intuitive to have none of the satellite boxes checked upon opening the app and allowing the user to specify which data they want to see instead of having to deselect everything and then select.

We have replaced the screenshot with a higher-resolution version, but the website is live and open access so the best way of exploring functionality would be to visit the website itself (the URL is provided in the caption). We did start out having none of the tick boxes checked but changed to checking all by default after consulting with the primary user (Timor-Leste Ministry of Fisheries).

Lines 75-78: There is not enough detail about the smoothing spline or how a user should decide whether to use this function. Equation 1 at line 163 does not include the smoothing spline either, therefore it is not possible to decipher how this aspect of the tool functions.

We added the smoothing spline function just to help users better visualize the data - rather than to generate statistically robust trends/time series. We are hesitant to provide guidance on setting the smoothing parameter - since this will depend a lot on the application and what insight the user is looking for.

We have added additional details in the text about how the smoothing spline is calculated: “...a slider widget is included for users to fit cubic smoothing splines weighted by trip effort to the CPUE data with a user defined smoothing parameter that is dynamically adjustable to aid in visualization” lines 90-94

Line 114: It looks like supplementary information 2 is a species list with growth parameters, am I missing supplementary file 2 to support ‘peskaPARSE.R’?

Our apologies. This should have been labelled Supplementary file 3, and the file was accidentally omitted in any case. We have provided the PeskaPARSE.R script with the revision submission as Supplementary file 3.

Line 143: Are shore-based data collectors how catch data are normally collected for these fisheries? The information provided under the Figure 2 Caption titled Catch document at landing sites is very helpful context. I would recommend this being added to the methods to help readers understand data collection a little more clearly. I also am not seeing Figure 2 (or Figure 3) referenced in the text, I see Figure 1 at line 73 and then Figure 4 at line 148.

I think there must have been an error with the original file as this section “Catch documentation at landings sites” is a section in the methods already, and is not a figure caption. We have added “METHODS” at the start of the section to clarify the paper structure. Figure 3 is referenced at the start of this paragraph (originally line 95). Figure 2 is referenced just before the figure itself (originally line 87).

Line 146: were the GPS/VMS units that were placed on the 5-15 boats per landing site placed on both power and canoe vessels?

Yes to both. Clarified in text.

Line 147: Is it costly to the harvesters to upload VMS data via cell phone? For people interested in implementing this system it could be helpful to get an idea of the overall cost to harvesters. Is there also a logbook on the cellphone that harvesters can record catches that then gets associated with the location data or that only comes from the shore side data?

There is zero cost to the fishers (line 187) Currently no data are recorded by the fishers themselves, but they could if trained to use the app. All catch data are recorded by government enumerators at landing sites on shore, and all geolocation data are recorded and communicated automatically by the VMS unit without any input from the fisher. Currently in Timor-Leste fisher participatory monitoring is only possible when smartphones can be provided, and even then literacy and capacity levels inhibit the scale of the work. However, an app that fishers can collect, hold and use their own data to improve efficiency and reduce costs is planned in the coming years. This is discussed in lines 280-292

Line 154: what does relative fishing success mean? I would recommend rephrasing this for clarity.

Rephrased to “To quantify how catch volume varied over time and space, the catch-per-unit-effort (CPUE) is used as a metric for relative fish abundance, and to track the response of fish stocks to fishing pressure [24]” (lines 200-1)

Line 188: are there a minimum number of observations that are needed to be able to use the data? For instance, US federal fisheries require a minimum of 3 observations to be able to aggregate data otherwise it can’t be shown. This would mean some data are left out, is this the case for Timor-Leste? It would be good to know if not all data are shown.

We consulted with the Timorese government on the issue of privacy and data granularity, and it was agreed that we would not reveal fisher’s details but that individual landing and track records were acceptable to present on the application. Hence, all data are present in the app regardless of minimum observation number.

Lines 198 – 200: I personally would like to have a bit more detail about how this tool is being utilized by the Timorese government than what is provided.

We have added text to the discussion to detail current and recent uses of the application and data generated (lines 240-3, 261-5, 284-8, and 312-4).

Line 204: the spatial data from VMS seems critical, unless the port samples are also considered to be part of the spatial data (doesn’t seem like it). Are there area closures or other types of management that make this spatial data critical to adaptive management?

There are some marine protected areas, but management is very limited and currently PDS tracking has not been integrated into formal or legal enforcement mechanisms related to them. This is being pursued by conservation NGOs with interests in these MPAs, but the government has not prioritized funding or activities to support this application as yet. Discussion of this has been added in lines 261-5

Lines 205-207 indicate the fishery footprint data are most useful for coastal zone planning, are they not used in the current fisheries management practices?

To date the spatial information from PeskAAS has not been used to zone coastal areas by user groups, but protecting the rights and fishing ground of small-scale fishers is a key element of the new National fisheries strategy that PeskAAS helped to inform. There are some marine protected areas, but management is very limited and currently PDS tracking has not been integrated into enforcement mechanisms related to them. This discussion has been added in lines 256-268

Figures 2 and 3 are not cited in the text from what I can tell.

There was an error with the original file formatting as the section “Catch documentation at landings sites” is a methods section, not a figure caption. We have added “METHODS” at the start of the section to clarify the paper structure. Figure 3 is referenced at the start of this paragraph (originally line 95). Figure 2 is referenced just before the figure itself (originally line 87).

It is not clear what Supplementary Information 2 is supporting

Species were grouped to streamline the options available for enumerators, with the most important species for the fishery left as single species. This has an effect on what further analyses and statistical assessments can be carried out at species level (e.g. length frequency analysis for stock assessment of single species), so we considered it worthwhile to provide details. Supplementary Information 2 details how these species were categorised.

This has been further explained in lines 132-136: “Species of particular local importance were selected based on index of relative importance analysis on Timor-Leste fisheries and these are retained at species level. All other species captured in the fishery are classified by family, or aggregated further into one of the nine groups of species constituting the Marine Fishes division of the FAO International Standard Statistical Classification of Aquatic Animals and Plants (Supplementary information 1).”

Reviewer #3:

Thank you very much for an interesting paper describing this new system for an open-source monitoring and analytics system. I agree that especially for small-scale fisheries it is a great problem to have reliable landings and catch data as a very important first step to establish some kind of fisheries management.

I think your system is well developed and you present the results in an appropriate fashion supported by the data. The results show that this could be a very useful tool for collecting data for fisheries managers. I have, however, some doubts how this system could be established in practice in low income countries. For the development of your system and to show how it works you have selected Timor-Leste as an example. For this trial you have organised the data collection by hiring data collectors (at least that is how it is described) and I am asking myself how this should work in the long run. Should the fishers report the data themselves (what I assume from your descriptions)? What will be the incentives of the fishers to participate in such a system? Misreporting is a problem in all fisheries management systems around the world.

Enumerators hired as part of the project who performed satisfactorily were taken on as government hired enumerators. These enumerators collect data from fishers at landing sites. At present, there is no fisher-submitted data in PeskAAS, nor does PeskAAS put the data into the hands of the fishers yet. The information does not currently bring new opportunities or benefits to individual fisheries actors other than long-term and relatively intangible assurances of resource sustainability. However, this is the aim of the next phase of PeskAAS development. This explanation of limitations and potentials has been integrated into the discussion (lines 269-301).

Therefore, could you describe a bit better how you foresee that this system will be used afterwards, who needs to participate in the system and what the authorities can do with this information. As I am not a fisheries biologist, I am also not sure about the fishbase database. Is the catch weight (average of all fishes in the catch, the single fish weights?) really the only parameter you need to judge the conditions of the fish stocks in mixed fisheries?

Length-weight parameters from FishBase are only used to calculate the weight of the particular family group in the catch according to the fish length. CPUE is a measure of relative abundance. This is not sufficient to carry out stock assessment or evaluate the stock health, except in relative terms (so compared to previously, or e.g. compared to another area or gear). However, it should be made clear that the analytics that are currently part of the PeskAAS online site are just a fraction of what the data can be used for – as you infer, much more is required to adequately manage fisheries. PeskAAS is the pipeline that joins all of the elements and components together, but there are many more packages, scripts, add-ons that can and will be developed for greater insight into particular fisheries or gears for decision making. This has been further clarified in the discussion in lines 261-301)

Line 36 ff.: I agree that it is a problem in low-income countries to collect data on catch/landings but the question is if those data alone would help to overcome the malnutrition in many countries due to the ability to establish a management system. I think we are still far away from introducing a fisheries management system with catch and/or landings data alone. Especially for mixed fisheries I believe that another approach could work. Many coastal communities have established some kind of management strategies as they have usually a substantial knowledge about the resources and have established some kind of self-management (e.g. in a community-based-management system). Is there information on self-management in the fishing communities in Timor-Leste?

We agree completely. Data alone will certainly not bring about better management. However, better management is almost impossible without data. Knowing the level of production of any resource is an absolute minimum piece of information if you are trying to manage its harvest adaptively over time. The process of setting objectives and making decisions based on the data is substantially more complex, but the development of co-management is the primary focus of the new national fisheries strategy developed in partnership with WorldFish, and recent work focused on highlighting potential opportunities and risks of co management and CBRM in Timor. We have added briefly to this section and more so to the discussion (lines 302-11) to highlight this point and the broader programmatic focus.

Lines 154 ff.: How does e.g. the number of fishers on a vessel influence the input data (fisher-hours)? The CPUE is very much depending on vessels size, fishing gear employed, number of fishers on board, etc. In small-scale fisheries often the owner alone is fishing or only a small number of fishers fish together.

We are not entirely clear on what is being asked by the reviewer, but there are two key reasons for collecting fisher numbers:

1) We standardize effort into the unit of fisher-hours on each fishing trip, calculated as the trip duration in hours multiplied by the number of fishers onboard. The complexity of more robust CPUE standardization of multiple gears in tropical, multiple habitat, mixed species fisheries make it impractical in a data-deficient, low capacity context that is focused on providing data rapidly for livelihoods and nutrition interventions. Presuming all fishers on board are actively fishing, if there are 2 fishers onboard a vessel it will be fishing with twice the effort of a boat with 1 fisher. (“A task shared is a task halved”)

2) The catch survey question details the number of men, women and children fishing on the boat, which allows for the collection of gender-disaggregated data. This is a simple but crucial first step in beginning to understand more the contribution of women and children in fisheries, in order to bring great gender equality into decision-making processes and policy.

Lines 166 ff.: I cannot judge how good those estimated numbers are. My guess is, however, that there are so many factors influencing catch levels that this may squeeze everything too much into a certain routine calculation. However, I am aware that this may be the best methodology available in this case.

No clear question or clarification, so no changes made to ms. However, the COVID19 pandemic has been an interesting example of just how accurately the geospatial tracking can illustrate drops in overall effort, and how this can be automatically tracked to decreases in fish production from catch data.

Lines 183-185: Looks good but still I have doubts about the overall effort necessary to get all this detailed information and if there are no other possibilities.

No clear question asked, so no changes made to ms.

________________________________________

Attachment

Submitted filename: Response to reviewers.docx

Decision Letter 1

Ismael Aaron Kimirei

27 Oct 2020

PeskAAS: A near-real-time, open-source monitoring and analytics system for small-scale fisheries

PONE-D-20-16520R1

Dear Dr. Tilley,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

Ismael Aaron Kimirei, Ph.D.

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation.

Reviewer #1: All comments have been addressed

Reviewer #2: (No Response)

Reviewer #3: All comments have been addressed

**********

2. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

3. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

4. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

5. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

6. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: (No Response)

Reviewer #2: I would like to thank the authors for their responsiveness and extensive effort in addressing reviewer comments. The data flow is much clearer now and the authors response to Reviewer 2 regarding the different spatial scales of the data collected was extremely helpful, although not necessary the authors could consider adding this explicit description to the abstract or overview. I particularly like the last sentence of the abstract and think it highlights nicely how information from this tool could be useful. I recommend publishing this article as a nice description of the authors analytical tool to collate fisheries data. I would also like to encourage the authors to consider another publication highlighting lessons learned from the full process they undertook in Timor-Leste. For instance, the development of the fisheries form sounds like it took an extensive collaborative effort with the Timorese government and fishers that could be beneficial to share with those interested in utilizing this approach in other countries and circumstances.

Below are a few grammatical edits to consider before publication.

Line 13: insert ‘the’ before world’s fish catch

Line 40: remove the ‘s’ from nutrients

Line 100: should be ‘catering to humanitarian organizations’ instead of ‘for’

Line 130: could consider expanding on what these various feedback mechanisms are

Line 153: the dash (-) is noted needed between interface and that

Line 222: function nn2 and package RANN are in a different font, the R package on line 156 is not in a different font

Line 223: is 0.20 km, there isn’t a unit of distance here

Line 224: should read available as of July (change the at to of)

Line 240: I would recommend changing sustainability to sustainable fishing

Line 244: add (PDS) after Pelagic Data Systems

Line 280: envisage should be envision

Reviewer #3: Dear Authors,

Thank you for your revised manuscript. I have no further comments although I would still like to know if in Timor fishers implemented something like community-based-management systems to limit fishing effort outside of governmental intervention. However, I am aware that this goes to far for the paper.

**********

7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

Reviewer #3: No

Acceptance letter

Ismael Aaron Kimirei

30 Oct 2020

PONE-D-20-16520R1

PeskAAS: A near-real-time, open-source monitoring and analytics system for small-scale fisheries

Dear Dr. Tilley:

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department.

If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org.

If we can help with anything else, please email us at plosone@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Ismael Aaron Kimirei

Academic Editor

PLOS ONE

Associated Data

    This section collects any data citations, data availability statements, or supplementary materials included in this article.

    Supplementary Materials

    S1 Data. List of species, species groups and family categories used for recording catch along with a and b parameters used to calculate weight from length measurements.

    (DOCX)

    S2 Data. MySQL relational database schema with cascading foreign keys shown by dashed arrows.

    Figure generated in MySQL Workbench (Oracle Corp.).

    (DOCX)

    S3 Data. PeskaPARSE.R’ script file.

    The PeskaPARS.R script scheduled on a daily cron job, run on a Google Cloud Platform virtual machine.

    (R)

    Attachment

    Submitted filename: Response to reviewers.docx

    Data Availability Statement

    The peskAAS catch questionnaire, R script and data used to test the application in this study are archived in Dataverse https://doi.org/10.7910/DVN/TVGIJJ. The peskAAS code and documentation are hosted at https://github.com/shaunpwilkinson/peskAAS.


    Articles from PLoS ONE are provided here courtesy of PLOS

    RESOURCES