An archaeological investigation before redevelopment of the railway station in Manduria, 20 miles east of Taranto, southeast Italy, has uncovered a large section of a defensive wall built by the pre-Italic Messapian people in the 4th century B.C. The structure is composed of limestone blocks that were precisely worked and laid dry in an alternating pattern. It was built inside a moat that encircled the inner wall of the older Archaic-era defensive walls.
The Messapians inhabited what is now the region of Apulia (the heel of Italy’s boot) from the 9th to the 3rd century B.C. They formed highly developed independent city-states and, fiercely defended that independence against numerous attacks from the Greek colonies of southern Italy. Manduria was one of the most prosperous Messapian cities, and built elaborate defenses to protect itself: a triple ring of megalithic walls constructed between the 5th and 3rd centuries B.C.
The newly-discovered section of wall is expanding our knowledge of the complex Messapian fortification systems. Its massive defenses were put to the test repeatedly, most notably when Manduria was besieged by Taras (Taranto) and its Spartan allies in 338 B.C. That attempt failed, and the Spartan king Archidamus III lost his life outside those imposing walls. The Romans took it in 266 B.C., but Hannibal besieged it in 212 B.C. during the Second Punic War and wrested it out of their grasp. Roman legions under Quintus Fabius Maximus, former dictator and at the time consul for the fifth time, reconquered Manduria and Tarantum in 209 B.C.
In agreement with the railroad, the best-preserved section of the wall will be preserved and displayed in situ. Information panels will give rail travelers an understanding of the Messapian city and its walls, thematically linking ancient Manduria and its infrastructure and connecting visitors to the Archaeological Park of the Messapian Walls a half mile down the road.
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server