Solar & Daylight Data

Updated 2026-08-31

Sun Path: Mlolongo, Kenya

How to research sun path for a specific site in Mlolongo — 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 KE dump](https://download.geonames.org/export/dump/KE.zip) (CC BY 4.0, snapshot 2026-08-31, GeoNames ID 9166066). Regulatory starting point: [National Construction Authority and the applicable county government](https://www.nca.go.ke/). 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 Mlolongo at -1.3964, 36.9403, the declination-only solar-noon altitude is approximately 65.2° at the June solstice, 88.6° at an equinox and 68.0° 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 9166066 in administrative area 31, at -1.3964, 36.9403; replace it with the surveyed parcel point before relying on the result. As a transparent geometry check, declination-only solar-noon altitude is about 65.2° at the June solstice, 88.6° at an equinox and 68.0° at the December solstice. Representative 21st-day geometry ranges from about 11.9 hours in June to 12.1 hours in December; 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 Mlolongo?

Mlolongo is represented here at approximately -1.3964, 36.9403 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 Mlolongo 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.

Mlolongo monthly solar geometry check for sun path

Representative dateDeclinationSolar-noon altitudeGeometric daylight
21 January-20.14°71.3°12.1 h
21 February-11.23°80.2°12.0 h
21 March-0.40°89.0°12.0 h
21 April+11.58°77.0°12.0 h
21 May+20.14°68.5°11.9 h
21 June+23.45°65.2°11.9 h
21 July+20.44°68.2°11.9 h
21 August+11.75°76.8°12.0 h
21 September-0.20°88.8°12.0 h
21 October-11.75°79.6°12.0 h
21 November-20.44°71.0°12.1 h
21 December-23.45°67.9°12.1 h

Month-by-month geometry interpretation

  • 21 January: approximate solar-noon altitude 71.3° (zenith angle 18.7°) and 12.1 hours of geometric daylight. That is 0.0 hours shorter than the preceding representative date in this annual sequence.
  • 21 February: approximate solar-noon altitude 80.2° (zenith angle 9.8°) and 12.0 hours of geometric daylight. That is 0.0 hours shorter than the preceding representative date in this annual sequence.
  • 21 March: approximate solar-noon altitude 89.0° (zenith angle 1.0°) and 12.0 hours of geometric daylight. That is 0.0 hours shorter than the preceding representative date in this annual sequence.
  • 21 April: approximate solar-noon altitude 77.0° (zenith angle 13.0°) and 12.0 hours of geometric daylight. That is 0.0 hours shorter than the preceding representative date in this annual sequence.
  • 21 May: approximate solar-noon altitude 68.5° (zenith angle 21.5°) and 11.9 hours of geometric daylight. That is 0.0 hours shorter than the preceding representative date in this annual sequence.
  • 21 June: approximate solar-noon altitude 65.2° (zenith angle 24.8°) and 11.9 hours of geometric daylight. That is 0.0 hours shorter than the preceding representative date in this annual sequence.
  • 21 July: approximate solar-noon altitude 68.2° (zenith angle 21.8°) and 11.9 hours of geometric daylight. That is 0.0 hours longer than the preceding representative date in this annual sequence.
  • 21 August: approximate solar-noon altitude 76.8° (zenith angle 13.2°) and 12.0 hours of geometric daylight. That is 0.0 hours longer than the preceding representative date in this annual sequence.
  • 21 September: approximate solar-noon altitude 88.8° (zenith angle 1.2°) and 12.0 hours of geometric daylight. That is 0.0 hours longer than the preceding representative date in this annual sequence.
  • 21 October: approximate solar-noon altitude 79.6° (zenith angle 10.4°) and 12.0 hours of geometric daylight. That is 0.0 hours longer than the preceding representative date in this annual sequence.
  • 21 November: approximate solar-noon altitude 71.0° (zenith angle 19.0°) and 12.1 hours of geometric daylight. That is 0.0 hours longer than the preceding representative date in this annual sequence.
  • 21 December: approximate solar-noon altitude 67.9° (zenith angle 22.1°) and 12.1 hours of geometric daylight. That is 0.0 hours longer than the preceding representative date in this annual sequence.

Harth calculation for latitude -1.3964°: 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 KE dump (CC BY 4.0, snapshot 2026-08-31, GeoNames ID 9166066). Regulatory starting point: National Construction Authority and the applicable county government. 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 Mlolongo establish?

The sun path record for Mlolongo establishes a reproducible discovery point at -1.3964, 36.9403 (GeoNames ID 9166066, administrative area 31) and a Kenya 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 Mlolongo?

For the sun path record in Mlolongo, replace the -1.3964, 36.9403 city reference with the surveyed site or parcel, identify the competent local authority, and verify the current documents under National Building Code and county development-control requirements. 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.