Official referenceenabled request time beta
Photon OpenStreetMap geocoder
User-requested place search for map navigation, never a safety assessment or verified directory record.
- Coverage
- Worldwide OpenStreetMap search data; Aamegh restricts public responses to India.
- Refresh
- Request-time beta with a six-hour process-local cache. Use a dedicated/self-hosted service before high traffic.
Review data handling
Owner: Photon contributors and OpenStreetMap contributors; public demo infrastructure is operated by Komoot.
Access: Server-side public Photon endpoint with an identifying User-Agent, bounded India query, cache, and rate limits.
Licence: Photon software is Apache-2.0; returned OpenStreetMap data is ODbL and requires OpenStreetMap attribution.
Allowed fields- OSM object reference
- display name
- broad address label
- coordinate
- place type
Never collect or publish- OSM contributor metadata
- raw upstream payload
- persistent query history
- search result presented as verified or safe
Approved database pathNo persistence by default.
Publication rule: Return a minimal navigation result only. It cannot create a score, support listing, safe place, or durable database record.
Map and infrastructurecredentials required
Mappls Maps
Place search and geocoding for a user-requested query, not a durable public directory.
- Coverage
- India-first; the provider documents global geocoding support.
- Refresh
- Request-time only. It is not an ingestion feed or a source-of-record refresh schedule.
Review data handling
Owner: Mappls
Access: Server-side Geocoding API with an access token; restrict the token by approved server IP or domain.
Licence: Commercial provider terms apply; persistent storage requires an explicit contract review.
Allowed fields- provider place identifier
- display name
- formatted address
- coordinate needed for the current search result
Never collect or publish- access token
- unreviewed provider response payload
- provider data retained beyond contract terms
Approved database pathNo persistence by default.
Publication rule: Return only a minimal search response. Do not treat search results as a verified organisation or safe-place listing.
Map and infrastructurecredentials required
Google Maps Platform
Optional global autocomplete fallback for a user-requested place search.
- Coverage
- Global.
- Refresh
- Request-time only. It is not a bulk directory or ingestion feed.
Review data handling
Owner: Google Maps Platform
Access: Server-side Places Autocomplete request with an API key, billing, API restrictions, and a session token where applicable.
Licence: Google Maps Platform terms apply; field minimisation and provider storage limits must be observed.
Allowed fields- provider place identifier
- display label
- structured secondary label
- place types needed for the current search result
Never collect or publish- API key
- unreviewed provider response payload
- persistent provider data outside approved terms
Approved database pathNo persistence by default.
Publication rule: Use only as a minimal search proxy. A provider suggestion never bypasses Aamegh verification or publication rules.
Map and infrastructurepreview dataset superseded pipeline available
OpenStreetMap data via Overpass
Candidate public infrastructure context, such as public amenities and transport features, for human review.
- Coverage
- Worldwide.
- Refresh
- Only an approved scheduled import with query bounds, caching, rate limits, and a recorded source timestamp.
Review data handling
Owner: OpenStreetMap contributors; public Overpass instances are shared community infrastructure.
Access: Bounded Overpass query for a reviewed city/category scope. Use a regional extract, managed service, or self-hosted service at scale.
Licence: Open Database License (ODbL) 1.0. Attribution, licence notice, and produced-work or derivative-database review are required.
Allowed fields- public feature identifier
- name
- category
- public opening-hours tag
- public website tag
- candidate coordinate for verification
Never collect or publish- OSM contributor identity
- changeset/user metadata
- direct browser-to-Overpass traffic
- unreviewed location publication
Approved database pathdata_sources, data_import_runs, verification_cases, organizations, safe_places, entity_sources
Publication rule: A candidate must be deduplicated, attributed, verified, and explicitly published. Never proxy map movement to a public Overpass instance.
Official referencepublished source context not score eligible
OpenStreetMap India bulk extract via Geofabrik
Viewport-bounded public infrastructure context at India scale without country-sized Overpass requests.
- Coverage
- India extract boundary; source completeness varies by place and category.
- Refresh
- Reviewed scheduled PBF refresh. Pin the resolved file timestamp, MD5, SHA-256, record counts, and category counts.
Review data handling
Owner: OpenStreetMap contributors; India extract distributed by Geofabrik.
Access: Checksum-verified India PBF bulk download, offline allowlist extraction, and draft-first batch import.
Licence: Open Database License (ODbL) 1.0. OpenStreetMap attribution and derivative-database obligations apply.
Allowed fields- public OSM object reference
- allowlisted infrastructure category
- name
- representative coordinate
- opening hours
- operator
- wheelchair tag
Never collect or publish- OSM contributor identity
- uid
- changeset
- object timestamp
- contact or phone fields
- Aamegh reports
- automatic safety scores
Approved database pathdata_sources, source_dataset_versions, source_context_observations, data_import_runs
Publication rule: Import every batch as draft. Publish the dataset and all its points only after checksums and complete record/category counts reconcile.
Official referencereviewed candidate not imported
Delhi Open Transit Data
Authority-published timetable and vehicle-position input for a future Delhi journey-routing graph.
- Coverage
- Delhi bus services and separately published DMRC static data; no coverage outside Delhi is implied.
- Refresh
- Feed metadata is checked before every graph build. Static and real-time feeds are versioned independently.
Review data handling
Owner: Department of Transport, Government of NCT of Delhi, in association with IIIT-Delhi.
Access: Static GTFS download; real-time vehicle positions require an authorised private key and acceptance of the current terms.
Licence: Delhi Open Transit Data terms apply. Terms, permitted use, attribution, and credential handling require release-specific review.
Allowed fields- agency
- route
- trip
- stop
- stop time
- calendar
- reviewed vehicle position
- feed timestamp
Never collect or publish- private access key
- registration details
- raw access logs
- coverage claims outside Delhi
- safety ranking inferred from transit availability
Approved database pathdata_sources, transit_feed_versions, journey_routing_publications, data_import_runs, cities
Publication rule: A feed version may power routing only after validation, source review, graph-build checks, and an explicit city-scoped routing publication.
Official referenceresource selection and access review required
India Urban Data Exchange
Discover city-authority mobility, utility, and civic datasets for resource-by-resource review.
- Coverage
- Participating Indian cities and onboarded resources only; resource availability and access policy vary by provider.
- Refresh
- Resource-specific. Re-check catalogue metadata, provider, access type, APIs, and observed freshness before each import.
Review data handling
Owner: India Urban Data Exchange, a Ministry of Housing and Urban Affairs initiative implemented by IISc Bengaluru.
Access: Catalogue discovery is separate from resource access. A resource can be open or secure, and secure resources require provider consent and an access token.
Licence: The selected resource provider's access policy, licence, consent, attribution, and retention terms are authoritative.
Allowed fields- catalogue metadata
- provider-approved aggregate observation
- public infrastructure status
- resource timestamp
- broad city geography
Never collect or publish- secure resource without consent
- camera or video feed
- vehicle or person tracking history
- device identifier
- precise participant movement
- automatic safety score
Approved database pathdata_sources, source_dataset_versions, data_import_runs, source_context_observations, transit_feed_versions, civic_actions, civic_action_events
Publication rule: Discovering a resource never publishes it. Only provider-authorised, minimised, broad, attributable outputs may enter a public projection.
Official referencecity deployment and authority agreement required
UPYOG Municipal Grievance Redressal
Source attributable, broad civic-action status after an authority confirms a public integration contract.
- Coverage
- Only a state or urban local body deployment that explicitly exposes an approved interface; UPYOG is not one nationwide grievance-record feed.
- Refresh
- Authority-specific event or scheduled status refresh with stale-record expiry and reconciliation.
Review data handling
Owner: National Urban Digital Mission / National Institute of Urban Affairs under the Ministry of Housing and Urban Affairs.
Access: City/state deployment API and data-access terms must be obtained from the responsible authority; the open reference implementation is not production data access.
Licence: Platform code and knowledge standards do not grant rights to a city's operational grievance records. The deploying authority's data terms control use.
Allowed fields- public authority reference
- broad issue category
- broad area
- public status
- status timestamp
- attributable source URL
Never collect or publish- complainant identity
- phone
- email
- free-text complaint
- exact address
- private attachment
- officer personal data
Approved database pathdata_sources, data_import_runs, civic_actions, civic_action_events, areas, safety_indicator_cells
Publication rule: Publish only a broad, attributable status ledger after authority review. Never republish the originating complaint or identify the complainant.
Area contextresource allowlist required
Open Government Data Platform India
Official aggregate context and official directory candidates after a resource-level review.
- Coverage
- India; coverage, fields, granularity, and availability are resource-specific.
- Refresh
- Read the resource metadata at every import; cadence is dataset-specific.
Review data handling
Owner: Government of India Open Government Data Platform (data.gov.in).
Access: Catalog/download and some resource-specific APIs. A catalog listing does not guarantee an API endpoint.
Licence: Record the resource-specific licence and attribution. Government Open Data License - India terms may apply where the resource identifies it.
Allowed fields- resource-approved aggregate metrics
- official directory fields
- resource identifier
- release date
- source attribution
Never collect or publish- personal identifiers
- exact incident records
- any field outside the reviewed allowlist
- credential values
Approved database pathdata_sources, data_import_runs, verification_cases, entity_sources, population_baselines
Publication rule: Treat each resource as an independent contract. Import into a review queue first and never publish directly from a catalog or API response.
Area contextreviewed historical baseline not imported
Census of India 2011 data and District Census Handbooks
Population denominators and historical town or village amenity context, never current service availability.
- Coverage
- India at published State, district, subdistrict, village, town, and selected ward geographies.
- Refresh
- Reference-year baseline. Every display must identify 2011 and must not imply current conditions.
Review data handling
Owner: Office of the Registrar General and Census Commissioner, India.
Access: Official tables, Data API, Population Finder, and downloadable District Census Handbooks.
Licence: Record the terms and attribution of the selected Census table or publication before reuse.
Allowed fields- published population
- official geography code
- town or village amenity count
- reference year
- table identity
Never collect or publish- current availability claim
- person or household microdata
- silent mapping to a newer boundary
- safety score from amenity presence
Approved database pathdata_sources, source_dataset_versions, population_baselines, data_import_runs, districts, cities
Publication rule: Publish only as a dated baseline at its source geography. Never describe a 2011 amenity as presently open or available.
Area contextresource selection required
NITI Aayog National Data and Analytics Platform
Selected district or State socioeconomic, health, and access indicators with standardized metadata.
- Coverage
- India; geography and time coverage vary by selected government dataset.
- Refresh
- Dataset-specific; pin the NDAP dataset, reference period, retrieval date, and checksum.
Review data handling
Owner: NITI Aayog, Government of India.
Access: Search, combine, visualize, and download selected government datasets; each selected dataset needs its own review.
Licence: Dataset-owner terms and NDAP attribution for the selected download are authoritative.
Allowed fields- aggregate indicator
- published geography
- reference period
- unit
- dataset owner and citation
Never collect or publish- person-level records
- incompatible geography joins
- undocumented composite score
- indicator presented as a safety verdict
Approved database pathdata_sources, source_dataset_versions, source_context_observations, research_datasets, data_import_runs
Publication rule: A selected indicator remains aggregate context and may not be combined into an area rating without a separately reviewed methodology.
Area contextcapture and draft import pipeline ready
MoRTH Road Accidents in India
City-level road-accident, killed, and injured context for journey preparation, not street-level risk prediction.
- Coverage
- India with published State/UT and million-plus city tables; table coverage varies by annual report.
- Refresh
- Annual report; record both report year and each table's reference year.
Review data handling
Owner: Ministry of Road Transport and Highways, Government of India.
Access: Downloadable annual official report with table-level extraction and checksum validation.
Licence: Official publication terms and MoRTH attribution require review for the selected table.
Allowed fields- aggregate accidents
- persons killed
- persons injured
- published city or State geography
- reference year
Never collect or publish- crash victim details
- invented street blackspot
- city total assigned to a locality
- road safety guarantee
Approved database pathdata_sources, source_dataset_versions, road_safety_aggregates, source_freshness_checks, data_import_runs, cities
Publication rule: Keep every value at the geography MoRTH published and label it as annual recorded road-accident context.
Area contextresource selection required
Health Management Information System
District health-service capacity context alongside separately verified facility listings.
- Coverage
- India; reporting availability and geography vary by indicator and period.
- Refresh
- Indicator-specific; retain reporting period, retrieval date, completeness note, and checksum.
Review data handling
Owner: Ministry of Health and Family Welfare, Government of India.
Access: Official HMIS publications and specifically approved aggregate downloads.
Licence: Selected publication or resource terms and MoHFW attribution must be reviewed.
Allowed fields- aggregate health-service indicator
- district or State
- reporting period
- unit
- source note
Never collect or publish- patient data
- facility currently-open claim
- clinical advice
- health capacity converted into a safety rating
Approved database pathdata_sources, source_dataset_versions, source_context_observations, research_datasets, data_import_runs
Publication rule: Present only dated aggregate capacity context. Verify any actionable facility record through a separate directory workflow.
Area contextresearch review only
MoSPI Microdata Library
Research design and aggregate analysis, including gender and time-use evidence, outside the public operational map.
- Coverage
- India; survey samples and release terms vary by catalog item.
- Refresh
- Release-specific research snapshot with immutable analysis inputs and disclosure review.
Review data handling
Owner: Ministry of Statistics and Programme Implementation, Government of India.
Access: Catalog resources and downloads subject to the selected survey's access and use terms.
Licence: The selected survey's data-access and citation terms control use; catalog visibility alone is not publication permission.
Allowed fields- survey documentation
- approved research microdata
- derived aggregate statistics
- citation
- methodology
Never collect or publish- respondent-level publication
- re-identification
- operational map points
- small-cell output
- individual prediction
Approved database pathdata_sources, research_datasets, data_import_runs
Publication rule: Keep restricted research inputs outside public-serving tables and release only disclosure-reviewed aggregate findings.
Area contextpublished source context not score eligible
NCRB Crime in India 2023 State/UT and 2024 metropolitan context
Population-normalised, aggregate crime context for methodology review. It is not an incident map or a safety certification.
- Coverage
- All India, 28 States and 8 Union Territories from 2023 Table 1A.3; 19 metropolitan cities from 2024 Table 1B.3.
- Refresh
- Annual release context; do not describe it as a live crime feed. Capture release year and catalog update date for every import.
Review data handling
Owner: National Crime Records Bureau, Ministry of Home Affairs, Government of India.
Access: Checksum-pinned reviewed report/download. The 2024 extracted table is retained from the reviewed OpenCity distribution because the official catalog does not provide a stable API for every resource.
Licence: Resource-specific government publication terms with NCRB attribution; the reviewed OpenCity 2024 distribution is marked Other (Public Domain).
Allowed fields- aggregate count
- crime category
- official reporting geography
- release/reference year
- published source metadata
Never collect or publish- incident-level rows
- victim or accused data
- exact locations
- unmapped police-district data
- State/UT aggregates assigned to a locality
Approved database pathdata_sources, source_dataset_versions, source_context_observations, data_import_runs, states, cities
Publication rule: Publish at the source geography only, beside its denominator and NCRB comparison warning. A separate methodology and approval are mandatory before any score use.
Area contexthistorical reference only
District-wise crimes committed against women (historical)
Historical methodology and trend research only. It is not eligible for a current city or locality indicator.
- Coverage
- India; historical police-district and special-police-unit reporting geography.
- Refresh
- Historical dataset, not a current operational feed.
Review data handling
Owner: Government of India Open Government Data Platform.
Access: Catalog/download after historical-research review.
Licence: Record the source-page licence and attribution before any research use.
Allowed fields- historical aggregate trend values
- published reporting geography
- reference year
- source citation
Never collect or publish- current safety scores
- locality-level claims
- unreviewed police-to-administrative mappings
Approved database pathdata_sources, data_import_runs, research_datasets
Publication rule: Do not use this source to rank, label, or describe any current area as safe or unsafe.
Area contextsource selection required
India official population baseline
Population denominator provenance for eligible aggregate comparisons.
- Coverage
- India; the reviewed Ministry of Statistics source is state-level projection context, not a Bengaluru-locality denominator.
- Refresh
- Reference-year based, not a live feed. Record the publication and projection year per baseline.
Review data handling
Owner: Ministry of Statistics and Programme Implementation / National Commission on Population source material.
Access: Reviewed official publication/download. Select a source only when its geography and reference year match the proposed metric.
Licence: Record the official publication terms, reference, and attribution for the chosen table or release.
Allowed fields- population
- reference year
- geography level
- methodology
- official source citation
Never collect or publish- individual-level data
- synthetic locality denominator presented as official
- a state projection used as a city/locality value
Approved database pathdata_sources, population_baselines, data_import_runs, verification_cases
Publication rule: Do not normalize a local metric until a compatible official denominator and geography mapping have been approved.
Support and referralsmanual verification required
National Legal Services Authority directory
Verify legal-aid referral information and direct users to an official source, not bulk scrape a directory.
- Coverage
- India.
- Refresh
- Manual re-verification before publication and on a documented recurring schedule.
Review data handling
Owner: National Legal Services Authority, Government of India.
Access: Manual source check and direct organisation confirmation.
Licence: Directory terms and attribution require review before copying any listing data.
Allowed fields- organisation name
- public service category
- public official contact route
- jurisdiction
- source URL and verification date
Never collect or publish- case details
- beneficiary data
- unverified phone or address data
- directory scraping at scale
Approved database pathdata_sources, organizations, organization_services, entity_sources, verification_cases
Publication rule: Publish a referral only after verification. Include a legal-information disclaimer and never imply legal representation or availability.
Support and referralscaptured draft verification required
Government One Stop Centre directory material
Candidate support-directory entries for verified referrals; it is not a blanket safe-place certification.
- Coverage
- India; official documents describe functional One Stop Centres.
- Refresh
- Check the official document version and verify the service directly before publication and at each scheduled review.
Review data handling
Owner: Ministry of Women and Child Development, Government of India.
Access: Checksum-pinned extraction of the downloadable 769-centre document, followed by direct service verification before any listing is published.
Licence: Government document terms and attribution require review before reuse.
Allowed fields- centre identity
- official State/UT and district labels
- public address
- scheme service categories
- source version and retrieval date
Never collect or publish- later PDF personal contact tables
- client/case data
- unverified hours or phone
- coordinates inferred from address
- safe-place claim without separate review
Approved database pathdata_sources, source_dataset_versions, data_import_runs, organizations, organization_services, entity_sources, verification_cases
Publication rule: Only publish a verified referral. A One Stop Centre record may not be labelled a safe place unless it separately meets that policy.
Support and referralscaptured stale aggregate only
Shakti Sadan State-wise directory
Identify government or NGO-operated support-home candidates for women in distress and trafficking survivors.
- Coverage
- India where the Ministry's current State-wise list reports a Shakti Sadan.
- Refresh
- Check for a newer State-wise document and directly confirm every proposed listing before publication.
Review data handling
Owner: Ministry of Women and Child Development, Government of India.
Access: Checksum-pinned capture of the State/UT aggregate dated 31 March 2024. It contains no named homes; reuse and current-operation review remain required.
Licence: Government page and document terms require a resource-specific reuse decision; download availability is not automatic republication permission.
Allowed fields- home identity
- implementing agency type
- State/district label
- public official contact route
- source version
Never collect or publish- resident or survivor data
- bed availability without confirmation
- personal staff contact
- precise map point without access review
- safe-place certification
Approved database pathdata_sources, source_dataset_versions, data_import_runs, organizations, entity_sources, verification_cases
Publication rule: Treat every row as a non-public candidate until the responsible operator confirms identity, services, contact route, and current operation.
Support and referralscaptured stale aggregate only
Sakhi Niwas functional working women hostel directory
Candidate housing-support references for working women, kept separate from safety and vacancy claims.
- Coverage
- India where the published State/UT-wise 12 April 2024 document lists a functional hostel.
- Refresh
- The known document is dated 12 April 2024; suppress current claims until a fresh direct verification exists.
Review data handling
Owner: Ministry of Women and Child Development, Government of India.
Access: Checksum-pinned capture of the State/UT aggregate dated 12 April 2024. It contains no named hostels; current operation, vacancy, operator consent, and reuse terms remain unverified.
Licence: Government page and document terms require a resource-specific reuse decision.
Allowed fields- hostel identity
- State/district label
- operator
- dated source reference
- verified public enquiry route
Never collect or publish- resident data
- unconfirmed vacancy
- safe accommodation claim
- personal staff contact
- inferred coordinates
Approved database pathdata_sources, source_dataset_versions, data_import_runs, organizations, entity_sources, verification_cases
Publication rule: A dated hostel listing is not evidence of current vacancy, quality, or safety. Publish only a verified enquiry pathway with an expiry.
Official referencestatic reference only
India Emergency Response Support System 112
Provide the official emergency-service direction in urgent-help guidance. Aamegh does not dispatch emergency help.
- Coverage
- India.
- Refresh
- Manual content review before publish and whenever official guidance changes.
Review data handling
Owner: Emergency Response Support System, Government of India.
Access: Official public website reference; no Aamegh ingestion or dispatch integration is planned.
Licence: Use only the reviewed public emergency reference and official attribution.
Allowed fields- official emergency number
- official scope statement
- official URL
- Aamegh non-dispatch disclaimer
Never collect or publish- caller data
- emergency requests
- implied dispatch status
- unofficial service availability claims
Approved database pathdata_sources, resources, entity_sources, verification_cases
Publication rule: Urgent-help screens must direct users to official emergency services and must never imply that Aamegh contacts them.
Official referenceofficial gateway live partner feed required
National Career Service
Direct people to the official national job, job-fair, career-guidance and training gateway while a governed data-sharing route is negotiated.
- Coverage
- India; individual vacancy coverage and freshness are controlled by the National Career Service portal.
- Refresh
- Request-time official handoff until a reviewed feed exists; then use source timestamps, expiry and daily stale-record checks.
Review data handling
Owner: Ministry of Labour and Employment, Government of India.
Access: Official public search deep-link now. Machine ingestion requires a documented NCS API, MoU or data-sharing agreement; Aamegh does not scrape the search pages.
Licence: Portal terms and any data-sharing agreement control reuse. Preserve NCS attribution and its no-fee/fraud warning.
Allowed fields- official vacancy reference
- job title
- employer display name
- district/state
- work mode
- expiry
- official apply URL
- source timestamp
Never collect or publish- jobseeker profiles
- contact details
- credentials
- automated application
- unreviewed vacancy text
- scraped search-result pages
Approved database pathdata_sources, data_import_runs, jobs, opportunity_locations, opportunity_source_snapshots, skills
Publication rule: Deep-link to NCS until a governed feed exists. An imported vacancy must pass the Aamegh source-snapshot and verification gates and must retain the official application destination.
Official referenceofficial gateway live partner feed required
Apprenticeship India
Provide an official apprenticeship discovery route for district and early-career opportunity journeys.
- Coverage
- India; apprenticeship availability is controlled by the official portal and participating establishments.
- Refresh
- Official handoff now; source-defined refresh and expiry reconciliation after integration approval.
Review data handling
Owner: Ministry of Skill Development and Entrepreneurship, Government of India.
Access: Official public portal handoff. No stable public vacancy API has been approved for Aamegh; automated access requires provider agreement.
Licence: Portal terms and an approved integration agreement control any vacancy reuse.
Allowed fields- official apprenticeship reference
- establishment name
- trade
- district/state
- stipend disclosure
- duration
- official apply URL
- source timestamp
Never collect or publish- candidate identity
- application records
- credentials
- unverified establishment contacts
- scraped listings
Approved database pathdata_sources, data_import_runs, jobs, opportunity_locations, opportunity_source_snapshots, skills
Publication rule: Keep the official portal as application system of record. Aamegh may expose only reviewed metadata and an attributable handoff.
Official referenceofficial gateway live partner feed required
Skill India Digital Hub
Connect work discovery to official skilling, reskilling and certification pathways without copying candidate data.
- Coverage
- India; course and programme availability is controlled by Skill India Digital Hub and its approved providers.
- Refresh
- Official handoff now; provider-defined schedule with course closure and centre re-verification after approval.
Review data handling
Owner: Ministry of Skill Development and Entrepreneurship, Government of India.
Access: Official public portal handoff. Course ingestion requires an approved API or provider export and resource-level terms.
Licence: Portal/provider terms govern course metadata and marks; candidate records are outside Aamegh's public-data scope.
Allowed fields- official course reference
- course title
- provider
- district/state
- format
- duration
- official enrolment URL
- source timestamp
Never collect or publish- learner identity
- assessment records
- certificates
- credentials
- unreviewed course claims
Approved database pathdata_sources, data_import_runs, jobs, opportunity_locations, opportunity_source_snapshots, skills
Publication rule: Publish a course pathway only with attributable source evidence and keep enrolment on the official/provider destination.
Official referenceofficial gateway live reference only
myScheme
Help people discover official employment, skilling, enterprise and livelihood schemes without Aamegh collecting eligibility profiles.
- Coverage
- India; Central and State/UT scheme discovery, with eligibility and application details maintained by the official platform and scheme owners.
- Refresh
- Request-time handoff with quarterly source review until a documented machine interface is approved.
Review data handling
Owner: Digital India Corporation, Ministry of Electronics and Information Technology, Government of India.
Access: Official discovery deep-link. Aamegh does not proxy the eligibility questionnaire or retain answers.
Licence: Platform and individual scheme-owner terms apply; keep the official source and application route authoritative.
Allowed fields- scheme name
- owning ministry
- public category
- state/UT applicability
- official scheme URL
- last reviewed date
Never collect or publish- demographic profile
- income
- social category
- eligibility answers
- application records
- credentials
Approved database pathdata_sources, entity_sources, jobs, opportunity_source_snapshots
Publication rule: Use myScheme as the eligibility and application authority; Aamegh may provide a contextual handoff but must not assert eligibility.
Official referenceofficial gateway live reference only
e-Shram employment schemes
Surface official rural and unorganised-worker scheme pathways without accessing the e-Shram worker registry.
- Coverage
- India; public employment and social-security scheme information for unorganised workers.
- Refresh
- Quarterly official-page review and immediate correction when a scheme owner changes guidance.
Review data handling
Owner: Ministry of Labour and Employment, Government of India.
Access: Official public scheme-reference handoff only. Worker registration and personal records remain entirely outside Aamegh.
Licence: Government website terms and each linked scheme's terms apply.
Allowed fields- scheme name
- public eligibility summary
- public benefit summary
- official URL
- review date
Never collect or publish- e-Shram registration data
- UAN
- Aadhaar
- worker identity
- beneficiary or application status
Approved database pathdata_sources, entity_sources, jobs, opportunity_source_snapshots
Publication rule: Only public scheme information may be reviewed for display. Never ingest or infer worker registration, eligibility or benefit status.
Official referenceofficial gateway live dataset contract required
Kaushal Bharat: DDU-GKY and RSETI
Make rural training and livelihood pathways discoverable by district after centre and course data are formally approved.
- Coverage
- India; rural training centres, courses and programme information maintained by the Ministry of Rural Development platform.
- Refresh
- Official handoff now; centre/course refresh and closure reconciliation after a reviewed integration is available.
Review data handling
Owner: Ministry of Rural Development, Government of India.
Access: Official public portal and reports. Structured centre/course reuse requires a documented download/API contract and field review.
Licence: Official publication and platform terms apply; programme and centre claims require source attribution and freshness evidence.
Allowed fields- programme
- training centre
- course/trade
- district/state
- public provider
- official URL
- source timestamp
Never collect or publish- candidate rows
- assessment data
- placement records linked to people
- DBT data
- private inspection material
Approved database pathdata_sources, data_import_runs, jobs, opportunity_locations, opportunity_source_snapshots, skills
Publication rule: Publish only current, attributable programme or centre metadata; never expose candidate-level training, payment or placement records.
Official referenceofficial gateway live context only
Mahatma Gandhi NREGA official portal
Explain and link the official rural employment pathway while preserving the distinction between programme entitlement and vacancies.
- Coverage
- Rural India with State, district, block and panchayat reporting; it is a demand-driven statutory programme, not a conventional vacancy feed.
- Refresh
- Official handoff now; aggregate reporting cadence is report-specific and must be recorded per import.
Review data handling
Owner: Ministry of Rural Development, Government of India.
Access: Official portal handoff and reviewed aggregate reports only. Aamegh does not retrieve job cards, muster rolls or worker-level records.
Licence: Official report terms and Government attribution apply to any approved aggregate use.
Allowed fields- public scheme guidance
- aggregate State/district/block context
- report period
- official URL
- source timestamp
Never collect or publish- job card details
- worker identity
- muster rolls
- wages linked to a person
- bank data
- vacancy claims
Approved database pathdata_sources, data_import_runs, research_datasets, districts, blocks
Publication rule: Present MGNREGA as an official scheme pathway and aggregate context, never as a scraped job listing or person-level work record.
Official referenceapproved ingestion available
Local Government Directory
Provide stable district and block identifiers for nationwide opportunity discovery and source reconciliation.
- Coverage
- India; official State, district, sub-district, development-block, village and local-body codes.
- Refresh
- Check live resource metadata monthly; store both catalog and row-reported dates and never substitute retrieval time for source freshness.
Review data handling
Owner: Ministry of Panchayati Raj, Government of India; maintained with States/UTs and hosted by NIC.
Access: Allowlisted OGD resources a71e60f0-a21d-43de-a6c5-fa5d21600cdb, 37231365-78ba-44d5-ac22-3deec40b9197, and 6be51a29-876a-403a-a6da-42fde795e751 using a server-side data.gov.in key.
Licence: Government Open Data License - India, with Ministry of Panchayati Raj and data.gov.in attribution.
Allowed fields- official geography code
- name
- parent code
- entity type
- active status
- source update date
Never collect or publish- contact details
- operator credentials
- CAPTCHA bypass
- synthetic code assignments
Approved database pathdata_sources, data_import_runs, states, districts, blocks
Publication rule: Apply only reconciled active names and codes after an explicit reference-data review; never infer a missing administrative relationship or claim a newer source date than the payload reports.
Official referenceapproved ingestion available
All India PIN Code Directory
Support optional PIN-based opportunity discovery without treating a PIN code as a precise user location.
- Coverage
- India Post offices and six-digit PIN codes with State and district labels.
- Refresh
- Read resource metadata on every import and reconcile office changes on the published update cadence.
Review data handling
Owner: Department of Posts, Ministry of Communications, Government of India, published through data.gov.in.
Access: Allowlisted OGD resource 5c2f62fe-5afa-4119-a499-fec9d604d5bd. The 2025 PIN-boundary GeoJSON is accepted only as a checksum-pinned official download while its OGD resource endpoint remains unavailable.
Licence: NDSAP/Government Open Data Licence terms identified by the selected resource, with India Post and data.gov.in attribution.
Allowed fields- office name
- PIN code
- office type
- delivery status
- district
- State
- resource identifier
- source update date
Never collect or publish- resident address
- person-level mail data
- API credentials
- unmapped district assignment
- precise user location
Approved database pathdata_sources, data_import_runs, postal_areas, districts, blocks
Publication rule: Use a PIN only as a broad postal or discovery area. Preserve unmatched official labels without guessing an LGD district; never attach crime counts or imply precise user location.
Official referenceapproved draft ingestion available
National Hospital Directory
Add source-reported hospital context to bounded map views and retain a reviewable national facility directory.
- Coverage
- India; row count and coordinate coverage are recorded from each checksum-pinned OGD payload.
- Refresh
- Check API and page metadata monthly and retain their reported dates separately when they disagree; never present retrieval time as the payload date.
Review data handling
Owner: Ministry of Health and Family Welfare, Government of India, published through data.gov.in.
Access: Allowlisted OGD resource 98fa254e-c5f8-4910-a19b-4828939b477d using a server-side data.gov.in key.
Licence: Government Open Data License - India, with Ministry of Health and Family Welfare and data.gov.in attribution.
Allowed fields- hospital name
- public facility classification
- systems of medicine
- public location label
- State/district/sub-district labels
- PIN code
- valid public coordinates
- specialties
- facilities
- accreditation
- established year
- bed count
- emergency-services label
- source timestamp
Never collect or publish- named nodal person
- nodal phone or email
- personal mobile
- unreviewed contact number
- registration scan
- patient data
- inferred coordinate
- Aamegh verification claim
Approved database pathdata_sources, data_import_runs, source_dataset_versions, official_facilities, source_context_observations
Publication rule: Import facilities as draft. Publish only the source-reported, contact-minimised projection after review; do not call a listed hospital Aamegh-verified or use it as a safety score input.
Area contextfuture adapter not enabled
Police.uk street-level crime API
Potential future approximate aggregate context after jurisdiction, retention, and methodology review.
- Coverage
- England and Wales only; it is not a Scotland or global coverage claim.
- Refresh
- Monthly availability check and approved cache/import schedule only; never a browser-side map query.
Review data handling
Owner: Police.uk / UK police open-data service.
Access: Official street-level crime API by month and location/polygon. The source documents approximate locations.
Licence: Review the current Police.uk data licence and attribution requirements before any adapter is enabled.
Allowed fields- crime category
- month
- jurisdiction
- approved broad-cell aggregate
- source availability metadata
Never collect or publish- source incident points
- raw approximate coordinates
- person-linked data
- coverage claims outside England and Wales
Approved database pathdata_sources, data_import_runs, safety_indicator_cells, score_configurations, safety_indicator_scores
Publication rule: Aggregate approved approximate data immediately into broad cells, label the jurisdiction, and never re-publish incident geometry.
aamegh