Closed jacobdadams closed 1 year ago
Patch coverage: 99.25%
and project coverage change: +1.09%
:tada:
Comparison is base (
8cfe1e9
) 90.75% compared to head (5230fa3
) 91.85%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
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?
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.
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.
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.
@stdavis and @steveoh, I'd love a final look at this and any last thoughts you've got.
Adding a new extractor to load data from a feature layer in a REST map or feature service endpoint.