3 ms·
The downside of a central system is that sites can't set really custom rules. Things like "we don't allow anyone not associated with the XYZ festival to book
by londons_explore 3y ago
The downside of a central system is that sites can't set really custom rules. Things like "we don't allow anyone not associated with the XYZ festival to book a spot in the 3 days leading up to the XYZ festival" are really hard to handle with a big centralized booking system - whereas they are easy to handle with a little local office that does everything by hand.
- solardev 3y agoYeah, a complex rules engine is indeed one of the challenges of such a system. But you can at least handle the most common scenarios and take some of the load off the park. Like in Yosemite, a basic Half Dome permit is handled through recreation.gov, but if you're doing overnight backpacking or big wall climbing in addition to Half Dome, those could be handled differently and outside of recreation.gov... https://www.nps.gov/yose/planyourvisit/hdpermits.htm https://www.nps.gov/yose/planyourvisit/hdpermits.htm For a festival, though, I imagine it could be handled similarly to hotel rooms... block off a certain # of sites for the exclusive use of some "XYZFEST23" coupon code or similar. Not sure if recreation.gov actually supports that, but it's not an insurmountable problem.