Methodology

Where the data comes from

Source: Source registers of census-amenities.json, health-education-facilities.json and villages-canonical.json, all edition 2026-08-04.
Last verified: 4 August 2026.

What this table cannot tell you It cannot promise these are the best sources that exist, only that they are the ones actually retrieved and read, and that no figure on this site comes from anywhere else.

The geography is awkward and the site does not hide it. Census 2011 has no Dholera taluka: Dholera appears only as a village, code 511931, inside Dhandhuka. Dholera taluka was constituted after the census, out of Dhandhuka and Barwala. So the census scope here is all 69 villages of Census 2011 Dhandhuka plus the three Barwala villages named on the DSIRDA boundary map, which is 72 records, and the 22 notified villages are a subset of those.

Source: villages-canonical.json name_variants block, edition 2026-08-04.
UDISE+ village register for Dholera block (blockId 34072), academic year 2025-26, retrieved 2026-08-04.
Last verified: 4 August 2026.

What this table cannot tell you It cannot tell you which spelling is correct. Each source keeps its own, and every village page prints the alternatives it was given.

How the two vintages are kept apart

The census amenity block carries an internal reference year of 2009 and is published under Census 2011. The health lists are as on 15 August 2018 and 30 June 2021. The school rows carry no as-on date at all. Those are three different things and they never share an uncaptioned table on this site. Every table states its vintage in its caption, every census table prints 2009 in an age gutter set in italic, and every figure older than five years is marked as old rather than presented as current.

Source: Derived from the operating_status, data_class and publishable_as_operating fields of health-education-facilities.json, edition 2026-08-04.
Last verified: 4 August 2026.

What this table cannot tell you It cannot make 49 aggregator rows into operating facilities. They stay at listed, not verified, until a government document names them.

Three of the five status codes this programme specifies are empty here. That is not an oversight. No source retrieved states that any health or education facility in Dholera is under construction, or has been tendered, or is not planned, so this register does not apply those codes to anything. A sixth code, listed but not verified, was added because 49 school records fit none of the five honestly: an aggregator lists them, no government document confirms them, and promoting them to operating would be the exact error this site exists to avoid.

The one door that stayed shut

Why is there no UDISE+ enrolment or class range in this dataset. The public search app is https://kys.udiseplus.gov.in (Know Your School). Its school result call is The school result call is getSchoolListBySearch(), which builds its query string as `searchType=${e}&searchParam=${a}&stateId=${s}&captcha=${o}`. A 6-character CAPTCHA is required and is verified SERVER-side before any school row is returned; the advance-search form refuses to route to /advancesearch until captchaVerify passes.

Bypassing that CAPTCHA was out of bounds and was not attempted. What was still retrieved, because it loads before the CAPTCHA, is the geography: the block record confirming Dholera block, UDISE code 240713, the official 39-village register for the block, and the official five-cluster structure for 2025-26. Those were used only to resolve each school's village from its code prefix, never to assert a facility attribute. Closing the remaining gap costs 55 schools would need 55 manual CAPTCHA solves by a human on kys.udiseplus.gov.in, roughly 60-90 minutes, to fill class range and enrolment. It cannot be automated within the rules.

What is missing, in full

Below is every gap the three source datasets declare about themselves, printed in full rather than summarised. A register that hides its holes is a brochure.

Gaps declared by the census extraction

• Dholera taluka does not exist in this source. Census 2011 records no sub-district named Dholera anywhere in Gujarat; Dholera appears only as a VILLAGE (code 511931) inside Dhandhuka taluka (sub-district code 03787), Ahmadabad district. Dholera taluka was constituted after the 2011 Census, so a taluka-level filter was impossible. Scope was therefore set to all 69 villages of Census 2011 Dhandhuka taluka plus the 3 DSIRDA-boundary villages that fall in Barwala taluka.
• No official list of the villages in present-day Dholera taluka exists in the supplied source artifacts, so no record is tagged with present-day taluka membership. The only sourced area overlay applied is the DSIRDA (Dholera SIR) boundary village list.
• Two DSIRDA map names required a transliteration match rather than an exact string match: DSIRDA 'Bavaliyari' -> Census 'Bavliyari' (511941) and DSIRDA 'Ambali' -> Census 'Ambli' (511905). Both are flagged per record in dsirda_name_match_method. No exact-spelling alternative exists in Ahmadabad, Bhavnagar or Surendranagar districts.
• DSIRDA 'Kadipur' matched to village 511927 in Dhandhuka. Three villages named Kadipur exist in Ahmadabad district (Viramgam 511514, Dholka 511725, Dhandhuka 511927); the Dhandhuka one was chosen because it sits inside the contiguous DSIRDA village code block 511924-511941. This is a judgement on locality, not an exact-identifier match.
• Mixed vintage inside one publication: the population and household counts are Census 2011 enumeration, but the amenity columns carry Reference Year 2009 (source column 13, value 2009 for all 18,225 Gujarat villages). Amenity presence therefore describes 2009 field conditions published under Census 2011.
• The data is 15 to 17 years old as of the 2026-08-04 extraction date. Nothing built after 2009-2011 is present: no Tata semiconductor fab, no Dholera international airport, no Ahmedabad-Dholera expressway, no SIR trunk infrastructure, no activation-area roads or utilities. Absence of an amenity in this dataset is NOT evidence of absence today.
• This sheet is the Village Directory only. It contains no literacy, no worker/workforce, no age or religion breakdown; those live in the Primary Census Abstract, which is not present in this workbook (workbook sheets are Village_Data_2400, Hamlet_Data_2400, Misc_Information only).
• No geographic coordinates, no village boundary geometry and no survey-number level data are present in the source.
• Blank cells in the source are emitted as null and are NOT interpolated. The workbook's Misc_Information sheet documents only one abbreviation: 'NA: Not Applicable'. Blank versus 0 versus 'N.A.' distinctions are preserved exactly as found.
• Village-level land-use hectare columns (379-394) are blank for a number of villages in the source; no totals were reconciled or back-filled.
• The 24 Barwala taluka villages outside the DSIRDA boundary list, and all Ranpur/Dholka taluka villages, were deliberately not extracted. They are available in the same source if the scope is later widened.
• The DSIRDA boundary village list was read from the label layer of dsirda_villages_map.pdf (single page, 22 village labels). The PDF itself carries no date of issue, so the currency of that boundary list cannot be established from the document.
• 28 of the 396 columns are blank for all 72 villages in the source and are emitted as null throughout: cols 22-23 (outside-State nearest town), 53 and 130 (nearest-facility status for the middle-school and 'education others' blocks), 209-210 (treated tap water year-round / summer functioning), 227-228 (spring functioning), 257-258 (post and telegraph office), 260, 267, 273, 286-287, 291, 303, 309, 313, 323, 337, 353 (follow-up distance-range codes left blank where the primary status column already answers), and 371-378 (manufacturers and handicrafts commodities, blank for every village here). These are empty in the Census source, not lost in extraction, and were not filled.
• This dataset carries no price, land-rate, project, developer or return figure of any kind. The Census Village Directory contains none, and none was imported from any other source.

Gaps declared by the health and education extraction

• level_or_class_range is null for all 55 schools. UDISE+ is the only authority that publishes it and its school search is CAPTCHA-gated (see the udise_plus_gating block). It was NOT inferred from school names: 'Kanya Shala', 'Primary School' and 'Uttar Buniyadi' hint at a level but do not establish a class range.
• enrolment_or_beds is null for all 55 schools. Same CAPTCHA gate. No other retrieved source carries enrolment.
• management is null for all 55 schools. Neither the Government of Gujarat table nor the aggregator has a management column, so no school is marked govt, private or aided. The aggregator only says its cluster pages 'include all private and govt. schools'.
• enrolment_or_beds is null for all 9 PHCs: the Gujarat PHC list has no bed column. Bed counts exist only for the 3 CHCs.
• 49 of the 55 schools rest on a third-party aggregator alone and are tagged data_class=REPORTED, operating_status=LISTED_UNVERIFIED, publishable_as_operating=false. Do not publish them in the present tense. Only 6 are confirmed by a government document.
• The 6 government-confirmed schools come from a laptop-upgrade tender annexure, which enumerates only schools receiving that hardware. 6 is a FLOOR for Dholera block, not the block total, and the block total is not established by any source retrieved.
• No as_of_date for any school record. The Government of Gujarat table carries no printed as-on date (PDF created 2018-12-17; the origin URL path contains '2019'), and the aggregator states no reference year anywhere.
• SUB-CENTRES: no named, current list of health sub-centres for Dholera taluka was found. Rural health statistics publish district totals, not facility names. The sibling dataset census-amenities.json carries per-village sub-centre presence, but from Census 2011 with an internal amenity reference year of 2009, roughly 17 years stale.
• PRIVATE health and education facilities are entirely absent. Every source used here is a government enumeration of government facilities. Private clinics, private hospitals and private schools in the Dholera area are not covered, so an absence in this dataset is not evidence that none exists.
• STALENESS: the health picture is as on 15-08-2018 (PHCs) and 30-06-2021 (CHCs). Neither list has been reissued in a form retrieved here. A PHC could have been added, upgraded or closed since. Present-tense publication should say 'as of the last state list, dated X'.
• CLUSTER DISCREPANCY, unresolved: the live UDISE+ register for 2025-26 returns 5 clusters for Dholera block (BHADIYAD, DHOLERA, HEBATPUR, PIPLI, SANDHIDA). The aggregator lists 6, including a KAMIYALA cluster carrying 7 schools. Either the aggregator is stale or Kamiyala was merged. The 7 Kamiyala schools are retained as REPORTED with their aggregator cluster recorded verbatim; their villages still resolve against the official UDISE+ village register.
• The multi-speciality hospital's construction status is NOT resolved. DSIRDA's own site places it under Upcoming Projects in the future tense with no operator, capacity or date. PHASE0-RAW-FINDINGS.md separately records a media report (deshgujarat.com, 6 Feb 2026) of a DICDL tender to operate an ALREADY-CONSTRUCTED hospital, with bed counts reported inconsistently as 100 and 200. That media claim was not re-verified in this session and is deliberately NOT a record here. Resolving it needs the DICDL tender document.
• No facility-level geocoordinates, contact numbers, staffing or opening hours are in any source used, so none are emitted.
• Village name spellings differ between sources and were NOT normalised: the PHC list prints 'Bhadiyad' and 'Pipli' while the UDISE+ village register prints 'BHYADIYAD' and 'PIPALI'. Each record keeps its own source's spelling; village_as_printed is preserved where the official school table differs.

Gaps declared by the village register

• name_gujarati is null for all 22 villages. No source document available to this extraction carries Unicode Gujarati village names. The DSIRDA map, the 2009 gazette schedule, the TP scheme maps and the census sheet are all Latin-script only. The jantri PDFs embed Gujarati in a legacy non-Unicode font that extracts as mojibake, so nothing there could be read reliably. Gujarati names were NOT transliterated or guessed.
• The Dholera taluka village list could not be established. Dholera taluka postdates the 2011 Census (which has no Dholera sub-district under Ahmadabad district 474), and no post-2015 government taluka village directory is present in the source set. NICDC states the 22 SIR villages are "of Dholera Taluka" (nicdc_cleanroom.pdf p.8) but that is not an enumeration, and it does not exclude the taluka containing further villages. This list is emitted EMPTY on purpose.
• Part-village land shares are unknown. Every TP/DTPS scheme declares "PART VILLAGES", meaning only a portion of each village falls inside. No source gives the hectares or percentage of each village inside each scheme, so no village can be described as wholly inside the Activation Area.
• Draft TP Schemes 2, 4, 5 and 6 have no village list. Only dtps1.pdf and dtps3.pdf are present in the source set; the DSIRDA site nav lists DTPS No.1 to No.6 and preliminary schemes 1A1, 1A2, 2B1, 2B2, 2B3, 3A, 3B, 4B1, 5A, 5B, 6A, none of which were available. Village membership of those schemes is therefore unknown.
• notif_dtps1.pdf does not name the DTPS-1 villages. The captured gazette page (323-1) ends mid-sentence at "Apex Authority (GIDB) hereby." and the schedule page is not in the file. The four DTPS-1 part villages come from the dtps1.pdf map legend instead.
• The 2009 notified SIR area (879.3377 sq km) and the current DSIRDA/NICDC figure ("about 920 sq. kms") differ by roughly 41 sq km. No source document explains the difference and no boundary-variation notification was available, so it is flagged, not reconciled.
• The gazette area column sums to 879.3379 against a printed total of 879.3377, i.e. the 22 rows exceed the printed total by 0.0002 sq km. The discrepancy is in the source document itself. Every cell was re-read at 340-700 dpi and no misreading was found; the survey-number column, by contrast, sums exactly to the printed 14574.
• Village-level population, area and amenity data from the census sheet were not extracted; this dataset carries only codes, names and the SIR schedule figures.
• Census codes are Census of India 2011 codes. Village codes are re-issued between censuses, so these must not be presented as current LGD (Local Government Directory) codes. No LGD codes were available.

Caveats on the village register

• Three different lists are emitted separately and MUST NOT be merged: the 2009 SIR notified area (22 villages), the Activation Area (4 part villages), and Dholera taluka (not established, empty).
• name_english uses the 2009 gazette spelling because that is the legal instrument. The DSIRDA map and the census spell three of them differently; all variants are carried in name_variants so any of the ten sites can match either spelling.
• All figures tagged OFFICIAL come from a government document. Nothing in this dataset is REPORTED or TARGET.
• The 2009 schedule is the notification as originally published. If the SIR boundary was later varied by a further notification, that document was not available and this dataset would not reflect it.

How to correct us

Write to corrections@dholera.life naming the page, the figure and the document that contradicts it. A correction needs a source: a gazette page, a departmental list, a UDISE+ record. Corrections are applied against the document, the changed figure keeps its new source in the visible table foot, and the build date at the bottom of every page moves. Opinions about Dholera, in either direction, are not corrections and will not change a number here.

This site publishes no price, no land rate, no project, no developer and no forecast, because none of the three datasets behind it carries any. Nothing was imported from any other source to fill that space.