How far gone?

[N4TRB0Y]

I was stoked to find this tool after suffering painfully trying to book (and failing to book) a campsite on the washington.goingtocamp web shite.

On another sad note, I think they may have changed their data structures, causing this awesome gocamp python tool to be in need of some overhaul.

I spent some time trying to fix a few small items. For example: results['resourcesOnMap'] now seems to be results['map']['mapResources']

Then as I went further I realized I can't even seem to find allowedEquipment in the results...

Wondering if the original contributor(s) have any insight into how salvageable this is. Happy to contribute myself but might benefit from the author's wisdom/insights.

[peckjon]

Hi @N4TRB0Y !

This project has been latent for the last year, but I finally stepped back into it just this week to discover, much to my horror, that goingtocamp has changed enough to make this project incompatible. Unfortunately, since this is all unofficially reverse-engineered from their web API, it'll take some time for me to go though the browser calls and revise (assuming it is even possible).

No immediate timeline, I'm afraid... but since they've "updated" the website to make it even LESS usable than last year (I didn't think it was possible!), there's certainly impetus for me to scope this out.

I'll let you know here if I'm able to find time to make any progress. Meanwhile, I absolutely welcome contributions if you or a colleague have time to send a PR along!

[thomasruns]

I also discovered that this wasn't up to date a year or so ago when I found it, so I wrote my own that worked great.. until sometime between last Friday, 5/7 (the last time I know for sure it worked) and today. At first I thought they had just blocked my IP address, but after further testing it looks like they locked it down to only accept requests from their own domain. I just figured I would pass that along to possibly save you some time in case it's just not possible to "fix" this after their changes.

[peckjon]

Thanks for the info @thomasruns! It might be possible to circumvent this... but yeah, probably not going to have time to fix it this season; maybe in Fall. Is your own project opensource (or would you be willing to open it)? Would love to take a look.

[thomasruns]

Unfortunately no, it's part of a project with some private family stuff in it. But basically I store the campgrounds, dates, etc in a database, then the code loops through each one and checks the appropriate reservation system.

I made a gist with the chunk of code that was making the request for goingtocamp campgrounds and parsing the response. It's some quick and dirty PHP I made last summer with plans to clean up over the winter which I never got around to. Anyway, this is what was working as of Friday: https://gist.github.com/thomasruns/aa79f32b7898f9f8055cd2be853d9fbc

[thomasruns]

I have no idea how long it will last, but their web api is open again so my tracker is working instead of returning 403 responses.

[stanraye3]

It looks like mapLinkLocalizedValues has been removed from MAPDATA results in list_camp_areas() :(
for map_id, info in results['mapLinkLocalizedValues'].items():
KeyError: 'mapLinkLocalizedValues'

[peckjon]

Sadly, yes. I haven’t been able to find a replacement source for that data.

[Justin31415]

Is it others' observations that in addition to this being outdated, that the service has been changed to prevent automated access. I'm running into captcha when just trying to load the page via Selenium/Puppeteer

[thomasruns]

They definitely changed some things over the last year, but I have been able to automate it again. My code on camperalerts.com has been scanning for several days now without any errors. I don't mind sharing what I changed to get it working, but I don't want to post it publicly here where someone could use that information to break my code :) Shoot me a message at gmail (same username) and we can chat.

[peckjon]

That's awesome, @thomasruns! Will do.

If you think the API portions could be broken out as a separate module from the rest of your site, I'd love to see that portion go public... unless you're specifically worried about the goingtocamp folks re-obfuscating the API based on what they see you using? In which case... actually, posting publicly might still be the best course. There's more of us OSS devs than there are of them :-o

[acaloiaro]

FYI @thomasruns @N4TRB0Y @Justin31415 Thanks to @peckjon providing a nice reference point with gocamp, I've begun to recreate its functionality in camply.

Feel free to track the issue with my draft PR attached: juftin/camply#94 and snag any of the code. It's in very rough shape at the moment. More of a proof of concept, but you can snag some of my code and port it back to gocamp if you like.