-
Notifications
You must be signed in to change notification settings - Fork 13
get parameter of a observation #176
Comments
Welcome and thank you very much for pointing this out, @borg1310. I checked the according code and made the following findings:
Hence, you have the following options to get a solution for your problem:
I am sorry that I cannot provide a solution at once. If you go for number 3, I will save this as a feature request. |
hi, i implemented the feature by myself. gruss juergen [0] test_getobservationbyid.R:134: failure: POX (SOS 1.0.0) test_getobservationbyid.R:135: failure: POX (SOS 1.0.0) test_getobservationbyid.R:135: failure: POX (SOS 1.0.0) test_getobservationbyid.R:136: failure: POX (SOS 1.0.0) test_getobservationbyid.R:148: failure: POX (2.0.0) test_getobservationbyid.R:148: failure: POX (2.0.0) test_getobservationbyid.R:149: failure: POX (2.0.0) test_getobservationbyid.R:150: failure: POX (2.0.0) test_getobservationbyid.R:150: failure: POX (2.0.0) test_getobservationbyid.R:151: failure: POX (2.0.0) test_getobservationbyid.R:168: failure: file saving works (2.0.0) test_getobservationbyid.R:168: failure: file saving works (2.0.0) ══ Terminating early ═══════════════════════════════════════════════════════════ Save workspace image? [y/n/c]: n nothing to commit, working tree clean |
@nuest Could you please verify that the master branch is the correct one to provide a solution for this issue |
hi,
the parameter of following getobs response om observation [0] is not available in parsed response of sos4r [1] (slot parameter)
regards,
juergen
[0]
[1]
The text was updated successfully, but these errors were encountered: