-
Notifications
You must be signed in to change notification settings - Fork 0
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
REST feature layer extractor #48
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #48 +/- ##
==========================================
+ Coverage 90.75% 91.85% +1.09%
==========================================
Files 7 7
Lines 898 1031 +133
Branches 128 146 +18
==========================================
+ Hits 815 947 +132
Misses 74 74
- Partials 9 10 +1
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks really useful. nice work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are some nice improvements. thanks for doing those.
I wonder, since you are using so many properties of the json response, that it might be best to create a class to represent that object that takes the response dictionary as a constructor and hydrates all the fields you are interested in. you could have a private method that safely pulls values out of the dictionary to set properties and some instance methods that return true or false if the service supports what it needs. yada yada. what do you think?
Ok, I think I've addressed all the different ideas and suggestions (minus creating a properties class...). Do you guys know of a non-OBJECTID service I can test the arbitrarily-named object id stuff against? |
Here's one that I just put up. Let me know when you are done testing so that I can clean it up. I just download the dataset as a shapefile and then re-uploaded it. |
Ok, duh, I could have done that :) But thank you! It works like it should. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is authenticated access to private layers on the radar?
I hadn't thought about that, but that would be a good idea. I'll add it to the list while I'm rethinking/refactoring. |
Ok, I think this is finally ready. I added access to the retry values as global variables that can be set by the client programs in case the default time/retries are not enough for a given application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great. a few comments for polish.
Adding a new extractor to load data from a feature layer in a REST map or feature service endpoint.