Tully Township, Van Wert County, Ohio

Tully Township is one of the twelve townships of Van Wert County, Ohio, United States. The 2000 census found 2,119 people in the township, 1,009 of whom lived in the unincorporated portions of the township.[3]

Tully Township, Van Wert County, Ohio
Fields and wind turbines in the township's far northeast
Location of Tully Township in Van Wert County
Coordinates: 40°56′19″N 84°44′10″W
CountryUnited States
StateOhio
CountyVan Wert
Area
  Total36.2 sq mi (93.6 km2)
  Land36.2 sq mi (93.6 km2)
  Water0.0 sq mi (0.0 km2)
Elevation781 ft (238 m)
Population
 (2000)
  Total2,119
  Density58.6/sq mi (22.6/km2)
Time zoneUTC-5 (Eastern (EST))
  Summer (DST)UTC-4 (EDT)
FIPS code39-77756[2]
GNIS feature ID1087094[1]

Geography

Located in the northwestern corner of the county along the Indiana line, it borders the following townships:

The village of Convoy is located in southeastern Tully Township.

Name and history

Statewide, the only other Tully Township is located in Marion County.[4]

Government

The township is governed by a three-member board of trustees, who are elected in November of odd-numbered years to a four-year term beginning on the following January 1. Two are elected in the year after the presidential election and one is elected in the year before it. There is also an elected township fiscal officer,[5] who serves a four-year term beginning on April 1 of the year after the election, which is held in November of the year before the presidential election. Vacancies in the fiscal officership or on the board of trustees are filled by the remaining trustees.

gollark: Well, because I dislike being creepily surveiled. Though I mostly don't go to much effort.
gollark: As far as I know ISPs can't see that you connect to your own LAN.
gollark: You may only ask dishonest questions.
gollark: VPNs prevent ISPs from seeing all this except possibly to some extent #3, but the VPN provider can still see it, and obviously whatever service you connect to has any information sent to it.
gollark: Anyway, with HTTPS being a thing basically everywhere and DNS over HTTPS existing, ISPs can only see:- unencrypted traffic from programs/services which don't use HTTPS or TLS- the *domains* you visit (*not* pages, and definitely not their contents, just domains) - DNS over HTTPS doesn't prevent this because as far as I know it's still in plaintext in HTTPS requestts- metadata about your connection/packets/whatever- also the IPs you visit, but the domains are arguably more useful anyway

References

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