Barker Ten Mile, North Carolina

Barker Ten Mile is a census-designated place (CDP) in Robeson County, North Carolina, United States. The population was 952 at the 2010 census. The land surrounding Barker Ten Mile includes multiple areas of local historic significance. the first being "The Meadows," which is the familial hunting grounds and horse pastures of the Goodes, French, McMillan, Sheppard and Godwin families. All of whom were prominent landholders, tobacco farmers and community members. Margeret Mclean, née French was the wife Angus Wilton Mclean grew up in Barker Ten mile.. The collection of family land holdings originally stretched from what is now Meadowbrook cemetery and north to Bee Gee road and Meadow road. From east to west the property extended along the boundaries of Meadow rd and traversed I-95 near the current location of Robeson County Community College. Barry Godwin French, Margaret French McLean's father was often referred to by the nickname "Bee Gee" and as such Bee Gee road, which bisected his land was named after him. Additionally Barker Ten Mile, is within the drainage area and immediately contains portions of Ten mile swamp and Saddle Tree swamp, both of which are of cultural significance to the Lumbee. The Locklear family (Lumbee) and the Goode's (Barker Ten Mile Scot's) were known to have hunted quail frequently together at the meadow and is reflective generally of the racial attitudes of the Barker Ten Mile Scots and Saddle tree / Barker Ten mile Lumbee.

Barker Ten Mile, North Carolina
CDP
Barker Ten Mile, North Carolina
Location within the state of North Carolina
Coordinates: 34°40′49″N 78°59′14″W
CountryUnited States
StateNorth Carolina
CountyRobeson
Area
 • Total2.3 sq mi (5.9 km2)
 • Land2.3 sq mi (5.9 km2)
 • Water0.0 sq mi (0.0 km2)
Elevation
135 ft (41 m)
Population
 (2010)
 • Total952
 • Density426.9/sq mi (164.8/km2)
Time zoneUTC-5 (Eastern (EST))
 • Summer (DST)UTC-4 (EDT)
FIPS code37-03665[1]
GNIS feature ID1867426[2]

Geography

Barker Ten Mile is located at 34°40′49″N 78°59′14″W (34.680310, -78.987307).[3]

According to the United States Census Bureau, the CDP has a total area of 2.3 square miles (6.0 km2), all of it land.

Demographics

As of the 2010 United States Census, there were 952 people living in the CDP. The racial makeup of the CDP was 67.9% White, 12.0% Black, 14.4% Native American, 2.1% Asian, 0.1% from some other race and 1.6% from two or more races. 2.0% were Hispanic or Latino of any race.

As of the census[1] of 2000, there were 976 people, 371 households, and 303 families living in the CDP. The population density was 426.9 people per square mile (164.6/km2). There were 386 housing units at an average density of 168.9 per square mile (65.1/km2). The racial makeup of the CDP was 77.56% White, 12.40% African American, 7.17% Native American, 1.13% Asian, 0.10% Pacific Islander, 0.82% from other races, and 0.82% from two or more races. Hispanic or Latino of any race were 1.02% of the population.

There were 371 households, out of which 35.6% had children under the age of 18 living with them, 72.8% were married couples living together, 6.5% had a female householder with no husband present, and 18.3% were non-families. 16.2% of all households were made up of individuals, and 6.7% had someone living alone who was 65 years of age or older. The average household size was 2.63 and the average family size was 2.93.

In the CDP, the population was spread out, with 23.7% under the age of 18, 4.7% from 18 to 24, 25.9% from 25 to 44, 34.0% from 45 to 64, and 11.7% who were 65 years of age or older. The median age was 43 years. For every 100 females, there were 99.6 males. For every 100 females age 18 and over, there were 96.6 males.

The median income for a household in the CDP was $66,833, and the median income for a family was $68,693. Males had a median income of $45,278 versus $28,958 for females. The per capita income for the CDP was $33,281. None of the population or families were below the poverty line.

gollark: At least it has generics.
gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.
gollark: - `make`/`new` are basically magic- `range` is magic too - what it does depends on the number of return values you use, or something. Also, IIRC user-defined types can't implement it- Generics are available for all of, what, three builtin types? Maps, slices and channels, if I remember right.- `select` also only works with the built-in channels- Constants: they can only be something like four types, and what even is `iota` doing- The multiple return values can't be used as tuples or anything. You can, as far as I'm aware, only return two (or, well, more than one) things at once, or bind two returns to two variables, nothing else.- no operator overloading- it *kind of* has exceptions (panic/recover), presumably because they realized not having any would be very annoying, but they're not very usable- whether reading from a channel is blocking also depends how many return values you use because of course

References
  1. "U.S. Census website". United States Census Bureau. Retrieved January 31, 2008.
  2. "US Board on Geographic Names". United States Geological Survey. October 25, 2007. Retrieved January 31, 2008.
  3. "US Gazetteer files: 2010, 2000, and 1990". United States Census Bureau. February 12, 2011. Retrieved April 23, 2011.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.