Recently found

 

If the Favorites on my 765T are in \Garmin\GPX\current.gpx, where are my Recently Found?

where's DorkusNimrod when you need him?

Oh, DN... where art thou 'o master? mrgreen

I suspect it's in a *.bin file.

--
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK

Current.gpx

jgermann wrote:

If the Favorites on my 765T are in \Garmin\GPX\current.gpx, where are my Recently Found?

Actually, favorites, recently found, routes, etc... are actually stored in hidden memory of the GPS. However, when the GPS boots up while connected to a computer, it writes information to the file called current.gpx so you can access the information in MapSource and other programs.

Current.gpx is an Output file only, it is never "read" by the GPS. No edits you make to the file will ever appear on the GPS.

When you open current.gpx in MapSource you will see your favorites, your programmed routes, and where you have been. Recently found are not expressly listed.

If you make changes to the GPX and then Send to GPS a file called "Temp.gpx" is created in the same directly as the Current.Gpx. The temp file will be read into GPS memory when the GPS boots. Next time the current.gpx is created, it will reflect your additions or changes.

Hope this helps

--
mbrun

.

jgermann wrote:

If the Favorites on my 765T are in \Garmin\GPX\current.gpx, where are my Recently Found?

Recently found items can only be viewed on your GPS. They are not available in current.gpx (or anytwhere else).

--
Nüvi 2595LMT

Sort Of?

mbrun wrote:

..
Current.gpx is an Output file only, it is never "read" by the GPS. No edits you make to the file will ever appear on the GPS.

..

On my 765T w/v3.90, I can connect via usb and edit Current.gpx (manually or with EPE), make additions, and they are in Favorites as soon as I reboot (disconnect). Deletions however, need to be made on the unit itself. Deletions directly to the Current.gpx file are never accepted, it seems. Also, in the Device.xml file Current.gpx is listed as both input and output (on my 765T).

I do find adding Temp.gpx or temp.gpx to work as you describe (adds to Favorites).

If you assign a category to the poi's added either way, and there is already a matching category in your Favorites, the additions will show in that category on the unit.

I've never seen the Recently Found entries, and I suspect (as others) that they are in a .bin file someplace and probably encrypted.

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

jgermann..

jgermann.. This doesn't address your Recently Found question, but I know you couldn't get the Temp.gpx file to add to Favs.

I remembered how I found this out myself, and it was because I had the unit's GPX dir in view while transferring a waypoint from MapSource directly to my 765T. It put Temp.gpx into the unit, nothing else.

So, I'm scratching my head as to why it doesn't work on yours, even if you are running v4.00 .. I would think it should work. ?

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

As was already mentioned,

As was already mentioned, the Recently Found list is stored in the nuvi's internal memory area and cannot be exported/saved from the unit to the PC nor is it stored as a file anywhere on the nuvi. They're wiped out with a unit hard reset or if you manually delete them from the unit itself.

--
nuvi 760, nuvi 765T, nuvi 855, nuvi 3790LMT, nuvi 3490LMT - SoCal area

verified as output only

Been through a bunch of steps and think the time stamp of the "temp.gpx" file may be part of the answer, but there must be something about how the file gets to my 765T.

This is not exhaustive but I did
01) connected 765T, used MapSource to send single point, safely disconnect, check favorites and single point had been added.
02) connected 765T, used Wordpad to make change to text in temp.gpx file, saved change, safely disconnect, check favorites and edited single point had been added (original single point still there).
03) connected 765T, used EPE to make change to text in temp.gpx file, saved change, safely disconnect, check favorites and re-edited single point had been added (original single point and first edited single point still there).
04) connected 765T, used EPE to make new single point file, save file on PC as temp.gpx, copied file to 765T, safely disconnect, check favorites and point not there <=====?????
05) connected 765T, used EPE to make change to second single point file, save file on 765T as temp.gpx, safely disconnect, check favorites and point is there.

Someone else try similar steps and see what you find.

Current.GPX

JD4x4 wrote:
mbrun wrote:

..
Current.gpx is an Output file only, it is never "read" by the GPS. No edits you make to the file will ever appear on the GPS.

..

On my 765T w/v3.90, I can connect via usb and edit Current.gpx (manually or with EPE), make additions, and they are in Favorites as soon as I reboot (disconnect). Deletions however, need to be made on the unit itself. Deletions directly to the Current.gpx file are never accepted, it seems. Also, in the Device.xml file Current.gpx is listed as both input and output (on my 765T).

I do find adding Temp.gpx or temp.gpx to work as you describe (adds to Favorites).

If you assign a category to the poi's added either way, and there is already a matching category in your Favorites, the additions will show in that category on the unit.

I've never seen the Recently Found entries, and I suspect (as others) that they are in a .bin file someplace and probably encrypted.

I stand corrected. I both manually edited existing name entries in Current.gpx and added a couple. Each was read into the Nuvi's internal memory as an additional entry.

--
mbrun

Current.gpx is growing...

I used EPE to edit and save favorite to Garmin device. The file size is X MBytes, smile for example.

After I reboot Garmin device, then, reconnect it to PC, the file size grows to X + Y MBytes.

Now, I understand Garmin adds other "current" stuff in this file and makes it bigger.

verified as output only

jgermann wrote:

04) connected 765T, used EPE to make new single point file, save file on PC as temp.gpx, copied file to 765T, safely disconnect, check favorites and point not there <=====?????

I have never use EPE for favorites, only POI. But I have been doing experimenting. So far I have been unsuccessful geting my 765 to read in any data from the single entry GPX files I created created using EPE, regardless of whether the file as created on my desktop or on the garmin. And whether it was named EPE.GPX or renamed to temp.gpx. However, if I open the file in mapsource and resave it 765 reads it in fine. Hmmmm....

--
mbrun

Rethinking output only

mbrun,

Let EPE save or save as something to a temp.gpx file directly to the 765 and see what happens.

Be interested in what you find out. My unit is gone for a week (daughter on vacation)

Temp.gpx files - Header is a factor

jgermann wrote:

mbrun,

Let EPE save or save as something to a temp.gpx file directly to the 765 and see what happens.

Be interested in what you find out. My unit is gone for a week (daughter on vacation)

jgermann,

Created single point temp.gpx with EPE directly on 765. Rebooted, point not in favorites.
Opened same temp.gpx with GeePeeEx Editor and saved as temp.gpx. Rebooted, point not in favorites.
Opened same temp.gpx with MapSource and saved again as temp.gpx. Rebooted...Point Now in favorites.

Create a new single point temp.gpx file with EPE and saved directly on 765. Rebooted, point not in favorites.
Opened this same temp.gpx and replaced the EPE file header information with header information from a known working mapsource file. Save file and rebooted, Point Now in favorites.

Conclusion? The header information in the file plays a factor in whether temp.gpx files created by third-party programs are read by the 765.

mbrun

--
mbrun

That was my feeling also

mbrun wrote:

Conclusion? The header information in the file plays a factor in whether temp.gpx files created by third-party programs are read by the 765.
mbrun

I think I did that header trick also and it as I recall it worked, but I don't have notes on that.

I think that the time stamp also must be greater that the time stamp on the last current.gpx.

Given that you have a temp.gpx file already on the 765, try using EPE to edit it and/or merge open another small file. then save back to 765. That seemed to work for me. However, I don't recall whether the temp.gpx file was a GoogleMap or Mapsource file to start with.

What did not work was creating the file in EPE and then saving to

Solution for adding favourites with EPE?

mbrun wrote:

Conclusion? The header information in the file plays a factor in whether temp.gpx files created by third-party programs are read by the 765.

Bingo! I played around with changing various keywords/operands.
My Nuvi 760 does not like the encoding="Windows-1252" in the <?xml> header. (both EPE and GeePeeEx use this parameter)

Mapsource uses encoding="UTF-8", and this is what works. (another solution is to simply omit encoding=)

Also, ANY .gpx file name --- temp.gpx, EPE.gpx, foo.gpx, etc. works to add favourites to my 760.

Can someone with a 765 verify that this is also the case for their unit? (Just create a single POI using EPE, then use Notepad or similar editor to remove the encoding="Windows-1252")

--
Nüvi 2595LMT

Good Catch!

WAASup wrote:
mbrun wrote:

Conclusion? The header information in the file plays a factor in whether temp.gpx files created by third-party programs are read by the 765.

Bingo! I played around with changing various keywords/operands.
My Nuvi 760 does not like the encoding="Windows-1252" in the <?xml> header. (both EPE and GeePeeEx use this parameter)

Mapsource uses encoding="UTF-8", and this is what works. (another solution is to simply omit encoding=)

Also, ANY .gpx file name --- temp.gpx, EPE.gpx, foo.gpx, etc. works to add favourites to my 760.

Can someone with a 765 verify that this is also the case for their unit? (Just create a single POI using EPE, then use Notepad or similar editor to remove the encoding="Windows-1252")

Good catch, WAASup! I don't have my765T right now, but my 200W also DOES NOT accept 'Windows-1252', but DOES 'UTF-8'.

The interesting thing is that I have EPE headers that use both encodings! After poking around, it looks like EPE will not change the encoding value if you edit a gpx that already has a UTF-8 header, but if you build a gpx from scratch with it it uses Windows-1252.

When I get my 765T back tomorrow I'll check it and report back, but something tells me that on the 765 there is also some time stamp funny business going on as well.

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

Look at your GarminDevice.xml file

WAASup wrote:

Also, ANY .gpx file name --- temp.gpx, EPE.gpx, foo.gpx, etc. works to add favourites to my 760.

It says that any file in "\Garmin\Gpx\ with an extension of .gpx is designated as "InputToUnit"

I take this to mean the current.gpx will be an input file

It also says that in the path "\Garmin\Gpx\ the file with the name Current and the extension GPX is designated as "OutputFromUnit".

I take this to mean that current.gpx is an output file.

Check again

jgermann wrote:
WAASup wrote:

Also, ANY .gpx file name --- temp.gpx, EPE.gpx, foo.gpx, etc. works to add favourites to my 760.

It says that any file in "\Garmin\Gpx\ with an extension of .gpx is designated as "InputToUnit"

I take this to mean the current.gpx will be an input file

It also says that in the path "\Garmin\Gpx\ the file with the name Current and the extension GPX is designated as "OutputFromUnit".

I take this to mean that current.gpx is an output file.

I looked at my device.xml file and it stated current,gpx is an output file only but all other files with a gpx extension were inputoutput.

--
Illiterate? Write for free help.

Saving Favorites with UTF-8 encoding

Using EPE, you can set the encoding to UTF-8 in the Preferences. You should set it to UTF-8 rather than "Same as Input". I think this is the most accepted encoding.

Starting with EPE v4.80, UTF-8 encoding will be set by default when using the "Save to Favorites" function. For all other Save or Save as, it will use the encoding from the Preferences.

If this broke something else, please let me know.

Turbo

Consider

Box Car wrote:

I looked at my device.xml file and it stated current,gpx is an output file only but all other files with a gpx extension were inputoutput.

Consider the hierarchy. Do you not think it possible that the way the xml is coded means that current.gpx only can be both input and output?

Input/Output is moot, really

I read the Device.xml as Current.gpx being both, but it's really a moot point because it's the unit software that makes the decision, yes?

And we already know there are differences in how Garmin models deal with gpx files of different names, so until we can see the unit's code it's a moot point.

Only thing I can say is that on my 765T(v390) and my 200W(v400) I can edit & save Current.gpx directly on the units via usb drive letter, and additions show in Favorites after unit reboot while deletions do not.

Your mileage may vary. grin

--
It's about the Line- If a line can be drawn between the powers granted and the rights retained, it would seem to be the same thing, whether the latter be secured by declaring that they shall not be abridged, or that the former shall not be extended.

Portability

turboccc wrote:

Using EPE, you can set the encoding to UTF-8 in the Preferences. You should set it to UTF-8 rather than "Same as Input". I think this is the most accepted encoding.

Turbo

Would it be possible to use an .ini file in the folder from which EPE is run to hold the "preferences". I think this would make EPE "portable" on a flash drive so that one would not have to review all of the changed settings when running on a new computer (like that in a friend house while one is on a trip).

Portability using ini file

Noted. I'll check.