Solar & Daylight Data

Updated 2026-08-31

Sun Path: Richmond, Canada

How to research sun path for a specific site in Richmond — the controlling authority, source documents, and checks to run before you rely on a number.

Last updated August 31, 2026 · Location data from the [GeoNames CA dump](https://download.geonames.org/export/dump/CA.zip) (CC BY 4.0, snapshot 2026-08-31, GeoNames ID 6122085). Regulatory starting point: [Codes Canada and the applicable provincial or territorial authority](https://nrc.canada.ca/en/certifications-evaluations-standards/codes-canada/codes-canada-publications). Figures are illustrative — verify against the current locally adopted edition for the site. Solar-method context: [NOAA Solar Calculation Details](https://gml.noaa.gov/grad/solcalc/calcdetails.html); the Harth monthly table uses a simpler declination and geometric-daylight approximation whose stated limitations must be retained.

Direct answer

For Richmond at 49.1700, -123.1368, the declination-only solar-noon altitude is approximately 64.3° at the June solstice, 40.8° at an equinox and 17.4° at the December solstice. Refine these geometry checks with the project date, civil time, facade azimuth, terrain and local horizon. The reproducible location record is GeoNames ID 6122085 in administrative area 02, at 49.1700, -123.1368; replace it with the surveyed parcel point before relying on the result. As a transparent geometry check, declination-only solar-noon altitude is about 64.3° at the June solstice, 40.8° at an equinox and 17.4° at the December solstice. Representative 21st-day geometry ranges from about 8.0 hours in December to 16.0 hours in June; this excludes atmospheric refraction, terrain and obstruction effects. The cited national authority is a discovery starting point; current local documents and a named qualified reviewer control project use of this sun path record.

Prepared by Harth · Prepared from the cited location and country sources; local project inputs remain unreviewed · Published 2026-08-26 · Updated 2026-08-31.

What must be verified for Richmond?

Richmond is represented here at approximately 49.1700, -123.1368 for discovery and workflow planning. A project address, parcel, elevation, exposure, authority, and submission date must replace that city-centre reference before design use.

How should sun path be established?

  1. Fix the surveyed site and local time basis.
  2. Select an authoritative weather source or a named solar-position algorithm.
  3. Record period, percentile or scenario and units.
  4. Test sensitivity to elevation, exposure, urban form and horizon.
  5. Save the source file, retrieval date and checker in the model record.
InputProject-specific evidenceQA question
Sitesurveyed coordinates, elevation and horizonDoes the point represent the building?
Weather/solar methodnamed dataset, algorithm, period and time basisAre station, time zone and units explicit?
Design scenariocurrent and future scenario agreed by the teamIs an average being mistaken for an extreme?
Complianceadopted local document and editionWas applicability confirmed with the authority?

What are the limits of this worksheet?

This sun-path-workflow page is a project-starting worksheet, not a design value or approval. The controlling authority and qualified professionals for the Richmond site remain authoritative.

This primary route consolidates the location evidence needed for Sun Path, Solar Altitude & Azimuth, Solar Shading Design, Daylight & Orientation. A narrower route should be released only when it adds a materially different official source, calculation, process, threshold or worked example.

Richmond monthly solar geometry check for sun path

Representative dateDeclinationSolar-noon altitudeGeometric daylight
21 January-20.14°20.7°8.7 h
21 February-11.23°29.6°10.2 h
21 March-0.40°40.4°11.9 h
21 April+11.58°52.4°13.8 h
21 May+20.14°61.0°15.3 h
21 June+23.45°64.3°16.0 h
21 July+20.44°61.3°15.4 h
21 August+11.75°52.6°13.9 h
21 September-0.20°40.6°12.0 h
21 October-11.75°29.1°10.1 h
21 November-20.44°20.4°8.6 h
21 December-23.45°17.4°8.0 h

Month-by-month geometry interpretation

  • 21 January: approximate solar-noon altitude 20.7° (zenith angle 69.3°) and 8.7 hours of geometric daylight. That is 0.7 hours longer than the preceding representative date in this annual sequence.
  • 21 February: approximate solar-noon altitude 29.6° (zenith angle 60.4°) and 10.2 hours of geometric daylight. That is 1.6 hours longer than the preceding representative date in this annual sequence.
  • 21 March: approximate solar-noon altitude 40.4° (zenith angle 49.6°) and 11.9 hours of geometric daylight. That is 1.7 hours longer than the preceding representative date in this annual sequence.
  • 21 April: approximate solar-noon altitude 52.4° (zenith angle 37.6°) and 13.8 hours of geometric daylight. That is 1.9 hours longer than the preceding representative date in this annual sequence.
  • 21 May: approximate solar-noon altitude 61.0° (zenith angle 29.0°) and 15.3 hours of geometric daylight. That is 1.5 hours longer than the preceding representative date in this annual sequence.
  • 21 June: approximate solar-noon altitude 64.3° (zenith angle 25.7°) and 16.0 hours of geometric daylight. That is 0.7 hours longer than the preceding representative date in this annual sequence.
  • 21 July: approximate solar-noon altitude 61.3° (zenith angle 28.7°) and 15.4 hours of geometric daylight. That is 0.6 hours shorter than the preceding representative date in this annual sequence.
  • 21 August: approximate solar-noon altitude 52.6° (zenith angle 37.4°) and 13.9 hours of geometric daylight. That is 1.5 hours shorter than the preceding representative date in this annual sequence.
  • 21 September: approximate solar-noon altitude 40.6° (zenith angle 49.4°) and 12.0 hours of geometric daylight. That is 1.9 hours shorter than the preceding representative date in this annual sequence.
  • 21 October: approximate solar-noon altitude 29.1° (zenith angle 60.9°) and 10.1 hours of geometric daylight. That is 1.8 hours shorter than the preceding representative date in this annual sequence.
  • 21 November: approximate solar-noon altitude 20.4° (zenith angle 69.6°) and 8.6 hours of geometric daylight. That is 1.5 hours shorter than the preceding representative date in this annual sequence.
  • 21 December: approximate solar-noon altitude 17.4° (zenith angle 72.6°) and 8.0 hours of geometric daylight. That is 0.6 hours shorter than the preceding representative date in this annual sequence.

Harth calculation for latitude 49.1700°: Cooper declination approximation, 90° - |latitude - declination| at solar noon, and centre-to-centre sunrise hour angle. See NOAA's solar calculation details for fuller method context. This screening table excludes equation-of-time/civil-time conversion, atmospheric refraction, terrain, facade azimuth and obstructions; it is not an hourly shading result.

Sources and method

Location data from the GeoNames CA dump (CC BY 4.0, snapshot 2026-08-31, GeoNames ID 6122085). Regulatory starting point: Codes Canada and the applicable provincial or territorial authority. Figures are illustrative — verify against the current locally adopted edition for the site. Solar-method context: NOAA Solar Calculation Details; the Harth monthly table uses a simpler declination and geometric-daylight approximation whose stated limitations must be retained.

Frequently asked questions

What does the sun path record for Richmond establish?

The sun path record for Richmond establishes a reproducible discovery point at 49.1700, -123.1368 (GeoNames ID 6122085, administrative area 02) and a Canada source path. It does not establish a final project value, approval or parcel decision.

What must be replaced before using this sun path workflow for a project in Richmond?

For the sun path record in Richmond, replace the 49.1700, -123.1368 city reference with the surveyed site or parcel, identify the competent local authority, and verify the current documents under National Building Code of Canada plus provincial, territorial, and municipal adoption. Record the edition, retrieval date, units, assumptions and named checker before relying on the result.

Design for your site's sun.Render it on your 3D model.