Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    business using business intelligence
    How to Use a Competitive Intelligence Dashboard to Turn Market Data Into Smarter Marketing Decisions 
    9 Min Read
    unusual trading activity
    Signal Or Noise? A Decision Tree For Evaluating Unusual Trading Activity
    3 Min Read
    software developer using ai
    How Data Analytics Helps Developers Deliver Better Tech Services
    8 Min Read
    ai for stock trading
    Can Data Analytics Help Investors Outperform Warren Buffett
    9 Min Read
    media monitoring
    Signals In The Noise: Using Media Monitoring To Manage Negative Publicity
    5 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Why you shouldn’t use JPGs for quantitative charts: a case study
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Mining > Why you shouldn’t use JPGs for quantitative charts: a case study
Data MiningPredictive Analytics

Why you shouldn’t use JPGs for quantitative charts: a case study

DavidMSmith
DavidMSmith
3 Min Read
SHARE

I’m not going to comment on the substance on the Republican “Road To Recovery” shadow budget document: plenty of more suitable forums have done so already. But I do want to use it as an illustration of why you should never use the JPG graphics format (and the jpeg graphics driver in R) for quantitative graphics. Let me pull up one chart, from page 5: I screen-captured that from the PDF file (and saved it as a PNG file for inclusion here: PNG is a lossless format, so you see it exactly as I saw it on my screen). Content…

I'm not going to comment on the substance on the Republican "Road To Recovery" shadow budget document: plenty of more suitable forums have done so already. But I do want to use it as an illustration of why you should never use the JPG graphics format (and the jpeg graphics driver in R) for quantitative graphics. Let me pull up one chart, from page 5:

More Read

The Netflix Prize, Occam’s Razor and PMML
IBM Launches New Advanced Analytics Center In New York,…
Help Change the World with Data Science
Intelligent Enterprise: You Can Predict that R Will Succeed
Big Data is Critical to the DoD Science and Technology Investment Agenda
Jpgchart
I screen-captured that from the PDF file (and saved it as a PNG file for inclusion here: PNG is a lossless format, so you see it exactly as I saw it on my screen). Content aside, that's a pretty awful-looking chart, and it's clearly a graphic that was saved in the JPG file format. See the blurriness around the text, especially between the title and the subtitle? Those are compression artifacts caused by saving the graphic as a JPG. The tick labels, legend, and source reference are basically impossible to read.

Zooming in on the graph doesn't help either — here's another screencapture after using the "Zoom" feature in my PDF viewer (Preview, on a Mac):

Jpggraphlarge
Because this is a JPG, zooming in doesn't make the chart any clearer: actually, it just makes it easier to see the compression artifacts around the lines on the chart itself. (JPG is especially poor at capturing straight lines and blocks of a single color.) Zooming doesn't make the tick marks any easier to read either, mostly because this chart was generated at low resolution and the compression artifacts swamp the small text.

If this chart had been saved as a high-resolution PNG or GIF file, the text and lines would have been much clearer, although with enough zooming you'd still eventually see the individual pixels that make up the chart. If it had been saved in a vector format like PostScript, PDF, or Windows MetaFile and then embedded in the PDF, the chart would remain crystal-clear at all levels of zoom, and would always be clear when printed.

GOP.gov: Road to Recovery

Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

AI driven big data company
How AI-Driven Workflows Are Changing the Way Companies Think About Data Risk
Artificial Intelligence Data Management Exclusive Risk Management
ai product development
Why Businesses Outsource AI Product Development Companies
Exclusive News
banking tools
The Fintech and Banking Tools Global Entrepreneurs Rely On
Fintech Infographic
business using business intelligence
How to Use a Competitive Intelligence Dashboard to Turn Market Data Into Smarter Marketing Decisions 
Analytics Big Data Exclusive Marketing

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

You Might also Like

Zero Latency: The Next Arms Race

7 Min Read
Image
AnalyticsBig DataBusiness IntelligenceData MiningData QualityData VisualizationData WarehousingHadoopITMapReduceOpen SourceSocial DataSoftwareSQLWorkforce Data

Can Big Data and Hadoop Feed the World?

5 Min Read

Decision Management, Tom Davenport and the New BI

3 Min Read

New Job at FinScore

2 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

data-driven web design
5 Great Tips for Using Data Analytics for Website UX
Big Data
AI and chatbots
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Artificial Intelligence Chatbots Exclusive

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?