-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to dump source #35
Comments
It looks like their firewall/proxy is misconfigured. Their webmap has query functionality (that makes a similar request as us) that is failing right now because of this error you're seeing with pyesridump: |
Okay, regardless of misconfigured firewall/proxy on their part, is there any way right now that pyesridump can scrape the data? I tried passing a custom
|
No, I don't think there's a way pyesridump can handle this server if it won't respond to the |
But you mentioned a brute force method... Did you try it on this layer and it worked? |
I have seen this behavior before on Esri servers. It's pretty rare but does happen. I can make this request as-is in both wget and chrome and get a JSON response:
So I assume that by starting at 1 (or wherever) and just incrementing until the server returns a 400/404, the data can be scraped. |
That will work for this layer because the first OID is The other annoying thing with this is that the Esri server won't do the reprojection like we do via /query for you when you query by OID. |
I've thought about ways to handle id gaps/offset but until a problematic source comes up, simple incrementing will do for now. |
Hi, just passing by, is possible dump with identify too. |
Trying to dump
https://gismaps.sedgwickcounty.org/arcgis/rest/services/Map/Op_SiteAddress_Dynamic_SP/MapServer/0
returns this error:How does one go about dumping a source that is locked down tightly like this one? Is it possible to do with pyesridump as-is? If so, could documentation be added so people who aren't well-versed in arcgis/esri/whatever-term can try different approaches to dealing with problematic servers (this is my situation)?
The text was updated successfully, but these errors were encountered: