Confirm the official park page before you travel. NPS alert data can lag the park website by about two hours.
ParkPulseU.S. National Park conditions

Where the conditions come from

ParkPulse shows official records and leaves a section blank when a source does not respond. It does not invent hours, fees, or alerts.

Park directory

Search uses a directory of National Park Service units stored on this server: unit code, name, designation, state labels, and a boundary centroid. The seed comes from the NPS Land Resources Division boundary service, which does not require an API key. It does not include descriptions, alerts, or hours. State labels are that service's administrative strings, so a long trail may not list every state it crosses until a refresh from the NPS Data API replaces the record.

NPS boundary service

National Park Service

Alerts and closures load from the public list the National Park Service shows on its alerts page. Hours, entrance fees, campgrounds, visitor centers, and photos load from the public record on each park's own page. Neither source needs an API key. Alert categories are Danger, Closure, Caution, and Information. A failed alerts download leaves the visit status unconfirmed instead of guessing that the park is open. A failed park record leaves hours, fees, and campgrounds blank for that park.

NPS alerts page

When a server key is set, road events, today's events, things to do, amenity lists, and the park outline come from the NPS Data API. The same key can refresh the directory. The key stays on the server and is sent as a header. It is not sent to the browser. NPS documents a default limit of 1,000 requests per hour. NPS says the API data load runs about every two hours, so a page can lag the park website. ParkPulse stops calling the API for the rest of the hour when that server's own counter passes 1,000. Two separate servers do not share one counter.

NPS API documentation

National Weather Service

The forecast and weather alerts use the park's published coordinates. api.weather.gov does not use an API key. It requires a User-Agent that identifies the application. The service resolves that point to one forecast grid. A large park covers more than one grid, so the forecast is for that point, not every trailhead.

NWS API documentation

Map

The basemap is the OpenFreeMap Liberty style, built from OpenStreetMap data. ParkPulse does not use the public OpenStreetMap tile server, which is not meant for application traffic. Park outlines come from the NPS boundary feed when the Data API is connected and the feed has a boundary. Directions open your maps app from the published coordinates.

OpenFreeMap

Saved parks

Saved parks stay in this browser. ParkPulse does not have accounts, and a saved park on one device is not on another. Clearing site data removes the list.