Build a Car Specification Comparison Readers Can Verify

Build a car specification comparison with one row per exact vehicle variant, not one row per model name. Then give each specification a consistent unit, definition and source.

The result should let a reader filter by drivetrain, compare fuel economy and check where a number came from. A small, documented table is more useful than a large sheet that silently mixes trims, markets or measurement methods.

Start with a matched example

This worked example uses three U.S.-market, model-year 2025 Toyota Camry variants, with sources checked on October 29, 2026. It illustrates dataset structure, not a current buying recommendation. FWD means front-wheel drive; AWD means all-wheel drive.

Variant	Drive	Hybrid system power (hp)	Wheel diameter (in)	Curb weight (lb)	EPA combined economy (U.S. mpg)
Camry LE	FWD	225	16	3,450	51
Camry LE	AWD	232	16	3,594	50
Camry SE	FWD	225	18	3,494	47

Power, wheel diameter and curb weight come from Toyota’s 2025 Camry product information. Combined fuel economy comes from FuelEconomy.gov’s 2025 Camry records.

Two details matter when preparing these rows:

• Power needs a definition. Toyota lists the gasoline engine at 184 hp, but the hybrid system at 225 hp for FWD and 232 hp for AWD. An unlabeled horsepower column could mix engine output with total system output.
• A source record may cover several trims. FuelEconomy.gov groups the FWD SE, XLE and XSE in one economy record. Apply its 47 mpg value to the SE row, but get SE-specific weight and wheels from Toyota—not from the grouped record.

This is why the row identity should include market, model year, make, model, trim, powertrain and drive. Add wheel or option-package identifiers whenever they distinguish the configurations you are comparing.

Give the spreadsheet a clear structure

Use a single header row and keep numeric cells numeric. Put units in headers rather than entering values such as 3,450 lb or 51 mpg as text.

A useful starter schema is:

Field group	Suggested columns	Purpose
Identity	variant_id, market, model_year, make, model, trim, drive, powertrain	Prevents ambiguous rows
Specifications	system_power_hp, curb_weight_lb, length_in, seats, wheel_diameter_in	Supports numeric comparison
Economy	epa_city_mpg_us, epa_highway_mpg_us, epa_combined_mpg_us	Keeps distinct estimates separate
Evidence	spec_source_url, economy_source_url, checked_on, notes	Makes the comparison auditable

For the example, all rows would have market = US and model_year = 2025. Give the two LE configurations different IDs, such as US-2025-Camry-LE-FWD and US-2025-Camry-LE-AWD.

For larger datasets, keep a separate evidence table with one row per variant and specification: field name, reported value, unit, source URL and date checked. Before publication, make sure the reader-facing table still carries the essential source links and caveats.

Normalize definitions before calculating

Choose one unit for each numeric field. Preserve the original reported value in your evidence table if you convert it.

Apply these rules:

• Keep U.S. and imperial mpg separate unless explicitly converted.
• Keep EPA and WLTP figures in separately labeled fields; do not treat them as interchangeable rankings. WLTP stands for the Worldwide Harmonised Light Vehicle Test Procedure, which reports laboratory results under specific test conditions.
• Distinguish engine power from hybrid system power.
• Label width as the source defines it, including whether mirrors are included.
• Preserve cargo-volume measurement methods and seat positions where supplied.
• Use explicit feature states: standard, optional, package-dependent, unavailable and not verified. Record the package name when a feature requires one.

For mixed gasoline and electric datasets, do not put MPG and MPGe in one unlabeled column. EPA defines MPGe as distance traveled using energy equivalent to one gallon of gasoline, rather than actual gallons consumed.

Keep missing numeric values blank and explain them in a status or notes field. Zero should mean a verified zero, not “not found.”

Add consumption only if it answers a question

To compare gasoline consumed over the same distance, calculate:

gallons_per_100_miles = 100 / combined_mpg_us

Using the published, rounded estimates, the LE FWD gives approximately 1.96 U.S. gallons per 100 miles, versus 2.13 for the SE FWD. Label these as calculations from rounded EPA values, not measured driving results.

EPA explains why consumption is useful: an equal increase in MPG does not imply an equal reduction in gallons used. Keep the published combined estimate rather than replacing it with a simple average of city and highway MPG.

Publish and check the reader’s view

Export the clean comparison as CSV, or prepare a workbook containing only the intended public data. Remove hidden research material, owner details, private vehicle identifiers and other sensitive information.

TablePage supports CSV, TSV, XLSX and XLS uploads and generates a public dataset page with a shareable link and filterable table. Upload the prepared file, then inspect the resulting page before sharing it:

1. Confirm that row counts and representative values match the spreadsheet.
2. Test filtering by drive or trim and check numeric ordering where available.
3. Check that units, source URLs and configuration notes remain readable.
4. Include a scope statement: market, model years, selection rules and source-check date.
5. Review generated charts for meaning. A chart of power does not establish the “best car,” and a few selected variants are not a market-wide sample.

If you add price, record currency, price date and what the figure includes—rather than mixing MSRP, configured prices and dealer offers. For broader comparisons, use the same variant-matching and missing-data rules across every brand.