Latitude/Longitude

[bmansion]

Hello there, total newbie here!

On board my boat I have:

• various Raymarine sensors (depth sounder, speedo, anemometer, wind vane)
• Raymarine Axiom 7+ control unit
• iKommunicate
• 4GConnect
  All this works very well.

I'm currently developing a digital logbook (under FileMaker), in which I retrieve data in JSON format.
It works for all data, except for position data.
For instance:

1. The demo test at:
   https://demo.signalk.org/signalk/v1/api/vessels/urn:mrn:signalk:uuid:a6eb6272-6715-4dcc-9d44-350be66bbe8a/navigation/position/value/longitude/
   returns: 24.732977899999998 - OK

2. On my boat, the following address: http://192.168.1.243/signalk/v1/api/vessels/urn:mrn:imo:mmsi:205297570/navigation/position/value/longitude/
   returns: {}

3. The address http://192.168.1.243/signalk/v1/api/vessels/urn:mrn:imo:mmsi:205297570/navigation/position/
   Returns:
   {« timestamp":"1946-06-22T18:4:48.000Z","latitude":42.554260,"longitude":8.637043,"source":"N2000-01"}
   or:
   {"timestamp":"2016-07-06T10:42:8.000Z","latitude":42.564949,"longitude":8.757783,"source":"N2000-01"}

Questions:
a. How do I get longitude (or latitude) data alone?
b. Why is the timestamp wrong?
c. Could it be a SignalK version issue?

I searched all over the web for the answer, but without success. Not being a computer scientist, the literature on GitHub is a bit obscure to me...

Thanks in advance for your help!

[sbender9]

The iKommunicate has not been produced or updated in many years. You are stuck with what you have.

I would look into getting a more modern and supported solution.

[bmansion]

Thank you!
... "a more modern and supported solution", such as?

[mairas]

I am banging my own drum here (I am the entrepreneur of Hat Labs), but a Marine Server Kit built around Raspberry Pi CM4, Sailor Hat for Raspberry Pi, and required interface hats and running OpenPlotter will provide you a modern, upgradable system for Signal K and OpenCPN as well (if you so desire).

https://shop.hatlabs.fi/products/marine-server-kit

[bmansion]

Very interesting, thank you.
But I don't want to run OpenPlotter for now and I think managed to find a solution with what I have.
Thanks though!

[tkurki]

As to your original question: there are small differences between the Signal K Server Node.js implementation and iKommunicate APIs. As long as you get what you need for your own use it probably does not matter much. If you plan to publish/share your app it is a different story.

As for position slash latitude and longitude in Signal K it is a so called object valued property and you should use it via navigation.position path, as that is what is consistent between the http api and the streaming WebSocket api, in case you want to go that way in the future.

[bmansion]

Thank you!