Record Atlas
United States of America · 0 volumes

Daggett County

Daggett County in United States of America. 0 record volumes and who holds them.

Nothing here has changed since this page began being watched on 2026-10-08. Follow what changes.

Comes out as a sheet for the reading room — what to ask for, who holds it, and every link written out in full.

This place

Where to begin

You know your family came from Daggett County. Here is the order I would work in, cheapest and easiest first — and what to do when that runs out.

  1. When you run out — and you will

    Everything above is what this atlas knows. It is not everything there is. Nine places in ten on this map have never been surveyed by anybody, so a gap here is usually our silence rather than the record's absence.

    Do this: write to the archive named in the era table for your year, even if we hold nothing for it. Then tell us what you found — a gap somebody has personally closed is the most useful thing a stranger can give this map.

How this place is on the map:

Whose archive this ground was

Not yet mapped. The record regions cover Istria, the Kvarner, Carnia and Dalmatia so far, and Daggett County is outside them. That is a gap in this map rather than a gap in the record — and the most useful thing anyone could fill in.

No volumes recorded here yet.

The ground worth walking

Within 25 km — 2 places. These neighbours hold 1 catalogued volume between them.

A register belongs to a parish, not to a village. A hamlet with no church of its own was written into the book of the church it walked to — and that book is catalogued under the other place's name. This is the ground to search before concluding a record does not exist.

Neighbours with volumes catalogued
Also within 25 km, nothing catalogued

Dutch John

Correctly placed and unread. A gap here is this atlas's silence, not the record's — the registers may well exist and nobody has walked them.

5 volumes catalogued here

The level below «a collection covers this place»: which book, for which years, and the link that opens its images. From FamilySearch's own catalogue. Nobody here has opened any of them. You can, though — mark the pages you have searched on any row below and this browser will remember where you stopped.

Other — 5

National sources for United States of America, unverified

From Wikidata, CC0 — the national archive and the national library where the country has one. Nobody here has opened these. The link answered when it was asked and that is the whole of what this map knows about them. They are listed because a country with no named source at all is the worse answer: 199 of the 237 countries here had nothing but the worldwide services, which cover everywhere and therefore say nothing about anywhere.

The sources for United States of America

National and regional sources that cover this ground whether or not anybody has walked it here — which makes them the answer, not the consolation, for a place with no volumes recorded on it.

  • National Archives Catalog (NARA) Images, free, no account Washington, D.C., United States
    The US National Archives catalogue and scans — naturalisations, passenger lists, military service, land.
  • Chronicling America Images, free, no account Washington, D.C., United States
    The Library of Congress's digitised American newspapers, full-text and free.
  • Macoupin County ILGenWeb — cemetery burial listings Images, free, no account
    Volunteer transcriptions of burials in Macoupin County, Illinois cemeteries, one page per letter-range (Calvary, Mt. Olive: calvarya.html, calvaryc.html … calvaryt.html), each row linking to a photograph of the stone. Free, no account. Read 17 October 2026 for the Calvary Catholic cemetery at Mount Olive: the R–S page lists thirteen Spudic/Spudick burials with birth and death years and photographs. It is a transcription by volunteers, not a register: the years come from the stones, not from a death record, and the page does not say how complete the cemetery coverage is.
  • Statue of Liberty–Ellis Island Foundation Images, free, account needed New York, United States
    Passenger arrivals at New York, 1820–1957, with manifest images. Free with an account.
  • Findmypast Images, behind a paywall
    Commercial. The strongest British and Irish collection, including parish registers licensed from diocesan archives and the 1921 census of England and Wales. BT 27 IS NOT ONE FORM AND ITS COLUMNS ARE NOT A CONSTANT. The outward passenger lists were re-drawn across the series, so a field present in one piece proves nothing about another and the era has to be checked before a row is planned around it. Sampled by the Luwinski archive: the 1907 form has NO «last address in the United Kingdom» column at all and buckets ages by nationality instead; the 1937 and 1939 form — printed «P.M. 21», columns (1)–(9) — carries last UK address at (6), country of last permanent residence at (8) and country of intended future permanent residence at (9); a 1951 piece is a typed US military transport manifest filed inside BT 27 with none of the Board of Trade form left. ACROSS EVERY REVISION SEEN, none gives an address in the DESTINATION country — the finest is a country and nothing below it, so «where in Australia did they settle» is not a question this series answers. SOUTH AFRICA IS NOT HERE, AND THE CATALOGUE WAS COUNTED TO SAY SO. Tested by the Booyzen archive on 12 October 2026, which had planned a week of a paid month around Cape passenger lists that do not exist. Searching all 2,977 record sets by place: «South Africa» returns 12 and EVERY ONE IS ANGLO-BOER WAR military (nominal rolls, rolls of honour, soldiers' wills, war memorials, and the Australian, New Zealand and Glasgow contingents); «Natal» returns NOTHING; «Cape» returns two and both are Cape Breton in Nova Scotia; «Transvaal» returns the same Boer War sets. There is no South African civil registration, no parish register, no passenger or arrival list, and nothing at all before 1899. The queries control each other — 12 relevant sets for one place name and 0 for another. THE ONE SOUTH AFRICAN SET WORTH THE TRIP is WO 127, «South Africa, Local Armed Forces Nominal Rolls 1899-1902», 53,416 records transcribed from The National Archives by Kevin Asplin, giving name, rank, regimental number, unit and often enrolment and discharge dates — enough to identify a rare surname and not enough for a common one, since it carries no age and no district. Note what it is: men who served the BRITISH in locally raised colonial units, so it is the opposite side from the Boer and Cape Rebel records. *** AND THE SEARCH INSTRUMENT ITSELF MISLEADS IN FIVE MEASURED WAYS, EVERY ONE OF WHICH PRODUCES A ZERO THAT LOOKS EXACTLY LIKE AN ABSENCE. Measured by the Luwinski archive, 12-13 October 2026. (1) NEVER YEAR-FILTER. Hertfordshire Baptisms, lastname=smith, no year: 15,122. The same search at year=1880 give or take 5: ZERO. At 1920: zero. The filter silently empties the set in some record collections and works normally in others — England & Wales Deaths year-filters correctly, returning 12,232 for Smith born 1887. So year-filter only with a positive control in the SAME SET in the same breath. (2) AN UNRECOGNISED URL PARAMETER IS TREATED AS A FILTER NOTHING MATCHES. Adding &page=5 to a results URL returns “0 results found”; the pagination parameter is `_page=`, with an underscore. (3) THE PLACE PARAMETER DIFFERS BY SET AND THE WRONG ONE IS SILENTLY IGNORED: `keywordsplace=` filters the census sets, `place=` filters the county parish sets. Using keywordsplace on Hertfordshire Baptisms returns the WHOLE COUNTY'S surname — 2,056 instead of 141 — while looking like a filtered result. Check by reading the place column of the rows returned. (4) A FORENAME SEARCH DOES NOT EXPAND ABBREVIATIONS AND FAILS SILENTLY. firstname=robert in Hertfordshire Burials returned ZERO for a burial indexed “ROBT”. Pre-1850 parish registers are full of Robt, Wm, Jas, Danl, Thos, Eliz and Jno. SEARCH THE SURNAME AND READ THE BLOCK; the rule “one spelling is not a search” applies to forenames, not just surnames. (5) THE BANNS SETS INDEX EACH CALLING SEPARATELY, so one wedding appears two or three times under different record ids — one of them reading “(the first of three)”. COUNTING ENTRIES IS NOT COUNTING MARRIAGES. And a banns entry is NOT a marriage: its marriage-year field is empty, banns are the announcement on three Sundays, and the wedding is not proved by them. *** THE IMAGES ARE SESSION-LOCKED AND REACHABLE ONLY FROM A SIGNED-IN BROWSER, and the URL form needs BOTH IDS: /record?id=<IMAGE id>&parentid=<TRANSCRIPT id> — the image id alone returns 500 and /transcript? with the image id returns 404. From there the IIIF service is /titan/marshal/record-gateway/image/<image id>/info.json with parentRecordId and recordMetadataId; it is level 2 with regionByPx, SO A SINGLE LINE CAN BE PULLED AT NATIVE RESOLUTION instead of squinting at the viewer. DO THAT FOR ANY FIGURE: a probate estate read “£1100 15s. 2d.” from a page view and “£1166 13s. 2d.” at native resolution. THE NUMERALS ARE THE FIRST THING TO GO. MEASURED 16 October 2026 by the Luwinski archive, signed in, in Hertfordshire. (1) HERTFORDSHIRE BAPTISMS: a surname-only, county-wide search returns twenty rows a page, and a transcript opens at transcript?id=GBPRS/M/<number> carrying the father's and mother's forenames, the father's occupation and, in most entries, the BIRTH DATE as well as the baptism date. That makes a birth-interval test possible: two children baptised to the same named parents with births nine months apart cannot share a mother, and a register that lists eleven children under one pair of forenames may be two families. (2) THE NAME-VARIANTS OPTION DID NOT BRIDGE BURCH AND BIRCH; the second spelling needs its own search. (3) HERTFORDSHIRE BURIALS STOPS ABOUT 1810 for a parish whose baptism set runs past 1860: the last entry for each of two surnames at one parish was 1808 and 1810. A missing burial after 1810 in this set is not a finding. (4) CENSUS: a transcript at transcript?id=GBC/<year>/<number> lists the WHOLE HOUSEHOLD, and neighbouring record numbers are neighbouring entries of one schedule, so a surname search can be read as households without opening the images. The 1851 transcript gives an age, a birth year and a birth place for every member, and a widow's birth place (a different county) separated two women of one forename that the baptism register could not. (5) o=yearofbirth sorts a census result set, but o=yearofbaptism did NOT sort the baptism set: its rows stayed in forename order. The page parameter is _page. ADDED 17 October 2026 by the Luwinski archive. (6) A MARRIAGE ENTRY IS TRANSCRIBED AS WRITTEN: a bride entered under one spelling in the banns entry was entered under another in the marriage entry of the same couple three weeks later, and a search on the first spelling could not find the second. Search both entries and a spelling variant. Hertfordshire Banns & Marriages marriage entries carry two witnesses and both parishes. (7) THE place FILTER ON A PARISH SET NEEDS THE PARISH'S FULL LABEL: place=aldenham worked, place=watford returned nothing, and place=watford%2C%20st%20mary returned 125 rows. (8) A general all-record-sets search with eventyear and keywordsplace lists the record sets that hold an entry, which is how to find a dataset's real name when a guessed name fails. ADDED 18 October 2026 by the Luwinski archive. (9) A SURNAME SEARCH CAN RETURN ZERO FOR A PERSON WHO IS IN THE INDEX: a census household was indexed under a different spelling of the family name (a Wallis family indexed as Wallace), a search on the right surname with the right forename and birth year returned eleven women from other counties and none from the county, and the person was found only by a forename, a parish and a birth year with NO surname. When a person who must exist is not there, drop the surname before concluding anything. (10) keywordsplace takes a parish or registration-district name and not a county: keywordsplace=hertfordshire returned nothing for a search that worked with the parish name. (11) A census household's other members are listed on its transcript page, and the 1881 index for the same household spelled the surname the way the baptism register did, so the spelling can change between censuses of one family.

Sources that cover everywhere

Not about United States of America in particular — these reach most of the world, which includes here. They are listed after the local sources because a body that holds this ground's own paper is a better first stop than one that holds a little of everywhere's. Worth knowing they exist all the same.

  • OldNews.com Nobody has walked this one yet
    Digitised historical newspapers, indexed by town. The CATALOGUE is harvested and published here — 38,151 papers in 6,450 towns across 75 countries, of which 5,968 towns join to a point on this map — because their robots.txt says Allow: /en/newspapers/* and the whole structure is in the URL. WHAT IT COSTS IS NOT KNOWN, and that is why this says unsurveyed rather than free or paid: the same robots.txt disallows /*/record and /*/search, so the pages that would answer it are the pages not to read. There is a log-in; whether an image is free behind it has not been established, and a colour on the map is a promise this cannot keep yet.
  • Internet Archive Images, free, no account
    Full-text search across millions of digitised books, including parish histories, nobiliaries and local monographs that name ordinary people. THREE THINGS VERIFIED 2026-10-11 WHILE REBUILDING A FAMILY'S 18th-CENTURY LINE FROM IT. (1) SEARCH THE RAREST TOKEN, NOT THE SURNAME. A search on one unusual middle name returned 329 hits and pulled out a 1972 family memoir, a reference work of colonial governors, a Falklands bibliography, an 1866 genealogical query and two monthly Army Lists — none of which a surname search had ever surfaced, because the book was CATALOGUED UNDER A MANGLED FORM OF THE SURNAME. (2) THE FULL-TEXT SEARCH HAS A PLAIN JSON API, which the site's own search page calls and which returns highlighted snippets: /services/search/beta/page_production/?service_backend=fts&user_query=%22PHRASE%22&hits_per_page=100&page=1&aggregations=false. It needs an ordinary browser User-Agent AND an Accept header; without the Accept header the site answers some requests with a flat 404. (3) FOR ANY OUT-OF-COPYRIGHT ITEM THE WHOLE TEXT IS ONE FILE — archive.org/download/<identifier>/<identifier>_djvu.txt — so a whole volume can be searched locally rather than page by page. Four Army Lists of 1775-1783, about 400KB of text each, were downloaded and searched entire in under a minute; that is how an absence can be MEASURED, by counting what the volume does contain. IN-COPYRIGHT ITEMS ARE LENDING-RESTRICTED: the item page still shows the metadata and the LIST OF ILLUSTRATIONS without borrowing, which was enough to recover a woman's missing middle name, but search-inside and the text need an account.
  • Arolsen Archives Images, free, no account
    The former International Tracing Service. Concentration camp, forced labour and displaced-persons records for some seventeen and a half million people, free and fully indexed.
  • Find a Grave Images, free, no account
    Volunteer-photographed headstones and cemetery indexes, worldwide, with very uneven coverage. Owned by Ancestry but free to read.
  • WikiTree Images, free, no account
    A free, single shared tree with an unusually strong sourcing culture. Not a record source.
  • Yad Vashem — Central Database of Shoah Victims' Names Images, free, no account
    Names and testimony pages for victims of the Shoah, free, no account. THE SEARCH IS FULLY URL-DRIVEN even though the site is an Angular app: /en/names/search-results-names?page=N&gn_last_name=X&gnt_last_name=yvSynonym&gn_first_name=Y&gnt_first_name=yvSynonym, with gnt_ taking yvSynonym, literal or soundex. THE RESULTS COME IN THREE TABS AND THE SECOND IS THE ONE ALMOST NOBODY USES: “Results Regarding Victims”, “RESULTS REGARDING DATA SUBMITTERS” (append #submitter to the URL) and “Additional Results”. The submitter tab lists every record whose SUBMITTER matched the name searched — so SEARCHING A SURVIVOR'S NAME THERE RETURNS THE DEAD HE WROTE DOWN, and one Page of Testimony can be turned into a whole family in a single query. There are also Submitter Last Name and Submitter First Name fields in the advanced form for the same purpose. TWO THINGS MEASURED IN USE. (1) THE SYNONYM EXPANSION IS LOOSE and will fold in a different submitter of a similar name from another country — in one test, 24 of 29 results belonged to somebody else and had to be separated by place — so a submitter set must be READ and not counted. (2) A PAGE OF TESTIMONY IS A RELATIONSHIP DOCUMENT, NOT A DATE DOCUMENT. Written from memory, often decades later and often in Hebrew and auto-translated back, it is the best evidence there is for who was whose son and the worst for when: in one family read here a Page disagreed with the German federal memorial list on a birth day AND a death year (the lists were right both times), two Pages by the same man for the same victim gave two different places of death, and the same parents appeared under German forenames on one form and Hebrew ones on the other — which is itself a gift, because it hands you the Hebrew names a community register would use. What a Page gives that no list gives is the single word in the “relationship to victim” field: son, nephew, grandson.
  • FamilySearch Images, free, account needed
    The largest free collection of record images and indexes in the world. A free account is required, and a minority of images are restricted to Family History Centres and affiliate libraries. TWO TRAPS IN THE CROATIAN HOLDINGS, both verified by use on 2026-10-09 and both capable of producing a confident false nil. (1) THE SAME PARISH SITS IN MORE THAN ONE COLLECTION. Bakar (Buccari) records are indexed under BOTH 'Croatia, Church Books, 1516-1994' (cc=2040054) AND 'Croatia, Delnice Deanery Catholic Church Books, 1571-1926'. A search restricted to 2040054 returns ZERO for records that demonstrably exist in the Delnice Deanery set - a marriage of 1783 at Bakar was found only once the collection filter was dropped. So a nil reported against one Croatian collection is a statement about that collection, never about the parish; and the catalogue's film list for a place may be split across collections that do not cross-reference each other. (2) SEARCH URL PARAMETERS SILENTLY FAIL. Hand-built query strings of the form /search/record/results?q.surname=X&q.anyPlace=Y returned 'Historical Record Search Results (0)' for a record whose own detail page gives exactly that surname and exactly that place string. The same query typed into the search form returns it. Place and collection parameters are the ones observed to fail; a bare q.surname + q.givenName pair did work. THE PRACTICAL RULE: never report a FamilySearch nil from a URL you assembled. Drive the form, and run a known-positive control - an ark id you already hold - through the same path first. An index entry is also a pointer and not a reading: the 1783 marriage above is indexed as two names and a date, and the words 'ex Gollogorizza' in the entry itself - the words that place the groom 130 km away in another crown land and make the record foreign to the Bakar set it sits in - appear nowhere in the index. Open the image before building or dismissing a household on an indexed record. Film and image-group identifiers DO work as stable handles where this collection's viewer carries no wc= waypoint: the Bakar marriage volume is film 005494714, 'Bakar. Religious Marriage Registers 1739-1808', item 1, 226 images, image group M99F-VRM. FULL-RESOLUTION IMAGES CAN BE DOWNLOADED, and it is worth knowing because the viewer's own zoom is a poor substitute for cropping locally. The download control in the image viewer opens a dialog offering 'PDF Record Image with Highlights', 'PDF with No Highlights', 'JPG Only' and 'No Record Image'. Choose JPG Only: it delivers the plate at native scan resolution - a Croatian parish register leaf came down at 5975x4206 - named <filmnumber>_<imagenumber>.jpeg, e.g. 005494714_00172.jpeg, which is a self-describing filename worth keeping. Note that the DeepZoom tiles the viewer itself loads (service/records/storage/deepzoomcloud/dz/v1/apid:<APID>/image_files/<level>/<col>_<row>.jpg) return 401 to an unauthenticated fetch and are blocked by CORS from the www origin, so scraping them is neither possible nor necessary; the download button is the supported route and it works. Resolution matters for more than comfort: a contested initial letter in a surname was settled only by cropping two words at identical magnification from the downloaded file, and the same comparison attempted through the viewer's zoom had been inconclusive.
  • Geni Images, free, account needed
    One shared world tree. Useful for finding other researchers on the same line; not a record source, and its assertions are only as good as their citations.
  • JewishGen Images, free, account needed
    The central Jewish genealogy resource — town-level KehilaLinks, burial and Holocaust databases, and revision lists for eastern Europe.
  • BillionGraves Partly free, partly paid
    GPS-tagged headstone photographs. Smaller than Find a Grave but its coordinates are per-stone, which Find a Grave's often are not. FREE AND PAID ARE SPLIT DOWN THE MIDDLE, surveyed 7 October 2026 at a South African cemetery: the search, the transcription — name with full birth and death dates — and the per-stone GPS coordinates are free and need no account, and so is a 180x135 thumbnail of the stone. THE FULL-RESOLUTION PHOTOGRAPH IS NOT: it requires an account and a subscription. The thumbnail is far too small to read an inscription, so a transcription taken from here CANNOT BE CHECKED AGAINST THE STONE without paying — which matters, because a volunteer's reading of a weathered date is exactly the thing an archive will want to verify. AND ITS SEARCH URL SILENTLY IGNORES WHAT YOU ASK IT, which makes it USABLE FOR A POSITIVE AND USELESS FOR A NEGATIVE: a hit here is a hit, and no absence may be quoted from it. Verified 9 October: `cemetery_country=United+Kingdom` is accepted and disregarded — the results still carry United States and Australian stones — and `page` does nothing at all, `page=7` returning the identical six records as `page=1` under a footer reading «Page 1 of 178». The footer asserts a depth the URL cannot reach, so the first page is not the result set and nothing that looks like «no match in that country» is one.
  • Geneanet Partly free, partly paid
    Member-contributed trees and transcriptions, strongest in France. Much is free; a Premium tier gates some search and images.
  • Ancestry Images, behind a paywall
    The largest commercial collection. Strong on the English-speaking world, censuses and immigration; weak on continental parish registers.
  • MyHeritage Images, behind a paywall
    Commercial, with a large tree network and good European newspaper and directory coverage. Search is free; opening a record is not. A LINK CHECKER CANNOT TELL YOU WHETHER A MYHERITAGE CITATION IS ALIVE, measured 2026-10-09 against 428 of them carried into a family archive from a GEDCOM export. Record pages answer an unauthenticated request in one of two ways, and NEITHER IS AN HONEST 200: either a 302 to a door, or HTTP 200 WITH AN 843-BYTE BODY READING «Request unsuccessful. Incapsula incident ID: …». A checker that reads the status code alone therefore reports every one of them as RESOLVING. Any archive auditing its outward citations has to read the body, and should grade these neither alive nor dead.

FamilySearch collections that reach here

A collection is a claim over an area, not a book standing in this town — so these are ranked by how specifically they reach Daggett County. A free account is needed to open the images, and some are restricted to a Family History Centre.

Elsewhere in the same country — 60

Narrower than the country but catalogued under some other district. Listed because a collection's title is not always where its records end, and never because it covers this ground.

…and 35 more.

See Daggett County on the map →

Everything in United States of America · All 55771 places · Correct something on this page