---
title: "Comment by Furqan Ashraf on \"I Built a National Parks Guide With 63 Parks and Only 62 Pages\" | Hashnode"
description: "On your question about filling a gap versus inventing an answer: I'd say data from a named source with a timestamp is filling the gap. Guessing from a neighbour"
url: "https://hashnode.com/posts/i-built-a-national-parks-guide-with-63-parks-and-only-62-pages/6af74e74caa07503df421cc8/comment/6afd9849640c299a00c31c77"
---

[Discussion](https://hashnode.com/posts/i-built-a-national-parks-guide-with-63-parks-and-only-62-pages/6af74e74caa07503df421cc8)

Comment [I Built a National Parks Guide With 63 Parks and Only 62 Pages](https://hashnode.com/posts/i-built-a-national-parks-guide-with-63-parks-and-only-62-pages/6af74e74caa07503df421cc8)

[Furqan Ashraf](https://hashnode.com/@jfreaks)

[7h ago](https://hashnode.com/posts/i-built-a-national-parks-guide-with-63-parks-and-only-62-pages/6af74e74caa07503df421cc8/comment/6afd9849640c299a00c31c77)

On your question about filling a gap versus inventing an answer: I'd say data from a named source with a timestamp is filling the gap. Guessing from a neighbouring park is inventing. Your "unknown, not zero" rule already puts you on the right side.

One thing I'd look for as a visitor is weather on each park page. You already have coordinates from the NPS data and a daily GitHub Action, so it's one more loop in the same job: 62 lat/lon calls, cached into the page data. Air quality is worth showing for the western parks in fire season, and sunrise/sunset is what photographers check first.

If you'd like those three on one key, APIFreaks has forecast, air quality and astronomy endpoints that all take lat/lon: [https://apifreaks.com/api/weather-forecast](https://apifreaks.com/api/weather-forecast). The free credits are enough to test it on all 62.
