Saint-Benoît, Alpes-de-Haute-Provence
Saint-Benoît is a commune in the Alpes-de-Haute-Provence department in southeastern France.
Saint-Benoît | |
|---|---|
 Bridge of Queen Jeanne over the Coulomp | |
 Coat of arms | |
Location of Saint-Benoît 
| |
  Saint-Benoît  Saint-Benoît | |
| Coordinates: 43°58′05″N 6°43′35″E | |
| Country | France |
| Region | Provence-Alpes-Côte d'Azur |
| Department | Alpes-de-Haute-Provence |
| Arrondissement | Castellane |
| Canton | Castellane |
| Intercommunality | Terres de Lumière |
| Government | |
| • Mayor (2008–2014) | Henri Ferraro |
| Area 1 | 21.03 km2 (8.12 sq mi) |
| Population (2017-01-01)[1] | 149 |
| • Density | 7.1/km2 (18/sq mi) |
| Time zone | UTC+01:00 (CET) |
| • Summer (DST) | UTC+02:00 (CEST) |
| INSEE/Postal code | 04174 /04240 |
| Elevation | 515–1,402 m (1,690–4,600 ft) (avg. 720 m or 2,360 ft) |
| 1 French Land Register data, which excludes lakes, ponds, glaciers > 1 km2 (0.386 sq mi or 247 acres) and river estuaries. | |
Population
| Year | Pop. | ±% |
|---|---|---|
| 1765 | 429 | — |
| 1793 | 550 | +28.2% |
| 1800 | 396 | −28.0% |
| 1806 | 445 | +12.4% |
| 1821 | 523 | +17.5% |
| 1831 | 512 | −2.1% |
| 1836 | 556 | +8.6% |
| 1841 | 590 | +6.1% |
| 1846 | 548 | −7.1% |
| 1851 | 516 | −5.8% |
| 1856 | 479 | −7.2% |
| 1861 | 431 | −10.0% |
| 1866 | 395 | −8.4% |
| 1872 | 392 | −0.8% |
| 1876 | 385 | −1.8% |
| 1881 | 405 | +5.2% |
| 1886 | 415 | +2.5% |
| 1891 | 402 | −3.1% |
| 1896 | 379 | −5.7% |
| 1901 | 269 | −29.0% |
| 1906 | 298 | +10.8% |
| 1911 | 258 | −13.4% |
| 1921 | 244 | −5.4% |
| 1926 | 248 | +1.6% |
| 1931 | 191 | −23.0% |
| 1936 | 183 | −4.2% |
| 1946 | 174 | −4.9% |
| 1954 | 146 | −16.1% |
| 1962 | 97 | −33.6% |
| 1968 | 71 | −26.8% |
| 1975 | 54 | −23.9% |
| 1982 | 66 | +22.2% |
| 1990 | 85 | +28.8% |
| 1999 | 112 | +31.8% |
| 2008 | 122 | +8.9% |
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
gollark: If you run too much current through beans they may vaporise/burn/etc.
gollark: You could make a mechanical computer from solidified beans.
gollark: Can beans be used for digital logic?
References
- "Populations légales 2017". INSEE. Retrieved 6 January 2020.
 |
Wikimedia Commons has media related to Saint-Benoît, Alpes-de-Haute-Provence. |
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.