This is my first message and i would like to thank Orux for his work.
I'm sorry for my bad English.
I'm using OruxMaps as a remote client of Okmap.
I see that in setting of OkmapClient there isn't a indication of the ID trace and when I use
OruxMaps in combination with OkMap the trace log isn't correct:
;9.62299;44.17219166666667;46.422;07/12/2014 17:00:32;0;0;3;-65536;
;9.622639999999999;44.17170333333333;65.43305;07/12/2014 17:00:41;0;0;3;-65536;
I found these specifications from OkMap forum:
-----------
This is the string to send via socket to OkMap to implement live track (fields are separated by semicolon):
1. Id (sender identification); any string that identify your sender
2. Longitude (decimal degrees); datum is specified in Preferences NMEA (default WGS84)
3. Latitude (decimal degrees); datum is specified in Preferences NMEA (default WGS84)
4. Altitude (meters); negative for deep
5. Date-Time (MM/dd/yyyy hh:mm:ss); universal time format
6. Speed (km/h); Double.MinValue if not specified
7. Bearing (0-359.9999...); Double.MinValue if not specified
8. Track tickness in pixel (Integer); optional, if not specified will be used the value specified in preferences
9. Track color (integer ARGB 32 bit); optional, if not specified will be used the value specified in preferences
Example:
TestLive;9.137600913291672;45.506435647252495;202.20291;06/08/2012 15:09:47;0;0;3;-65536;
------------
Now isn't possible to work with two client Oruxmaps linked simultaneously at one server OkMap.
What you necessary to have set in OruxMaps to have a correct string?
Thank you and I apologize again. :roll:
Stef
Quote from: sldp2k
I'm sorry for my bad English.
I'm using OruxMaps as a remote client of Okmap.
I see that in setting of OkmapClient there isn't a indication of the ID trace and when I use
OruxMaps in combination with OkMap the trace log isn't correct:
;9.62299;44.17219166666667;46.422;07/12/2014 17:00:32;0;0;3;-65536;
;9.622639999999999;44.17170333333333;65.43305;07/12/2014 17:00:41;0;0;3;-65536;
I found these specifications from OkMap forum:
-----------
This is the string to send via socket to OkMap to implement live track (fields are separated by semicolon):
1. Id (sender identification); any string that identify your sender
2. Longitude (decimal degrees); datum is specified in Preferences NMEA (default WGS84)
3. Latitude (decimal degrees); datum is specified in Preferences NMEA (default WGS84)
4. Altitude (meters); negative for deep
5. Date-Time (MM/dd/yyyy hh:mm:ss); universal time format
6. Speed (km/h); Double.MinValue if not specified
7. Bearing (0-359.9999...); Double.MinValue if not specified
8. Track tickness in pixel (Integer); optional, if not specified will be used the value specified in preferences
9. Track color (integer ARGB 32 bit); optional, if not specified will be used the value specified in preferences
Example:
TestLive;9.137600913291672;45.506435647252495;202.20291;06/08/2012 15:09:47;0;0;3;-65536;
------------
Now isn't possible to work with two client Oruxmaps linked simultaneously at one server OkMap.
What you necessary to have set in OruxMaps to have a correct string?
Thank you and I apologize again. :roll:
Stef
Hi, Stef,
I think that the string 'Id' hasn't been mandatory ever.
OruxMaps has never sent any value, and I think that worked.
But I can add an Id in the next versions.
orux
orux
Hi Orux,
vtnks.
Now OkMap and OruxMaps work correctly only if there is a single client OruxMaps connected to the server okmap since without ID there is no way to distinguish traces from multiple client OkMap.
I have done tests with two client OruxMaps and the track on the server OkMap is unique.
I thank you Orux and i'll wait for the new version.
Bye
Stef
Hi Orux,
I ask you, if possible, to insert this change. it is really difficult to manage multiple traces sent from oruxmaps client to okmap server ... The automatic IDs you use are very long and it is important to identify with certainty who the trace is. I use oruxmaps for search and rescue. If you can thank you.
Stef