\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[ngerman,greek,english]{babel}



\usepackage{float}








\begin{document}

\title{Optimal Terrain Correction Software for Window Remove-Restore Technique
with a Case Study for Africa}



\author[1]{Hussein A. Abd-Elmotaal}%
\author[2]{Norbert Kühtreiber}%
\affil[1]{Minia University}%
\affil[2]{Graz University of Technology}%


\vspace{-1em}



  
  \date{May 07, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
The window remove-restore technique, suggested by Abd-Elmotaal and
K\selectlanguage{ngerman}ühtreiber (2003) to get rid of the double consideration of the
topographic-isostatic masses within the data window, is implemented for
the African gravity field recovery in the framework of the activities of
the IAG Sub-Commission on the gravity and geoid in Africa. Within the
course of the window technique, one needs to compute the effect of the
topographic-isostatic masses (terrain correction) for the full data
window. Since the African data window is fairly large (-42º \selectlanguage{english}[?] \selectlanguage{greek}φ \selectlanguage{english}[?] \selectlanguage{english}44\selectlanguage{ngerman}º;
-22º \selectlanguage{english}[?] \selectlanguage{greek}λ \selectlanguage{english}[?] \selectlanguage{english}62\selectlanguage{ngerman}º), the computation of the effect of the
topographic-isostatic masses of the full data window consumes very long
CPU time using the common TC-program (Forsberg, 1984). This
investigation proposes an optimal terrain correction software for the
window remove-restore technique. It uses three radii around the
computational point. The first radius is used for the innermost zone
utilizing the finest DTM for a relatively short radius (around 2 km).
The second radius is used for the inner zone up to a short radius (10-15
km). Here a reasonably fine DTM is sufficient. The third radius is used
for the rest of the full data window utilizing a coarse DTM. A thorough
comparison between the developed software and the TC-program is
performed to assess the quality of the developed technique and to
compare the needed CPU time to perform the terrain correction for
Africa.%
\end{abstract}\selectlanguage{ngerman}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

