Data Analyst Portfolio Projects Using Indian Public Datasets: 10 Ideas With Data Sources

Last updated: October 2026

Most beginner data analyst portfolios have the same problem.

Open a portfolio, and you will find another sales dashboard. Another customer churn dataset. Another e-commerce analysis. Another set of charts showing monthly revenue.

The work may be technically correct, but there is very little that makes the analyst memorable.

Now imagine replacing that with a project that asks:

Which Indian states are seeing the biggest changes in employment? Why does rainfall vary so sharply across regions? Which states have changed the most in tourism? How different are education facilities across districts?

Suddenly, the project has a story.

That is why Indian public datasets can be incredibly useful for building a data analyst portfolio. They give you real-world data, messy questions, geographical differences, historical trends, and problems that cannot be solved by simply making a colourful dashboard.

I’m Riten, founder of Fueler, a skills-first portfolio platform building the career infrastructure for 100 million creative professionals. Fueler connects talented individuals with companies through assignments, portfolios, and projects, not just resumes or CVs. Think of it as Dribbble/Behance for work samples combined with AngelList for hiring infrastructure.

In this guide, I’ll break down 10 data analyst portfolio project ideas using Indian public datasets, including what to analyse, useful metrics, project questions, and ways to make each project stronger.

The goal is not to collect datasets.

The goal is to create work that makes someone think, “This person knows how to analyse data.”

What Makes a Good Data Analyst Portfolio Project?

The dataset itself is not the project.

A strong project begins with a question, uses data to investigate it, and ends with a clear explanation of what the numbers actually tell us.

For a beginner, this is more valuable than choosing the biggest dataset available.

• Start with a real question: Ask something specific such as “How has female labour-force participation changed across Indian states?” rather than “Analyse employment data.” A focused question gives your project direction and makes every query, calculation, chart, and conclusion easier to justify.

• Use multiple dimensions: State, district, year, gender, rural or urban classification, age group, sector, or category gives you opportunities to compare groups. These comparisons demonstrate practical data analysis skills far better than a single average or total.

• Look for change over time: Historical data allows you to study trends, growth, decline, unusual periods, and regional differences. A dataset covering several years can turn a basic descriptive project into a much stronger time-series analysis.

• Understand the source first: Government datasets often contain definitions, notes, missing values, units, geographic limitations, and methodology changes. Read these before analysing the numbers. Understanding the data is part of the analyst's job.

• Connect analysis to a decision: Ask what someone could do with your findings. A good project can help explain demand, identify regional differences, find unusual patterns, or support resource allocation. That makes the project feel closer to actual analytical work.

The best data analyst projects are not necessarily complicated.

They are specific, well-researched, transparent, and useful.

1. Indian Employment Trends Using PLFS Data

Employment is much more complicated than one unemployment number.

The Periodic Labour Force Survey, or PLFS, provides labour-market indicators across areas and population groups. That gives you enough depth to analyse employment from several angles instead of creating another basic percentage chart.

Data source: Ministry of Statistics and Programme Implementation, PLFS.

• Compare Indian states: Analyse indicators such as Labour Force Participation Rate, Worker Population Ratio, and Unemployment Rate across states. Instead of only finding the highest and lowest values, look for states where these indicators move differently and investigate what the difference reveals.

• Study gender differences: Compare male and female labour-force participation across rural and urban populations. Use percentage-point differences to make comparisons clearer. This creates a useful data analysis project around segmentation, comparison, and interpretation.

• Analyse rural versus urban employment: Build separate trends for rural and urban areas. Look at whether changes in the overall figure are being driven by one group or whether both are moving in the same direction.

• Track employment over time: Use multiple PLFS periods to identify major changes. Clearly label the period being studied and check the methodology before comparing different releases.

• Create an employment dashboard: Include state filters, gender comparisons, rural-urban analysis, and trend charts. Add written insights beside the visuals so the viewer understands what you found instead of having to interpret every chart independently.

This project demonstrates something important: you can work with social and economic data without reducing a complicated subject to one number.

2. Indian Inflation Analysis Using Consumer Price Index Data

Inflation becomes far more interesting when you stop looking at one national figure.

Consumer Price Index data can be used to compare price movements across states and between rural and urban areas. It is ideal for a data analyst portfolio because it naturally creates time-series and comparison questions.

Data source: Open Government Data platform, state-level Consumer Price Index datasets.

• Compare inflation across states: Analyse how CPI changes across selected Indian states. Look at trends rather than creating a single ranking. Identify periods where particular states moved differently from the wider pattern.

• Compare rural and urban prices: Separate rural and urban CPI series and calculate the difference between them. Show when the gap increased or decreased and clearly explain the period used for each comparison.

• Calculate inflation rates: Where the data supports it, calculate year-over-year or month-over-month changes. Explain the formula in simple language so the reader understands exactly what your percentage represents.

• Find unusual periods: Identify months or years with unusually large changes. Then investigate the source data and surrounding periods instead of immediately declaring the movement a major economic event.

• Build an inflation dashboard: Add state filters, rural-urban comparisons, CPI trends, and percentage changes. Keep the dashboard focused. Every chart should answer a question.

This project is particularly useful for demonstrating time-series analysis, percentage calculations, filtering, aggregation, and data storytelling.

3. Indian Rainfall and Monsoon Analysis

India does not experience rainfall in one uniform pattern.

Rainfall changes dramatically across regions and seasons. Historical rainfall data therefore gives analysts an excellent opportunity to work with geography, seasonality, trends, and deviations from normal rainfall.

Data source: India Meteorological Department rainfall datasets available through the Open Government Data platform.

• Compare rainfall across regions: Analyse monthly and annual rainfall across Indian meteorological subdivisions. Look at both total rainfall and rainfall deviation where available.

• Study the monsoon season: Focus on June to September and calculate seasonal rainfall. Compare actual rainfall with the relevant normal value instead of looking only at raw totals.

• Find unusual rainfall years: Identify years with significant departures from normal rainfall. Compare several years before deciding whether an observation represents a broader pattern or an isolated event.

• Analyse monthly seasonality: Calculate how much rainfall different months contribute to the yearly total. This is a straightforward way to demonstrate grouping, percentage calculations, and time-series visualisation.

• Combine rainfall with another dataset: An advanced project could connect rainfall with agriculture, rural employment, or another compatible dataset. The challenge is matching geography and time periods correctly, which itself demonstrates useful data-cleaning skills.

A rainfall project can become much stronger when you explain what normal rainfall means, how you calculated deviations, and where the dataset has limitations.

4. Indian School Education Analysis Using UDISE Plus Data

Education data can reveal much more than the number of schools in a state.

UDISE Plus contains information related to enrolment, teachers, infrastructure, school categories, and other education indicators. This makes it useful for both beginner and intermediate data analyst projects.

Data source: UDISE Plus datasets available through the Open Government Data platform.

• Analyse school infrastructure: Compare indicators such as electricity, computers, toilets, drinking water, playgrounds, or other available facilities. Use percentages where appropriate so states of different sizes can be compared fairly.

• Study pupil-teacher relationships: Use compatible enrolment and teacher data to calculate ratios. Explain the calculation clearly and do not present your own calculated metric as an official government indicator.

• Analyse enrolment: Break enrolment down by class, age, gender, state, or district depending on the dataset. Look for patterns that deserve further investigation instead of automatically treating unusual values as problems.

• Compare school categories: Where management information is available, compare government and private schools using clearly defined indicators. Keep the analysis descriptive unless the data supports a stronger conclusion.

• Build a district-level dashboard: Allow users to filter by state and district. Display selected infrastructure and enrolment indicators and include short written findings beside the visuals.

Education data is also a good way to demonstrate responsible analysis because the numbers represent real students and institutions. Your conclusions should stay within what the dataset can actually establish.

5. Indian Crime Data Analysis Using NCRB Data

Crime data can produce an impressive portfolio project, but it requires careful interpretation.

The National Crime Records Bureau publishes crime statistics across categories and geographic areas. The data can be used to study reported cases, crime categories, state-level differences, and changes over time.

Data source: National Crime Records Bureau, Crime in India datasets available through the Open Government Data platform.

• Analyse one crime category: Choose a specific category and track reported cases across years. A focused project is easier to explain and allows you to investigate the category properly.

• Use population-adjusted rates: Raw case counts favour larger populations. Where compatible population data exists, calculate a rate per population unit and clearly label it as your own calculation.

• Study crime composition: Examine which categories contribute most to reported cases in a selected geography. This creates a useful percentage and segmentation analysis.

• Compare geographic patterns: Compare states or metropolitan areas only when they belong to the same geographic level. Do not mix state-level and city-level observations in one calculation.

• Explain data limitations: Reported crime is not necessarily the same as all crime that occurs. Reporting behaviour, registration, legal definitions, and police procedures can influence recorded statistics. Mentioning this limitation makes your analysis more responsible.

This project can demonstrate that you know an important analyst skill: numbers need context before they become conclusions.

6. Indian Tourism Data Analysis by State

Tourism data naturally creates questions around demand, geography, growth, and changing visitor behaviour.

The Ministry of Tourism publishes statistics covering areas such as domestic tourist visits and foreign tourist visits across states and Union Territories.

Data source: Ministry of Tourism, India Tourism Statistics datasets.

• Compare domestic and foreign tourism: Separate domestic tourist visits from foreign tourist visits. Analyse their relative contribution and avoid treating the two groups as one audience.

• Find changing tourism patterns: Compare tourist visits across years and calculate absolute and percentage changes. Be careful when interpreting percentage growth from a very small starting value.

• Study state-level differences: Build a state comparison for a selected year. Then investigate which states changed position over time rather than creating a static ranking.

• Analyse tourism recovery: If your selected years cover a major disruption, compare the periods before and after it. Clearly identify the years rather than describing the dataset as representing current tourism.

• Create a tourism dashboard: Include state filters, domestic and foreign visitors, trends, percentage changes, and geographic visuals. Keep the number of charts limited and make the key findings obvious.

Tourism analysis is useful for a portfolio because the questions are easy to understand while the underlying data still offers enough depth for meaningful analysis.

7. MGNREGA and Rural Employment Analysis

MGNREGA data lets you investigate rural employment at a much more practical level.

Depending on the dataset selected, you can analyse employment generated, participation, households, person-days, districts, states, and other programme indicators.

Data source: MGNREGA datasets available through the Open Government Data platform.

• Compare employment across districts: Analyse person-days, households, job cards, or another clearly defined metric. Always explain whether the number represents people, households, or workdays.

• Study women's participation: Where gender information is available, calculate the share of participation by women. Show the underlying count alongside the percentage so the result has proper context.

• Find geographic differences: Map district-level indicators and identify clusters of higher or lower values. Treat these as patterns to investigate, not automatic explanations for why differences exist.

• Track changes over financial years: Compare programme indicators across years. Investigate whether a major change appears across several related measures before describing it as a broad trend.

• Build a rural employment dashboard: Add state and district filters, employment indicators, participation measures, and trends. Include a methodology note explaining the calculations and definitions used.

The project becomes stronger when you avoid trying to answer whether the programme is simply “good” or “bad.” Ask measurable questions and let the data answer those questions.

8. Indian Population and Demographic Analysis

Population data looks simple until you start asking better questions.

Census-related public datasets provide state-level population, population density, and decadal growth information. These variables are useful for understanding how raw population numbers can tell very different stories from population-adjusted measures.

Data source: Census-related population datasets available through the Open Government Data platform.

• Compare population density: Compare states using population per unit of area instead of population size alone. Explain why density answers a different question from total population.

• Analyse population growth: Study the available decadal growth figures and clearly label the period. Historical Census data should never be presented as a current population estimate.

• Compare population and density: Create a scatter plot with total population and density. Look for states that are large in population but relatively less dense and smaller regions with much higher concentration.

• Combine population with another dataset: Join population data with education, tourism, employment, healthcare, or rainfall data where the geography and period are compatible.

• Build a demographic dashboard: Show population, density, growth, regional comparisons, and state-level filters. Include definitions for every metric so the dashboard can be understood without a separate explanation.

This project teaches one of the most important habits in data analysis: always ask what the denominator is.

9. Indian Healthcare Infrastructure Analysis

Healthcare infrastructure data can help you study how facilities are distributed across states and regions.

The Open Government Data ecosystem contains datasets related to healthcare facilities, including categories such as sub-health centres, primary health centres, and district hospitals.

Data source: Ministry of Health and Family Welfare datasets available through the Open Government Data platform.

• Map healthcare facilities: Count facilities by state and category. Add a geographic visual, but keep the underlying numbers visible so the map does not become the entire analysis.

• Calculate population-adjusted measures: Where compatible population data exists, calculate facilities per population unit. Clearly state the population year and healthcare-data year.

• Compare facility categories: Examine how primary facilities, sub-health centres, and district hospitals are distributed. Focus on describing the structure rather than declaring which state has the “best” healthcare system.

• Find regional differences: Compare states or regions using consistent measures. Use differences as starting points for investigation rather than claiming that infrastructure alone explains healthcare outcomes.

• Build an infrastructure dashboard: Combine facility counts, population-adjusted metrics, state filters, and geographic visuals. Add limitations explaining that infrastructure is only one part of healthcare access.

The value of this project is not the number of charts. It is your ability to explain exactly what the available data can and cannot tell you.

10. Combine Two Indian Public Datasets for a Deeper Analysis

Once you have built a few individual projects, try combining datasets.

For example, you could investigate rainfall and agriculture, tourism and population, or employment and demographic data. The interesting part is no longer just analysing one table. It is figuring out whether two datasets can actually answer one question together.

• Find a common key: Look for a shared state, district, year, or financial year. Check spelling and geographic definitions before joining. A technically successful database join can still be analytically wrong.

• Create a data dictionary: Record every column, unit, definition, source, and transformation. This is particularly useful when combining government datasets created by different departments.

• Test relationships carefully: Use charts and descriptive statistics before making conclusions. If two variables move together, that does not automatically prove that one caused the other.

• Investigate outliers: Find observations that behave differently from the general pattern. Check the original source before removing them. An outlier can be an error, but it can also be the most interesting part of the project.

• Tell the complete story: Explain the question, sources, cleaning, joins, calculations, findings, and limitations. The finished project should feel like a small analytical assignment rather than two unrelated datasets placed beside each other.

This is often where a beginner portfolio starts showing stronger analytical maturity.

How to Present a Data Analyst Portfolio Project

A recruiter should understand your project before opening your dashboard.

Start with the question. Then explain the data, what you did with it, what you found, and what the findings mean.

You do not need twenty screenshots.

• Use a specific project title: “Indian Rainfall Trends Using IMD Data” communicates far more than “Data Analysis Project.” Your title should tell the reader what you analysed.

• Write a short project summary: Mention the problem, dataset, period, and objective. Keep it short enough to scan quickly.

• Show three to five important findings: Do not publish every observation. Selecting the most useful findings demonstrates judgment.

• Explain the methodology: Mention cleaning, calculations, joins, filters, and analytical methods. A recruiter should understand how you reached the result.

• Document limitations: State missing data, historical periods, incompatible variables, methodology changes, or other constraints. Good analysts do not hide uncertainty.

This is also where a portfolio becomes more useful than a resume. Lisha works in product management, where decisions depend heavily on understanding problems, users, and evidence. Data analysts operate differently, but the underlying portfolio principle is similar: show the work behind the claim.

What Skills Should Your Data Analyst Portfolio Demonstrate?

Your portfolio should not simply say “SQL, Excel, Python, Power BI.”

The projects themselves should provide evidence of those skills.

• Data cleaning: Show how you handled missing values, duplicates, inconsistent labels, incorrect formats, and other problems found in real datasets.

• SQL and querying: Use filtering, grouping, joins, aggregations, conditional logic, and calculations to answer actual questions rather than writing queries only to demonstrate syntax.

• Visualisation: Select charts according to the question. Trends need trends, geographic differences need geographic comparisons, and relationships need suitable comparison charts.

• Analytical thinking: Explain why you chose the metric and what the finding means. A technically correct calculation is not enough if it does not answer the original question.

• Communication: Write conclusions in plain English. Someone who does not know SQL should still understand your main finding.

Analytics also appears in neighbouring roles. Priyanshu is listed under SEO and performance marketing, where data is used to understand traffic and campaign performance. Amanpreet is listed in digital marketing, another field where measurement influences decisions.

The lesson is useful for aspiring analysts: data becomes valuable when it helps someone decide what to do next.

How Can You Make Your Data Analyst Portfolio Stand Out?

You do not need the most advanced machine learning model.

You need a project that is easier to trust than the average portfolio project.

Use Indian public data. Explain the source. Show your cleaning. Make your calculations transparent. Write conclusions that match the evidence.

• Use unfamiliar datasets: Employment, rainfall, tourism, education, healthcare, and rural development data can make your portfolio more distinctive than another generic sales dataset.

• Ask a narrow question: “What happened to Indian employment?” is too broad. “How did female labour-force participation differ between rural and urban populations?” is much easier to analyse properly.

• Show the messy work: Real data is rarely perfect. Showing how you handled the problems can be more valuable than showing another polished dashboard.

• Explain what surprised you: If the data contradicted your original expectation, mention it. Good analysis is not about proving your first assumption was correct.

• Make every chart earn its place: If a chart does not answer a question or support a conclusion, remove it.

The same principle applies across other portfolio-driven careers. Kartik Kochhar represents development work, while Mehul Kundu represents UI/UX work. Different professions require different skills, but the strongest portfolios make the actual work visible.

How Many Data Analyst Projects Should You Have?

You do not need 20 projects.

Three to five strong projects are enough to demonstrate range if each one has a clear question, proper analysis, useful visuals, and a documented conclusion.

Choose projects that show different types of thinking.

• One simple project: Use rainfall, tourism, or population data to demonstrate basic cleaning, analysis, and visualisation.

• One deeper project: Use employment, education, or healthcare data with multiple dimensions and more complex comparisons.

• One time-series project: Demonstrate how you analyse change rather than only comparing static values.

• One project using multiple datasets: Show that you can clean, match, join, and interpret data from different sources.

• One project with strong communication: Make the final output easy for a non-technical person to understand.

You can also learn from how other professionals present their work. Sharvin works in content and social media strategy, while Vikravardhan is listed as a content writer. Their disciplines are different, but the portfolio lesson remains relevant: the work should make the skill visible.

Where Can You Find Indian Public Datasets?

The Open Government Data platform, data.gov.in, is one of the best starting points for Indian public datasets.

You can find data from government ministries and departments covering areas such as employment, education, health, agriculture, tourism, economy, environment, and more.

Other useful sources include ministry websites, MoSPI publications, Census resources, IMD datasets, NCRB publications, Ministry of Tourism data, UDISE Plus resources, and MGNREGA data.

Before using any dataset, check:

• Who published it?

• What period does it cover?

• What exactly does each column mean?

• Is the data updated?

• Are there missing values?

• Are the geographic boundaries consistent?

• Has the methodology changed?

• Can the data actually answer your research question?

A historical dataset is not a bad dataset.

You simply need to label it correctly.

That distinction alone can separate careful analysis from misleading analysis.

How does this connect to Building a Strong Career or Portfolio?

A data analyst's value is easier to understand when people can see the work behind the skill. Showing the question, dataset, cleaning process, calculations, findings, and limitations gives recruiters something concrete to evaluate. It also creates better interview conversations because you can discuss decisions you actually made. A portfolio on Fueler can present that proof of work clearly, but the project itself is what earns attention.

Final Thoughts

The easiest way to build a forgettable data analyst portfolio is to copy the same datasets everyone else is using.

Indian public datasets give you another route.

Pick a question that matters. Find the right data. Clean it properly. Analyse it honestly. Explain the result without hiding behind complicated language.

You do not need to predict the future or build an enormous machine learning model.

Sometimes, a well-researched answer to one good question is enough to prove that you can think like a data analyst.

Data Analyst Portfolio FAQs

What are the best Indian public datasets for data analyst projects?

PLFS, UDISE Plus, IMD rainfall, CPI, NCRB, MGNREGA, tourism, healthcare, and Census-related datasets are strong options. The best choice depends on your project question, the available time period, and the type of analysis you want to demonstrate.

Where can I find Indian government datasets for data analysis?

Start with the Open Government Data platform at data.gov.in. You can also explore datasets and publications from MoSPI, IMD, NCRB, Ministry of Tourism, Ministry of Health and Family Welfare, UDISE Plus, and other government departments.

What should a data analyst portfolio project contain?

Include the problem, data source, time period, cleaning process, calculations, analysis, visualisations, findings, limitations, and conclusion. If you use SQL, Python, Excel, or another method, show enough of the process to demonstrate how you reached the result.

Are Indian government datasets good for beginner data analysts?

Yes. They provide real-world problems such as missing values, inconsistent names, multiple geographic levels, historical data, and detailed documentation. Start with one focused question rather than trying to analyse an entire government dataset.

How many projects should a data analyst portfolio have?

Three to five strong projects are generally enough to demonstrate your abilities. Focus on variety, depth, and clear communication. A few complete projects with meaningful findings are more useful than a long list of unfinished dashboards.

Why 100,000+ professionals use Fueler

Fueler helps professionals showcase proof of work through projects, assignments, case studies, and achievements.

• Thousands of professionals use Fueler to create their digital portfolio

• Thousands of projects are published on Fueler. Check here

• Startups and Companies hire through proof of work on Fueler

• Used by freelancers, creators, marketers, video editors, writers, designers, and product managers

Our mission is to help the next 100 million professionals build a verified professional identity through proof of work