Book PDF layout: Figures

[VuokkoH]

Comments about figures in the PDF version

• Anticipating that some screenshots get old, could e.g. add "retrieval date" of the screenshot. See, for example, Figures 1.17. - 1.19 in installation instructions.
• Figures 1.17. - 1.19 are redundant for book purposes; consider what to do with them in the book build @davewhipp
• Check size of matplotlib plots in the book PDF. E.g. Figure 2.9 in modules-section eats up more than half a page in the book. Other similar examples include Figures 4.4; 4.5; 4.11; 4.12; 6.60; 6.61;  6.31; 6.66; 6.68...
• Part II getting started (section 5); @HTenkanen
  • Figure 5.5. is informative so I would keep it but it now eats up a full page (could the bullet point list continue directly under the figure? - this is perhaps a question to @davewhipp )
  • Figure 5.10 in map projections; perhaps poor quality / lacking reference to source?
  • Figure 5.11 in map projections; source?
• SEction 6, Figure 6.70 in data classification - this is a product of GeoDataFrame.explore() - needs the static version for the book.
• Section 7: Check layout of Figure 7.38 caption in the PDF (starts 1 row too early after the figure). Online in here.
• Section 8: Figure 8.1. in static maps NOT RENDERING in the PDF
• Section 8.4: interactive maps; Figures NOT RENDERING in the PDF (need to create static versions for the book when revising this section)
• APPENDIX:
  • A.3.2 >Figure A.X  code_quality.png NOT RENDERING (The dangers of coding without coding conventions. Source: https://xkcd.com/1513/)
  • A.3 > Figure A.X PhD comics - COULD BE REMOVED..? Fun, but perhaps not needed for the book and would save a whole page.
  • A.3.13; huge figures in the PDF (perhaps not needed at all..)
  • A.5 > Figure A.X  The occasional reality of using Git. Source: https://xkcd.com/1597. Consider if we want / can add this into the PDF while revising the section contents.