Traffic Safety Research (TSR template)

@article{belin_2012,
    author = {Belin, Matts-Åke and Tillgren, Per and Vedung, Evert},
    title = {Vision Zero---a road safety policy innovation},
    journal = {International Journal of Injury Control and Safety Promotion},
    volume = {19},
    number = {2},
    pages = {171--179},
    year = {2012},
    DOI = {10.1080/17457300.2011.635213}
}

@article{Godthelp_2023,
    author = {Godthelp, Hans},
    title = {Towards a safe system in low- and middle-income countries: vehicles that guide drivers on self-explaining roads},
    journal = {Traffic Safety Research},
    volume = {5},
    pages = {e000029},
    year = {2023},
    DOI = {10.55329/avnw4364}
}

@techreport{Gettman_2008,
  author = {Gettman, Douglas and Pu, Lili and Sayed, Tarek and Shelby, Steve},
  title = {Surrogate safety assessment model and validation},
  institution = {Federal Highway Administration},
  year = {2008},
  number = {FHWA-HRT-08-051},
  URL = {https://www.fhwa.dot.gov/publications/research/safety/08051/08051.pdf}}

@conference{Elvik_2009,
    author = {Elvik, Rune and Erke, Alena and Christensen, Peter},
    eventtitle = {TRB Annual Meeting},
    venue = {Washington D.C., USA},
    title = {Elementary units of exposure},
    year = {2009}
}

@conference{Guttinger_1982,
    author = {Güttinger, V. A.},
    eventtitle = {International Workshop on Traffic Conflicts Techniques},
    venue = {Leidschendam, the Netherlands},
    title = {From accidents to conflicts: alternative safety measurement},
    year = {1982},
    URL = {https://www.ictct.net/wp-content/uploads/XX-Leidschendam-1982/Guttinger_1982.pdf}
}

@book{Edvardsson_Bjornberg_2023,
    editor = {Edvardsson Björnberg, Karin and Hansson, Sven Ove and Belin, Matts-Åke and Tingvall, Claes},
    title = {The {Vision Zero} handbook: theory, technology and management for a zero casualty policy},
    publisher = {Springer},
    year = {2023},
    DOI = {10.1007/978-3-030-76505-7}
}

@book{Hauer_2015,
    author = {Hauer, Ezra},
    title = {The art of regression modelling in road safety},
    publisher = {Springer},
    year = {2015},
    DOI = {10.1007/978-3-030-76505-7_2}
}

@incollection{Hansson_2023,
    author = {Hansson, Sven Ove},
    title = {Zero visions and other safety principles},
    booktitle = {The {Vision Zero} handbook: theory, technology and management for a zero casualty policy},
    editor = {Edvardsson Björnberg, Karin and Hansson, Sven Ove and Belin, Matts-Åke and Tingvall, Claes},
    publisher = {Springer},
    year = {2023},
    DOI = {10.1007/978-3-030-76505-7_2}
}

@phdthesis{Hyden_1987,
    author = {Hydén, Christer},
    title = {The development of a method for traffic safety evaluation: the {Swedish} traffic conflict technique},
    school = {Lund University, Sweden},
    year ={1987},
    URL = "https://www.ictct.net/wp-content/uploads/SMoS_Library/LIB_Hyden_1987.pdf"
}

@online{FHWA_n_d,
  title = {Crash modification factors clearinghouse},
  author = {{Federal Highway Administration}},
  year = {n.d.},
  url = {https://www.cmfclearinghouse.org/}
}

\documentclass[12pt]{article}
\usepackage{csquotes}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{amsfonts}
\usepackage{color}
\usepackage[table]{xcolor}
\usepackage{hyperref}
\usepackage{enumitem} 
\usepackage{soul}
\usepackage{graphicx} % Required for inserting images
\usepackage[a4paper, top=2.5cm, bottom=2.5cm, left=2.5cm, right=2.5cm]{geometry}
\usepackage[skip=6pt]{parskip}
\usepackage{titlesec}
\usepackage[backend=biber, style=apa]{biblatex}
\setlength{\bibhang}{1em}

\usepackage[pagewise]{lineno}
\linenumbers

\usepackage{tabularx}
\usepackage{multirow}
\usepackage{array}
\usepackage{threeparttable}

\setlength{\parindent}{0pt}

\addbibresource{References.bib}
\DeclareBibliographyDriver{inproceedings}{
    \printnames{author}
    \printtext{ (\printfield{year})}
    \newunit
    \printfield[titlecase]{title}
    \newunit
    \printtext{\mkbibitalic{\printfield{eventtitle}}}
    \setunit*{\addcomma\space}
    \printfield{venue}
    \printtext{.}
    \newunit
    \usebibmacro{doi+eprint+url}
}

\hypersetup{colorlinks=true, linkcolor=blue, filecolor=blue, urlcolor=blue, citecolor=blue}

\titleformat{\section}{\Large\bfseries}{\thesection}{1em}{}
\titleformat{\subsection}{\large\bfseries}{\thesubsection}{1em}{}
\titleformat{\subsubsection}{\normalsize\bfseries}{\thesubsubsection}{1em}{}

\title{Your paper}



\begin{document}
\author{}
\date{} % leave blank, other wise the date will be printed
\maketitle



\textbf{Name Surname}\textsuperscript{1} https://orcid.org/0000-XXXX-XXXX-XXXX
\\\textbf{Name Surname}\textsuperscript{1,2*} https://orcid.org/0000-XXXX-XXXX-XXXX
\\\textbf{Name Surname}\textsuperscript{2} https://orcid.org/0000-XXXX-XXXX-XXXX

\textsuperscript{1} Institution, Country https://ror.org/xxxxxxxxx
\\\textsuperscript{2} Institution, Country https://ror.org/xxxxxxxxx

\textsuperscript{*} Corresponding author: [email protected]



\subsection*{Abstract} \label{abstract}
Write the abstract in one paragraph. Do not use text treatments (\textbf{bold}, \emph{italic}, \underline{underline}). Do not use references, images, or formulas. Be concise and stick to what is unique and most important. What is the (real) traffic safety problem that motivated your work? What is the specific research question you tried to answer? What data and method did you use? What are your most important findings and conclusions? How does your work add to already existing knowledge?



\subsection*{Keywords} \label{keywords}
keyword\_1
\\keyword\_2
\\keyword\_3

Place one keyword per line. Write keywords in lowercase, except for terms that require capitalization, such as abbreviations and proper names. For example:

‘traffic safety’

but

‘LMICs (low- and middle-income countries)’ (abbreviation)
\\‘Vision Zero’ (proper name).



\section{Technical requirements} \label{technical-requirements}
\subsection{General} \label{general}
\begin{itemize}
    \item Use built-in \LaTeX\ commands to logically structure the document and to create section headings (\verb|\section{}, \subsection{}, \subsubsection{}|, etc.).
    \item Make sure to remove all comments and accept all changes. Always provide a version of the manuscript that is free from ambiguity and ready for evaluation.
\end{itemize}



\subsection{Submitting revisions} \label{submitting-revisions}
\begin{itemize}
    \item Make sure to remove all comments and accept all changes.
    \item \colorbox{yellow}{Highlight your revisions} using the command \verb|\colorbox{}|.
    \item Provide a detailed response to each of the reviewers' comments in a \emph{separate} document.
\end{itemize}



\subsection{Submitting for production} \label{submitting-for-production}
\begin{itemize}
    \item Make sure to remove all comments and accept all changes.
    \item Provide the following:
    \begin{itemize}
        \item compiled .pdf file (as a formatting reference for the typesetting team) 
        \item .tex file (manuscript)
        \item .bib file (references), containing only the titles cited in the manuscript
        \item image files for figures (.jpg or .png).
    \end{itemize}
\end{itemize}



\section{Manuscript length} \label{manuscript-length}
The \emph{TSR} does not impose any specific restrictions on the length of the manuscripts. The length should be adequate in relation to the contents, allowing for description of the work done in sufficient detail yet not giving the impression of lengthiness.

During the review stage, the authors may receive recommendations from the editor regarding shortening or expanding the manuscript or its specific parts.



\section{Language standard} \label{language-standard}
The \emph{TSR} publishes materials written in English language. British, American, and other varieties are equally acceptable. It is expected that the authors have proofread their manuscript prior to the submission, consulting specialized language services if necessary. Manuscripts written sloppily, or found difficult to understand due to language issues, will be desk rejected by the editor.

Given the fact that the majority of the \emph{TSR}'s authors, reviewers, and editors are not native English speakers, a certain share of ‘language imperfections’ is unavoidable. However, they should not hinder the reading flow or create ambiguity about the contents.

In case AI tools are used to improve the language, it should be disclosed under ‘Declaration of generative AI use’ (see \autoref{declaration-of-generative-ai-use}).



\section{‘Crash’ or ‘accident’?} \label{crash-or-accident}

The \emph{TSR} editorial team considers the ‘crash or accident’ debate overheated and, on some occasions, counterproductive. The journal acknowledges that both sides of the debate have raised issues worthy of consideration (e.g. \href{https://doi.org/10.1023/A:1016260130224}{here} and \href{https://doi.org/10.1016/j.aap.2016.05.024}{here}). It does not, however, regard language policing as an appropriate means of addressing these issues. Accordingly, authors are free to decide which term they consider most suitable. Reviewers are advised to refrain from commenting on this matter, and editors are instructed to disregard such comments when making their decisions.



\section{Titles and headings} \label{titles-and-headings}
Article title, section headings, and table and figure captions should use sentence case (capitalize only the first word and proper nouns).

Do not add a full stop (\verb|.|) at the end of a heading or a caption unless it forms a complete sentence (containing a subject and a verb). For example, see captions for \autoref{Table_1} and \autoref{Figure_1}.

Do not use more than three levels of headings.



\section{Text matter treatments}\label{text-matter-treatments}
Generally, text treatments should be applied sparsely. Untreated roman type is the standard typeface.

Use \emph{italics} to emphasize parts of the text. \textbf{Bold} and \underline{underline} type should be generally avoided.




\section{Numbers and dates}\label{numbers-and-dates}
\subsection{Number formatting} \label{number-formatting}
Make sure that the selected number format (decimal point, three-digit separation, etc.) is used consistently throughout the paper, including in the numbers that appear in the text, formulae, tables, and graphs.

Use words for quantities below ten and use digits for larger quantities (‘five participants’, but ‘25 bicyclists’). Do not mix them, though: ‘5 to 25 participants’, not ‘\st{five to 25}’.

\subsection{Units of measure}\label{units-of-measure}
Both abbreviated and fully written units of measure are separated by a (thin) non-breaking space: ‘23~kg’; ‘90~km/h’; ‘11~a.m.’; ‘23~kilograms’; ‘3~miles’; ‘a structure weighing 63~tonnes’’.

The exceptions are per cent and degree symbols which are not spaced: ‘25\%’; ‘33.5º’.

Fully written units become plural when the quantity is more than one (‘0.5~litre’, but ‘3~kilograms’). 



\subsection{Currencies} \label{currencies}
The currency symbols precede the numerals (no space): ‘\$25’; ‘€70.5’; ‘\$15~billion’.

Three-letter currency codes are separated with a (thin) non-breaking space: ‘EUR~40~000’; ‘USD~1~billion’; ‘SEK~500’.



\subsection{Number ranges} \label{number-ranges}
Use \emph{en rule} ( -- ) to link the range numbers (no spaces): ‘12--15’; ‘95~000--110~000’; ‘4.5--5.6’.

For ranges including negative numbers, use words to avoid confusion: ‘-7.56 to -6.15’.

Units of measure are not repeated: ‘5--6~kg’; ‘1~000--2~500~litres’.

The exceptions are per cents and degrees: ‘25\%--30\%’; ‘12.5°--13.5°’.



\subsection{Dates} \label{dates}
The preferred date format is: ‘12 September 2022’.

A named day is separated by a comma: ‘Friday, 30 September 2022’.

Do not use -st, -rd, -th in conjunction with the figure (‘\st{1st April 1980}’). Avoid using all-figure forms as they could mean different things in different countries (‘\st{7/5/12}’).

Use \emph{en rule} ( -- ) to indicate a date range: ‘12--15 September 2020’; ‘data collection during the winter period 2019--2020’.



\section{Tables} \label{tables}
Place tables in the manuscript directly after the first paragraph in which it is referred to. Make sure that all tables are referred to in the text (see \autoref{Table_1}).

\begin{threeparttable}[ht]
    \centering 
    \caption{Example table title (keep it short, move long explanations to table notes)}
    \begin{tabularx}{\textwidth}{X X X X X}
        \hline
        \rowcolor{lightgray}
        \multicolumn{1}{l}{Column header} & \multicolumn{1}{c}{Column header} & \multicolumn{2}{c}{Column header} & \multicolumn{1}{c}{Column header}\\
        
        \rowcolor{lightgray}
        & & \multicolumn{1}{c}{Sub-header} & \multicolumn{1}{c}{Sub-header} & \\
        \hline
        
        Row header & \multicolumn{1}{c}{Type A} & \multicolumn{1}{r}{11\tnote{*}} & \multicolumn{1}{r}{11~212} & \multicolumn{1}{r}{45.6}\\
        
        & \multicolumn{1}{c}{Type B} & \multicolumn{1}{r}{n/a} & \multicolumn{1}{r}{5~137} & \multicolumn{1}{r}{11.5}\\
        
        Row header & \multicolumn{1}{c}{Type B} & \multicolumn{1}{r}{25} & \multicolumn{1}{r}{56~733} & \multicolumn{1}{r}{32.0}\\
        
        Row header & \multicolumn{1}{c}{Type A} & \multicolumn{1}{r}{31} & \multicolumn{1}{r}{877} & \multicolumn{1}{r}{35.8}\\
        
        & \multicolumn{1}{c}{Type C} & \multicolumn{1}{r}{n/a} & \multicolumn{1}{r}{31~255} & \multicolumn{1}{r}{0.4\tnote{\textdagger}}\\
        
        \multicolumn{2}{l}{TOTAL} & \multicolumn{1}{r}{---} & \multicolumn{1}{r}{105~214} & \multicolumn{1}{r}{125.3}\\
    \hline
    \end{tabularx}
    
    \begin{tablenotes}
        \footnotesize{
            \item Here is a general note related to the entire table.
            \item[*] Here is a note related to a specific value/cell in the table. Mark specific notes with a system of indices different from that used in the main text (e.g.~use 1, 2, 3, ... in the main text and *, †, ‡, §, \#, ... in the tables).
            \item[\textdagger] Omitting leading zero (‘.4’ instead of ‘0.4’) for numbers between 0 and 1 is permitted though not recommended. Same approach should be used consistently throughout all the tables.
        }
    \end{tablenotes}
    \label{Table_1}
\end{threeparttable}

General formatting requirements are:

\begin{itemize}
    \item Do not create single-columned tables, consider making a list instead.
    \item Avoid using shading and border lines, except for separating the header and the bottom of the table.
    \item In case individual cells contain colour coding, images or equations, convert the table to a figure instead.
    \item Centre-align all column headers, except for the first column which is always left-aligned.
    \item Left-align table data: (\emph{i}) contents of the first column; (\emph{ii}) columns containing long text.
    \item Centre-align table data: columns containing short text.
    \item Right-align table data: columns with numerical data.
    \item For numerical data, use the same number of decimal digits within the same column.
    \item Tables with multiple sections must have the same number of columns across all sections. If that is not possible, split them into multiple tables.
    \item Avoid making table structure overly complex through excessive usage of merged cells. Values that do not belong to any particular column (AIC, BIC, R\textsuperscript{2}, etc.) are better fit in the table footnotes.
\end{itemize}



\section{Figures} \label{figures}
Always import a figure as \emph{one} single image (.png or .jpg). Editable objects such as Excel charts, textboxes, lines, etc. must be exported as an image and then imported again.

Place the figure in the manuscript directly after the paragraph in which it was first mentioned. Make sure that all figures are referred to in the text (see \autoref{Figure_1}).

\begin{figure}[ht]
    \centering
    \includegraphics[width=5.73512in,height=2.01446in]{Figure_1.png}
    \caption{Example figure title (keep it short): (\emph{a}) first figure panel; (\emph{b}) second figure panel}
    \label{Figure_1}
\end{figure}

General formatting requirements are:

\begin{itemize}
    \item Make sure the text size is readable.
    \item Select colours that work well in black-and-white print.
    \item Use \textcolor{red}{one} signal colour if necessary.
    \item Avoid clutter, such as 3D-effects, diagram area borders, gridlines, etc.
    \item Keep text orientation horizontal.
\end{itemize}



\section{Equations} \label{equations}
General recommendations are:
\begin{itemize}
    \item Do not overload the text with formulae; consider placing detailed mathematical derivations in an appendix rather than in the main text.
    \item Provide explanation for each variable included in the formula.
    \item Number your equations; this is not necessary for equations written in-line with the text.
    \item Do not insert equations inside tables.
\end{itemize}

‘Travel distance is calculated as:
\begin{equation}
    S = v_{0} \cdot t + \frac{a \cdot t^{2}}{2}\label{equation:1}
\end{equation}
where $v_{0}$ is the initial speed, m/s; $t$ is the time elapsed, s; and $a$ is the acceleration, m/s\textsuperscript{2}.’



\section{Compulsory sections} \label{compulsory-sections}
The manuscript \emph{must} contain the following sections:
\begin{itemize}
    \item Author information
    \item CRediT contribution statement
    \item Declaration of competing interests
    \item Declaration of generative AI use
    \item Prior dissemination declaration
    \item Ethics statement
    \item Funding statement
    \item Data availability statement
    \item Code availability statement.
\end{itemize}

Additionally, the manuscript \emph{may} contain:

\begin{itemize}
    \item Acknowledgements.
\end{itemize}



\subsection*{Author information} \label{author-information}
The manuscript \emph{must} include a photo and a short professional biography (4--8 lines) for each of the authors. For example:

\includegraphics[width=0.98425in,height=0.98425in]{Author_1.png}

‘Name Surname received her PhD at the University of Sciences. Her research interests cover traffic safety, urban planning, and, recently, decision making and policy implementation within large state organizations. Since 2023, she acts as the head of the Virtual Reality lab at the University of Sciences.’



\subsection*{CRediT contribution statement} \label{credit-contribution-statement} 
All authors of a submitted manuscript \emph{must} state their contributions. The same applies even if the manuscript has a single author.

CRediT, Contributor Roles Taxonomy (\href{https://doi.org/10.3789/ansi.niso.z39.104-2022}{link}), is a high-level taxonomy that includes 14 roles typically played by the authors of a scientific paper. These include:

\begin{itemize}
    \item \textbf{Conceptualization:} ideas; formulation or evolution of overarching research goals and aims
    \item \textbf{Data curation:} management activities to annotate (produce metadata), scrub data and maintain research data (including software code, where it is necessary for interpreting the data itself) for initial use and later re-use
    \item \textbf{Formal analysis:} application of statistical, mathematical, computational, or other formal techniques to analyze or synthesize study data
    \item \textbf{Funding acquisition:} acquisition of the financial support for the project leading to this publication
    \item \textbf{Investigation:} conducting a research and investigation process, specifically performing the experiments, or data/evidence collection
    \item \textbf{Methodology:} development or design of methodology; creation of models
    \item \textbf{Project administration:} management and coordination responsibility for the research activity planning and execution
    \item \textbf{Resources:} provision of study materials, reagents, materials, patients, laboratory samples, animals, instrumentation, computing resources, or other analysis tools
    \item \textbf{Software:} programming, software development; designing computer programs; implementation of the computer code and supporting algorithms; testing of existing code components
    \item \textbf{Supervision:} oversight and leadership responsibility for the research activity planning and execution, including mentorship external to the core team
    \item \textbf{Validation:} verification, whether as a part of the activity or separate, of the overall replication/reproducibility of results/experiments and other research outputs
    \item \textbf{Visualization:} preparation, creation and/or presentation of the published work, specifically visualization/data presentation
    \item \textbf{Writing -- original draft:} preparation, creation and/or presentation of the published work, specifically writing the initial draft (including substantive translation)
    \item \textbf{Writing -- review \& editing:} preparation, creation and/or presentation of the published work by those from the original research group, specifically critical review, commentary or revision---including pre- or post-publication stages.
\end{itemize}

The role titles must be used as is, without any modifications.

For example:

‘\textbf{Name Surname:} Conceptualization, Funding acquisition, Methodology, Visualization, Writing -- original draft, Writing -- review \& editing. \textbf{Name Surname:} Supervision, Validation, Writing--review \& editing. \textbf{Name Surname:} Methodology, Supervision, Validation, Writing -- review \& editing.’



\subsection*{Acknowledgements} \label{acknowledgements}
The Acknowledgements section is common, but \emph{not} compulsory. It usually contains expressions of gratitude to people and organizations who helped with the research but do not qualify as co-authors. Typical examples of such contributions are:

\begin{itemize}
    \item field data collection
    \item access to equipment and facilities
    \item advice on statistical tools and methods
    \item feedback on early drafts
    \item helpful discussions
    \item mentorship
    \item permissions to use materials or datasets.
\end{itemize}

For example:

‘The authors would like to thank the Science Laboratory at the Important Research Institute for providing access to XTS-2351b molecular stabilizer. We are also grateful to Ms Biggest Expert for her valuable comments on the early draft of this manuscript.’


\subsection*{Declaration of competing interests} \label{declaration-of-competing-interests}
The manuscript \emph{must} include a declaration of competing interests. If the authors have no competing interests to declare, they should state this explicitly.

Competing interests may be financial (e.g. employment, collaboration, receipt of grants, patents held or pending) or non-financial (e.g. political, legal, or other involvements). A competing interest does not imply that the objectivity of the work has been compromised, but rather that it could be \emph{perceived} as such. As a rule of thumb, authors should disclose any relationships that, if revealed at a later stage, might cause embarrassment.

For example:

‘The authors report no competing interests.’

‘This work received in-kind support from Technology Ltd. The company has a commercial interest in the findings and intends to apply the results in the development of new products.’



\subsection*{Declaration of generative AI use} \label{declaration-of-generative-ai-use}
The authors \emph{must} state whether in preparation of the manuscript they used generative artificial intelligence (AI) or AI-assisted tools, and if so, specify the tool and for which tasks it was used.

For example:

‘The authors declare that no generative AI was used in preparing this work.’

‘During the preparation of this work the authors used [tool, version] in order to [reason]. The output was reviewed and revised by the authors who take full responsibility for the contents of the publication.’



\subsection*{Prior dissemination declaration} \label{prior-dissemination-declaration}
The authors \emph{must} state whether the current research has been disseminated earlier (e.g. as a preprint, conference presentation or poster, report, academic theses, etc.).

For example:

‘This manuscript presents original work that has not been previously published or disseminated in any form.’

‘An earlier version of this work was presented as [format] at [conference name], held in [location], on [date]: [link]’.

‘An extended version of this work was also published as [report type], [report number]: [link].’

‘The pre-review version of this manuscript was included in [thesis type] by [author], defended on [date] at [university, country]: [link].’

‘The pre-review version of this manuscript was published as a preprint on [date] at [platform]: [link].’



\subsection*{Ethics statement} \label{ethics-statement}
A submitted manuscript \emph{must} include the ethics statement. Usually, it will contain a reference to the ethical evaluation of the research plan performed by a relevant authority (specifying the authority and the decision identifier). If a study was exempted from requiring an ethical approval, the reasons for and the procedure for arriving at such conclusion must be provided.

For example:

‘The methods for data collection, analysis, and preservation in the present study have been approved by [authority], [decision identifier].’

‘This research utilized only official accident statistics data provided by [source], [link]. The data is available in aggregated form only and contain no personal records or any sensitive details. Therefore, no ethical evaluation was applied for.’



\subsection*{Funding statement} \label{funding-statement}
The authors \emph{must} state which funding agencies, and through which grants, financed the research described in the manuscript. If no external funding was received, it should be clearly stated so.

If a funder directly affected some of the decisions related to this research, this must be clearly described. 

For example:

‘This research was funded by the [agency], grant [grant identifier]. The funder participated in defining the initial scope of the study and identifying priority research questions. The funder had no role in data analysis and the interpretation of results, and all authors retained full autonomy over the writing of the manuscript.’

‘No external funding was used in this research.’



\subsection*{Data availability statement} \label{data-availability-statement}
The manuscript \emph{must} include a statement specifying how the data underlying the study can be accessed, with a justified explanation where the data cannot be made accessible.

The  \emph{TSR} recognizes that not all research data can be made public. Ethical restrictions, personal-data protection, confidentiality agreements, commercial interests, and other legitimate constraints sometimes make sharing impossible. Our aim is not to impose openness where it would be inappropriate, but to make transparency and sharing the norm whenever circumstances allow.

However, whenever the data can legitimately be shared, authors are expected to make them openly available by the time of publication in an open-access repository (e.g. Zenodo, \href{https://www.zenodo.org}{www.\hspace{0pt}zenodo.\hspace{0pt}org}). The statement ‘Data available on request’ is \emph{not acceptable}.

It remains the authors' duty to share the data responsibly. Responsible data sharing aims to maximize transparency and scientific value while ensuring that no information is disclosed that could compromise the privacy, dignity, or safety of the individuals involved. This is achieved through a combination of ethical, technical, and procedural safeguards such as:

\begin{itemize}
    \item obtaining of informed consents
    \item removing or transforming identifiable information
    \item applying data-minimization principles
    \item using controlled-access repositories
    \item implementing legal and contractual protections
    \item providing transparent metadata and documentation so that methods and decisions are visible even when raw data cannot be released.
\end{itemize}

Before publishing, ensure that all data are clearly organized with descriptive filenames, documented variables, and a structure that allows others to understand and reuse the dataset without additional explanation. State clearly the level of access and the specific licence applied to their dataset.

The recommended statement template is:

‘The data supporting the findings of this study are available at [repository name], [DOI], licensed under [license]. The dataset includes [contents]. Restrictions: [if any, justify].’

For example:

‘The data supporting the findings of this study are available at Zenodo, \href{https://doi.org/10.5281/zenodo.19353202}{https://\hspace{0pt}doi.org/\hspace{0pt}10.5281/\hspace{0pt}zenodo.\hspace{0pt}19353202}, shared under the \href{https://creativecommons.org/licenses/by/4.0/}{Creative Commons Attribution 4.0 International} licence, which permits reuse and distribution provided proper attribution is given.’

‘Due to constraints specified in the ethics approval and the participant consent procedure, the datasets generated during this study cannot be publicly shared. However, detailed metadata and documentation describing the data collection, variables, and analytical procedures are available at Zenodo, \href{https://doi.org/10.5281/zenodo.19353202}{https://\hspace{0pt}doi.org/\hspace{0pt}10.5281/\hspace{0pt}zenodo.\hspace{0pt}19353202}, shared under the \href{https://creativecommons.org/licenses/by/4.0/}{Creative Commons Attribution 4.0 International} licence.’

Alternatively, when there are no data to share:

‘Data sharing is not applicable, as no datasets were generated or analysed for this study.’



\subsection*{Code availability statement} \label{code-availability-statement}
The manuscript \emph{must} include a statement specifying the availability of the code underlying the study, with a justified explanation where the code cannot be made accessible.

Whenever the code can legitimately be shared, authors are expected to make it openly available by the time of publication in an open-access repository (e.g. Zenodo, \href{https://www.zenodo.org}{www.\hspace{0pt}zenodo.\hspace{0pt}org}). The statement ‘Code available on request’ is \emph{not acceptable}.

The code may be published alongside the data or released separately. Any custom scripts, analysis code, or computational workflows used in the study should be organized, documented, and runnable. Any confidential information, passwords, or locally specific paths must be removed before publication. The specific licence under which the code is released must be clearly stated.

If proprietary code is used, clearly disclose its nature (identify the software or package by name and version, and describe the specific functions or modules used). Justify non‑sharing by referring to licensing restrictions, intellectual property agreements, or third‑party ownership. If relevant, provide pseudocode, workflow diagrams, or algorithmic descriptions to support transparency and reproducibility.

The recommended statement template is:

‘The source code supporting the findings of this study is available at [repository name], [DOI], licensed under [license]. The source includes [contents]. The code is designed to run in [software/language] version [version number], using the following packages and dependencies: [list]. Restrictions: [if any, justify].’

For example:

‘The source code supporting the findings of this study is available at Zenodo, \href{https://doi.org/10.5281/zenodo.19353576}{https://\hspace{0pt}doi.org/\hspace{0pt}10.5281/\hspace{0pt}zenodo.\hspace{0pt}19353576}, shared under the \href{https://opensource.org/licenses/MIT}{MIT licence}. The source includes data-processing scripts, statistical analysis routines, and figure-generation code. The code was developed in R version 4.3.2, using the packages tidyverse (2.0.0), lme4 (1.1-35), and ggplot2 (3.4.4).’

‘The code underlying the analyses in this study cannot be made publicly available because it is based on proprietary software components that are subject to licensing restrictions. Pseudocode and workflow diagrams are available at Zenodo, \href{https://doi.org/10.5281/zenodo.19353576}{https://\hspace{0pt}doi.org/\hspace{0pt}10.5281/\hspace{0pt}zenodo.\hspace{0pt}19353576}, shared under the \href{https://creativecommons.org/licenses/by/4.0/}{Creative Commons Attribution 4.0 International} licence.’

‘The code is available from the authors on request.’ [This formulation will soon no longer be accepted; if the code is available, it should be made accessible through a public repository.]

Alternatively, when there is no code to share:

‘Code sharing is not applicable, as no custom code or scripts were developed or used for this study.’



\section*{References}
\emph{Traffic Safety Research} applies the APA referencing style, 7th edition (\href{https://apastyle.apa.org/style-grammar-guidelines/references}{link}).

The URL or DOI identifier should always be provided when available. Note that the DOI must be a full hyperlink including ‘\href{https://doi.org/}{https://\hspace{0pt}doi.org/…}’.



\subsection*{In-text citations} \label{in-text-reference-examples}
Under \texttt{biblatex} package, use the command \verb|\textcite{}| for Author (Year) and \verb|\cite{}| for (Author, Year) citations. For example:

‘As shown by \textcite{belin_2012}, \textcite{Godthelp_2023}, and \textcite{Gettman_2008}, it is important to account for confounding factors.’

‘Many studies point out the importance of accounting for confounding factors (\cite{Elvik_2009}, \cite{Guttinger_1982}, \cite{Edvardsson_Bjornberg_2023}, \cite{Hauer_2015}, \cite{Hansson_2023}, \cite{Hyden_1987}, \cite{FHWA_n_d}).’



\subsection*{Reference list}
\subsubsection*{Journal article} 
\printbibliography[type=article, heading=none]



\subsubsection*{Report} 
\printbibliography[type=report, heading=none]



\subsubsection*{Conference paper/presentation} 
\printbibliography[type=inproceedings, heading=none]



\subsubsection*{Book} 
\printbibliography[type=book, heading=none]



\subsubsection*{Book section} 
\printbibliography[type=inbook, heading=none]



\subsubsection*{Thesis} 
\printbibliography[type=thesis, heading=none]



\subsubsection*{Web page} 
\printbibliography[type=online, heading=none]



\end{document}