Small Border Traffic and Cross-Border Tourism Between Poland and the Kaliningrad Oblast of the Russian Federation
Bibliographic record
Abstract
Abstract Polish and Russian cross-border cooperation is governed by lawful agreements. The enlargement of the Schengen Area had a significant impact on Kaliningrad Oblast relations and cross-border cooperation with its neighbours. The introduction of visas between Poland and Russia hindered and restricted local border trade which had for years been the only measure mitigating social and economic problems of the cross-border regions. Nevertheless, border traffic between Poland and Kaliningrad grew steadily, to exceed four million in 2012. Poland and Russia, supported by Germany, applied to the EU for small border traffic to cover the entire territory of the Oblast. According to the European Commission, the proposed solution would be a European exception. The agreement on small border traffic came into force on July 27, 2012, covering the entire area of the Kaliningrad Oblast and selected Polish poviats of Pomerania and Warmia-Mazuria voivodeships. Towards the end of the first quarter of 2013, the number of Poles crossing the border showed a rising tendency, and starting from the second through the third quarter of 2013, the number of Russians coming to Poland grew more dynamically. The visits of Kaliningrad residents, apart from commercially oriented ones, also include recreation, tourism, medical tourism visits, etc. Kaliningrad citizens looking for leisure, recreation and entertainment come to participate in great sporting and cultural events in Gdańsk, Sopot and Gdynia. The local self governments of poviats covered by small border traffic noted a clear upturn in the economies and trade of their regions. The development of cross-border cooperation, including small border traffic, has not resulted in attracting a substantial number of Polish tourists to the Kaliningrad Oblast, but it has provided such a possibility. This region is quite expensive for the average Pole. However, as scientists from Kaliningrad projected, with the easing of the visa system and the development of transport and tourist infrastructure the role of tourism shows a growing trend.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.004 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".