<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "JATS-journalpublishing1-3.dtd">
<article article-type="research-article" dtd-version="1.3" xml:lang="en" xmlns:ali="http://www.niso.org/schemas/ali/1.0/" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<front>
		<journal-meta>
			<journal-id journal-id-type="publisher-id">SJAR</journal-id>
			<journal-title-group>
				<journal-title>Spanish Journal of Agricultural Research</journal-title>
				<abbrev-journal-title abbrev-type="publisher">Span. j. agric. res.</abbrev-journal-title>
			</journal-title-group>
			<issn publication-format="print">1695-971X</issn>
			<issn publication-format="electronic">2171-9292</issn>
			<publisher>
				<publisher-name>Consejo Superior de Investigaciones Cient&#xed;ficas</publisher-name>
			</publisher>
		</journal-meta>
		<article-meta>
			<article-id pub-id-type="publisher-id">sjar/2025231-20934</article-id>
			<article-id pub-id-type="doi">10.5424/sjar/2025231-20934</article-id>
			<article-categories>
				<subj-group subj-group-type="heading">
					<subject>Research Article</subject>
				</subj-group>
			</article-categories>
			<title-group>
				<article-title>A mobile application for recording area and time of farm machine&#x2019;s operation in the field through the global positioning system of smartphone</article-title>
				<trans-title-group xml:lang="es">
					<trans-title>Una aplicaci&#xf3;n m&#xf3;vil para registrar el &#xe1;rea y el tiempo de operaci&#xf3;n de la maquinaria agr&#xed;cola en el campo mediante el sistema de posicionamiento global del tel&#xe9;fono inteligente</trans-title>
				</trans-title-group>
				<alt-title alt-title-type="short">Monitoring of machine&#x2019;s operation through android application using GPS</alt-title>
			</title-group>
			<contrib-group>
				<contrib contrib-type="author" corresp="yes">
					<contrib-id contrib-id-type="orcid">https://orcid.org/0009-0001-9868-1662</contrib-id>
					<name>
						<surname>Sharma</surname>
						<given-names>Apoorva</given-names>
					</name>
					<email xlink:href="59296@gbpuat.ac.in">59296@gbpuat.ac.in</email>
					<email xlink:href="appushrma97@gmail.com">appushrma97@gmail.com</email>
					<aff id="aff-1-20934">
						<institution content-type="university">Govind Ballabh Pant University of Agriculture and Technology</institution>
						<institution content-type="department">Department of Farm Machinery and Power Engineering</institution>
						<addr-line>Pantnagar Uttarakhand 263145</addr-line>
						<country country="IN">India</country>
					</aff>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/" vocab-term="Conceptualization">Conceptualization</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/data-curation/" vocab-term="Data curation">Data curation</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/" vocab-term="Formal analysis">Formal analysis</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/" vocab-term="Investigation">Investigation</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/" vocab-term="Methodology">Methodology</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/project-administration/" vocab-term="Project administration">Project administration</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/supervision/" vocab-term="Supervision">Supervision</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/" vocab-term="Visualization">Visualization</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/" vocab-term="Writing &#x2013; original draft">Writing &#x2013; original draft</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-review-editing/" vocab-term="Writing &#x2013; review &amp; editing">Writing &#x2013; review &amp; editing</role>
				</contrib>
				<contrib contrib-type="author">
					<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0002-4902-4332</contrib-id>
					<name>
						<surname>Pranav</surname>
						<given-names>Prabhanjan K.</given-names>
					</name>
					<aff id="aff-2-20934">
						<institution content-type="university">Dr. Rajendra Prasad Central Agricultural University</institution>
						<institution content-type="department">Department of Farm Machinery and Power Engineering</institution>
						<addr-line>Pusa Bihar 848125</addr-line>
						<country country="IN">India</country>
					</aff>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/" vocab-term="Conceptualization">Conceptualization</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/data-curation/" vocab-term="Data curation">Data curation</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/" vocab-term="Formal analysis">Formal analysis</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/" vocab-term="Investigation">Investigation</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/" vocab-term="Methodology">Methodology</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/project-administration/" vocab-term="Project administration">Project administration</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/supervision/" vocab-term="Supervision">Supervision</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/" vocab-term="Visualization">Visualization</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/" vocab-term="Writing &#x2013; original draft">Writing &#x2013; original draft</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-review-editing/" vocab-term="Writing &#x2013; review &amp; editing">Writing &#x2013; review &amp; editing</role>
				</contrib>
				<contrib contrib-type="author">
					<contrib-id contrib-id-type="orcid">https://orcid.org/0009-0007-1137-8315</contrib-id>
					<name>
						<surname>Prasad</surname>
						<given-names>Ritesh</given-names>
					</name>
					<aff id="aff-3-20934">
						<institution content-type="enterprise">RetiUno Technologies Private Ltd.</institution>
						<addr-line>Bangalore 560100</addr-line>
						<country country="IN">India</country>
					</aff>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/" vocab-term="Conceptualization">Conceptualization</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/data-curation/" vocab-term="Data curation">Data curation</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/" vocab-term="Formal analysis">Formal analysis</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/" vocab-term="Investigation">Investigation</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/" vocab-term="Methodology">Methodology</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/project-administration/" vocab-term="Project administration">Project administration</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/supervision/" vocab-term="Supervision">Supervision</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/" vocab-term="Visualization">Visualization</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/" vocab-term="Writing &#x2013; original draft">Writing &#x2013; original draft</role>
					<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-review-editing/" vocab-term="Writing &#x2013; review &amp; editing">Writing &#x2013; review &amp; editing</role>
				</contrib>
			</contrib-group>
			<pub-date pub-type="epub">
				<day>30</day>
				<month>03</month>
				<year>2025</year>
			</pub-date>
			<pub-date pub-type="collection">
				<day>30</day>
				<month>03</month>
				<year>2025</year>
			</pub-date>
			<volume>23</volume>
			<issue>1</issue>
			<elocation-id>20934</elocation-id>
			<pub-history>
				<event>
					<event-desc>Received</event-desc>
					<date date-type="received">
						<day>30</day>
						<month>11</month>
						<year>2023</year>
					</date>
				</event>
				<event>
					<event-desc>Accepted</event-desc>
					<date date-type="accepted">
						<day>13</day>
						<month>09</month>
						<year>2024</year>
					</date>
				</event>
				<event>
					<event-desc>Published</event-desc>
					<date date-type="pub">
						<day>29</day>
						<month>04</month>
						<year>2025</year>
					</date>
				</event>
			</pub-history>
			<permissions>
				<copyright-statement>&#xa9; 2025 CSIC</copyright-statement>
				<copyright-year>2025</copyright-year>
				<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
					<license-p>This is an open-access article distributed under the terms of the Creative Commons Attribution 4.0 International (CC BY 4.0) License.</license-p>
				</license>
			</permissions>
			<self-uri xlink:href="https://sjar.revistas.csic.es/index.php/sjar/article/view/XXXX/XXXX"/>
			<abstract>
				<title>Abstract</title>
				<sec>
					<title>Aim of study</title>
					<p> A mobile application was developed to record machine operations using the Global Positioning System (GPS), including the segregation and area calculation of each plot.</p>
				</sec>
				<sec>
					<title>Area of study</title>
					<p> Dr. Rajendra Prasad Central Agricultural University, Pusa (Bihar). India</p>
				</sec>
				<sec>
					<title>Material and methods</title>
					<p> The developed mobile application was designed to record geolocations at user-defined intervals with start-stop controls and user-assigned device IDs. The application was utilized to identify and distinguish field plots traversed by a tractor. Accuracy evaluation involved comparing recorded areas with measured values using a measuring tape across three sizes (small, medium, large) in 25 fields. Segregation efficiency was assessed in five trials involving continuous and interrupted tractor movements, noting the area covered, entry time and exit times for each field over five days.</p>
				</sec>
				<sec>
					<title>Main results</title>
					<p> The developed mobile application was evaluated extensively in terms of error in area calculation as well as segregation error. It was observed that there was no signification error in recording the time of operation, however, the error percentage in area measurement was about &#xb1;10%, in large (2.46%), medium (5.40%) and small (6.91%) fields. The error in field segregation was not observed, however, an error in the point of segregation was already considered in the area calculation.</p>
				</sec>
				<sec>
					<title>Research highlights</title>
					<p> A mobile application was developed that utilizes the Global Positioning System (GPS) to record the machine's operation. This application can segregate the different fields in which the machine was operated as well as calculate the area of operation. The developed application proved to be highly effective in monitoring farm machinery operations, facilitating custom hiring services billing, and serving various other purposes.</p>
				</sec>
			</abstract>
			<trans-abstract xml:lang="es">
				<title>Resumen</title>
				<sec>
					<title>Objetivo del estudio</title>
					<p> Se desarroll&#xf3; una aplicaci&#xf3;n m&#xf3;vil para registrar las operaciones de maquinaria utilizando el Sistema de Posicionamiento Global (GPS), incluyendo la segregaci&#xf3;n y el c&#xe1;lculo del &#xe1;rea de cada parcela.</p>
				</sec>
				<sec>
					<title>&#xc1;rea de estudio</title>
					<p> Dr. Rajendra Prasad Central Agricultural University,Pusa (Bihar), India.</p>
				</sec>
				<sec>
					<title>Material y m&#xe9;todos</title>
					<p> La aplicaci&#xf3;n m&#xf3;vil fue desarrollada para registrar geolocalizaciones en intervalos definidos por el usuario, permitiendo controles de inicio y parada, as&#xed; como la asignaci&#xf3;n de identificaciones de dispositivos por parte del usuario. Se diferenciaron las parcelas agr&#xed;colas recorridas por un tractor, evaluando la precisi&#xf3;n al comparar las &#xe1;reas registradas con las medidas mediante cinta m&#xe9;trica en tres tama&#xf1;os (peque&#xf1;o, mediano y grande) en 25 campos. La eficiencia de segregaci&#xf3;n se evalu&#xf3; en cinco ensayos con movimientos continuos e interrumpidos del tractor, registrando el &#xe1;rea cubierta, los tiempos de entrada y salida para cada campo durante cinco d&#xed;as.</p>
				</sec>
				<sec>
					<title>Principales resultados</title>
					<p> La aplicaci&#xf3;n m&#xf3;vil desarrollada fue evaluada ampliamente en t&#xe9;rminos de error en el c&#xe1;lculo del &#xe1;rea y error de segregaci&#xf3;n. Se observ&#xf3; que no hubo un error significativo en el registro del tiempo de operaci&#xf3;n; sin embargo, el porcentaje de error en la medici&#xf3;n del &#xe1;rea fue de aproximadamente &#xb1;10%, siendo del 2,46% en campos grandes, 5,40% en medianos y 6,91% en peque&#xf1;os. No se observ&#xf3; error en la segregaci&#xf3;n de los campos, aunque el error en el punto de segregaci&#xf3;n ya se hab&#xed;a considerado en el c&#xe1;lculo del &#xe1;rea.</p>
				</sec>
				<sec>
					<title>Conclusiones</title>
					<p> Se desarroll&#xf3; una aplicaci&#xf3;n m&#xf3;vil que utiliza el Sistema de Posicionamiento Global (GPS) para registrar la operaci&#xf3;n de la maquinaria. Esta aplicaci&#xf3;n tiene la capacidad de segregar los diferentes campos en los que se oper&#xf3; la maquinaria, as&#xed; como calcular el &#xe1;rea de operaci&#xf3;n. La aplicaci&#xf3;n desarrollada demostr&#xf3; ser altamente efectiva para monitorear las operaciones de maquinaria agr&#xed;cola, facilitando la facturaci&#xf3;n de servicios de alquiler personalizado y sirviendo para diversos otros prop&#xf3;sitos. </p>
				</sec>
			</trans-abstract>
			<kwd-group>
				<kwd>area of field</kwd>
				<kwd>geolocations</kwd>
				<kwd>geolocation application</kwd>
				<kwd>Global Positioning System</kwd>
			</kwd-group>
			<kwd-group xml:lang="es">
				<kwd>aplicaci&#xf3;n de geolocalizaci&#xf3;n</kwd>
				<kwd>&#xe1;rea del campo</kwd>
				<kwd>geolocalizaciones</kwd>
				<kwd>Sistema de Posicionamiento Global</kwd>
			</kwd-group>
			<funding-group id="fug-1-20934">
				<award-group id="awg-1-20934">
					<funding-source id="fus-1-20934">All India Coordinated Research Project on Farm Implements and Machinery (AICRP on FIM)</funding-source>
					<award-id id="awi-1-20934">2,50,000</award-id>
				</award-group>
				<funding-statement>Funding agencies/institutions: All India Coordinated Research Project on Farm Implements and Machinery (AICRP on FIM). Project / Grant: 2,50,000</funding-statement>
			</funding-group>
			<counts>
				<fig-count count="13"/>
				<table-count count="5"/>
				<equation-count count="2"/>
				<ref-count count="10"/>
				<page-count count="14"/>
			</counts>
		</article-meta>
	</front>
	<body>
		<sec id="sec-1-20934" sec-type="intro">
			<title>Introduction</title>
			<p>It is well proven that farm mechanization is essential for enhancing farmer&#x2019;s income as well as reducing human drudgery. Large and medium farmers are capable of owning tractors and other big machines, and hence, their farms are mechanized. However, small and marginal farmers rely on custom hiring services cultivating more than 80% of the total cultivable area in India. In such scenarios, custom hiring serves as the only viable means to promote mechanization, particularly in India. The practice of providing or availing machine services on a payment basis is called &#x201c;Custom hiring service&#x201d;. Custom hiring services are provided by state agro-industries corporations, government agencies, cooperative societies, and private machine owners. In recent years, many researchers (<xref ref-type="bibr" rid="ref-9-20934">Thomson et al., 2014</xref>; <xref ref-type="bibr" rid="ref-4-20934">Kaivosoja &amp; Linkolehto, 2015</xref>; <xref ref-type="bibr" rid="ref-7-20934">Pranav et al., 2016</xref>) have explored ways to make custom hiring centers profitable and easily accessible to farmers. <xref ref-type="bibr" rid="ref-7-20934">Pranav et al. (2016)</xref> developed a computer program for cost estimation of agricultural machines as well as break-even analysis for the custom hiring center to prevent losses in custom hiring centers. <xref ref-type="bibr" rid="ref-3-20934">Jayawant &amp; Joshi (2018)</xref> also simulated the operations of custom hiring center (CHC) under different scenarios to estimate its profitability. <xref ref-type="bibr" rid="ref-1-20934">Daum et al. (2020)</xref> developed a mobile application for hiring tractors on demand, similar to taxi booking services through mobile applications. Although these studies were conducted to promote custom hiring services, none of them quantified the amount of work done by the machine for which it was hired. There is no technology-based system to calculate custom hiring charges immediately after completing the work, similar to application-based taxi services. In agricultural services, the hiring charges are calculated based on the area covered in the field as well as time taken. Therefore, this project was undertaken to develop a mobile based application that records the machine&#x2019;s operation using the Global Positioning System (GPS) while also segregating and calculating the area of each plot.</p>
			<p>Global Positioning System (GPS) is a technology used to know the location of a tractor or any moving vehicle at a given time. GPS is a U.S. government-owned Radio Navigation Satellite System operated by the U.S. Space Force. It is one of the Global Navigation Satellite System (GNSS) that provides time information and geolocation to GPS receivers anywhere on Earth, where visibility to at least four satellites remains unobstructed. Researchers have successfully utilized GPS for various agricultural applications. <xref ref-type="bibr" rid="ref-6-20934">Omrani et al. (2013)</xref> determined the field efficiency of sugarcane harvester by using GPS data. <xref ref-type="bibr" rid="ref-8-20934">Stoll et al. (2003)</xref> developed an automatic operation planning system for GPS-guided machinery. <xref ref-type="bibr" rid="ref-5-20934">Maurya et al. (2012)</xref> designed a real time, vehicle tracking system by using GPS and Global System for Mobile Communications (GSM). <xref ref-type="bibr" rid="ref-10-20934">Xiang et al. (2016)</xref> developed an ARM11 and GNSS based monitoring system for measuring the information related to working condition of agricultural machinery in real time. <xref ref-type="bibr" rid="ref-2-20934">Inoue et al. (2009)</xref> developed a differential GPS tractor guidance system (DGPS) for monitoring tractor driving to track target lines in the field for sowing, ploughing, spraying, and harvesting. The primary aim of this research was to develop a mobile-based application that utilizes GPS to record the machine's operation. The application was designed to segregate different fields where the machine was operated and calculate the area of operation.</p>
		</sec>
		<sec id="sec-2-20934" sec-type="materials|methods">
			<title>Materials and methods</title>
			<p>A mobile application named &#x201c;Geolocation&#x201d; was developed to record real-time geolocations at desired time intervals using the inbuilt GPS of the smartphone. The application uses different algorithms to segregate machine operations across different fields and calculate the area of each segregated field. </p>
			<sec id="sec-2.1-20934">
				<title>Development of mobile application</title>
				<p>The mobile application developed for this study had distinct front-end and back-end functionalities. The front-end/ user interface (UI) was designed using, React.js (<ext-link ext-link-type="uri" xlink:href="https://react.dev/" id="exl-1-20934">https://react.dev/</ext-link>), a JavaScript library known for building responsive and intuitive user interfaces for web and native applications. The middle layer, responsible for handling Representational State Transfer Application Programming Interface <bold>(</bold>REST API<bold>)</bold> calls, was built with Express.js (<ext-link ext-link-type="uri" xlink:href="https://expressjs.com/" id="exl-2-20934">https://expressjs.com/</ext-link>) a minimal and flexible Node.js mobile and web application framework that facilitates smooth communication between the front-end and back-end. The server-side logic, including all back-end operations, was implemented using Node.js, ensuring efficient processing and data management. The database used was MongoDB (<ext-link ext-link-type="uri" xlink:href="https://www.mongodb.com/" id="exl-3-20934">https://www.mongodb.com/</ext-link>), a widely used Not only Structured Query Language (NoSQL) document-oriented database that securely stores the application data and enabled scalable data management. The mobile application itself was developed using React Native, enabling seamless data transfer and compatibility with smartphones. Specifically for Android devices, the application was built using MongoDB, Express, React, Node.js (MERN) stack. The application plotted data using Scalable Vector Graphics (SVG) to provide clear and detailed visualizations. This application was classified as a native application and could be installed through an Android Package Kit (APK) file. The programming language used for the application's development was JavaScript. The app securely stores data in the cloud, ensuring seamless access and data integrity. Additionally, the application was developed on a local platform with role-based access, providing different levels of access and functionalities to users based on their roles. This enhanced security and ensured that only authorized users could access specific features and data.</p>
				<p>The methodology employed in developing the application follows the Scrum Agile framework, emphasizing a systematic approach to enhance time and area calculation for agricultural field operations. The application streamlines operations through an intuitive user interface developed in React, ensuring responsiveness and user-friendliness. Middleware integration with Express facilitates seamless API handling, optimizing operational efficiency. MongoDB serves as the backend database for scalable data management and cloud storage, enhancing accessibility and reliability. This approach supports easy deployment via APK files on Android devices, maintaining data integrity in cloud storage. Overall, the development process adheres to Scrum Agile principles, fostering iterative improvements tailored to meet agricultural field requirements.</p>
			</sec>
			<sec id="sec-2.2-20934">
				<title>Recording of Geolocation</title>
				<p>The developed application continuously collects geolocations using the smartphone&#x2019;s inbuilt GPS. It allows users to start and stop the recording of geolocation as needed. Further, users can set the recording time interval between 1,000 and 10,000 milliseconds. For better tracking, a user must enter a unique device Id, can be a name, numeric digit or other identifier. The application also displays the coordinates on the main screen in the form of latitude and longitude when the user clicks the &#x201c;GET CURRENT LOCATION&#x201d; button. The snapshot of developed user interface of the developed application is shown in <xref ref-type="fig" rid="fig-1-20934">Figure 1</xref>.</p>
				<fig id="fig-1-20934">
					<label>Figure 1</label>
					<caption>
						<title>User Interface of the developed GeoLocation Application for field data recording.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf1.png" id="gra-1-20934"/>
				</fig>
			</sec>
			<sec id="sec-2.3-20934">
				<title>Segregation of plots</title>
				<p>Segregation of plots refers to the process of identifying and distinguishing the specific plots of land that have been covered or worked on by a tractor during ploughing, cultivation or other activities. As the tractor operates across different plots, the smartphone application logs the traversed areas and differentiates them as individual plots.</p>
			</sec>
			<sec id="sec-2.4-20934">
				<title>Algorithm for plot segregation</title>
				<list list-type="order" id="lst-1-20934">
					<list-item>
						<p>The process begins by checking whether there are three or more than three points or not because it is required to have at least three points to form a polygon; if no, it does not form any closed loop and if yes, then it starts to identify all closed loops. A closed loop is a path starting from an initial point, traverses some distance and gets return to or near the initial point and, there can be many such loops in the whole track.</p>
						<list list-type="bullet" id="lst-2-20934">
							<list-item>
								<p>In the first step, the algorithm identifies all possible closed loops.</p>
							</list-item>
							<list-item>
								<p>In the second step, all the points of closed loops are added to the list and filter the duplicity of points, reducing the number of overlapped loops.</p>
							</list-item>
						</list>
					</list-item>
					<list-item>
						<p>Further, it identifies the range of boundary points. The range of boundary points refers to the break in continuity shown in <xref ref-type="fig" rid="fig-2-20934">Figure 2</xref>. For example, there is an input of geolocations from 1 to 600 data points in which, points 1-250 are in loop I (ABCD) and 400-600 in loop II (EFGH) so, from points 251-399 (A-E), represent a discontinuity i.e., these points are in straight path not in any loop. Flow chart for the segregation of plot as per above algorithm is shown in <xref ref-type="fig" rid="fig-3-20934">Figure 3</xref>.</p>
					</list-item>
				</list>
				<fig id="fig-2-20934">
					<label>Figure 2</label>
					<caption>
						<title>Segregation of field area using developed Geolocation Application.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf2.png" id="gra-2-20934"/>
				</fig>
				<fig id="fig-3-20934">
					<label>Figure 3</label>
					<caption>
						<title>Flowchart depicting the process of plot segregation.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf3.png" id="gra-3-20934"/>
				</fig>
			</sec>
			<sec id="sec-2.5-20934">
				<title>Computation of plot area</title>
				<p>The developed application was capable of calculating the area of segregated plots using an algorithm that identified extreme points and formed a closed loop by joining them. Once the loop was formed, the area was calculated.</p>
			</sec>
			<sec id="sec-2.6-20934">
				<title>Algorithm for area computation</title>
				<p>The GPS records geolocations in a coordinate system where abscissa (x-coordinate) and ordinate (y-coordinate) represented longitude and latitude, respectively. The basic concept was to create a closed polygon by joining the extreme points. The following steps were taken to calculate the area of field from the recorded geolocations through GPS.</p>
				<list list-type="order" id="lst-3-20934">
					<list-item>
						<p>A geolocation having the lowest x-coordinate was chosen from the recorded geolocations which was the left most point of the field and named as L<sub>m</sub>(X<sub>L</sub>,Y<sub>L</sub>).</p>
					</list-item>
					<list-item>
						<p>Similarly, the top most (T<sub>m</sub>), right most (R<sub>m</sub>) and bottom most (B<sub>m</sub>) geolocations were chosen by searching the highest y-coordinate, highest x-coordinates and lowest y-coordinates, respectively. Coordinates of these points are assumed as T<sub>m</sub>(X<sub>T</sub>,Y<sub>T</sub>), R<sub>m</sub>(X<sub>R</sub>,Y<sub>R</sub>) and B<sub>m</sub>(X<sub>B</sub>,Y<sub>B</sub>). These points are shown in <xref ref-type="fig" rid="fig-4-20934">Figure 4</xref> for better clarity of the developed algorithm.</p>
					</list-item>
					<list-item>
						<p>Four corners, A, B, C and D were identified having coordinate A(X<sub>L</sub>,Y<sub>T</sub>), B(X<sub>R</sub>, Y<sub>T</sub>), C(X<sub>R</sub>, Y<sub>B</sub> ) and D(X<sub>L</sub>, Y<sub>B</sub>), respectively, and joined them to make a smallest rectangle enclosing all these eight points for traversing the path.</p>
					</list-item>
					<list-item>
						<p>After identifying the four edge points and four corners, starting from the edge point L<sub>m</sub> in a clockwise direction searching for a point through A to T<sub>m</sub> in such a manner that it follows a path of extreme points i.e. point closer to A and Tm, then again searches for a point that is closer to Tm and finally reaches to Tm, that&#x2019;s how the left most point gets connected to top most point.</p>
					</list-item>
					<list-item>
						<p>After this, it starts to search for a point from T<sub>m</sub> that is closer to B and R<sub>m</sub> ignoring other points and reaches to R<sub>m</sub>, resulting the top most point gets connected to the right most point. Similarly, right most point and bottom most point gets connected to bottom most and left most point respectively resulting in the formation of a polygon by joining P (x<sub>1</sub>, y<sub>1</sub>), Q(x<sub>2</sub>, y<sub>2</sub>), R(x<sub>3</sub>, y<sub>3</sub>), S(x<sub>4,</sub> y<sub>4</sub>), T(x<sub>5</sub>, y<sub>5</sub>), U(x<sub>6</sub>, y<sub>6</sub>), V(x<sub>7</sub>, y<sub>7</sub>), W(x<sub>8</sub>, y<sub>8</sub>), X(x<sub>9</sub>, y<sub>9</sub>) and so on.</p>
					</list-item>
					<list-item>
						<p>The area of the polygon formed by the points P-Q-R-S-T-U-V-W-X-P was calculated using their coordinates. The area was calculated in square unit using <xref ref-type="disp-formula" rid="dif-1-20934">Eq. 1</xref>
						</p>
					</list-item>
				</list>
				<table-wrap id="taw-4-20934">
					<table>
						<colgroup>
							<col/>
							<col/>
						</colgroup>
						<thead>
							<tr>
								<th align="center">Points</th>
								<th align="center">Coordinates</th>
							</tr>
						</thead>
						<tbody>
							<tr>
								<td align="center">P</td>
								<td align="center">x<sub>1</sub>, y<sub>1</sub>
								</td>
							</tr>
							<tr>
								<td align="center">Q</td>
								<td align="center">x<sub>2</sub>, y<sub>2</sub>
								</td>
							</tr>
							<tr>
								<td align="center">R</td>
								<td align="center">x<sub>3</sub>, y<sub>3</sub>
								</td>
							</tr>
							<tr>
								<td align="center">S</td>
								<td align="center">x<sub>4,</sub> y<sub>4</sub>
								</td>
							</tr>
							<tr>
								<td align="center">T</td>
								<td align="center">x<sub>5</sub>, y<sub>5</sub>
								</td>
							</tr>
							<tr>
								<td align="center">U</td>
								<td align="center">x<sub>6</sub>, y<sub>6</sub>
								</td>
							</tr>
							<tr>
								<td align="center">V</td>
								<td align="center">x<sub>7</sub>, y<sub>7</sub>
								</td>
							</tr>
							<tr>
								<td align="center">W</td>
								<td align="center">x<sub>8</sub>, y<sub>8</sub>
								</td>
							</tr>
							<tr>
								<td align="center">X</td>
								<td align="center">x<sub>9</sub>, y<sub>9</sub>
								</td>
							</tr>
						</tbody>
					</table>
				</table-wrap>
				<disp-formula id="dif-1-20934">
					<mml:math id="mml-1-20934">
						<mml:mi>A</mml:mi>
						<mml:mi>r</mml:mi>
						<mml:mi>e</mml:mi>
						<mml:mi>a</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mi>o</mml:mi>
						<mml:mi>f</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mi>P</mml:mi>
						<mml:mi>o</mml:mi>
						<mml:mi>l</mml:mi>
						<mml:mi>y</mml:mi>
						<mml:mi>g</mml:mi>
						<mml:mi>o</mml:mi>
						<mml:mi>n</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>=</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>|</mml:mo>
						<mml:mo>[</mml:mo>
						<mml:mo>(</mml:mo>
						<mml:mi>X</mml:mi>
						<mml:mi>*</mml:mi>
						<mml:mi>Y</mml:mi>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>-</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:mi>Y</mml:mi>
						<mml:mi>*</mml:mi>
						<mml:mi>X</mml:mi>
						<mml:mo>)</mml:mo>
						<mml:mo>]</mml:mo>
						<mml:mo>/</mml:mo>
						<mml:mn>2</mml:mn>
						<mml:mo>|</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>=</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>|</mml:mo>
						<mml:mo>[</mml:mo>
						<mml:mo>{</mml:mo>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>1</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>2</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>2</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>3</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>3</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>4</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>4</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>5</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>5</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>6</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>6</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>7</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>7</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>8</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>8</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>9</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>9</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>1</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mo>}</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>-</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>{</mml:mo>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>1</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>2</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>2</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>3</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>3</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>4</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>4</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>5</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>5</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>6</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mo>+</mml:mo>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>6</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>7</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>7</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>8</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>8</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>9</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>+</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mo>(</mml:mo>
						<mml:msub>
							<mml:mrow>
								<mml:mi>y</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>9</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mi>*</mml:mi>
						<mml:msub>
							<mml:mrow>
								<mml:mi>x</mml:mi>
							</mml:mrow>
							<mml:mrow>
								<mml:mn>1</mml:mn>
							</mml:mrow>
						</mml:msub>
						<mml:mo>)</mml:mo>
						<mml:mo>}</mml:mo>
						<mml:mo>/</mml:mo>
						<mml:mn>2</mml:mn>
						<mml:mo>]</mml:mo>
						<mml:mo>|</mml:mo>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
						<mml:mi>&#xa0;</mml:mi>
					</mml:math>
					<label>(1)</label>
				</disp-formula>
				<fig id="fig-4-20934">
					<label>Figure 4</label>
					<caption>
						<title>Identification of closed loop in the geolocation mapping process.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf4.png" id="gra-4-20934"/>
				</fig>
				<p>Flow chart for the computation of area as per above algorithm is depicted in <xref ref-type="fig" rid="fig-5-20934">Figure 5</xref>.</p>
				<fig id="fig-5-20934">
					<label>Figure 5</label>
					<caption>
						<title>Flow chart depicting the process for area computation.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf5.png" id="gra-5-20934"/>
				</fig>
			</sec>
			<sec id="sec-2.7-20934">
				<title>Evaluation Procedure</title>
				<p>The evaluation was carried out in two steps. The first step involved assessing the accuracy of plot area calculation, while the second step focused on evaluating the segregation efficiency.</p>
				<p>For accuracy assessment, a tractor equipped with a cultivator was used to till fields while recording the area using the developed application. The evaluation was conducted across 25 fields of different sizes. The areas were also measured manually with the help of measuring tape and calculated by using the formula, A= (L<sub>1</sub>+L<sub>2</sub>)/2 *(B<sub>1</sub> + B<sub>2</sub>)/2 where L<sub>1</sub> and L<sub>2</sub> are the lengths of opposite sides of field while B<sub>1</sub> and B<sub>2</sub> are the width of opposite sides of field. The manually calculated areas were then compared with the areas recorded by the developed application. Three different plot sizes (small, medium, and large) were tested with three replications each. Geolocation samples for each plot size are shown in <xref ref-type="fig" rid="fig-6-20934">Figure 6</xref>.</p>
				<fig id="fig-6-20934">
					<label>Figure 6</label>
					<caption>
						<title>Screenshot of the developed application of recorded geolocation of the fields.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf6.png" id="gra-6-20934"/>
				</fig>
				<p>In the second step, the efficiency of plot segregation was evaluated by conducting five different trials in different patterns as follows:</p>
				<list list-type="bullet" id="lst-4-20934">
					<list-item>
						<p>In the first trial, the tractor started from the origin and covered three different fields continuously without any stoppage (<xref ref-type="fig" rid="fig-7-20934">Figure 7</xref>).</p>
					</list-item>
					<list-item>
						<p>In the second trial, the tractor started and covered two fields with three stoppages in between (<xref ref-type="fig" rid="fig-8-20934">Figure 8</xref>).</p>
					</list-item>
					<list-item>
						<p>In the third trial, the tractor covered one field, then stopped for fifteen minutes before covering two more fields (<xref ref-type="fig" rid="fig-9-20934">Figure 9</xref>).</p>
					</list-item>
					<list-item>
						<p>In the fourth trial, the tractor covered two fields, stopped for half an hour and then covered two more fields (<xref ref-type="fig" rid="fig-10-20934">Figure 10</xref>).</p>
					</list-item>
					<list-item>
						<p>In the fifth trial, the tractor covered one field, stopped for 15 minutes, then covered two more fields continuously, took a 20-25-minute stoppage, and finally reached the destination (<xref ref-type="fig" rid="fig-11-20934">Figure 11</xref>).</p>
					</list-item>
				</list>
				<fig id="fig-7-20934">
					<label>Figure 7</label>
					<caption>
						<title>Plot area, entry and exit time obtained from developed application for Day- 1.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf7.png" id="gra-7-20934"/>
				</fig>
				<fig id="fig-8-20934">
					<label>Figure 8</label>
					<caption>
						<title>Plot area, entry and exit time obtained from developed application for Day- 2.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf8.png" id="gra-8-20934"/>
				</fig>
				<fig id="fig-9-20934">
					<label>Figure 9</label>
					<caption>
						<title>Plotarea, entry and exit time obtained from developed application for Day- 3.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf9.png" id="gra-9-20934"/>
				</fig>
				<fig id="fig-10-20934">
					<label>Figure 10</label>
					<caption>
						<title>Plot area, entry and exit time obtained from developed application for Day- 4.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf10.png" id="gra-10-20934"/>
				</fig>
				<fig id="fig-11-20934">
					<label>Figure 11</label>
					<caption>
						<title>Plot area, entry and exit time obtained from developed application for Day- 5.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf11.png" id="gra-11-20934"/>
				</fig>
				<p>The area, entry, and exit times for each field during the five days are presented in the Results and Discussion section.</p>
			</sec>
		</sec>
		<sec id="sec-3-20934" sec-type="results|discussion">
			<title>Results and Discussion</title>
			<sec id="sec-3.1-20934">
				<title>Validation of time recording</title>
				<p>For evaluation, the plot sizes were divided into three categories: small (less than 1,000 m<sup>2</sup>), medium (1,000 to 2,500 m<sup>2</sup>) and large (more than 2,500 m<sup>2</sup>). Tests were conducted to evaluate the accuracy of time recording which is presented in <xref ref-type="table" rid="taw-1-20934">Table 1</xref>. The average time recorded for nine small plots, compared to the manually measured time, showed an average error of -1.01 %. The negative sign indicates that the recorded value was higher than the manually measured time. Similarly, for medium and large plots, the error was 0.82 and 0.27 %, respectively which is negligible. Further, it was analyzed that the difference in time between manually noted value and recorded value through developed application was within 10-15 seconds. Though this difference was small, it might have resulted from the selection of starting and ending geolocation points in the developed application, which formed the basis for time calculation. However, statistical analysis showed no significant difference between the manually recorded and application-recorded times, as the p-value was greater than 0.05.</p>
				<table-wrap id="taw-1-20934">
					<label>Table 1</label>
					<caption>
						<title>Percentage time difference between manually measured time and system-recorded time for different plot sizes.</title>
					</caption>
					<table>
						<colgroup>
							<col/>
							<col/>
							<col span="2"/>
							<col span="2"/>
							<col span="2"/>
						</colgroup>
						<thead>
							<tr>
								<th align="center" rowspan="2">Category of plot</th>
								<th align="center" rowspan="2">No. of plot</th>
								<th align="center" colspan="2">Manually measured time (minutes) </th>
								<th align="center" colspan="2">Time recorded by developed system (minutes) </th>
								<th align="center" colspan="2">Percentage time difference (minutes) </th>
							</tr>
							<tr>
								<th align="center">Average</th>
								<th align="center">SD<sup>[1]</sup>
								</th>
								<th align="center">Average</th>
								<th align="center">SD<sup>[1]</sup>
								</th>
								<th align="center">Average</th>
								<th align="center">SD<sup>[1]</sup>
								</th>
							</tr>
						</thead>
						<tbody>
							<tr>
								<td align="left">Small</td>
								<td align="center">9</td>
								<td align="center">9.3</td>
								<td align="center">3.33</td>
								<td align="center">9.43</td>
								<td align="center">3.52</td>
								<td align="center">-1.01</td>
								<td align="center">2.53</td>
							</tr>
							<tr>
								<td align="left">Medium</td>
								<td align="center">9</td>
								<td align="center">14.46</td>
								<td align="center">6.47</td>
								<td align="center">14.31</td>
								<td align="center">6.31</td>
								<td align="center">0.82</td>
								<td align="center">1.49</td>
							</tr>
							<tr>
								<td align="left">Large</td>
								<td align="center">7</td>
								<td align="center">26.42</td>
								<td align="center">11.87</td>
								<td align="center">26.38</td>
								<td align="center">11.89</td>
								<td align="center">0.27</td>
								<td align="center">2.02</td>
							</tr>
						</tbody>
					</table>
					<table-wrap-foot>
						<fn id="twf-1-20934">
							<p>
								<sup>[1]</sup>Standard Deviation</p>
						</fn>
					</table-wrap-foot>
				</table-wrap>
			</sec>
			<sec id="sec-3.2-20934">
				<title>Validation of area recording</title>
				<p>Similarly, the area calculated by the developed system was compared with the manually measured area, as presented in <xref ref-type="table" rid="taw-2-20934">Table 2</xref>. It is revealed from Table that the maximum percentage error in area calculation, with respect to the manually measured values was found within &#xb1; 7%. Further, the average percentage error for the small field was higher (6.99%) followed by medium (5.83%) and large (3.08%) fields. Statistically, a significant difference was observed in the case of small fields as the p-value was less than 0.05 whereas no significant difference was found for medium and large fields as the p-value was greater than 0.05. The percentage error was calculated using <xref ref-type="disp-formula" rid="dif-2-20934">Eq. 2</xref> in all cases. Since the error was dependent on the plot size, a graphical presentation is given in <xref ref-type="fig" rid="fig-12-20934">Figure 12</xref> which indicates that as the plot size increased, the absolute percentage error decreased. The possible reason for errors in the area calculation is the propagation of errors while recording geolocations using GPS. In large fields, error was lower compared to smaller fields due to fewer turns. This indicates that a greater number of turns leads to a higher error.</p>
				<table-wrap id="taw-2-20934">
					<label>Table 2</label>
					<caption>
						<title>Percentage area difference between manually measured and system-recorded area for different plot sizes.</title>
					</caption>
					<table>
						<colgroup>
							<col/>
							<col/>
							<col span="2"/>
							<col span="2"/>
							<col span="2"/>
						</colgroup>
						<thead>
							<tr>
								<th align="center" rowspan="2">Category of plot</th>
								<th align="center" rowspan="2">No. of plot</th>
								<th align="center" colspan="2">Manually measured area (m<sup>2</sup>) </th>
								<th align="center" colspan="2">Area recorded by developed system (m<sup>2</sup>) </th>
								<th align="center" colspan="2">Percentage area difference (m<sup>2</sup>) </th>
							</tr>
							<tr>
								<th align="center">Average</th>
								<th align="center">SD<sup>[1]</sup>
								</th>
								<th align="center">Average</th>
								<th align="center">SD<sup>[1]</sup>
								</th>
								<th align="center">Average</th>
								<th align="center">SD<sup>[1]</sup>
								</th>
							</tr>
						</thead>
						<tbody>
							<tr>
								<td align="left">Small</td>
								<td align="center">9</td>
								<td align="center">822.56</td>
								<td align="center">115.55</td>
								<td align="center">760.71</td>
								<td align="center">115.18</td>
								<td align="center">6.99</td>
								<td align="center">11.32</td>
							</tr>
							<tr>
								<td align="left">Medium</td>
								<td align="center">9</td>
								<td align="center">1,778.99</td>
								<td align="center">356</td>
								<td align="center">1,668.99</td>
								<td align="center">313.13</td>
								<td align="center">5.83</td>
								<td align="center">4.69</td>
							</tr>
							<tr>
								<td align="left">Large</td>
								<td align="center">7</td>
								<td align="center">2,748.23</td>
								<td align="center">1,082.91</td>
								<td align="center">2,667.01</td>
								<td align="center">1,067.25</td>
								<td align="center">3.08</td>
								<td align="center">2.64</td>
							</tr>
						</tbody>
					</table>
					<table-wrap-foot>
						<fn id="twf-2-20934">
							<p>
								<sup>[1]</sup>Standard Deviation</p>
						</fn>
					</table-wrap-foot>
				</table-wrap>
				<fig id="fig-12-20934">
					<label>Figure 12</label>
					<caption>
						<title>Relationship between plot size and error in area measurement.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf12.png" id="gra-12-20934"/>
				</fig>
				<p>The percentage error is presented in a histogram of the frequency distribution curve (<xref ref-type="fig" rid="fig-13-20934">Figure 13</xref>) which indicates that the maximum frequency of percentage error falls between 5% and 10%. This positive value indicates that, in most cases, the area obtained through the developed application was less than the manually measured area. This recommends that the developed system can be used with an expected error range of 5-10%. The error can be further reduced by using a more precise GPS.</p>
				<fig id="fig-13-20934">
					<label>Figure 13</label>
					<caption>
						<title>Frequency distribution curve of percentage error.</title>
					</caption>
					<graphic xlink:href="SJAR-23-01-20934-gf13.png" id="gra-13-20934"/>
				</fig>
				<disp-formula id="dif-2-20934">
					<mml:math id="mml-2-20934">
						<mml:mrow>
							<mml:mi>E</mml:mi>
							<mml:mi>r</mml:mi>
							<mml:mi>r</mml:mi>
							<mml:mi>o</mml:mi>
							<mml:mi>r</mml:mi>
							<mml:mo>&#xa0;</mml:mo>
							<mml:mfenced>
								<mml:mi>%</mml:mi>
							</mml:mfenced>
							<mml:mo>=</mml:mo>
							<mml:mfenced>
								<mml:mrow>
									<mml:mi>A</mml:mi>
									<mml:mi>r</mml:mi>
									<mml:mi>e</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mo>&#xa0;</mml:mo>
									<mml:mi>m</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mi>n</mml:mi>
									<mml:mi>u</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mi>l</mml:mi>
									<mml:mi>l</mml:mi>
									<mml:mi>y</mml:mi>
									<mml:mo>&#x2212;</mml:mo>
									<mml:mi>A</mml:mi>
									<mml:mi>r</mml:mi>
									<mml:mi>e</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mo>&#xa0;</mml:mo>
									<mml:mi>i</mml:mi>
									<mml:mi>n</mml:mi>
									<mml:mo>&#xa0;</mml:mo>
									<mml:mi>d</mml:mi>
									<mml:mi>e</mml:mi>
									<mml:mi>v</mml:mi>
									<mml:mi>e</mml:mi>
									<mml:mi>l</mml:mi>
									<mml:mi>o</mml:mi>
									<mml:mi>p</mml:mi>
									<mml:mi>e</mml:mi>
									<mml:mi>d</mml:mi>
									<mml:mo>&#xa0;</mml:mo>
									<mml:mi>a</mml:mi>
									<mml:mi>p</mml:mi>
									<mml:mi>p</mml:mi>
									<mml:mi>l</mml:mi>
									<mml:mi>i</mml:mi>
									<mml:mi>c</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mi>t</mml:mi>
									<mml:mi>i</mml:mi>
									<mml:mi>o</mml:mi>
									<mml:mi>n</mml:mi>
								</mml:mrow>
							</mml:mfenced>
							<mml:mo>/</mml:mo>
							<mml:mfenced>
								<mml:mrow>
									<mml:mi>A</mml:mi>
									<mml:mi>r</mml:mi>
									<mml:mi>e</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mo>&#xa0;</mml:mo>
									<mml:mi>m</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mi>n</mml:mi>
									<mml:mi>u</mml:mi>
									<mml:mi>a</mml:mi>
									<mml:mi>l</mml:mi>
									<mml:mi>l</mml:mi>
									<mml:mi>y</mml:mi>
								</mml:mrow>
							</mml:mfenced>
							<mml:mo>&#xd7;</mml:mo>
							<mml:mn>100</mml:mn>
						</mml:mrow>
					</mml:math>
					<label>(2)</label>
				</disp-formula>
			</sec>
			<sec id="sec-3.3-20934">
				<title>Validation of area segregation</title>
				<p>The area of segregated fields recorded by the developed application over five days is tabulated along with the manually measured area in <xref ref-type="table" rid="taw-3-20934">Table 3</xref>. The area segregation efficiency was 100% as total of 15 fields were covered on different days and accordingly, the developed system calculated the area for all 15 fields. . Further, the table shows that though maximum error was about 20%, the average error was 9.41 %. Additionally, as the field size increased, the error decreased. Since the data were recorded using the GPS of the smartphone, the possible cause of error can be the satellite position, GPS drift, signal obstruction, calculation inaccuracies, and rounding errors. However, the likelihood of error in area calculation is minimal, as the system employs standard mathematical formulas. The measured error can be further reduced by using a more precise GPS with higher accuracy.</p>
				<table-wrap id="taw-3-20934">
					<label>Table 3</label>
					<caption>
						<title>Error percentage between manually measured area and system-recorded area for different fields over multiple days.</title>
					</caption>
					<table>
						<colgroup>
							<col span="2"/>
							<col/>
							<col/>
							<col/>
							<col/>
						</colgroup>
						<thead>
							<tr>
								<th align="left" colspan="2">No. of Days </th>
								<th align="left">Field</th>
								<th align="left">Manually (m<sup>2</sup>)</th>
								<th align="left">Developed Application (m<sup>2</sup>)</th>
								<th align="left">Error (%)</th>
							</tr>
						</thead>
						<tbody>
							<tr>
								<td align="left" rowspan="3">Day 1</td>
								<td align="center"> </td>
								<td align="center">F1<sup>[1]</sup>
								</td>
								<td align="center">1,890.22</td>
								<td align="center">1,576.625</td>
								<td align="center">16.59</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F2<sup>[2]</sup>
								</td>
								<td align="center">1,581.07</td>
								<td align="center">1,332.875</td>
								<td align="center">15.7</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F3<sup>[3]</sup>
								</td>
								<td align="center">1,615.62</td>
								<td align="center">1,298.625</td>
								<td align="center">19.62</td>
							</tr>
							<tr>
								<td align="left" rowspan="2">Day 2</td>
								<td align="center"> </td>
								<td align="center">F1<sup>[1]</sup>
								</td>
								<td align="center">2,685.75</td>
								<td align="center">2,835.4</td>
								<td align="center">-5.57</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F2<sup>[2]</sup>
								</td>
								<td align="center">3,200.5</td>
								<td align="center">2,973.59</td>
								<td align="center">7.09</td>
							</tr>
							<tr>
								<td align="left" rowspan="3">Day 3</td>
								<td align="center"> </td>
								<td align="center">F1<sup>[1]</sup>
								</td>
								<td align="center">2,769.37</td>
								<td align="center">2,511.75</td>
								<td align="center">9.3</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F2<sup>[2]</sup>
								</td>
								<td align="center">2,294.13</td>
								<td align="center">2,035.4</td>
								<td align="center">11.28</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F3<sup>[3]</sup>
								</td>
								<td align="center">2,679.83</td>
								<td align="center">2,719</td>
								<td align="center">-1.46</td>
							</tr>
							<tr>
								<td align="left" rowspan="4">Day 4</td>
								<td align="center"> </td>
								<td align="center">F1<sup>[1]</sup>
								</td>
								<td align="center">3,692.6</td>
								<td align="center">3,419.5</td>
								<td align="center">7.4</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F2<sup>[2]</sup>
								</td>
								<td align="center">2,788.69</td>
								<td align="center">2,495.5</td>
								<td align="center">10.51</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F3<sup>[3]</sup>
								</td>
								<td align="center">4,285.22</td>
								<td align="center">4,009.875</td>
								<td align="center">6.43</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F4<sup>[4]</sup>
								</td>
								<td align="center">4,200.62</td>
								<td align="center">3,987.5</td>
								<td align="center">5.07</td>
							</tr>
							<tr>
								<td align="left" rowspan="3">Day 5</td>
								<td align="center"> </td>
								<td align="center">F1<sup>[1]</sup>
								</td>
								<td align="center">1,353.37</td>
								<td align="center">1,083.75</td>
								<td align="center">19.92</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F2<sup>[2]</sup>
								</td>
								<td align="center">2,978.55</td>
								<td align="center">2,635.5</td>
								<td align="center">11.52</td>
							</tr>
							<tr>
								<td align="center"> </td>
								<td align="center">F3<sup>[3]</sup>
								</td>
								<td align="center">3,240.33</td>
								<td align="center">2,988.87</td>
								<td align="center">7.76</td>
							</tr>
							<tr>
								<td align="left">Average</td>
								<td align="center"> </td>
								<td align="center"> </td>
								<td align="center"> </td>
								<td align="center"> </td>
								<td align="center">9.41</td>
							</tr>
						</tbody>
					</table>
					<table-wrap-foot>
						<fn id="twf-3-20934">
							<p>
								<sup>[1] [2] [3] [4]</sup> Denote different fields (Field 1, Field 2, Field 3, Field 4) in the study area.</p>
						</fn>
					</table-wrap-foot>
				</table-wrap>
			</sec>
		</sec>
		<sec id="sec-4-20934" sec-type="conclusions">
			<title>Conclusion</title>
			<p>A mobile application was developed to record the geolocation of machine&#x2019;s movement using the GPS of a smartphone. The developed application was capable of segregating the tractor&#x2019;s operation in different fields and calculating the area of each field. It also recorded the time taken in each field. It was observed that the error in time measurement, compared to the manually noted values, was non-significant. However, in the case of area measurement, the average percentage error was found to be 6.91% for small fields (area less than 1,000 m&#xb2;), 5.40% for medium fields (area between 1,000 and 2,500 m&#xb2;), and 2.46% for large fields (area more than 2,500 m&#xb2;). This indicates that as the plot size increases, the error decreases. Furthermore, no error was found in field segregation, confirming that the developed system is capable of identifying field operations and idle movement. Therefore, the developed application can be considered an effective tool for monitoring farm machines&#x2019; operation in terms of area coverage and time taken, which will ultimately be useful for charging the custom hiring services.</p>
		</sec>
	</body>
	<back>
		<ack>
			<title>Acknowledgements</title>
			<p>Authors hereby express their profound gratitude, and cordial thanks to the Department of Farm Machinery and Power Engineering, College of Agricultural Engineering, Dr. Rajendra Prasad Central Agricultural University, Pusa, Bihar, India, and RetiUno Technologies Private Ltd. Bangalore, India for the completion of this research.</p>
		</ack>
		<sec id="sec-5-20934" sec-type="ai-statement">
			<title>Statement about use of generative AI</title>
			<p>The translation of the title, abstract, and keywords from the original version in English to Spanish has been generated using OpenAI, ChatGPT GPT-4o mini (2024).</p>
		</sec>
		<sec id="sec-6-20934" sec-type="transparency-statement">
			<title>Competing interests</title>
			<p>The authors have declared that no competing interests exist.</p>
		</sec>
		<sec id="sec-7-20934" sec-type="author-contributions">
			<title>Authors&#x2019; contributions</title>
			<p>Apoorva Sharma: Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Project administration, Supervision, Visualization, Writing - original draft, Writing - review &amp; editing. Prabhanjan Kumar Pranav: Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Project administration, Supervision, Visualization, Writing - original draft, Writing - review &amp; editing. Ritesh Prasad: Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Project administration, Supervision, Visualization, Writing - original draft, Writing - review &amp; editing.</p>
		</sec>
		<sec id="sec-8-20934" sec-type="apoyo">
			<title/>
			<table-wrap id="taw-5-20934">
				<table>
					<colgroup>
						<col/>
						<col/>
					</colgroup>
					<thead>
						<tr>
							<th align="justify">Funding agencies/institutions</th>
							<th align="justify">Project / Grant</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<td align="justify">All India Coordinated Research Project on Farm Implements and Machinery (AICRP on FIM).</td>
							<td align="justify">2,50,000</td>
						</tr>
					</tbody>
				</table>
			</table-wrap>
		</sec>
		<ref-list id="refl-1-20934">
			<title>References</title>
			<ref id="ref-1-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Daum</surname>
							<given-names>T</given-names>
						</name>
						<name>
							<surname>Villalba</surname>
							<given-names>R</given-names>
						</name>
						<name>
							<surname>Anidi</surname>
							<given-names>O</given-names>
						</name>
						<name>
							<surname>Mayienga</surname>
							<given-names>SM</given-names>
						</name>
						<name>
							<surname>Gupta</surname>
							<given-names>S</given-names>
						</name>
						<name>
							<surname>Birner</surname>
							<given-names>R</given-names>
						</name>
					</person-group>
					<year>2020</year>
					<article-title>Uber for tractors? Opportunities and challenges of digital tools for tractor hire in India and Nigeria</article-title>
					<source>World Dev</source>
					<volume>144</volume>
					<fpage>1</fpage>
					<lpage>15</lpage>
					<pub-id pub-id-type="doi">10.1016/j.worlddev.2021.105480</pub-id>
				</element-citation>
			</ref>
			<ref id="ref-2-20934">
				<element-citation publication-type="confproc">
					<person-group person-group-type="author">
						<name>
							<surname>Inoue</surname>
							<given-names>K</given-names>
						</name>
						<name>
							<surname>Nii</surname>
							<given-names>K</given-names>
						</name>
						<name>
							<surname>Zhang</surname>
							<given-names>Y</given-names>
						</name>
					</person-group>
					<year>2009</year>
					<source>Tractor guidance system for field work using GPS and GYRO</source>
					<conf-name>Proc Int Sci Conf Energy Eff Agric Eng</conf-name>
					<conf-date>Oct 1</conf-date>
					<fpage>280</fpage>
					<lpage>295</lpage>
				</element-citation>
			</ref>
			<ref id="ref-3-20934">
				<element-citation publication-type="confproc">
					<person-group person-group-type="author">
						<name>
							<surname>Jayawant</surname>
							<given-names>YA</given-names>
						</name>
						<name>
							<surname>Joshi</surname>
							<given-names>N</given-names>
						</name>
					</person-group>
					<year>2018</year>
					<source>Modeling operations of a custom hiring center using agent based modeling and discrete event simulation</source>
					<conf-name>Proc III Asia-Pacific Conf on Complex Systems Design &amp; Management</conf-name>
					<conf-sponsor>CSD&amp;M Asia</conf-sponsor>
					<fpage>13</fpage>
					<lpage>24</lpage>
					<pub-id pub-id-type="doi">10.1007/978-3-030-02886-2_2</pub-id>
				</element-citation>
			</ref>
			<ref id="ref-4-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Kaivosoja</surname>
							<given-names>J</given-names>
						</name>
						<name>
							<surname>Linkolehto</surname>
							<given-names>R</given-names>
						</name>
					</person-group>
					<year>2015</year>
					<article-title>GNSS error simulator for farm machinery navigation development</article-title>
					<source>Comput Electron Agric</source>
					<volume>119</volume>
					<fpage>166</fpage>
					<lpage>177</lpage>
					<pub-id pub-id-type="doi">10.1016/j.compag.2015.10.021</pub-id>
				</element-citation>
			</ref>
			<ref id="ref-5-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Maurya</surname>
							<given-names>K</given-names>
						</name>
						<name>
							<surname>Singh</surname>
							<given-names>M</given-names>
						</name>
						<name>
							<surname>Jain</surname>
							<given-names>N</given-names>
						</name>
					</person-group>
					<year>2016</year>
					<article-title>Real time vehicle tracking system using GSM and GPS technology-an anti-theft tracking system</article-title>
					<source>Int J Electron Comput Sci Eng</source>
					<volume>1</volume>
					<issue>3</issue>
					<fpage>1103</fpage>
					<lpage>1107</lpage>
				</element-citation>
			</ref>
			<ref id="ref-6-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Omrani</surname>
							<given-names>A</given-names>
						</name>
						<name>
							<surname>Shiekhdavoodi</surname>
							<given-names>MJ</given-names>
						</name>
						<name>
							<surname>Shomeili</surname>
							<given-names>M</given-names>
						</name>
					</person-group>
					<year>2013</year>
					<article-title>Determine Sugarcane harvester field efficiency using global positioning system (GPS) data</article-title>
					<source>Elixir Agric</source>
					<volume>56</volume>
					<fpage>13260</fpage>
					<lpage>13263</lpage>
				</element-citation>
			</ref>
			<ref id="ref-7-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Pranav</surname>
							<given-names>PK</given-names>
						</name>
						<name>
							<surname>Phukan</surname>
							<given-names>Y</given-names>
						</name>
						<name>
							<surname>Saha</surname>
							<given-names>B</given-names>
						</name>
					</person-group>
					<year>2016</year>
					<article-title>Computer program for cost estimation of agricultural machines</article-title>
					<source>Agric Eng</source>
					<volume>1</volume>
					<fpage>1</fpage>
					<lpage>10</lpage>
				</element-citation>
			</ref>
			<ref id="ref-8-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Stoll</surname>
							<given-names>A</given-names>
						</name>
						<name>
							<surname>Stafford</surname>
							<given-names>J</given-names>
						</name>
						<name>
							<surname>Werner</surname>
							<given-names>A</given-names>
						</name>
					</person-group>
					<year>2003</year>
					<article-title>Automatic operation planning for GPS-guided machinery</article-title>
					<source>Precis Agric</source>
					<volume>3</volume>
					<fpage>657</fpage>
					<lpage>664</lpage>
					<pub-id pub-id-type="doi">10.3920/9789086865147_101</pub-id>
				</element-citation>
			</ref>
			<ref id="ref-9-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Thomson</surname>
							<given-names>SJ</given-names>
						</name>
						<name>
							<surname>Huang</surname>
							<given-names>Y</given-names>
						</name>
						<name>
							<surname>Smith</surname>
							<given-names>LA</given-names>
						</name>
					</person-group>
					<year>2014</year>
					<article-title>Portable device to assess dynamic accuracy of global positioning system (GPS) receivers used in agricultural aircraft</article-title>
					<source>Int J Agric Biol Eng</source>
					<volume>7</volume>
					<issue>2</issue>
					<fpage>68</fpage>
					<lpage>74</lpage>
					<pub-id pub-id-type="doi">10.3965/j.ijabe.20140702.008</pub-id>
				</element-citation>
			</ref>
			<ref id="ref-10-20934">
				<element-citation publication-type="journal">
					<person-group person-group-type="author">
						<name>
							<surname>Xiang</surname>
							<given-names>M</given-names>
						</name>
						<name>
							<surname>Wei</surname>
							<given-names>S</given-names>
						</name>
						<name>
							<surname>Zhang</surname>
							<given-names>M</given-names>
						</name>
						<name>
							<surname>Li</surname>
							<given-names>M</given-names>
						</name>
					</person-group>
					<year>2016</year>
					<article-title>Real-time monitoring system of agricultural machinery operation information based on ARM11 and GNSS</article-title>
					<source>IFAC-Pap</source>
					<volume>49</volume>
					<fpage>121</fpage>
					<lpage>126</lpage>
					<pub-id pub-id-type="doi">10.1016/j.ifacol.2016.10.023</pub-id>
				</element-citation>
			</ref>
		</ref-list>
	</back>
</article>