Loyal (town), Wisconsin

Loyal is a town in Clark County in the U.S. state of Wisconsin. The population was 787 at the 2000 census. The City of Loyal is located within the town. The unincorporated community of Spokeville is also located partially in the town.

Geography

According to the United States Census Bureau, the town has a total area of 34.7 square miles (90.0 km²), all of it land.

Demographics

As of the census[1] of 2000, there were 787 people, 215 households, and 187 families residing in the town. The population density was 22.7 people per square mile (8.7/km²). There were 225 housing units at an average density of 6.5 per square mile (2.5/km²). The racial makeup of the town was 99.49% White, 0.13% Black or African American and 0.38% Native American. Hispanic or Latino of any race were 0.13% of the population.

There were 215 households out of which 43.7% had children under the age of 18 living with them, 76.7% were married couples living together, 7.0% had a female householder with no husband present, and 12.6% were non-families. 10.2% of all households were made up of individuals and 2.3% had someone living alone who was 65 years of age or older. The average household size was 3.66 and the average family size was 3.94.

In the town, the population was spread out with 38.0% under the age of 18, 10.2% from 18 to 24, 25.4% from 25 to 44, 18.7% from 45 to 64, and 7.8% who were 65 years of age or older. The median age was 27 years. For every 100 females, there were 107.7 males. For every 100 females age 18 and over, there were 115.9 males.

The median income for a household in the town was $45,417, and the median income for a family was $46,667. Males had a median income of $23,828 versus $21,397 for females. The per capita income for the town was $14,023. About 11.7% of families and 15.8% of the population were below the poverty line, including 20.3% of those under age 18 and 4.5% of those age 65 or over.

gollark: Okay, very hacky but technically workable: have an XTMF metadata block of a fixed size, and after the actual JSON data, instead of just ending it with a `}`, have enough spaces to fill up the remaining space then a `}`.
gollark: XTMF was not really designed for this use case, so it'll be quite hacky. What you can do is leave a space at the start of the tape of a fixed size, and stick the metadata at the start of that fixed-size region; the main problem is that start/end locations are relative to the end of the metadata, not the start of the tape, so you'll have to recalculate the offsets each time the metadata changes size. Unfortunately, I just realized now that the size of the metadata can be affected by what the offset is.
gollark: The advantage of XTMF is that your tapes would be playable by any compliant program for playback, and your thing would be able to read tapes from another program.
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.

References

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