Use pyodk for ODK Central API calls #212
Replies: 3 comments 2 replies
-
OdkClient.py pre-dates pyodk,but offers slightly different functionality. Also osm-fieldwork has the odk_client program, which offers a command line interface which I use frequently. I haven't looked at pyodk for a while, but it was lacking functionality FMTM needs, and the only command line utility was unmaintained. |
Beta Was this translation helpful? Give feedback.
-
OdkCentral.py is just one program in osm-fieldwork. :-) It has been handling requests nicely, so why replace it ? If OdkCentral.py was missing and endpoint, for example entities and dataset support, that would be a reason to use pyodk in addition to OdkCentral.py. |
Beta Was this translation helpful? Give feedback.
-
(put this in main thread for clarity) On second thought, it's probably not worth the hassle. We would have to wrap each pyodk call we need in a method of OdkClient or OdkUser anyway, so it doesn't really reduce maintenance. We already handle session pooling, so the only advantage I see is perhaps better error handling of failed responses from Central. If we don't need Entity/Dataset endpoints either, then this probably doesn't make sense. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
requests
library.pyodk
a year ago & in theory it should track any future updates to the API.The question is: should we use pyodk instead of managing this ourselves in OdkCentral.py?
This could be implemented alongside #206 if we decide to go that route.
Beta Was this translation helpful? Give feedback.
All reactions