Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed because of a cast error
Error code: DatasetGenerationCastError
Exception: DatasetGenerationCastError
Message: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 4 new columns ({'flock_safety', 'license_plate_reader', 'week_start', 'flock_camera'}) and 3 missing columns ({'state', 'flock_camera_interest', 'geo_code'}).
This happened while the csv dataset builder was generating data using
hf://datasets/crawlora-net/flock-camera-search/data/interest-over-time-weekly.csv (at revision a6f81deed455c60d1c4415c475b0eb2fea2b7f1f), ['hf://datasets/crawlora-net/flock-camera-search@a6f81deed455c60d1c4415c475b0eb2fea2b7f1f/data/interest-by-region.csv', 'hf://datasets/crawlora-net/flock-camera-search@a6f81deed455c60d1c4415c475b0eb2fea2b7f1f/data/interest-over-time-weekly.csv', 'hf://datasets/crawlora-net/flock-camera-search@a6f81deed455c60d1c4415c475b0eb2fea2b7f1f/data/related-queries.csv']
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1837, in _prepare_split_single
writer.write_table(table)
~~~~~~~~~~~~~~~~~~^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 765, in write_table
self._write_table(pa_table, writer_batch_size=writer_batch_size)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 773, in _write_table
pa_table = table_cast(pa_table, self._schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2369, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2297, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
week_start: string
flock_safety: int64
license_plate_reader: int64
flock_camera: int64
-- schema metadata --
pandas: '{"index_columns": [{"kind": "range", "name": null, "start": 0, "' + 777
to
{'geo_code': Value('string'), 'state': Value('string'), 'flock_camera_interest': Value('int64')}
because column names don't match
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1683, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1839, in _prepare_split_single
raise DatasetGenerationCastError.from_cast_error(
...<4 lines>...
)
datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 4 new columns ({'flock_safety', 'license_plate_reader', 'week_start', 'flock_camera'}) and 3 missing columns ({'state', 'flock_camera_interest', 'geo_code'}).
This happened while the csv dataset builder was generating data using
hf://datasets/crawlora-net/flock-camera-search/data/interest-over-time-weekly.csv (at revision a6f81deed455c60d1c4415c475b0eb2fea2b7f1f), ['hf://datasets/crawlora-net/flock-camera-search@a6f81deed455c60d1c4415c475b0eb2fea2b7f1f/data/interest-by-region.csv', 'hf://datasets/crawlora-net/flock-camera-search@a6f81deed455c60d1c4415c475b0eb2fea2b7f1f/data/interest-over-time-weekly.csv', 'hf://datasets/crawlora-net/flock-camera-search@a6f81deed455c60d1c4415c475b0eb2fea2b7f1f/data/related-queries.csv']
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
geo_code string | state string | flock_camera_interest int64 |
|---|---|---|
US-WV | West Virginia | 100 |
US-AR | Arkansas | 57 |
US-KY | Kentucky | 55 |
US-ID | Idaho | 53 |
US-ND | North Dakota | 52 |
US-NE | Nebraska | 50 |
US-OH | Ohio | 49 |
US-IN | Indiana | 49 |
US-SD | South Dakota | 49 |
US-OK | Oklahoma | 49 |
US-MT | Montana | 48 |
US-IA | Iowa | 47 |
US-WI | Wisconsin | 46 |
US-MO | Missouri | 46 |
US-SC | South Carolina | 46 |
US-DE | Delaware | 44 |
US-KS | Kansas | 43 |
US-MN | Minnesota | 43 |
US-MI | Michigan | 43 |
US-TN | Tennessee | 42 |
US-NM | New Mexico | 39 |
US-NC | North Carolina | 39 |
US-AL | Alabama | 38 |
US-UT | Utah | 36 |
US-RI | Rhode Island | 36 |
US-ME | Maine | 35 |
US-GA | Georgia | 34 |
US-TX | Texas | 34 |
US-IL | Illinois | 34 |
US-VA | Virginia | 34 |
US-AZ | Arizona | 33 |
US-PA | Pennsylvania | 33 |
US-AK | Alaska | 33 |
US-FL | Florida | 31 |
US-CO | Colorado | 31 |
US-WA | Washington | 31 |
US-MS | Mississippi | 30 |
US-OR | Oregon | 30 |
US-CT | Connecticut | 30 |
US-WY | Wyoming | 29 |
US-NH | New Hampshire | 29 |
US-LA | Louisiana | 29 |
US-MD | Maryland | 28 |
US-VT | Vermont | 28 |
US-NV | Nevada | 27 |
US-MA | Massachusetts | 26 |
US-CA | California | 24 |
US-NJ | New Jersey | 22 |
US-DC | District of Columbia | 20 |
US-NY | New York | 18 |
US-HI | Hawaii | 17 |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
null | null | null |
End of preview.
"Flock camera" — how a surveillance brand name entered US search
Google Trends aggregates covering how the American public learned the phrase "Flock camera": a 53-week US interest-over-time series comparing three names for the same technology, a 51-state regional breakdown, and the complete rising and top related-query sets (9 and 25 rows — not selections). Snapshot 2026-07-27.
Companion to the study "Flock Camera" Searches Just Hit a 12-Month High. "License Plate Reader" Never Moved.
Headline findings
- A brand name beat the technology's real name, by roughly 50 to 1. US search
interest in
Flock camerasat flat between 1 and 4 for 36 consecutive weeks (2025-07-27 → 2026-03-29), broke that ceiling on 2026-04-12, and reached 100 — its 12-month peak — in the week of 2026-07-26. Over the same 53 weeks,license plate reader, the generic name for the same device, never once exceeded 2. - The public is still at the definition stage. All 9 of 9 rising related queries are asking what the thing is, led by "what is a flock camera and what does it do" at +950%. None concerns privacy law, contracts, or removal.
- Then it wants a map. The two highest-volume related queries are tied at the
ceiling —
flock map(100) andflock camera map(100) — withflock camera locations(19),flock cameras map(8) andflock camera near me(5) behind them. - The geography inverts the news coverage. Interest is highest in West Virginia (100), Arkansas (57), Kentucky (55), Idaho (53) and North Dakota (52); lowest in Hawaii (17), New York (18), DC (20), New Jersey (22) and California (24) — despite California and the Northeast generating a large share of national reporting.
- Nothing in either query set is about interfering with equipment. Across all 25
distinct queries, the nearest is
deflock(top, value 4) — a camera-mapping project.
Files
| File | Contents |
|---|---|
data/summary.json |
Full aggregate: pull parameters, per-keyword peaks and baselines, region extremes, query-set counts and caveats |
data/interest-over-time-weekly.csv |
53 weekly points, US, today 12-m, for Flock Safety, license plate reader and Flock camera on one shared scale |
data/interest-by-region.csv |
51 rows (50 states + DC), US, today 3-m, Flock camera |
data/related-queries.csv |
Complete rising (9) and top (25) related-query sets, US, today 3-m, Flock camera |
Methodology
Pulled live on 2026-07-27 via Crawlora's Google Trends
endpoints: google_trends_explore_interest_over_time (geo=US,
time_range=today 12-m, web search, all three keywords in one call),
google_trends_explore_interest_by_region, google_trends_explore_rising_queries and
google_trends_explore_top_queries (each geo=US, time_range=today 3-m,
keyword Flock camera).
The DeFlock figures in summary.json (121,464 LPRs mapped; 94 cities listed as
rejecting) were scraped from deflock.org's front page the same day via Crawlora's
web_scrape endpoint.
Caveats — please read before using
- Google Trends values are relative, not search counts. A value of 100 means "the highest point in this particular pull," not a volume.
- Only the three interest-over-time keywords are comparable to each other. They were requested in a single call, so Trends normalized them onto one shared 0-100 scale — which is what makes "100 versus never above 2" a valid statement. The region series is a separate call on its own 0-100 scale (100 = highest state) and must not be compared against the time-series numbers.
Flockis a polluted query term (birds, the former browser, flock printing, church usage). This shows up in the data:what is a flockappears in both query sets and is certainly not all ALPR intent. The paired terms (flock camera,flock camera map) are the cleaner signal.- Region data is interest, not deployment. A state ranking high means people there searched the term relatively more, not that it has more cameras.
related_topicsreturned empty for this keyword — no error, simply no mapped topic entity. It is not included here.- The DeFlock numbers are the project's own self-reported counts, not an independently audited census, and they change continuously.
- This is a snapshot of a moving story. The finding that 100% of rising queries are definitional is specific to the three months ending 2026-07-27 and is expected to change as the topic matures.
Scope
These are aggregates only: search-interest values and query strings. No personal data, no user-level records, and nothing tied to any individual.
License
CC BY 4.0 — free to use with attribution to
Crawlora. See CITATION.cff.
- Downloads last month
- 28