Messages

Thanks, -Oz- and Indrid Gold!

One of the mapsets on my account, Priest Lake Topos, is no more since it has been absorbed into my larger project, Northwest Topos.  I'm having a hard time figuring out how to delete the mapset from here, though.  Can someone point me to the process?  I can't see a delete or archive option in the Map Management section.

Thanks!

What version of Northwest Trails are you running above?  Are you sure that you are not looking at some previously cached imagery? I absolutely could not get the trails to display on top of the background map until I removed the overlap in zoom levels!

The issue isn't with MapSource, but with the fact that it is now stricter with what you can do with preview maps.  You could downgrade if you absolutely need to see Northwest Trails on your computer right now, but otherwise I'd say stick with 6.16.1 until Northwest Trails is updated.

You should be fine if you go back to the previous release of MapSource.  However, since MapSource does some significant caching of map tiles for display on the computer, it's likely that you are simply not seeing the changes on the computer screen.  If you delete the MapSource cache, you can be sure that you are seeing the latest data.

Even if that doesn't work, the issue is only with display of the map in MapSource; if you select any portion of Washington and upload, you will get all of the Washington data on your GPS.

I appear to have tracked down what is causing the problem and will have a new release of Northwest Trails out next week (1.58) that will contain the necessary changes.

Map selection polygons should be 0x4a, I believe; I think 0x4b is for map coverage polygons (which seem to be created automatically by the compiler).

In any case, I discovered the issue!    It seems that BaseCamp and the new version of MapSource are not as forgiving of overlapping zoom levels between the detailed maps and the preview map.  CGPSMapper has always prevented you from defining a preview map with a zoom level more detailed than the lowest zoom level in the detailed maps, but in the past users have been able to manually create custom preview maps with any zoom levels they desired and use these in place of the one created by CGPSMapper during compilation.  That no longer is the case.  You can still create a custom preview map, but you now *must* keep the zoom levels lower than those in the transparent detailed maps.

The good news is that my maps are now visible in both BaseCamp and Mapsource, while the bad news is that the background map used for reference with my transparent maps is much less detailed.  It should be workable, though.

Northwest Trails is set to transparent (=Y), but I use a custom preview map that includes roads, lakes, etc. - things that don't upload to the GPS but help users locate where they are on the map when viewing the mapset in MapSource.  I can leave it out (i.e. just compile the default preview map using the .mp file generated by cgpsmapper) and the transparent map overlays display, but the helpful background image is of course gone.  It is this ability to use a custom preview map that has stopped working for me with the latest release of MapSource (and several iterations of BaseCamp).

You won't hit this problem unless your transparent mapset uses a custom preview map.  It looks like your transparent mapset does not.

The "S" option creates a layer between the map layer and the polygonal layer generated by cpreview.  Maps compiled with Transparent=Y show all the nasty background polygons. 

Sorry for being thick but I still don't follow.  What nasty background polygons are you referring to?  When I create my transparent mapsets, I get no default background at all - just the map selection polygons.  I *want* a background map to show through, but not prevent the display of the overlying detail map data (i.e. my transparent trail data).

This has been the case for a while with BaseCamp, but now with the upgrade to MS v6.16.1 I am seeing it in MapSource as well: the non-transparent preview map that I include with my transparent Northwest Trails mapset is all that displays in the application; the detail maps (featuring the trails themselves) do not.

I know that others are encountering this issue so I am not alone, but I have not been able to determine if anyone has found a workaround.  So far the only solution I have found is to not upgrade (something I can't expect users of the mapset to not do), or to remove the custom preview map I have created to go with the transparent detail maps.

Anyone have any other ideas or solutions?

I was able to solve the problem of Puget Sound not displaying by changing the ocean (type code 0x28) to lake (type code 0x3C).  It looks like cGPSmapper (I assume) might have trouble compiling ocean, at least when it is full of passages and bays like the Puget Sound.  I see that everyone has encountered this problem, as the lack of water in the Sound is seen in all of the mapsets on here, from Ibycus's street maps to the various topo maps.

I'm using ArcGIS for merging the separate pieces as well as splitting them out into smaller chunks; I use Global Mapper for the hand editing of borders.

Hi all,

I've been working on the production of a topographic mapset for Washington State and adjacent areas and have run into some issues that I can't seem to solve.  I'm hoping that others with more experience than I may know the solution or be able to pinpoint the cause of the problem from a look at the mapset.

I've posted a small chunk of the mapset at http://www.switchbacks.com/Maps/downloads/NW_Topos_v0.01.zip (I've also attached it to this message).  This is the tile that contains the Seattle area.  The biggest issue I'm encountering is a failure of Puget Sound to render.  They polygons comprising the Sound are attributed as ocean (type hex of 0x28), but the area is not rendering as ocean in Mapsource (I've haven't checked yet to see if the same issue is present when loaded to the GPS, but expect that it would be so).  I've looked at other mapsets for the area available here and they exhibit the same behavior - no Puget Sound.  I've tried merging the overlapping ocean polygons obtained from NHD hydro data, splitting them up into smaller chunks, hand-editing the border to remove potential conflicts, etc. but have had no success.  Any thoughts?

A second issue I'm having (possibly related to the above) is that I am seeing "unknown area" when hovering over areas of the map that do not contain an area polygon (i.e. undesignated land).  Other mapsets I have been examining do not read "unknown area" in these cases, but instead just show up blank (i.e. no label when the cursor hovers over them).  What setting is needed to achieve this latter behavior?

Lastly, no matter how careful I think I am at aligning the borders of my map tiles, my roads, contours, area borders, etc. all display a gap or break at the tile boundaries.  Is there a trick to overcoming this?

Thank you in advance for any help you can offer.

Jon