Camanche North Shore, California

Camanche North Shore is a census-designated place in Amador County, California. Camanche North Shore sits at an elevation of 308 feet (94 m). The 2010 United States census reported Camanche North Shore's population was 979.

Camanche North Shore
Location of Camanche North Shore in Amador County, California.
Camanche North Shore
Position in California.
Coordinates: 38°14′40″N 120°57′14″W
Country United States
State California
CountyAmador
Area
  Total2.306 sq mi (5.974 km2)
  Land2.306 sq mi (5.974 km2)
  Water0 sq mi (0 km2)  0%
Elevation308 ft (94 m)
Population
 (2010)
  Total979
  Density420/sq mi (160/km2)
Time zoneUTC-8 (Pacific (PST))
  Summer (DST)UTC-7 (PDT)
GNIS feature ID2582959
[3]

Demographics

Historical population
CensusPop.
U.S. Decennial Census[4]

The 2010 United States Census[5] reported that Camanche North Shore had a population of 979. The population density was 424.5 people per square mile (163.9/km2). The racial makeup of Camanche North Shore was 860 (87.8%) White, 3 (0.3%) African American, 14 (1.4%) Native American, 12 (1.2%) Asian, 3 (0.3%) Pacific Islander, 38 (3.9%) from other races, and 49 (5.0%) from two or more races. Hispanic or Latino of any race were 150 persons (15.3%).

The Census reported that 979 people (100% of the population) lived in households, 0 (0%) lived in non-institutionalized group quarters, and 0 (0%) were institutionalized.

There were 391 households, out of which 125 (32.0%) had children under the age of 18 living in them, 217 (55.5%) were opposite-sex married couples living together, 39 (10.0%) had a female householder with no husband present, 21 (5.4%) had a male householder with no wife present. There were 31 (7.9%) unmarried opposite-sex partnerships, and 3 (0.8%) same-sex married couples or partnerships. 87 households (22.3%) were made up of individuals, and 30 (7.7%) had someone living alone who was 65 years of age or older. The average household size was 2.50. There were 277 families (70.8% of all households); the average family size was 2.86.

The population was spread out, with 230 people (23.5%) under the age of 18, 67 people (6.8%) aged 18 to 24, 204 people (20.8%) aged 25 to 44, 344 people (35.1%) aged 45 to 64, and 134 people (13.7%) who were 65 years of age or older. The median age was 44.1 years. For every 100 females, there were 105.7 males. For every 100 females age 18 and over, there were 107.5 males.

There were 480 housing units at an average density of 208.1 per square mile (80.4/km2), of which 391 were occupied, of which 305 (78.0%) were owner-occupied, and 86 (22.0%) were occupied by renters. The homeowner vacancy rate was 4.4%; the rental vacancy rate was 9.5%. 736 people (75.2% of the population) lived in owner-occupied housing units and 243 people (24.8%) lived in rental housing units.

gollark: Slower, even.
gollark: Oops, it turns out I'm accidentally sorting by it instead of the rank, but it's equally slow after fixing that.
gollark: ```nonlocality=# EXPLAIN ANALYZE SELECT url, ts_rank(fts, query), ts_headline(fts::text, query, 'MaxWords=60') AS rank FROM pages, websearch_to_tsquery('bee') query WHERE fts @@ query ORDER BY rank LIMIT 1; QUERY PLAN ------------------------------------------------------------------------------------------------------------------------------------------------- Limit (cost=860.92..860.92 rows=1 width=96) (actual time=8506.425..8506.427 rows=1 loops=1) -> Sort (cost=860.92..861.05 rows=52 width=96) (actual time=8506.423..8506.425 rows=1 loops=1) Sort Key: (ts_headline((pages.fts)::text, query.query, 'MaxWords=60'::text)) Sort Method: top-N heapsort Memory: 25kB -> Nested Loop (cost=688.65..860.66 rows=52 width=96) (actual time=1.362..8505.403 rows=348 loops=1) -> Function Scan on websearch_to_tsquery query (cost=0.25..0.26 rows=1 width=32) (actual time=0.023..0.025 rows=1 loops=1) -> Bitmap Heap Scan on pages (cost=688.40..846.49 rows=52 width=142) (actual time=0.353..1.502 rows=348 loops=1) Recheck Cond: (fts @@ query.query) Heap Blocks: exact=231 -> Bitmap Index Scan on page_search_index (cost=0.00..688.39 rows=52 width=0) (actual time=0.320..0.320 rows=387 loops=1) Index Cond: (fts @@ query.query) Planning Time: 0.190 ms Execution Time: 8506.463 ms(13 rows)```
gollark: It's not a condition, it's an extra row on the output, and I can see exactly what it does via `EXPLAIN ANALYZE`.
gollark: Maybe I need a better full text search backend?!

References

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