This object is in archive!
Weird circles with numbers shown on map after import with new version 3.50.0
Solved
Hi,
I just installed the new version 3.50.0 and then imported a new track previously created with routeconverter (as I do every week). Now there are weird circles with numbers shown on the map when displaying the track. How can I switch off these circles? And what are the numbers?
BR
tkansgar
The same problem 
Hello ,
We apologize for the inconvenience.
Can you please send a screenshot?
Thank you
Have a nice day
Andrea
Hello ,
We apologize for the inconvenience.
Can you please send a screenshot?
Thank you
Have a nice day
Andrea
To do.
Track has multiple waypoints ?
1. Zoom in: Circles gone ?
2. Check: Settings > Points & Tracks > Enable POI grouping > Deselect.
3. Not solved ? + Attach example file to test
To do.
Track has multiple waypoints ?
1. Zoom in: Circles gone ?
2. Check: Settings > Points & Tracks > Enable POI grouping > Deselect.
3. Not solved ? + Attach example file to test
Hi, please post the track GPX for testing here and a screenshot of the issue. Thanks.
Hi, please post the track GPX for testing here and a screenshot of the issue. Thanks.
Hi,
> Track has multiple waypoints ?
No, I don't have any waypoints in my tracks created with routeconverter. There are only track points.
> 1. Zoom in: Circles gone ?
Here Locus Map behaves some what differently. On my first zoom I saw additional circles at some intermedate points. But when zooming in more closely, all circles are gone. Only very, very small circles (without numbers) are visible on each track point of the newly imported track (not so on older imported tracks). Now, when zooming out and in again, less number circles are displayed at the same zoom levels than before.
When zooming out, the concentration of number circles remains nearly constant (some intermedate circles disapear, additional circles appear at some newly visible track points).
> 2. Check: Settings > Points & Tracks > Enable POI grouping > Deselect.
The number circles are gone now, but the very, very small circles remain.
My newest imported track is attaceched here. To provide a screenshot I first must install a screenshot app on my device now.
Hi,
> Track has multiple waypoints ?
No, I don't have any waypoints in my tracks created with routeconverter. There are only track points.
> 1. Zoom in: Circles gone ?
Here Locus Map behaves some what differently. On my first zoom I saw additional circles at some intermedate points. But when zooming in more closely, all circles are gone. Only very, very small circles (without numbers) are visible on each track point of the newly imported track (not so on older imported tracks). Now, when zooming out and in again, less number circles are displayed at the same zoom levels than before.
When zooming out, the concentration of number circles remains nearly constant (some intermedate circles disapear, additional circles appear at some newly visible track points).
> 2. Check: Settings > Points & Tracks > Enable POI grouping > Deselect.
The number circles are gone now, but the very, very small circles remain.
My newest imported track is attaceched here. To provide a screenshot I first must install a screenshot app on my device now.
Know why this happens . Surpise by routeconvertor unknown. I plublish a changed file. Later tell you more
Know why this happens . Surpise by routeconvertor unknown. I plublish a changed file. Later tell you more
You mean, that routeconvertor each track point gives a name? Locus Map never had an issue with that before.
Will the very, very small circles also disappear in your new version? They violate the map screen when zooming out more and more.
And last question: It's an import issue, right? So I must reimport my gpx file with your new version?
You mean, that routeconvertor each track point gives a name? Locus Map never had an issue with that before.
Will the very, very small circles also disappear in your new version? They violate the map screen when zooming out more and more.
And last question: It's an import issue, right? So I must reimport my gpx file with your new version?
@ tkansgar
Correct. I had to sleep on this first. Next I will discuss this with Menion. You can certainly avoid this.
By the way, do you know for what purpose Route converter adds names to each track point? Or is it just leftovers from conversions?
@ Menion
Dozens of tracks tracked and tested, no comment from LM4 beta, but didn't expect this Route Converter conversion result.
Too late, was already possible years ago, but the simple system by a track unfortunately has been stolen away in front of us.
Anyway Route You also can offer the more exclusive Locus direct route version as a download. They already have 19 different choices for various GPS and apps, but another one extra is possible. The GPS world is already quite incompatible from the past. The best food for Gps Babel and Route converter.
The direct route mode is present in Locus for two years without problems, so now be quick before someone else steals it back.
The associated waypoint method is not possible as this pollutes the info waypoint list added with every track or route download.
Info wpt are always positioned around tracks or route, usually fed by the city or municipality tourist office to promote the region you will be driving through.
These wpts contain so location targeted, more beautiful and above all much more complete information than you can ever put in universal osm poi lists.
@ Menion pse let me know what you prefee, than I can quickly inform the contact designer. Suppose now prefer the direct(rte) route mode ?
@ tkansgar
Correct. I had to sleep on this first. Next I will discuss this with Menion. You can certainly avoid this.
By the way, do you know for what purpose Route converter adds names to each track point? Or is it just leftovers from conversions?
@ Menion
Dozens of tracks tracked and tested, no comment from LM4 beta, but didn't expect this Route Converter conversion result.
Too late, was already possible years ago, but the simple system by a track unfortunately has been stolen away in front of us.
Anyway Route You also can offer the more exclusive Locus direct route version as a download. They already have 19 different choices for various GPS and apps, but another one extra is possible. The GPS world is already quite incompatible from the past. The best food for Gps Babel and Route converter.
The direct route mode is present in Locus for two years without problems, so now be quick before someone else steals it back.
The associated waypoint method is not possible as this pollutes the info waypoint list added with every track or route download.
Info wpt are always positioned around tracks or route, usually fed by the city or municipality tourist office to promote the region you will be driving through.
These wpts contain so location targeted, more beautiful and above all much more complete information than you can ever put in universal osm poi lists.
@ Menion pse let me know what you prefee, than I can quickly inform the contact designer. Suppose now prefer the direct(rte) route mode ?
@ tkansgar next comment is not about you personally.
As It is good that you reported the problem quickly. As a user, you simply experience what your tools export.
@ Menion. I have to admit that it upsets me a bit that such weird built-up files will torpedo a possibly nice project. Notice also the strange timestamps. You know, my uncle was a small farmer. But his dunghill contained more discipline than some of the GPS files produced. Exported GPS files need to be properly and correctly constructed, but unfortunately some results are just very sad to see.
@ tkansgar next comment is not about you personally.
As It is good that you reported the problem quickly. As a user, you simply experience what your tools export.
@ Menion. I have to admit that it upsets me a bit that such weird built-up files will torpedo a possibly nice project. Notice also the strange timestamps. You know, my uncle was a small farmer. But his dunghill contained more discipline than some of the GPS files produced. Exported GPS files need to be properly and correctly constructed, but unfortunately some results are just very sad to see.
@ tkansgar
You can easily and quickly solve the problem with incorrect timestamps with following program.
http://www.gpstrackeditor.com/
@ import, the program immediately notices incorrect timestamps and proposes to solve this. In the pop-up than choose the average speed. This way you can export a corrected gpx file back within a minute with now perfect and relevant timestamps. The program supports basic elements latitude longitude Altitude Time. Bonus: The name element is gone.
@ Menion
Problems with navigation instructions or not can be solved fairly elegantly.
Only you still have to do some extra work for this, sorry. I suspect simple.
If you know the history of the Locus forum you than will notice that it is often not all good for everyone.
Send a gpx file without navigation instructions, you will later be asked to attach navigation instructions. (Difficult)
Send a gpx file with navigation instructions and sometimes find complaints that these are polluting the track display.
This with navigation instructions in system associated waypoints as well as in route points or now also track points.
Proposal: Function Set
EXISTS. At gpx file gpx export select to attach navigation waypoints or not.
NEW. At gpx file import select whether you want to import display and use the specific navigation instructions or not.
@ tkansgar
You can easily and quickly solve the problem with incorrect timestamps with following program.
http://www.gpstrackeditor.com/
@ import, the program immediately notices incorrect timestamps and proposes to solve this. In the pop-up than choose the average speed. This way you can export a corrected gpx file back within a minute with now perfect and relevant timestamps. The program supports basic elements latitude longitude Altitude Time. Bonus: The name element is gone.
@ Menion
Problems with navigation instructions or not can be solved fairly elegantly.
Only you still have to do some extra work for this, sorry. I suspect simple.
If you know the history of the Locus forum you than will notice that it is often not all good for everyone.
Send a gpx file without navigation instructions, you will later be asked to attach navigation instructions. (Difficult)
Send a gpx file with navigation instructions and sometimes find complaints that these are polluting the track display.
This with navigation instructions in system associated waypoints as well as in route points or now also track points.
Proposal: Function Set
EXISTS. At gpx file gpx export select to attach navigation waypoints or not.
NEW. At gpx file import select whether you want to import display and use the specific navigation instructions or not.
@tkansgar
A way to prevent routeconverter to store the name element in the gpx file can be found here in the routconverter forum.
To correct timestamps between waypoints in routeconverter you can do the following (sorry sometimes I have to use german):
(1.) Make sure that you can see the column "Zeit" in the waypoint grid (right click on the grid header --> check "Zeit" in the popup menu).
(2.) Correct the column "Zeit" of the first waypoint by doubleclick on the column "Zeit" of that waypoint. For example "00:00:00"
(3.) Do the same with the last waypoint in grid. For example "04:00:00".
(4.) Mark first waypoint in grid via Click.
(5.) Mark last waypoint in grid via Shift + Click.
(6.) Right Click in grid and select "Vervollständigen...->Zeit"
(7.) The waypoints betwenn first and last waypoint should be correcteted.
Unfortunately the Field "Dauer" above the grid only gets updated when you save and reopen the gpx file.
See also attached file corrected with routeconverter.
PS: I always rename my name element in the gpx-file with unique numbers via routeconverter function and have so far no problems when importing these gpx-files to locus pro.
PPS: I just discovered that you might repeat steps (3.) to (7.) a second time. In first run routconverter sets the time of the last waypoint to "20:00:00". Do not know why. If you correct the time of the last waypoint back to "04:00:00" again everything works as expected.
@tkansgar
A way to prevent routeconverter to store the name element in the gpx file can be found here in the routconverter forum.
To correct timestamps between waypoints in routeconverter you can do the following (sorry sometimes I have to use german):
(1.) Make sure that you can see the column "Zeit" in the waypoint grid (right click on the grid header --> check "Zeit" in the popup menu).
(2.) Correct the column "Zeit" of the first waypoint by doubleclick on the column "Zeit" of that waypoint. For example "00:00:00"
(3.) Do the same with the last waypoint in grid. For example "04:00:00".
(4.) Mark first waypoint in grid via Click.
(5.) Mark last waypoint in grid via Shift + Click.
(6.) Right Click in grid and select "Vervollständigen...->Zeit"
(7.) The waypoints betwenn first and last waypoint should be correcteted.
Unfortunately the Field "Dauer" above the grid only gets updated when you save and reopen the gpx file.
See also attached file corrected with routeconverter.
PS: I always rename my name element in the gpx-file with unique numbers via routeconverter function and have so far no problems when importing these gpx-files to locus pro.
PPS: I just discovered that you might repeat steps (3.) to (7.) a second time. In first run routconverter sets the time of the last waypoint to "20:00:00". Do not know why. If you correct the time of the last waypoint back to "04:00:00" again everything works as expected.
Hello guys,
you have quite a long discussion here :).
The problem, as correctly mentioned between lines
- since 3.50.0, Locus Map loads trkpt a little different. It uses a similar tool as for loading rtept points. The result is, that in case, trkpt contains any additional metadata, like name or comment, simple location is converted into waypoint > sorry.
The reason for this was to allow attaching of navigation commands directly into <trkpt>.
Solution:
New version 3.50.1 will be published during the next few days. Only in case, trkpt will contains and navigation instructions, it will be converted to the waypoint. Otherwise, it will remain good old trackpoint as before.
Sorry for this minor issue.
Menion
Hello guys,
you have quite a long discussion here :).
The problem, as correctly mentioned between lines
- since 3.50.0, Locus Map loads trkpt a little different. It uses a similar tool as for loading rtept points. The result is, that in case, trkpt contains any additional metadata, like name or comment, simple location is converted into waypoint > sorry.
The reason for this was to allow attaching of navigation commands directly into <trkpt>.
Solution:
New version 3.50.1 will be published during the next few days. Only in case, trkpt will contains and navigation instructions, it will be converted to the waypoint. Otherwise, it will remain good old trackpoint as before.
Sorry for this minor issue.
Menion
Replies have been locked on this page!