\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,english]{babel}



\usepackage{float}








\begin{document}

\title{Intuitively usable Cycling Infrastructure -- a systematic Literature
Review}



\author[1]{David Friel}%
\affil[1]{Technische Universität Berlin}%


\vspace{-1em}



  
  \date{June 11, 2024}


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





\selectlanguage{english}
\begin{abstract}
While infrastructure planning guidelines frequently emphasise the need
of comprehensible, easy to use or unambiguously understandable
infrastructure, they lack information on how to design such intuitively
usable cycling infrastructure. Furthermore, while cyclists already
criticise the current traffic system not to be intuitively usable, this
issue will be even more relevant as cycling usage may increase in the
next years. Thus, this paper presents a systematic literature review to
identify studies that already investigated the intuitiveness of cycling
infrastructure. Furthermore, this study aims to identify major research
gaps. Searching three databases with a predefined set of keywords
resulted in more than 1300 titles. Applying inclusion and exclusion
criteria, eleven titles remained in the last review step and were
analysed in detail. Results show that these studies use a variety of
methods and terms to describe and investigate intuitiveness of various
cycling infrastructure designs. Conclusions from these studies range
from very specific infrastructure design recommendations over highly
general design advices to recommendations that do not refer to
infrastructure design at all. Three main research gaps were identified.
Firstly, there are various infrastructure types that have not been
covered by the studies. Furthermore, there is a need for basic research
on how to apply principles of intuitive design to cycling infrastructure
design in general. Lastly, a large amount of research investigated
behavioural responses to infrastructural changes but was not designed to
specifically assess intuitiveness. Thus, there are large research gaps
to be filled by upcoming studies to design intuitively usable cycling
infrastructure.%
\end{abstract}%



\sloppy




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

