Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ianL

Hello Menion

I have checked the link that you provided and all the associated sub-links but unfortunately my problem remains
1  When I export caches from c:geo to Locus using the method outlined in User Guide:
the logs that are in the c:geo cache details are not transferred to Locus
2  (for the record only - I do not want to use this function) If I then select the cache "point" in Data Manager, go on-line and select "Jigsaw puzzle piece"/Download logs I get the logs stored for off-line use but the Listing information (from c:geo} is also deleted and replaced by the webpage link
I suspect that this is all about basic membership limits but it makes me think that GC4L is not really a practical possibility for basic members wishing to cache offline
If there is no solution to my problem #1 then I can use the .gpx export method I outlined before

Add-ons / GC4L v c:geo For Downloading Caches
May 19, 2016, 00:10:49
I do a small amount of geocaching via basic membership of
Since the most recent updates to Locus Pro v 3.16.2 and G4L v 2.1.4 I can no longer download full details of even one cache  GC4L seems to be unusable for basic members so I therefore use c:geo and (as Locus User Guide) use 
Stored/Menu/Show on Map/Export to Locus which transfers the details directly to Locus Data Manager Points folders All details are then available for each cache in Locus except the logs and images are not shown  If I then use "Download logs" in Data Manager the logs are downloaded and remain available offline but the Listing is then deleted and no longer available offline
If in c:geo I use Stored/Menu/Export/GPX and then Import to Locus all details including logs (but not images) are transferred I can live without the images in Locus but perhaps someone could advise me please how to get the logs to Locus via the Stored/Menu/Show on Map/Export to Locus route

Many thanks
Thanks for that clarification - the light has switched on!   As a test I have again imported  Nearest caches and as you advise I get the  window in your Reply #1 with 'Warning Empty selected folder'  when on the previous screen I have checked the box with 'Empty selected folder'
A point of detail In the context of the Warning screen the words 'Empty selected folder' are strictly in English read as an instruction to the user to take action and that is what fooled me The correct wording is the advisory 'Selected folder will be emptied' Not important for experienced users but useful for a first timer Perhaps this small point could be  considered by the developers
Again thanks for your help
Many thanks for the guidance
1  Your suggestion for improvements to Backup Agree and will give this a vote
2 Warning:  Empty folder etc Thanks for the way out of this problem My recollection is that the window I saw  with the Empty ... etc was different than this Will do some tests and get it sorted for future Do you know why there is such a small limit to the maximum size a folder can be? In this case I had only approx 100 very standard caches without images
I am using Locus Pro Ver 3.16.2 and Geocaching4Locus/ Ver 2.1.4

When importing some caches using G4L/Nearest I noticed 'Warning: Empty folder' (or similar)  Thinking I had plenty of storage space anyway I continued and found that all previous data in the destination folder was deleted    I suggest the on-screen warning should be expanded to read 'Warning: Existng data will be deleted Empty folder' or similar

I then read the manual about Backup Manager/Restore  There is little information here  I followed the dialogue boxes and selected the latest auto backup file and ticked Field notes and Points/Tracks   I was expecting but do not recall seeing an option to select Restore for just the folder I had messed up   The app restarted and I had lost in every folder any new data created after the date of the backup file  Again have I missed something?  If not then it would be great if the manual could say just a little bit more to help  The implications for me this time are not huge but I can see it may have been useful for me to have done a manual backup before trying to recover the old folder  Is there any way to then recover the missing new data?  Or could I before the Restore have renamed all the existing folders I did not want to lose and then do some folder renaming and deleting afterwards?  All seems a bit messy  Is there a better way?  I have not found any relevant previosu post

Any assistance or reference to relevant post would be greatly appreciated
A very clear reply and thanks for the link
The problem obviously sits with the Orux .kml file definitions
Sorry for the bother
Hello Menion
Some further observations on the above topic
Back on December 21 2015 I advised that the waypoint icons from Orux .gpx tracks (black dots) were now correctly positioned 
I did not at that time re- check on the icons from Orux .kml tracks (balloons/inverted tear-drops) Refer my reply of 25 November 2015  I note that the balloon icons are still positioned to touch true location at top centre  See screen shots  All icons have exactly the same coordinates  I note also that the brown "i" icon from Locus seems to move a little at high zooms

Perhaps a fix for the balloon icon can be arranged at some future date
Ver 3.14.0 (Free) has definitely fixed the original problem  When I import OruxMaps .gpx tracks the waypoint icons are now positioned correctly relative to the waypoint coordinates
Merry Christmas
Hello menion

Effective analysis + clear explanation + decision to take action = normal service from Locus 
Impressive  Thanks for the very satisfactory outcome
Hello balloni55
Thanks for taking an interest in this matter This is important to me because the black dot icons give a false idea about the location of places I am trying to find sometimes in heavy forest

I have taken your lead about the created icon size and looked at that from another angle 
Put the map centre (cursor) exactly on the coordinates for one of the black dot POI's  (My method - tap on black dot and then follow the pop-up labels, select "Point detail" and then tap the map symbol at bottom)  The black dot is shown with a clear gap to the cursor and gives the appearance of being unrelated to the POI at map centre  Then zoom up and down  The black dot stays fixed relative to the cursor   Measurement from icon to map centre is approximately 2.5mm on screen ie about 80 pixels on my phone   The 24x24 icon still would not touch the map centre at bottom of icon
Conclusion?  Your idea about the icon size is right  If the appropriate icon was selected then our problems would disappear  The original Orux icon was an inverted tear-drop touching true location at bottom centre but in Locus this has changed to a black dot which does not touch the true POI location As noted before the start and finish circles are perfectly centred on location so it seems to be a Locus icon selection problem  Is that right?
I like the use of blue or black dots for generic waypoints centred on the POI true location  Is that possible to do?

Just to demonstrate a little further I have attached a .kml version of the same track  This shows the POI icons with both the black dot and the Orux type tear-drop  Note however that the tear-drop icons touch the true location at TOP-CENTRE (approximately)!  May be there are some wider problems with icon selection/positioning

Thanks again

EDIT/CORRECTION   Reference to 80 pixels above should be 40 pixels

Here is a file  Hope it is attached The Preview did not show it!

To demonstrate I go to zoom 22 place screen centre cursor on a black square then go out to zoom 16  The black square moves about 50 - 60m north  Do the same for the start or finish circles and the icon stays in perfect centre of cursor

In .gpx text I see the waypoint 'type' is Starting Point and Finishing Point for the circle icons and Waypoint for the black squares

Hope you can make somethings from this

On a regular basis I import .gpx  track files that are generated in OruxMaps  The files show recorded tracks and associated waypoints  When the files are displayed in Locus Map Free (v 3.12.2) the manually created waypoints are displayed as small black squares  Start and end waypoints are green and red circles  At zoom 20 - 22 the black squares are on or very close to the track   On zooming out the black squares move off the track   At zoom 16 the black squares are displayed approx 50-60m north of the true position  The track and the start/end waypoints remain in the correct position throughout 

As a check I have imported .gpx files from other sources:
1  BaseCamp  A route prepared using 'Via Points'  These points also appear in Locus as small black squares that move north as I zoom out  However, when the route is prepared using Blue Flag waypoints the display in Locus appears to be correct for all zoom levels
2  GraphHopper  On-line route and waypoints displayed correctly for all zoom levels

Another Locus (Pro) user has replicated the above behaviour

Can someone please direct me to a relevant previous post or advise how I can overcome this problem of the shifting waypoints?  I can provide a .gpx file if useful