Voranava

Voranava or Voronovo (Belarusian: Воранава, Russian: Вороново, Polish: Woronów, Werenowo, Lithuanian: Voranavas) is a town in Belarus, in Grodno Region. It is the administrative center of the Voranava district. It is located about 32 km (20 mi) from Lida and 13 km (8 mi) from the Belarusian-Lithuanian border.

Voranava
Town
Flag
Coat of arms
Voranava
Coordinates: 54°09′N 25°19′E
Country Belarus
RegionGrodno Region
DistrictVoranava District
Elevation
165 m (541 ft)
Population
 (2007)
7,000

History

Within the Grand Duchy of Lithuania, Voranava was part of Vilnius Voivodeship. In 1795, the town was acquired by the Russian Empire in the course of the Third Partition of Poland.

From 1921 until 1939, Voranava was part of the Second Polish Republic. In September 1939, the town was occupied by the Red Army and, on 14 November 1939, incorporated into the Byelorussian SSR. From 23 June 1941 until 11 July 1944, Voranava was occupied by Nazi Germany and administered as a part of the Generalbezirk Weißruthenien of Reichskommissariat Ostland.

Population
  • 1865 — 468 people, (333 Jews, 117 Catholics, 18 Orthodox).
  • 1905 — 500
  • 1921 — 1232
  • 1976 — 3600.
  • 1990 — 6800.
  • 1996 — 6700.
  • 2004 — 6600.
  • 2005 — 6559
  • 2006 — 6498
  • 2007 — 6400.
  • 2008 — 6400.
  • 2015 — 6200
  • 2016 — 6434

In Voronovo district today live more than 32000 people, 83% are ethnic Poles.

Sights
  • Church of the God's Mercy
  • Church of the God's Mercy
  • Church of the God's Mercy inner interior
  • Building of the Voranava district court
  • Pharmacy building
  • District house of culture
  • Monument to defenders of the motherland World War II
  • Monument to defenders of the motherland World War II
  • Voranava lake 2015
  • Palace of Scipio del Campo (19th century)
  • Synagogue 20th century
  • Voranava Farm machinery
  • Church of Alyaksandar Neuski
gollark: Pretty much all of the algorithms reduced size by ~50% or so and the difference is maybe 5% or so between them all, so this is definitely premature optimization, but bees?
gollark: I tested four different compression algorithms and brotli did fairly well; I would have used zstandard but the node bindings for it are awful, and brotli actually did do better on small inputs.
gollark: For example, it stores created/updated timestamps in a way which allows them to be looked up more quickly, makes it faster to look up the latest revision of stuff, allows me to do compression (I implemented brotli compression to reduce storage requirements a lot), and allows revisions to have data and represent stuff other than "the page content changed".
gollark: The new version *is* better, even if it involves something like 70 lines more code.
gollark: I've reworked minoteaur's design a bit again because productivity is BEES and happens to other people.```sqlCREATE TABLE pages ( id INTEGER PRIMARY KEY, name TEXT NOT NULL, updated INTEGER NOT NULL, content TEXT NOT NULL);``` I went from that small and thus uncool database thingy to this:```sqlCREATE TABLE versions ( vuuid TEXT PRIMARY KEY COLLATE BINARY, rawSize INTEGER NOT NULL, encoding TEXT, data BLOB NOT NULL);CREATE TABLE pages ( title TEXT PRIMARY KEY, created INTEGER NOT NULL, updated INTEGER NOT NULL, latestVersion TEXT NOT NULL REFERENCES versions(vuuid));CREATE TABLE revisions ( ruuid TEXT PRIMARY KEY COLLATE BINARY, page TEXT NOT NULL REFERENCES pages(title), timestamp INTEGER NOT NULL, type TEXT NOT NULL, data TEXT NOT NULL, -- JSON version TEXT NOT NULL REFERENCES versions(vuuid));CREATE INDEX revisions_page_ix ON revisions(page);```


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.