Fort des Adelphes

The Fort des Adelphes, or Fort Richepance, is part of the fortifications of Épinal. It was built near the village of Deyvillers between 1883 and 1885, and was modernized beginning in 1907. It is an example of a Séré de Rivières system fortification. During World War II the fort surrendered to German forces and was then used by the Germans to fire on neighboring forts Longchamp and Dogneville. The fort is now occupied by an activity of the French Air Force associated with Base aerienne 133 Nancy-Ochey and is not accessible to the public.

Fort des Adelphes
Part of Séré de Rivières system, Fortified Region of Épinal
France
Fort des Adelphes
Coordinates48.18796°N 6.4966°E / 48.18796; 6.4966
TypeFort
Site information
OwnerFrench Air Force
Controlled byFrance
Open to
the public		No
ConditionAltered
Site history
Built1883 (1883)
MaterialsBrick, stone, concrete
Battles/warsBattle of France

Located 3.75 kilometres (2.33 mi) northeast of Épinal, the Fort des Adelphes is part of a 43-kilometre (27 mi) line of sixteen major fortifications around Épinal designed to bar the advance of a German army into France.

Description

The fort is situated at an altitude of 419 metres (1,375 ft), overlooking the road to Saint-Dié between the Fort de Razimont and the Deyvillers works. The fort is laid out as a walled pentagon, surrounded by a ditch. Construction extended from 1883 to 1885. The fort includes fortified barracks, storage facilities and magazines, and shelters for troops. The initial garrison comprised 235 men, and the construction cost of the original fort amounted to about 1.2 million francs. The principal armament consisted of five 155mm and three 120mm guns on the fort's ramparts.[1]

The Fort des Adelphes was almost immediately improved with a concrete covered barracks for 150 men in 1892-1894. Between 1900 and 1906 a number of spiral queues de cochon or pig-tail infantry shelters were constructed around the fort. From 1907 to 1914 the fort was extensively reinforced, including the replacement of the caponiers guarding the ditch with more effective counterscarps, while a second reinforced barracks was added, along with a casemate de Bourges covering the ground in the direction of the ouvrage de Deyvillers.Between 1907 and 1909, armored observation positions and a 75mm gun turret were added. A third observation cupola and a machine gun turret were added in 1909-1910. Finally, the fort was connected to the electrical grid in 1913. The fort's garrison was by this time 400 troops.[1][2][3]

Two 155mm gun turrets were planned for a battery located outside the walls of the fort, but work was stopped by the outbreak of war in 1914.[1]

History

The fort fired its 75mm gun turret at a German airplane during the First World War, but failed to hit the airplane. The fort fired on German troops in June 1940 during the Battle of France, but the fort surrendered to the Germans on 20 June and was then used to fire on its neighbors. The fort was stripped of equipment and armament in 1943.[1]

Status

The Fort des Adelphes was significantly altered in 1990 to support a French Air Force electronic warfare squadron. It continues in that role.[4] The fort is not accessible to the public.[1]

gollark: It could record locally and upload later, though.
gollark: This person apparently reverse-engineered it statically, not at runtime, but it *can* probably detect if you're trying to reverse-engineer it a bit while running.
gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.

References
  1. Vaubourg, Cédric & Julie (2010). "Le fort des Adelphes ou fort Richepance" (in French). fortiffsere.fr. Retrieved 13 April 2010.
  2. "Le fort des Adelphes" (in French). Association pour la Restauration du Fort d'Uxegney et de la Place d'Epinal. 2010. Retrieved 13 April 2010.
  3. Mary, Jean-Yves; Hohnadel, Alain; Sicard, Jacques (2001). Hommes et Ouvrages de la Ligne Maginot, Tome 1 (in French). Histoire & Collections. p. 16. ISBN 2-908182-88-2.
  4. "Historique de la Base" (in French). Ministère de la Défense. 21 April 2006. Archived from the original on 20 July 2011. Retrieved 13 April 2010.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.