-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.tex
1925 lines (1418 loc) · 65.6 KB
/
index.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
% Options for packages loaded elsewhere
\PassOptionsToPackage{unicode}{hyperref}
\PassOptionsToPackage{hyphens}{url}
\PassOptionsToPackage{dvipsnames,svgnames,x11names}{xcolor}
%
\documentclass[
letterpaper,
DIV=11,
numbers=noendperiod]{scrreprt}
\usepackage{amsmath,amssymb}
\usepackage{iftex}
\ifPDFTeX
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{textcomp} % provide euro and other symbols
\else % if luatex or xetex
\usepackage{unicode-math}
\defaultfontfeatures{Scale=MatchLowercase}
\defaultfontfeatures[\rmfamily]{Ligatures=TeX,Scale=1}
\fi
\usepackage{lmodern}
\ifPDFTeX\else
% xetex/luatex font selection
\fi
% Use upquote if available, for straight quotes in verbatim environments
\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
\IfFileExists{microtype.sty}{% use microtype if available
\usepackage[]{microtype}
\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
}{}
\makeatletter
\@ifundefined{KOMAClassName}{% if non-KOMA class
\IfFileExists{parskip.sty}{%
\usepackage{parskip}
}{% else
\setlength{\parindent}{0pt}
\setlength{\parskip}{6pt plus 2pt minus 1pt}}
}{% if KOMA class
\KOMAoptions{parskip=half}}
\makeatother
\usepackage{xcolor}
\setlength{\emergencystretch}{3em} % prevent overfull lines
\setcounter{secnumdepth}{5}
% Make \paragraph and \subparagraph free-standing
\ifx\paragraph\undefined\else
\let\oldparagraph\paragraph
\renewcommand{\paragraph}[1]{\oldparagraph{#1}\mbox{}}
\fi
\ifx\subparagraph\undefined\else
\let\oldsubparagraph\subparagraph
\renewcommand{\subparagraph}[1]{\oldsubparagraph{#1}\mbox{}}
\fi
\providecommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}\usepackage{longtable,booktabs,array}
\usepackage{calc} % for calculating minipage widths
% Correct order of tables after \paragraph or \subparagraph
\usepackage{etoolbox}
\makeatletter
\patchcmd\longtable{\par}{\if@noskipsec\mbox{}\fi\par}{}{}
\makeatother
% Allow footnotes in longtable head/foot
\IfFileExists{footnotehyper.sty}{\usepackage{footnotehyper}}{\usepackage{footnote}}
\makesavenoteenv{longtable}
\usepackage{graphicx}
\makeatletter
\def\maxwidth{\ifdim\Gin@nat@width>\linewidth\linewidth\else\Gin@nat@width\fi}
\def\maxheight{\ifdim\Gin@nat@height>\textheight\textheight\else\Gin@nat@height\fi}
\makeatother
% Scale images if necessary, so that they will not overflow the page
% margins by default, and it is still possible to overwrite the defaults
% using explicit options in \includegraphics[width, height, ...]{}
\setkeys{Gin}{width=\maxwidth,height=\maxheight,keepaspectratio}
% Set default figure placement to htbp
\makeatletter
\def\fps@figure{htbp}
\makeatother
% definitions for citeproc citations
\NewDocumentCommand\citeproctext{}{}
\NewDocumentCommand\citeproc{mm}{%
\begingroup\def\citeproctext{#2}\cite{#1}\endgroup}
\makeatletter
% allow citations to break across lines
\let\@cite@ofmt\@firstofone
% avoid brackets around text for \cite:
\def\@biblabel#1{}
\def\@cite#1#2{{#1\if@tempswa , #2\fi}}
\makeatother
\newlength{\cslhangindent}
\setlength{\cslhangindent}{1.5em}
\newlength{\csllabelwidth}
\setlength{\csllabelwidth}{3em}
\newenvironment{CSLReferences}[2] % #1 hanging-indent, #2 entry-spacing
{\begin{list}{}{%
\setlength{\itemindent}{0pt}
\setlength{\leftmargin}{0pt}
\setlength{\parsep}{0pt}
% turn on hanging indent if param 1 is 1
\ifodd #1
\setlength{\leftmargin}{\cslhangindent}
\setlength{\itemindent}{-1\cslhangindent}
\fi
% set entry spacing
\setlength{\itemsep}{#2\baselineskip}}}
{\end{list}}
\usepackage{calc}
\newcommand{\CSLBlock}[1]{\hfill\break\parbox[t]{\linewidth}{\strut\ignorespaces#1\strut}}
\newcommand{\CSLLeftMargin}[1]{\parbox[t]{\csllabelwidth}{\strut#1\strut}}
\newcommand{\CSLRightInline}[1]{\parbox[t]{\linewidth - \csllabelwidth}{\strut#1\strut}}
\newcommand{\CSLIndent}[1]{\hspace{\cslhangindent}#1}
\KOMAoption{captions}{tableheading}
\makeatletter
\@ifpackageloaded{tcolorbox}{}{\usepackage[skins,breakable]{tcolorbox}}
\@ifpackageloaded{fontawesome5}{}{\usepackage{fontawesome5}}
\definecolor{quarto-callout-color}{HTML}{909090}
\definecolor{quarto-callout-note-color}{HTML}{0758E5}
\definecolor{quarto-callout-important-color}{HTML}{CC1914}
\definecolor{quarto-callout-warning-color}{HTML}{EB9113}
\definecolor{quarto-callout-tip-color}{HTML}{00A047}
\definecolor{quarto-callout-caution-color}{HTML}{FC5300}
\definecolor{quarto-callout-color-frame}{HTML}{acacac}
\definecolor{quarto-callout-note-color-frame}{HTML}{4582ec}
\definecolor{quarto-callout-important-color-frame}{HTML}{d9534f}
\definecolor{quarto-callout-warning-color-frame}{HTML}{f0ad4e}
\definecolor{quarto-callout-tip-color-frame}{HTML}{02b875}
\definecolor{quarto-callout-caution-color-frame}{HTML}{fd7e14}
\makeatother
\makeatletter
\@ifpackageloaded{bookmark}{}{\usepackage{bookmark}}
\makeatother
\makeatletter
\@ifpackageloaded{caption}{}{\usepackage{caption}}
\AtBeginDocument{%
\ifdefined\contentsname
\renewcommand*\contentsname{Table of contents}
\else
\newcommand\contentsname{Table of contents}
\fi
\ifdefined\listfigurename
\renewcommand*\listfigurename{List of Figures}
\else
\newcommand\listfigurename{List of Figures}
\fi
\ifdefined\listtablename
\renewcommand*\listtablename{List of Tables}
\else
\newcommand\listtablename{List of Tables}
\fi
\ifdefined\figurename
\renewcommand*\figurename{Figure}
\else
\newcommand\figurename{Figure}
\fi
\ifdefined\tablename
\renewcommand*\tablename{Table}
\else
\newcommand\tablename{Table}
\fi
}
\@ifpackageloaded{float}{}{\usepackage{float}}
\floatstyle{ruled}
\@ifundefined{c@chapter}{\newfloat{codelisting}{h}{lop}}{\newfloat{codelisting}{h}{lop}[chapter]}
\floatname{codelisting}{Listing}
\newcommand*\listoflistings{\listof{codelisting}{List of Listings}}
\makeatother
\makeatletter
\makeatother
\makeatletter
\@ifpackageloaded{caption}{}{\usepackage{caption}}
\@ifpackageloaded{subcaption}{}{\usepackage{subcaption}}
\makeatother
\ifLuaTeX
\usepackage{selnolig} % disable illegal ligatures
\fi
\usepackage{bookmark}
\IfFileExists{xurl.sty}{\usepackage{xurl}}{} % add URL line breaks if available
\urlstyle{same} % disable monospaced font for URLs
\hypersetup{
pdftitle={Flow mapping with Arabesque 2},
pdfauthor={Françoise Bahoken},
colorlinks=true,
linkcolor={blue},
filecolor={Maroon},
citecolor={Blue},
urlcolor={Blue},
pdfcreator={LaTeX via pandoc}}
\title{Flow mapping with Arabesque 2}
\author{Françoise Bahoken}
\date{2024-06-04}
\begin{document}
\maketitle
\renewcommand*\contentsname{Table of contents}
{
\hypersetup{linkcolor=}
\setcounter{tocdepth}{2}
\tableofcontents
}
\bookmarksetup{startatroot}
\chapter*{Welcome}\label{welcome}
\addcontentsline{toc}{chapter}{Welcome}
\markboth{Welcome}{Welcome}
This is the \textbf{\emph{Flow mapping with Arabesque 2}} online home
book.
\emph{Arabesque} is part of the Free and Open Source Software for
Geospatial (FOSS4G) movement. It is a web application dedicated to flow
mapping from origin-destination matrices and spatial networks datasets.
This books presents the functionnalities and how \emph{Arabesque} 2 can
be used to draw flowmaps.
It will be progressively updated following \emph{Arabesque} 2 current
development.
\begin{itemize}
\tightlist
\item
On ligne version of \emph{Arabesque} can be accessed here:
\href{https://arabesque.univ-eiffel.fr/}{arabesque.univ-eiffel.fr}
\end{itemize}
\begin{itemize}
\tightlist
\item
The development version (the most complete) can be accessed here:
\href{https://tonhauck.github.io/dev-arabesque/}{./dev-arabesque}
\end{itemize}
This book is reproducible and generated in R with Quarto.\\
Feel free to help us make it better and report any issue on
\href{https://github.com/gflowiz/arabesque}{GitHub}.
\href{http://creativecommons.org/licenses/by-nc-sa/4.0/}{\includegraphics{index_files/mediabag/88x31.png}}\\
This work by the geographic flow vizualisation research team is licensed
under a
\href{http://creativecommons.org/licenses/by-nc-sa/4.0/}{Creative
Commons Attribution-NonCommercial-ShareAlike 4.0 International License}.
\href{https://github.com/gflowiz/arabesque2-doc}{\includegraphics[width=0.41667in,height=\textheight]{images/github.png}}
View source
\bookmarksetup{startatroot}
\chapter{Preface}\label{preface}
This Quarto book contains the online documentation of the second version
of \href{arabesque.univ-eiffel.fr}{\emph{Arabesque}}, a web application
for thematic flow mapping created within the geographic flow
vizualisation research program
(\href{https://geoflowiz.hypotheses.org/accueil/abstract}{gflowiz})
funded by \href{www.univ-eiffel.fr}{Univ. Gustave Eiffel} (former
IFSTTAR).
\hfill\break
The gflowiz project was originally led by Françoise Bahoken and
co-directed by Étienne Côme (Univ. Gustave Eiffel), with the scientific
collaboration of Laurent Jégou (Univ. Toulouse 2 Jean Jaurès). The main
developer of the first version of \emph{Arabesque} was Thomas Bapaume
(ESIEE student engineer), then Paul Fabre (UGE/IGN student
geographer/geomatician) ; Tony Hauck (freelance geomatician) is
developping the \emph{Arabesque2} version. Other contributors include
for the conception \& design of the app : Marion Maisonobe and Grégoire
le Campion (CNRS), and t for the Arabesque 1 documentation : Nicolas
Roelandt (Univ. Gustave Eiffel).
\emph{Arabesque} is an innovative cartographic application that meets
the contemporary challenges of spatial networks geovisualisation.
\section{Challenges}\label{challenges}
The analysis of the dynamics of urban areas or metropolises in one hand,
the delimitation of their functional areas and the spatio-temporal
comparison of their patterns in the other hand, are often limited by two
categories of problems inherent in data and tools.\\
\strut \\
The lack of open origin-destination (OD) data sets depicting territorial
interactions and interrelations limited the possibility of empirical
analysis. Similarly, the lack of dedicated geovisualization and
cartographic analysis tools means that many images of visual and
analytical interest are no longer part of the current cartographic
landscape. In addition to these specific problems regarding online OD
data, it is important to focus attention on the current possibilities
offered by online possibilities of OD cartography.
The current range of possibilities for exploring flows and networks
datasets on the geoweb is symptomatic of the ongoing enthusiasm of a
growing interdisciplinary community. While for a long time the efforts
were limited to direct visualisation alone, applications specifically
dedicated to flows have recently come on line.
\section{State of the Art}\label{state-of-the-art}
Three development approaches seem to be coexisting. The first one seems
to be dedicated to the development of large volumes of data in a digital
cartographic form, as is the case with the United Nations
\href{https://comtrade.un.org/}{Comtrade} for example. The second
approach consists of applications for the visual geographical
exploration of one's own OD datasets as in
\href{https://flowmap.blue/}{flowmap.blue}, for example. Academic
applications offer different graphical models allowing co-visualization,
such as the
\href{https://networkcube.github.io/vistorian/index.html}{Vistorian}
(Serrano Molinero \& al., 2017) and
\href{https://www.irit.fr/netscity/}{Netscity} (Maisonobe \& al., 2019).
The third approach is specific to heavy online thematic mapping software
infrastructures such as \hyperref[0]{Magrit} or \hyperref[0]{Kepler} in
response to the shortcomings of current editors regarding flow mapping.
It is interesting to note that all these solutions are being developed
in line with the growing practice of open-source development with a view
to reproducibility (Giraud, Lambert, 2017).
Few applications, however, appear to be fully aligned with the
``visualization mapping'' paradigm as defined by A. Mac Eachren (2004).
Indeed, efforts still seem to be focused more on displaying layers and
simply exploring them. Existing tools still do little to combine within
a single interface the three pillars of cartographic representation:
(geo)visualization and the processing of statistical and geographic
data.
In this context, \emph{Arabesque's} objectives are as follows.
\section{Objectives}\label{objectives}
\emph{Arabesque's} ambition is to meet the high demand for analysis of
one's own flow dataset in a free, open source and ergonomic way - this
need corresponding to the main result of our survey conducted in 2018.\\
\strut \\
\emph{Arabesque} is part of the french Lemaire Law for a digital
republic. It falls under the general objective of increasing
understanding of the geographical determinants of the spatial mobility
of goods, people and so on.\\
\strut \\
\emph{Arabesque} aims to respond to the need to visualize the results of
fundamental or applied research within theoretical and methodological
development frameworks that can be considered both transverse to several
subjects (population, habitat, environment, transport, i.e.) and
interdisciplinary by nature (geography, demography, environment,
geomatics, engineering sciences, human and social sciences, i.e.). These
subjects also contribute to the societal challenges linked to the rise
of the digital society, which they help to address.
From a scientific point of view, \emph{Arabesque} aims to innovate in
the handling of flow and network data currently available on the geoweb
(Bahoken et al, 2020). This is why it is part of the Mac Eachren (2005)
new paradigm of ``visualization mapping''.\\
\emph{Arabesque} combines in the same environment geo-visualization and
geographic and statistical information processing devices - initially
for descriptive purposes. On the other hand, it enables the processing
of complex relational datasets, which can be both voluminous and display
different dimensions of spatial mobilities (several thematic categories
and/or temporalities).\\
Particular attention is paid to rendering, both in terms of drawing and
the cartographic semiology of linear features. The desire to improve the
quality of the images of flows produced should lead to the development
of a sensible approach to the geo-visualization of mobilities and
spatial interactions.
Françoise Bahoken and Étienne Côme
Paris, Mai 2024.
\textbf{Quoted references:}
Keim D., Andrienko G., Fekete J.-D., Görg C., Kohlhammer J., Melançon G.
(2008), \emph{Visual Analytics: Definition, Process, and Challenges},
In: Kerren A. \& al.~(Eds.): Information Visualization, Springer-Verlag
Berlin Heidelberg, LNCS 4950, pp.~154--175.
Mac Eachren A. (2005), \emph{How Maps Work. Representation,
Visualization, and Design, New-York, The Guildford Press.}
Maisonobe M., Jégou L., Yakimovich N., Cabanac G. (2019), NETSCITY: a
geospatial application to analyse and map world scale production and
collaboration data between cities, \emph{International Conference on
Scientometrics and Informetrics (ISSI 2019)}, sep. 2019, Rome, Italy,
\href{https://hal.science/hal-02301035}{〈hal-02301035〉}
Giraud T., Lambert N. (2017), Reproducible cartography, in:
\emph{Advances in Cartography and GISsciences}, International
Cartographic Conference, ICACI'2017, Springer, pp.173-183.
Serrano Molinero V., Bach B., Plaisant C., Dufournaud N.,Fekete J.-D.
(2017), Understanding the Use of The Vistorian: Complementing Logs with
Context Mini-Questionnaires, \emph{Visualization for the Digital
Humanities}, Oct.~2017, Phoenix, United States.
\href{https://inria.hal.science/hal-01650259}{⟨hal-01650259⟩}.
\bookmarksetup{startatroot}
\chapter{Introduction}\label{introduction}
\emph{Arabesque} is dedicated to origin-destination flow and network
datasets. This second version enables data to be explored, filtered,
geovisualised and represented. \emph{Arabesque} lets you create flow
maps from your own datasets, using a web browser running \emph{Mozilla},
\emph{Chrome} or \emph{Brave}. It is based on current technological
possibilities, in particular those offered by the new web visualization
and mapping libraries (\emph{openlayers, d3, OSM, Turf,
NaturalEarthData}).
\textbf{General keywords}: cartography, geovisualisation, matrice,
flows, networks
\section{Main steps}\label{main-steps}
There are 5 main stages in creating a flowmap with \emph{Arabesque}:
\begin{enumerate}
\def\labelenumi{\arabic{enumi}.}
\tightlist
\item
Importing your flowdata sets (at least for weighted links)
\item
Processing flow data (creation of indicators)
\item
Data exploration and configuration
\begin{enumerate}
\def\labelenumii{\arabic{enumii}.}
\tightlist
\item
Numerical filtering of data
\item
Dealing with geography layers or tiles
\end{enumerate}
\item
Graphical symbolization (geometry and semiology)
\item
Exporting and saving the \emph{Arabesque} workspace
\end{enumerate}
\bookmarksetup{startatroot}
\chapter{Summary}\label{summary}
This is the \textbf{\emph{Flow mapping with Arabesque}} online home
book, a free and open Source Software web application funded by the
french Université Gustave Eiffel.
Arabesque is dedicated to flow and network mapping, from
origin-destination simple or complexes matrices. Arabesques allows users
to filter flow data sets (nodes, links and flow values), to play with
geographic context (add tiles), reprojecting geography and to
parameterise the semiology of the drawings.
Built in javascript and HTML 5, Arabesque provides a full toolset to
explore, filter and geovisualize your Origin-Destination matrices. It
allows also to build clearer and understandable flow maps that respect
the principles of contemporary cartographic semiology.
Arabesque 2 is currently under development. See
\href{https://github.com/gflowiz/arabesque-dev}{arabesque-dev github
repository}.
\textbf{Contacts} :
\href{mailto:[email protected],[email protected]}{Françoise
BAHOKEN \& Étienne CÔME}
\bookmarksetup{startatroot}
\chapter{Arabesque' interface}\label{arabesque-interface}
Arabesque interface is accessible via its general home page.
\section{Arabesque Home page}\label{arabesque-home-page}
\includegraphics{images/Arabesque_homepage.png}
Through this home page, you can:
\begin{itemize}
\tightlist
\item
Start a new flowmap by loading at least your flow data. See Data
importation chapter.
\end{itemize}
\includegraphics{images/Arabesque_homepage_newmap.png}
\begin{itemize}
\item
Load a previous map via the Arabesque workspace
\includegraphics{images/Arabesque_homepage_savemap.png}
\item
Load the example of school mobility flows (mobscol data set). See
Examples for more information.
\includegraphics{images/Arabesque_homepage_sample.png}
\end{itemize}
\section{General structure}\label{general-structure}
\subsection{The main banner}\label{the-main-banner}
\includegraphics{images/main_banner.png}
\includegraphics{images/Buton_home.png} Return to
\href{https://arabesque.univ-eiffel.fr/}{the home page} to start a new
view.
\includegraphics{images/main_doc.png} Access to documentation
\includegraphics{images/main_about.png} Access to credits
\href{https://www.univ-gustave-eiffel.fr/}{\includegraphics{images/main_univ-gustave-eiffel.PNG}}
Access to documentationgo to the Gustave Eiffel University home page
\href{https://geoflowiz.hypotheses.org/accueil/le-projet-gflowiz}{\includegraphics{images/main_gflowiz_program.PNG}}
go to the Geographic flow visualisation programme home page
\href{https://github.com/gflowiz}{\includegraphics{images/main_github-gflowiz.png}}
go go to the home page of the
\href{https://github.com/gflowiz/arabesque-dev}{github/com/glowiz}
\subsection{The three panels}\label{the-three-panels}
Arabesque interface is composed of three panels.
\begin{itemize}
\tightlist
\item
The \textbf{central panel} is for displaying the map - centered in
France here.
\end{itemize}
The two side panels are for playing with information:
\begin{itemize}
\item
The \textbf{left panel} is for dealing with geometries and
geographical layers.
\item
The \textbf{right panel} is for fitering the flow data set. Here, only
the flows up to
\end{itemize}
\includegraphics{images/panels_arabesque.png}
\section{The central panel}\label{the-central-panel}
The central part of Arabesque corresponds to the \textbf{map view}. It
results from the choice of the layers to be displayed (from the left
panel) and the filtering of the values of the links and nodes (from the
right panel).
This central panel also presents different buttons allowing the
implementation of primary actions.
\subsection{Primary actions with
butons}\label{primary-actions-with-butons}
The white page of Arabesque is decorated with blue action buttons.
\includegraphics{images/central_panel_clear.png} \textbf{Details of the
different buttons}
\includegraphics{images/Buton_in_out.png} Successively zoom in/out - the
same way as with the mouse wheel.
\includegraphics{images/Buton_sauv.png} Save the project in .ZIP for
later use.
\includegraphics{images/Buton_export.png} Export the map in .PDF vector
format including legends in the bottom of the page.
\includegraphics{images/Buton_leg.png} Show/hide the legend.
\subsection{Primary legend}\label{primary-legend}
A legend is automatically generated for each map for nodes and links
plot.
\includegraphics{images/center_legend.png}
The symbolization elements (size, color and opacity) of the nodes and
links are included in the legend. Here (for a default map), it is the
volume of flows and the degree of places that are represented.
\section{The geographic panel}\label{the-geographic-panel}
The left panel is to \textbf{design the map}:
\begin{itemize}
\item
dealing with the map background as the geographical/geometrical
layers: Arabesque reference layer, Tile Layer or your own geojson
layers
\item
customize the \emph{design}/style of the nodes and links features map.
\end{itemize}
The management of geographic information is composed of three
sub-sections:
\begin{figure}[H]
{\centering \includegraphics{images/geom_panel.png}
}
\caption{General geographic information management panel}
\end{figure}%
Actions on the \textbf{background of the map} are for changing
projections of the current map and/or to add other layers : remote or
personal one.
See \href{./Design-map-background.html}{Design map background} section.
Actions on the design/style is to set the parameters for the geometry of
the lines/arrows and their semiology
See \href{./Design-flowmap-signs.html}{Design flowmap signs} section.
\subsection{The geographic layer
manager}\label{the-geographic-layer-manager}
In practice, a map is composed by several layer such as the bounding
boxes, the graticules, the countries of land. All can be loaded in the
map design background section Layers.
They then appear in the layer manager sub-panel, one above the other as
shown below.
\includegraphics{images/Types_layers.png}
The present layers are all available on the map - but not necessarily
all of them are visible.
The layers on the view are positioned in an order that affects their
visibility. The top layer will be visible in the foreground.
\subsection{Layer rearrangement}\label{layer-rearrangement}
The drawing of the different layers and their objects can be finely
parameterized in \emph{Arabesque}, in order to take into account the
possible complexity of the information (density of the matrix) which
requires a particular management of the superimpositions and the
arrangements of the layers of links and nodes.
In the example below, the largest links are placed in the foregroundby
default, while the largest circles are not. After their rearrangement,
the largest links are background and their color intensity has been
changed (See Chapter \href{./Design-flowmap-signs.html}{Designing
flowmap signs}).
\emph{EXAMPLE:} rearrangement of nodes and links.
\includegraphics{images/Dispositions.png}
The position of the layers above and below (foreground/lowerground) can
be modified by a simple drag and drop.
\includegraphics{images/Layout_dragdrop.png}
\begin{quote}
\textbf{\emph{Do it yourself !}}:
-- Click on the link layer and hold it down;
-- Drag/drop the link layer and place it in the foreground;
-- Release the layer;
-- Repeat the same operation with the node layer if necessary.
\end{quote}
After that, it can be seen that the layer of links has just been brought
to the forefront.
\section{The statistical panel}\label{the-statistical-panel}
The \textbf{right panel} is for playing with the flow data sets : the
nodes and/or links in order to \textbf{filter the map} with the Add
filter button.
\includegraphics{images/Add_filter.PNG}
The statistics panel describes also the share (as a percentage) of flow
information that is represented in the central view, before/after the
application of a filter.
\includegraphics{images/Filter_statistics.png}
\begin{quote}
\textbf{\emph{Interpretation:}}
-- for links: 1.3973 links are depicted on the map, i.e.~53.01\% of the
total number of links, which corresponds to a density (or matrix fill
rate) of 53.01\%. These links represent 49.31\% of the total
interaction.
-- for nodes: 100\% of nodes are represented (here N=100 nodes)
\end{quote}
The filters applied are displayed in the second part of the panel,
depending on the type of data (continuous, categorical, etc.). See
\includegraphics{images/icon_links_filtering.png} Filter on a link
attribute
\includegraphics{images/icon_nodes_filtering.png} Filter on a node
attribute
See filtering flow data section.
\bookmarksetup{startatroot}
\chapter{Data importation}\label{data-importation}
Arabesque also allows you to import your own data sets via the home
page, in order to create a new map.
At least a link/flow origin-destination data file is required,
formatting with three colums. A node file is also required for the
geolocalisation of the origin and destination places.
In Arabesque 2, you have to declare or to import your nodes firstly.
\includegraphics{images/Arabesque_homepage_newmap.png}
For this tutorial, we will use for example the historical trade flows
listed in the mobscol file. For more informations about this dataset see
in arabesque-examples.
\section{Nodes importation}\label{nodes-importation}
If your nodes are specific, see
\hyperref[custom-localisation-file]{Custom localisation file}, otherwise
you can use predefined locations with
\hyperref[standard-localisation-codes]{Standard localisation codes}.
\subsection{Standard localisation
codes}\label{standard-localisation-codes}
\begin{center}
\includegraphics{images/Nodes_import_standard.PNG}
\end{center}
Arabesque provides a list of codes identifying the most common spatial
units at different geographical scales, at global, at European or at a
national level.
\includegraphics{images/Preset.PNG}
At global level, for example, different grids are available (countries,
towns, ports, etc.).
\includegraphics{images/Preset_world_countries.png}
The choice of the world country level, for example, then leads to the
identification of the type of identifier code: ISO2, ISO3, etc.
\includegraphics{images/Preset_world_countries_iso.png}
Once the type of identifier code has been selected (e.g.~ISO2), the link
file must be chosen.
\begin{center}
\includegraphics{images/Flow_import.PNG}
\end{center}
\subsection{Custom localisation file}\label{custom-localisation-file}
If you have custom nodes data associated with your ODs, you can load the
corresponding files by selecting the custom button.
\begin{center}
\includegraphics{images/Nodes_import_custom.PNG}
\end{center}
Then you have to browse to pick a .CSV or a GEOJSON file.
The .CSV file must be in long format, and have separator : , and decimal
: .
See example below.
\begin{quote}
Example: the SAGEO\_RIcardo\_nodes.CSV file
\end{quote}
\includegraphics{images/Example_RICarto_nodes.PNG}
The most important here are the column `lat' (Y) and `long' (X) which
will be used to geolocate the origin and the destination places, then
the column `ID'
Once you have identified these three columns (ID, lat, long), you can
import the nodes.
\begin{center}
\includegraphics{images/Nodes_custom_import.PNG}
\end{center}
If you do not have a file for the geometry, you can use the codes
identifying the reference data (e.g.~INSEE codes of the French communes,
ISO codes of the countries), to automatically geolocate your nodes. See
Preset.
\section{Flow/links importation}\label{flowlinks-importation}
After loading the nodes files, you have to browse your directories to
upload your origin-destination matrix.
The flow/links file must be in \textbf{.CSV (separator : , and decimal :
.}) in \textbf{long format}.
It must contain at least 3 columns : the ID of the place of origin, the
ID of the place of destination locations and the flow values.
\subsection{Unique flow OD matrices}\label{unique-flow-od-matrices}
Unique OD matrices have a unique value for each pair of locations - this
makes them different from complex matrices {[}See
\hyperref[complex-od-matrices]{Complex OD matrices}{]}.
See example below.
\begin{quote}
Example: the Mobscol origin-destination .CSV file. Simple matrice with 3
columns.
\includegraphics{images/Example_mobscol_ODsimple_CSV.PNG}
\end{quote}
The ID of the place of origin is ``CODE\_DEP''.
The ID of the place of destination is ``DEP\_ETUD''
The flow value is ``flow'' or is ``count''.
Once the origin and destination IDs have been identified, they need to
be declared in Arabesque for importing flows.
\begin{center}
\includegraphics{images/Flowdata_import_simple.png}
\end{center}
If the matrix is complex (as in that example), you have to choose a
method for aggregating the links when importing. {[}See
\hyperref[complex-od-matrices]{Complex OD matrices}{]}
\subsection{Complex OD matrices}\label{complex-od-matrices}
The matrices concerned here are characterized by several attributes, for
categorical matrices (e.g.~flows that concern several social groups,
several goods transported) or for temporal matrices (e.g.~flows occur on
several dates).
If so, agregations procedures are suggested when importing the dataset
in \emph{Arabesque}. By default, the sum function is applied in the lack
of any other specifications. However, you can choose to apply an
average, minimum, maximum or median function calculated on all the
matrices or graphs provided.
It is also possible to choose a single date or to aggregate the data,
according to a given function, over a period or for categories.
\begin{quote}
Example: the Mobscol origin-destination. Complex matrice.
.CSV format
\includegraphics{images/Example_mobscol_OD_CSV.PNG}
.XLXS format.
\begin{center}
\includegraphics{images/Example_mobscol_OD.PNG}
\end{center}
\end{quote}
This OD matrix is available for different categories (i.e.~SEXE=``1'' or
SEXE=``2''), so you will need to choose a method for aggregating the
links when importing, hereby the sum function.
\begin{center}
\includegraphics{images/Flowdata_import_aggregation.png}
\end{center}
This aggregation function is important because it defines the default
flowmap which will be proposed at the entry of \emph{Arabesque}: the
percent of links, nodes and interaction depicted, the intensity of the
colors and the opacity of the corresponding signs (see Data processing
chapter).
After aggregation, Arabesque will draws only one line (and not as many
lines for each attribute in the flow file).
\begin{tcolorbox}[enhanced jigsaw, rightrule=.15mm, bottomrule=.15mm, colback=white, breakable, opacityback=0, colframe=quarto-callout-note-color-frame, toprule=.15mm, leftrule=.75mm, arc=.35mm, left=2mm]
\begin{minipage}[t]{5.5mm}
\textcolor{quarto-callout-note-color}{\faInfo}
\end{minipage}%
\begin{minipage}[t]{\textwidth - 5.5mm}
\vspace{-3mm}\textbf{Note:}\vspace{3mm}
This aggregation does not interfere with the geo-visualization
possibilities that will remain available for all existing attributes.
The flow mapping according to one of these attributes can be performed
in the filtering section.
\end{minipage}%
\end{tcolorbox}
After loading the link and node files, Arabesque automatically performs
a join of the common attributes between the two files.
\section{Checking missing nodes/links
features}\label{checking-missing-nodeslinks-features}
Links that do not have an origin and/or destination ID are automatically
deleted. Nodes that don't have an ID code that allows them to be
geographically located are also not kept.
The list of links and nodes that may have been delete during the
importation procedure is displayed in a new window.
\includegraphics{images/import_suppr_entities.png}
This list is for quick reference only. You must copy and paste it (into
a text file, for example) if you want to keep the summary of the deleted
entities : here 5 nodes and 729 likns. Nodes have been deleted because
they are not related to other nodes.
After loading the link and node files, Arabesque automatically performs
a join of the common attributes between the two files and computes
indicator on botk links and nodes data.
\section{Import a previous workspace}\label{import-a-previous-workspace}
Import a previously workspace of flowmapping by loading a project file
in .zip format.
\includegraphics{images/import_zipfile.png}
\begin{tcolorbox}[enhanced jigsaw, rightrule=.15mm, bottomrule=.15mm, colback=white, breakable, opacityback=0, colframe=quarto-callout-warning-color-frame, toprule=.15mm, leftrule=.75mm, arc=.35mm, left=2mm]
\begin{minipage}[t]{5.5mm}
\textcolor{quarto-callout-warning-color}{\faExclamationTriangle}
\end{minipage}%
\begin{minipage}[t]{\textwidth - 5.5mm}
\vspace{-3mm}\textbf{.zip file}\vspace{3mm}
Do not modify this .zipfile, otherwise it will no longer work with
Arabesque, and you will not be able to load your workspace.
\end{minipage}%
\end{tcolorbox}
\bookmarksetup{startatroot}
\chapter{Data pre processing}\label{data-pre-processing}
After loading the data, the creation of a flow map with Arabesque can be
broken down into the following main steps.
\begin{tcolorbox}[enhanced jigsaw, rightrule=.15mm, bottomrule=.15mm, colback=white, breakable, opacityback=0, colframe=quarto-callout-tip-color-frame, toprule=.15mm, leftrule=.75mm, arc=.35mm, left=2mm]
\begin{minipage}[t]{5.5mm}
\textcolor{quarto-callout-tip-color}{\faLightbulb}
\end{minipage}%
\begin{minipage}[t]{\textwidth - 5.5mm}
\vspace{-3mm}\textbf{Flow mapping tips}\vspace{3mm}
\begin{enumerate}
\def\labelenumi{\arabic{enumi}.}
\tightlist
\item
Importing flow data (links/nodes)
\item
Processing flow data (automatic indicators calculation, \ldots)
\item
Geographical data computing (layering, \ldots)
\item
Statistical data computing (filtering, \ldots)
\item
Designing links and arrows (geometry and semiology)
\item
Designing nodes (semiology)
\item
Map cosmetics (title, sources, \ldots)
\item
Export
\end{enumerate}
\end{minipage}%