Messages

>> I thought "StreetDesc=" was for street addresses.

Yes.  But the question in my mind was whether that info might show up on the GPS screen where a POI's lat/lon & elevation info is displayed.  For the Oregon, the screen I am talking about appears when one moves the pin to a POI such that the POI name is displayed in a box which appears at the top, and one then taps on that box (don't know if that box has an official name!).  It seemed the only way to answer the question definitively was by actually testing.  But no joy.

To me it would seem logical for POI's to have a "description" field associated with them, just as GPX waypoints have a "<desc>" field associated with them and KML placenames have a "<description>" field - but I've never heard such a field mentioned.

>> Is Apple Tree Camp really a levee?

No, that's I use an obscure type which is not used elsewhere in the map for my POIs,  using a TYP file to provide the desired icon.

FWIW, since I was currently in the process of creating maps so had everything already setup, I did a test where I set "StreetDesc=" in an .mp file to some text and compiled with cgpsmapper (a full-feature version, not the free version)  - but when I display the POI information in my Oregon that extra text does not appear. 

I am making the POI myself, using input to cgpsmapper ala
[POI]
Type=0x6409
Label=Apple Tree Camp
Endlevel=1
Data0=(36.37257,-121.79912)
[END]

Did a search on POI, looked at all 6 pages but nothing useful so am posting here.

I'm creating POIs in a Garmin .img file using cgpsmapper.  When I display a POI in an Oregon, the POI lat/lon and elevation are displayed, but there is also much blank space.  I was wondering whether it is possible to include "description" text, separate from the label, which might be displayed there.  For example, if I put some text into cgpsmapper's "StreetDesc=" field would that appear there?

Also, anyone know where the elevation came from?  I certainly did not include it in the input to cgpsmapper.

Followup: When starting to insert some text notes to myself at  the top of file map_install_x64-x86.nsi file,  I noticed that the _correct_ lines to modify are specified there.  That gave more confidence as to what was needed, so made appropriate changes (to include TYP and MDX  processing) and it did compile with NSIS.  Tested the resulting installation executable and it did work!  Hopefully the instruction page will get corrected some day.

Are people creating setup (installation) files using the instructions
"how-to-create-garmin-topo-maps---part-9---compiling-data" ?


The instruction line numbers do not match what the current "setup template file" map_install_x64-x86.nsi file ("Updated 4 Dec 11").  For example, the instructions refer to uncommenting line 130 which is a blank line and line 122 which is a actual comment line, not a commented-out instruction.