Jump to content

Improved Export From Gsak To Memory Map


roolku

Recommended Posts

Okay, nearly there.

 

Can export to memory map fine using the script which used to link to the exported HTML files.

NOW using GSAK 7 the exported HTML files are no longer named _1, _2 etc etc but are named as per their GC code, the result tapping the PDA screen on an icon no longer links to a HTML cache page.

 

I can't find where to change the HTML name back to a running number, any clues please.

Link to comment

In your CSV.XSL file, find

 

<xsl:text>\Storage Card\Cache\</xsl:text>

 

Change the NEXT line to (sorry, cant remem what the line said before I changed it!) :

 

<xsl:value-of select="gpx:name"/>

 

to give you :

 

<xsl:text>\Storage Card\Cache\</xsl:text>

<xsl:value-of select="gpx:name"/>

<xsl:text>.htm</xsl:text>

Link to comment

Okay tried that, no improvements, what that gives me is:

 

HTML generates all the cache pages with their title as the code i.e GC codes or TP codes for trigs.

 

The custom export for Memory Map gives the correct icons as before but clicking on the PDA still gives "unable to find page" and it is looking for an HTML file that isnt anything like the HTML page name.

 

Could someone using GSAK 7 to use this script to export to MM and linking to the generated HTML files within a PDA have a look at their HTML export settings and the CSV script section as outlined by PUP above, and let me know what they are.

 

Previously my HTML export gave cache pages numbered _1, _2 etc etc up to the number of caches involved and the MM icons linked diectly to them, now there is some mismatch between the two.

 

Many thanks.

Link to comment

This is becoming frustrating.

 

Using the code provided (thank you pirates) the custom export doesn't generate icons that link to the GC codes as generated in the HTML export.

 

Substituting the script line <xsl:value-of select="gpx:name" />

with <xsl:number/>

 

generates MM icons that link to the numbered HTML pages as with GSAK 6 but the HTML pages are named with the full GC codes so the two will never match up.

 

I have discarded the code "gpx:name" etc for thr number/ one as I know this previously worked, just need the help for the HTML generation to match it, any ideas?

Link to comment

You may be going about this the wrong way, rather than getting the script to match GSAK, is it possible for GSAK to match the script?

I have had a look at both v6 and v7, I can't find a setting in either that handles the export naming. Checked the forums, and it's a non-customisable change.

Actually, the new way of doing it is nicer, a unique ID. (reasons)

I have no experience with the XSL (and no need for it), but may take a look at it out of interest sometime.

 

 

For the exact reason of simplicity is why GSAK has now got a Memory-Map export feature built in. There's a box in this export that allows you to fill in the file path (with GSAK tags, %code)

Link to comment

I'm running GSAK 6.6.4 i have followed the instructions with no problem until this stage

 

in GASK open "File/Export/GPSBabel custom export" and put the following line in the box that says "GPSBabel statement ..." (you might want to adapt the output path to your requirement)

 

msxsl temp\babel.gpx mxf.xsl -o d:\geocache.mxf

 

There is no "GPSBabel Custom Export" Option, just a "Custom Export" Option

I tried the "Custom Export" option but under that section the is no "GPSBabel Statement" box

 

any help appreciated

 

Cheers

 

Andy

Link to comment

Okay, thanks for the assistance so far.

 

The new GSAK7 HTML export just provides a GC code as the HTML page, this cannot be changed and is a new improvement.

 

Accepting this I now need to change the script to generate memory map exports under custom exports that generates an icon that links to a GC named HTML page.

 

Using the script provided by PUP it creates a link to an HTML file that has a name the same as the hint!

 

Having now edited my script so many times I am not overly sure where the mistakes exist.

 

Could someone who is successfully running this script on GSAK7 post the lines of script that are around the "<xsl:text>\Storage Card\Cache Files\</xsl:text>" line that generates this correctly please.

 

This is currently driving me to distraction so failing that if there is a script guru I could send mine to look at that would be excellent.

 

Thanks, again.

Link to comment

Odd that it works for me, between the comments :

 

<!-- everything else (unfound traditional larger than micro) -->

<xsl:otherwise>

<xsl:text>06</xsl:text>

</xsl:otherwise>

</xsl:choose>

<xsl:text>, "</xsl:text>

<xsl:value-of select="gpx:desc"/>

<xsl:text>", "</xsl:text>

<xsl:value-of select="gpx:name"/>

<xsl:text>", "</xsl:text>

<xsl:text>\Storage Card\Cache\</xsl:text>

<xsl:value-of select="gpx:name"/>

<xsl:text>.htm</xsl:text>

<xsl:text>", 0.0</xsl:text>

<xsl:text>, 1</xsl:text>

<xsl:text>, "</xsl:text>

<xsl:value-of select="gpx:name"/>

<xsl:text>", 1</xsl:text>

<xsl:text>, 1</xsl:text>

<xsl:text>, "</xsl:text>

<xsl:choose>

<!-- Other -->

Link to comment

OK, now releasing a working version (TBs, Owned, Found, Archived/Temp Dis) of the GSAK memory-map export.

This is set up to use LE's icons and the new memory-map export function which is now built into GSAK.

 

Plus, this version supports trigs in the form from T:UK.

 

Thanks to dakar4x4 for assisting with some of the code, and persuading me to continue this.

 

http://grand.edgemaster.googlepages.com/MMExport.zip

Link to comment

Just a side note, I use a different numbering scheme for icons from the roolku script, so you may wish to delete all icons before swapping. (They'll be re-added on first import)

 

Overlay > Icons... > Remove

 

Also, this script is highly customisable, if you keep UK benchmark and flush-bracket listings in GSAK (as I do) the macro can easily be changed to give them icons. I have a set of icons for these here.

Link to comment

OK.... upgraded to GSAK V7. I got those lovely icons to work fine in V6 but now with V7 I got a problem!

Export - Custom Export only gives me 100 caches in the resultant csv file (there are 300 caches in the GSAK database). This export worked fine on V6 so I wonder if it is something in V7?

Custom Export is using this statement:

"c:\program files\gsak\msxsl" "c:\program files\gsak\temp\babel.gpx" csv.xsl -o "c:\custom.csv"

 

If I export using Export - Memory Map I get all 300.

 

Another problem with Export - Memory Map is that all micros show as a blue dot! The other caches show the correct icons.

Export - Memory Map is using this script which Edge kindly posted: C:\Program Files\GSAK\Macros\icons.txt

 

Hmmmm.. any help appreciated!

Chris

Edited by The Blorenges
Link to comment

OK.... upgraded to GSAK V7. I got those lovely icons to work fine in V6 but now with V7 I got a problem!

Export - Custom Export only gives me 100 caches in the resultant csv file (there are 300 caches in the GSAK database). This export worked fine on V6 so I wonder if it is something in V7?

Custom Export is using this statement:

"c:\program files\gsak\msxsl" "c:\program files\gsak\temp\babel.gpx" csv.xsl -o "c:\custom.csv"

 

If I export using Export - Memory Map I get all 300.

 

I think v7 uses the settings in the GPX export dialog...

 

Another problem with Export - Memory Map is that all micros show as a blue dot! The other caches show the correct icons.

Export - Memory Map is using this script which Edge kindly posted: C:\Program Files\GSAK\Macros\icons.txt

 

Will look into this, probably a typo somewhere ;)

Link to comment

Another problem with Export - Memory Map is that all micros show as a blue dot! The other caches show the correct icons.

Export - Memory Map is using this script which Edge kindly posted: C:\Program Files\GSAK\Macros\icons.txt

 

Will look into this, probably a typo somewhere :lol:

 

Oops, forgot to add micros to my memory.txt file included there, that'll teach me to juggle versions. ;)

 

A new version has been uploaded to the link above.

 

Yes, I've also reshuffled memory.txt's IDs some more, added default types for all child waypoints, and corrected a variable name that was lingering from an older revision.

Edited by Edgemaster
Link to comment

Regarding lordelphs icons, from the GSAK documentation, if you place them in the "UserImages" directory under GSAK (and edit your memory.txt accordingly to point there for them) they are automatically included in GSAK's backups. This could be handy for future upgrades with GSAK!

 

Cheers

 

Jon

Link to comment

Just updated my version of Edgemasters export script to utilise the Motorway Mayhem icons in Lordelphs collection. I added the following (along with additonal entries for the icons in the lookup file memory.txt): -

 

# If this is a Motorway Mayhem cache assign MM icon name
if upper(left($d_Name,15)) = "MOTORWAY MAYHEM" AND $wCacheType = "Traditional"
$wCacheType = "MM"
EndIf

# If this is a Traditional cache in a Micro container assign
# special micro icon
If $d_Container = "Micro" AND $wCacheType = "Traditional"
$wCacheType = "Micro"
EndIf

 

Are there any Motorway Mayhem caches that use other wording, such as M-WAY MAYHAM etc... that I need to check for???

 

Cheers

 

Jon

 

Edited to check on Waypoint name not description

Edited by dakar4x4
Link to comment

Just updated my version of Edgemasters export script to utilise the Motorway Mayhem icons in Lordelphs collection. I added the following (along with additonal entries for the icons in the lookup file memory.txt): -

 

Are there any Motorway Mayhem caches that use other wording, such as M-WAY MAYHAM etc... that I need to check for???

 

Cheers

 

Jon

 

Edited to check on Waypoint name not description

 

I had this thought too, I forgot to do anything about it though. I know that the G:UK scrollable map uses the word Motorway as the key (since my Motorway Maybe cache gets listed as a MM).

From adambro's MM bookmark list, they all have the name Motorway Mayhem (in mixing cases, and sometimes with punctuation surrounding) except for one, named Motorway Madness which is on a junction that has never been opened.

 

To cover the caches named something like 'M12 Somewhere services (Motorway Mayhem), I have slightly changed the matching condition from dakar4x4's -

If not(at("MOTORWAY MAYHEM", upper($d_Name)) = 0)
if $cacheType = "Traditional" OR $cacheType = "Letterbox"
$cacheType = "MM"
EndIf
EndIf

I'm matching the letterbox too, since currently the only UK letterbox MM is at the coords given.

 

Updated files here.

Link to comment

To cover the caches named something like 'M12 Somewhere services (Motorway Mayhem), I have slightly changed the matching condition from dakar4x4's -

If not(at("MOTORWAY MAYHEM", upper($d_Name)) = 0)
if $cacheType = "Traditional" OR $cacheType = "Letterbox"
$cacheType = "MM"
EndIf
EndIf

I'm matching the letterbox too, since currently the only UK letterbox MM is at the coords given.

 

Updated files here.

 

Thanks for that, top stuff. I see as well as Traditional and the Letterbox type you mentioned, there are also Multi cache and Mystery Motorway Mayhems... I guess at this point we have to decide what is more important to be reflected in the Icon? That's it's a Motorway Mayham or that it's a Multi Cache, Mystery or indeed a Letterbox? Is this a can of worms that has been opened?

 

Jon

Link to comment

Got an odd one again with this using the files above. Export using the MMap option OK into MMap - all icons show up fine for all caches. But when I export the data to my pda (Mio P550) some caches only show as blue dots. It's all caches that have a travel bug in them (icon with the small black dot). So why does it display fine on the PC but not the pda? I've tried the MMap option to 'export data to pda' as well as to save the overlay in Mmap on the pc, copy it to the pda and run it from there.

 

Chris

Edited by The Blorenges
Link to comment

Got an odd one again with this using the files above. Export using the MMap option OK into MMap - all icons show up fine for all caches. But when I export the data to my pda (Mio P550) some caches only show as blue dots. It's all caches that have a travel bug in them (icon with the small black dot). So why does it display fine on the PC but not the pda? I've tried the MMap option to 'export data to pda' as well as to save the overlay in Mmap on the pc, copy it to the pda and run it from there.

 

Chris

I think there's a limit on the number of icons in the PDA version? I'm not too familiar with it...

Link to comment

Got an odd one again with this using the files above. Export using the MMap option OK into MMap - all icons show up fine for all caches. But when I export the data to my pda (Mio P550) some caches only show as blue dots. It's all caches that have a travel bug in them (icon with the small black dot). So why does it display fine on the PC but not the pda? I've tried the MMap option to 'export data to pda' as well as to save the overlay in Mmap on the pc, copy it to the pda and run it from there.

 

Chris

I think there's a limit on the number of icons in the PDA version? I'm not too familiar with it...

 

delete the overlay file on memory map on the pda the retry it

Link to comment

Got an odd one again with this using the files above. Export using the MMap option OK into MMap - all icons show up fine for all caches. But when I export the data to my pda (Mio P550) some caches only show as blue dots. It's all caches that have a travel bug in them (icon with the small black dot). So why does it display fine on the PC but not the pda? I've tried the MMap option to 'export data to pda' as well as to save the overlay in Mmap on the pc, copy it to the pda and run it from there.

 

Chris

I think there's a limit on the number of icons in the PDA version? I'm not too familiar with it...

 

delete the overlay file on memory map on the pda the retry it

 

I tried just exporting a few caches that had bugs in them - they still show up on the pda as blue dots. So not a numbers issue. Have tried deleting overlay as well. Always get the same thing. Any other caches are fine. Has to be something with how the pda is getting the info about the images. Don't know enough about it! Not a problem, I just have to remember that blue dots are any cache type with a bug in it!!

Chris

Link to comment

Got an odd one again with this using the files above. Export using the MMap option OK into MMap - all icons show up fine for all caches. But when I export the data to my pda (Mio P550) some caches only show as blue dots. It's all caches that have a travel bug in them (icon with the small black dot). So why does it display fine on the PC but not the pda? I've tried the MMap option to 'export data to pda' as well as to save the overlay in Mmap on the pc, copy it to the pda and run it from there.

 

Chris

I think there's a limit on the number of icons in the PDA version? I'm not too familiar with it...

 

delete the overlay file on memory map on the pda the retry it

 

I tried just exporting a few caches that had bugs in them - they still show up on the pda as blue dots. So not a numbers issue. Have tried deleting overlay as well. Always get the same thing. Any other caches are fine. Has to be something with how the pda is getting the info about the images. Don't know enough about it! Not a problem, I just have to remember that blue dots are any cache type with a bug in it!!

Chris

 

I'm not a PPC man myself, but I think Edgy meant numbers of icons rather than number of caches. The PPC only holds a certain number of icons and the MM export runs out of icons, so not all of them are exported. I presume the 'with bug' icon is at the bottom of the list!

 

I'm guessing by deleting the overlay, this should free up some icon space, but I don't know! Another possible option is deleting unused icons from the PDA - if this is possible? MM has a large collection of inbuilt icons I believe, and I'm sure you don't use all of them! Thats one for a PPC expert though!

 

Dave

Link to comment

But when I export the data to my pda (Mio P550) some caches only show as blue dots. It's all caches that have a travel bug in them (icon with the small black dot).

 

Chris

 

Check that you have the latest patch for MM for your version from the memory-map web site (and make sure it is installed on your PDA). There was a Version 4 patch that increased the number of icons available on MMPocketNav, but I can't recall the exact numbers.

Link to comment

Check that you have the latest patch for MM for your version from the memory-map web site (and make sure it is installed on your PDA). There was a Version 4 patch that increased the number of icons available on MMPocketNav, but I can't recall the exact numbers.

 

I've not got the icon problem you describe, I have the patched version 4 of Memory Map on the PC from which PocketNav was installed to my IPAQ PDA with. Help/About on both Memory-Map & Pocketnav shows version 4.4.3 Build 565. The patches for version 4 are available here

 

Cheers

 

Jon

 

Edited for version 4 patches, not 5

Edited by dakar4x4
Link to comment

I see what you mean about the number of icons..rather than caches. The blue dots do seem to be when Mem Map can't display an icon. Will check that. I'm actually using V5 of memory map but might try V4 to see if that is different. Unfortunately work keeps catching up with me and I have to stop playing with the PDA!!

Thanks for the tips

Chris

Link to comment

I see what you mean about the number of icons..rather than caches. The blue dots do seem to be when Mem Map can't display an icon. Will check that. I'm actually using V5 of memory map but might try V4 to see if that is different. Unfortunately work keeps catching up with me and I have to stop playing with the PDA!!

Thanks for the tips

Chris

You should beware when trying to migrate between v4 and v5, the maps are incompatible. Although they can be made compatible if you hexedit the map or the program.

 

Although, v5 seems to be a continuation of v4. http://www.memory-map.co.uk/mm_navigator_version_changes.htm

Edited by Edgemaster
Link to comment

OK - still struggling with this.. any help much appreciated!

 

Using GSAK 7/Mmap 4 and 5 (tried both) and the 'Lordelph' icon set.

 

Using the csv.xsl script file and GSAK 'custom export' I get all the lovely icons displaying fine in MMap on the PC and my PDA (Mio P550). But when I click on an icon on the PDA it links me to the web page for the cache. I want to link to the local HTML files I've created in GSAK and got on the PDA storage card.

 

Using the icon.txt file that Edge created and using the GSAK export to 'Memory Map' everything works fine in MMap and I get the HTML link from the icons on the PDA but (big but) I don't get the icons displaying properly on the PDA. They all display fine on the PC but any icon that has a black dot - siginifying a travel bug - shows as a single blue dot on the PDA. No idea why. Must be something to do with the transfer from PC to PDA. I have tried reducing the number/type of caches exported to the PDA but any 'bug' icons still show as blue dots.

 

So if anyone out there has any idea I'd appreciate knowing 1) how to link to local HTML files using the GSAK 'custom export' or 2) using the 'Memory Map' GSAK export how to get my missing icons to display!

 

Cheers

 

Chris

Link to comment

Regarding the MM icons, have you tried logging a call with MM support? Once the icons reach MM on the PC, if they work fine but then fail to get to the PDA then it's almost definately a problem/limitation/feature* within the MM system.

 

ADDITIONAL - just checked the MM forums and from a previous question raised by McKryten in January they are saying custom icon downloads from the MM PC to Pocket Navigator do NOT WORK! Strange then how it works for me on verison 4.4.3 then....

 

Cheers

 

Jon

 

* Delete as appropiate

Edited by dakar4x4
Link to comment

I've had a lot of trouble with this, I can only get 14 different icons to display on my PDA with any icon above that number displaying as the default blue dot. According to Jason at MM, pocket navigator isn't designed to be able to display user defined icons at all but it's too complicated a feature to be working by accident.

Link to comment

I've had a lot of trouble with this, I can only get 14 different icons to display on my PDA with any icon above that number displaying as the default blue dot. According to Jason at MM, pocket navigator isn't designed to be able to display user defined icons at all but it's too complicated a feature to be working by accident.

 

Hi McKryton,

 

Looks like we'll have to sort this one out ourselves.... So if you manually add a Mark in Pocket Navigator, how many icons are there on the list in the Mark properties (including the built it ones at the top of the list)? Also, when you do a MENU, HELP, ABOUT on the Pocket nav version, what version and build are you running.

 

I get 24 default icons (Dot to Geocache) and 76 Custom ones (_blank_N to MM_OBug) and am running version 4.4.3 buld 565

 

Jon

Link to comment

Hmm, I have a hunch that the two sets of icons may be duplicated. Delete all icons and then reimport a csv, see if it works.

I don't know, clutching at straws.

 

I think you are right Edgemaster. The numbers for the icons in the association file are different between the V6 and new V7 script. This will increase the number of icons overall and if there are too many the PPC version uses the default dot for some (it will work still display correctly on the PC though). To solve: delete all the icons in MM and then reload the csv file.

 

Let us know how you get on everyone,

 

Helen

Edited by T-girls
Link to comment
...

The numbers for the icons in the association file are different between the V6 and new V7 script.

...

 

I'll note that both scripts can be used in both versions (Memory Map feature was added sometime in V6).

 

Also, I am considering renumbering my script to match the xsl script's icon numbering scheme, hopefully this'll avoid future problems.

Link to comment

OK, yet another version of my script.

 

This one is a minor change to bring the icon IDs in line with the Roolku script.

 

This should help prevent collisions between the two 'sets' and stop them overflowing to blue dots in the Pocket PCs.

But, you will first need to delete all current custom icons that have been added by one of these scripts.

Remember to keep a copy of any changes you made to the files yourself, and to edit the provided memory.txt to point to your icons.

 

New version is at the same link as above, which is here.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...