CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · Places & Architecture

Datha princely state

town, former princely state in India

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJan 9, 2026
Entity authorityQ28171902 ↗
Source-derived summary

Datha is a town and former non-salute Rajput princely state on Saurashtra peninsula in Gujarat, Western India.

The village lies on the Bagad river, in Kathiawar.

History

The princely state, in Gohelwar prant, was ruled by Sarvaiya Rajput Chieftains.

In 1901 it comprised 24 villages, covering 69 square km, with a population of 9,452, yielding 31,339 Rupees state revenue (1903–4, mostly from land), and paid 5,398 Rupees tribute, to the Gaikwar Baroda State and Junagadh State.

Editorial summary

This brief starts where responsible research should: with the source description of “Datha princely state” as town, former princely state in India. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA strong orientation record where physical form, institutional use and historical geography need to be read together. The current lead gives the account dated anchors—1901, 1903—that can be checked directly. The selected authority fields contribute no independent date. The account is most persuasive where Datha, princely and state can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the places & architecture register because the source frames it as town, former princely state in India. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Jan 9, 2026. The linked authority identifier is Q28171902. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1901 and 1903.

Critical limits

Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Datha princely state”, its source revision and the description used here.
  2. Expand the search: follow Datha princely state primary sources, Datha princely state archive and Datha research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Datha princely state”?
  2. Which authority defined the place, boundary or structure at the relevant date?
  3. What physical evidence or contemporary plan supports the description?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Datha princely state” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.