paper/paper.md

title: 'Gala: A Python package for galactic dynamics' tags: - Python - astronomy - dynamics - galactic dynamics - milky way authors: - name: Adrian M. Price-Whelan^[co-first author] # note this makes a footnote saying 'co-first author' orcid: 0000-0003-0872-7098 affiliation: "1, 2" # (Multiple affiliations must be quoted) - name: Author Without ORCID^[co-first author] # note this makes a footnote saying 'co-first author' affiliation: 2 - name: Author with no affiliation^[corresponding author] affiliation: 3 affiliations: - name: Lyman Spitzer, Jr. Fellow, Princeton University index: 1 - name: Institution Name index: 2 - name: Independent Researcher index: 3 date: 13 August 2017 bibliography: paper.bib

Optional fields if submitting to a AAS journal too, see this blog post:

https://blog.joss.theoj.org/2018/12/a-new-collaboration-with-aas-publishing

aas-doi: 10.3847/xxxxx <- update this with the DOI from AAS once you know it. aas-journal: Astrophysical Journal <- The name of the AAS journal.

Summary

We often take the availability of a cross-section of national statistical indicators for granted. Eurostat, the European statistical body, usually publishes data on 25-35 European countries, and global bodies often on more. For statistical comparisons, these are not large cross-sections, even if they are organized in longitudinal panels. There is a growing need to provide statistical indicators on a sub-national level, for example, for instead of treated the United States or Germany as an aggregation unit, using xxxx or xxxxx.

This task is far more difficult than it appears, because while international borders are relatively stable, sub-national boundaries of provinces, states, regions, metropolitan areas change very rapidly – within the European Union there were many thousand changes since 1999. This poses three important problems: the aggregation is not made on the same territory (or its human, enterprise population); the regional units get new names and new geographical ID codes. Because of the very frequent changes, if you try to join data from two independent regional statistics sources, it is almost certain that many geographical codes will not match, or, even if they match, they will not refer to the same boundary. Our package aims to help with these programs in the countries that apply Europe’s NUTS territorial divisions, which includes the European Union, the European Economic Area, and many candidate countries. We also aim to provide some level of global comparability.

This package is an offspring of the Eurostat package, which provides programmatic, reproducible access to the Eurostat data warehouse. We soon realized that the problem of sub-national geographical coding, naming, correct imputation, is a very large task and we created a new package. The resulting clean crossesctional data and longitudional panels already have made some scientific achievements in non-statistical domains

Statement of need

Location is a key attribute to many statisticial and business indicators: it provides the structure for collecting, processing, storing, analysing and aggregating data. The framework provided by a specific geographic feature, such as a national border, or a province, proximity to a city as a larger metropolitan area is key to both the creation and understanding of most statistical indicators. While statistical indicators defined over national borders, such as GDP, are the most often cited indicators, they are not always optimal for research purposes. Countries have very different sizes, and therefore, very different levels economic or cultural heteogeneity: the United States or China is one country, and so is Luxembourg, Malta or Liechtenstein.

In international comparison, using nationally aggregated indicators often have many disadvantages, which result from the very different levels of homogeneity, but also from the often very limited observation numbers in a cross-sectional analysis. When comparing European countries, a few missing cases can limit the cross-section of countries to around 20 cases which disallows the use of many analytical methods. Working with sub-national statistics has many advantages: the similarity of the aggregation level and high number of observations can allow more precise control of model parameters and errors, and the number of observations grows from 20 to 200-300.

Yet the change from national to sub-national level comes with a huge data processing price. While national boundaries are relatively stable, with only a handful of changes in each recent decade. The change of national boundaries requires a more-or-less global consensus. But states are free to change their internal administrative boundaries, and they do it with large frequency. This means that the names, identification codes and boundaries of regions change very frequently. Joining data from different sources and different years can be very difficult.

The use of such typologies are very useful for social scientific or policy research. Within a metropolitan region, people are likely to work in the functional urban center even if they live in a different LAU -- therefore LAU-level economic indicators tend to become meaningless; population density is different at day and night. Island regions tend to have higher level of unemployment levels. In Southern Europe, coastal areas have extremely high level of tourist populations during the summer, and mountain regions often in the winter. Therefore the analysis of most tourism related indicators should control for coastal and mountain areas.

Overview of Territorial Nomenclature

Eurostat’s Methodological manual on territorial typologies [] It may also be of interest to users of subnational statistics so they may better understand and interpret the wide range of official statistics that are available at a subnational level for the EU.

The decision to make this publication reflects

The NUTS classification (Nomenclature of territorial units for statistics) is a hierarchical system for dividing up the economic territory of the EU, the United Kingdom, and some other European countries for the purpose of collection, development and harmonisation of European regional statistics.

It has three hierarchical levels with one connecting top-level territory, i.e. the country itself, and the LAU unit for cities, villages, settlements and their surroundings.

The NUTS system used to have smaller NUTS 4 and NUTS 5 definitions, but they were so rapidly changing that it became impractical to use them for statistical aggregation. Eventually they were replaced with the LAU classification (municipalities, communes, parishes or wards), which is updated annually.

The LAU system is the basis of further typologies that can be very useful for researchers and policymakers, such as

The NUTS classification is set out in Annex I of Regulation (EC) No 1059/2003. I

, and which provides a hierarchical connection to settlements, municipalities.

The currently valid NUTS 2021 classification lists 104 regions at NUTS 1, 283 regions at NUTS 2 and 1345 regions at NUTS 3 level. The currently most used NUTS 2016 classification that was valid in the period 2018-2020 listed 104 regions at NUTS 1, 281 regions at NUTS 2 and 1348 regions at NUTS 3 level.

The NUTS is a European standard, and it is not interoperable with the ISO-3166-2 standard on sub-national subdivisions. The ISO-3166-2 is a global standard, but it was developed mainly for public administration and not statistical purposes. It’s greatest shortcoming for statistical application is that it is not hierarchical, i.e. there is no clear additive connection between two metropolitan areas that are located in the same province, for example. In many cases, European ISO-3166-2 boundary definitions (and naming, coding metadata) coincide with NUTS1, NUTS2 or NUTS3 boundary definitions. But in many cases, they are so differently defined that there is no clear way to match them, even by aggregated or grouping several units.

Recoding And Renaming

The simplest changes that occur after the redefinition of the NUTS or ISO-3166-2 boundaries is that the territorial units receive a new code or a new name, even if the boundary is not changed. This is a good practice: by assigning a new identification code to the same region in the 2016 definition of NUTS, even if the boundary did not change from the 2013 definitions makes it unambiguous that your are working with data aggregated according to the boundaries defined in 2016 (and in place for the period 2018-2020.) Similarly, sometimes regions, provincies and other territorial units are simply renamed.

In Europe, member states share much statistical information via Eurostat and the ESSnet system, but they are usually not back-casting historically released data. This means that the regional section of the Eurostat data warehouse often contains indicators with mixed coding, and mixed name definitions. In the same dataset, you find regions with NUTS 2010, NUTS 2013 and NUTS 2016 definitions. This problem is even greater if you start to work with other data sources, which may be less proficient with territorial statistics, and may not be even aware of NUTS changes.

In our understanding, recoding, and renaming only affects the metadata of a territory, and the metadata of any statistical aggregates that were created on the population of that territory. If the actual territory changes, then aggregates are no longer comparable, and this must be reflected in the metadata by assigning new codes and applying new names. One of the reasons why it is dangerous to use the ISO-3166-2 boundaries for statistical purposes is that boundary changes are often not reflected in the coding. (If a village is administered from a different provincial city, it has no significant importance in public administration; and as the ISO-3166-2 is a public administration standard, the lack of aggregation compatibility is not a criterion of its definition.)

Our package helps with recoding and renaming problems with .....

Projection and Imputation

It is very rare to find a large cross-sectional or longitudional regional dataset that is complete; and for many analytic purposes, imputation is desirable. Yet most imputation methods work on the assumption that data is not systematically omitted, which is exactly the case with missing territorially aggregated data. Europe’s NUTS territories are explicitly defined on a homogeneity criterion. The data shows very strong spatial autocorrelation, but other, more complex relationship with its neighbours, for example, two NUTS 3 level neighbours are divided because on part of the broader territory is more urban, the other is more rural. Assuming that these two geographically close neighbors are similar for imputation purposes is wrong. It is likely that the typical occupations, education level, age composition is very different – that is why they were defined as separate statistical units.

Our package handles missing values when the hierarchical definition of the territorial boundaries allows an unambiguous filling of missing values. In published datasets, this solves a surprisingly high number of issues.

....

Applications

Cross-sectional analysis

Small area statistics

Mathematics

Single dollars ($) are required for inline mathematics e.g. $f(x) = e^{\pi/x}$

Double dollars make self-standing equations:

$$\Theta(x) = \left{\begin{array}{l} 0\textrm{ if } x < 0\cr 1\textrm{ else} \end{array}\right.$$

You can also use plain \LaTeX for equations \begin{equation}\label{eq:fourier} \hat f(\omega) = \int_{-\infty}^{\infty} f(x) e^{i\omega x} dx \end{equation} and refer to \autoref{eq:fourier} from text.

Citations

Citations to entries in paper.bib should be in rMarkdown format.

 If you want to cite a software repository URL (e.g. something on GitHub without a preferred
                                               citation) then you can do it with the example BibTeX entry below for @fidgit.

For a quick reference, the following citation commands can be used:
  - `@author:2001`  ->  "Author et al. (2001)"
- `[@author:2001]` -> "(Author et al., 2001)"
- `[@author1:2001; @author2:2001]` -> "(Author1 et al., 2001; Author2 et al., 2002)"

Figures

Figures can be included like this:
  ![Caption for example figure.\label{fig:example}](figure.png)
and referenced from text using \autoref{fig:example}.

Figure sizes can be customized by adding an optional second parameter:
  ![Caption for example figure.](figure.png){ width=20% }

Acknowledgements

We acknowledge contributions from Brigitta Sipocz, Syrtis Major, and Semyeong
Oh, and support from Kathryn Johnston during the genesis of this project.

References



antaldaniel/regions documentation built on Sept. 27, 2022, 1:15 a.m.