Good morning everyone.
By studying the capabilities of the REST API better, I can now access the reports and individual values of some TAGS.
Now my problem is accessing a set of values for which I am not receiving the value I expect.
If I query the value
I would wait to receive the value 26.036540985107422 as reported in line:
0022.1019 (OphthalmicAxialLength): 26.036540985107422
but in the file I find 4 incomprehensible characters corresponding to the HEX sequence d6 4a d0 41.
Can anyone tell me why this happens?
The interested part of the source istance is in this image:
Thank you Alain
I’ve just tried this way but with no result
If I use the /tags route with no other parameters I get all the tags in instance, if I use the full path to get a single value the result is “404 not found”, I think because this command looks for the tags under the requested position and not for the content of the TAG; if I use the /content switch I get the same result of the first post in topic.
This is the istance full image
No more ideas? Do you think I must parse all the /tags report to extract the values I need?
Isn’t there an easyer or faster way to reach my goal? Really cannot I get the float value of a single tag?
Isn’t there a way to convert the raw value in its relative float value?
Of course. Parsing JSON is a piece of cake for any scripting language.
Really cannot I get the float value of a single tag?
No, you are actually the first one to request such a low level API route. All human readable tags are available in the /tags route. The /content route is only useful for binary tags that can not be represented in a JSON document.
I think that the overhead (TCP/IP , HTTP,…) of a request that would retrieve a single float value makes it quite useless compared to calling /tags and picking the required value.
Plus maybe this would lead some beginners to perform a zillion requests to retrieve many tags, which would be cataclysmic in terms of performance.
