Messages

1

TopoFusion Pro / Re: Merge Tracks assistance

« on: January 21, 2010, 09:22:51 PM »

It was not my intent to seem critical above; I hope you're not taking it that way.

I was confused because I expected a certain behavior, and didn't understand what I was seeing.  I understand the way that part of the program works now. 

I know I pop up out of the blue for a few months, bug the tar out of you with questions and suggestions, then disappear again.  Pretty much follows my life and when I have time enough to do outdoors things and experiment with your program.

My personal experience is that it's not the most intuitive program, but it is a very powerful one for the parts I figured out.  TopoFusion is a regular part of my mapping arsenal and I keep plucking away at the different things it can do.  You ever hold a class or Q&A session in Tucson (when I'm in town) and I'll be there.

Thanks again for the help and the patience.

2

TopoFusion Pro / Re: Merge Tracks assistance

« on: January 21, 2010, 12:46:04 PM »

I had been operating under the assumption that any time I worked on a set of tracks, they were shown by a file in the bottom pane.

For example, when I create a trail network, an automatic new file is created with tracks and waypoints.  I was assuming that joined tracks, but joined.  Instead, the new "file" is invisible, until right-click>>save.

Another suggestion to make the program more consistent would be when you join tracks, automatically create a "joined tracks layer."

Sorry, I'm looking at this with outside eyes and putting suggestions in the help forum to try to make it easier, rather than in the suggestion forum.

3

TopoFusion Pro / Re: Merge Tracks assistance

« on: January 21, 2010, 09:44:05 AM »

BTW, the tool does not remove the original tracks.  The "merged track" is only temporarily there, and you have to right click and do "save as..." to make it permanent.  (Saving it out also removes the highlight).

I saw that "save as" in the help and apparently didn't understand it.  You're saying if I merge two tracks in a file, then I save that file, it does not include the merged track?

The "clear all segments" was a great clarification, thanks.  I was thinking that "clear all segments" cleared them out (i.e. removed them).  Since they were on top of each other, I wasn't certain 'cause I couldn't see underneath.

Additional suggestions would be to:
- Rename "clear all tracks" to "remove highlighting" or something without the word "clear" which implies "remove" to me.

- Update the help page to include the information here ... although if I'm the first to ask this, most people seem to understand it.

4

TopoFusion Pro / Merge Tracks assistance

« on: January 20, 2010, 11:40:03 PM »

Just so I redeem myself slightly on what's probably an obvious solution:
- I did read the manual.  http://www.topofusion.com/manual.php#toolbar
- I did search the forum and was unable to find help.

When I merge two tracks (both blue), I wind up with a black track, yellow highlight.  If I understand correctly from the help, it merges the tracks thus the two original tracks are gone, and there is a new, single merged track.

My problem is....I can't get it back to the simple track line with the trackpoints.  I have to quit the program and restart.

How do you cancel the "merged tracks" view without killing the program?

5

Feature Requests / Re: Track Reduction - multiple suggestions

« on: January 20, 2010, 11:23:08 PM »

I just wanted to bump this one back into your memory.

6

Beta Testing / Re: Sneak Peak - shaded relief

« on: August 25, 2009, 03:15:59 PM »

That is awesome.  I was kidding.  I never met a program that let me adjust it before.

The North East thinks the sun rises on it.  And of course, California thinks the sun sets on it.

7

Beta Testing / Re: Sneak Peak - shaded relief

« on: August 25, 2009, 02:15:20 PM »

Can you move the sun?
Better yet, can users move the sun?

Looks very nice.

8

TopoFusion Pro / Re: Track tool: How do I draw tracks on current layer

« on: August 11, 2009, 01:10:33 PM »

I thought I might be missing something, or a step might be missing from the instructions.

Since TF can combine multiple tracks into a single file, I as assuming there was a way for a user to do that as well.  I was reading into a capability I saw the program doing.

You might want to include a comment in the help that each user-created track must be a unique file and maybe that only track averaging can create multiple tracks in a single file.  That would make it clear.

Congrats on the race, I was tracking you and your friends on the website.

9

TopoFusion Pro / Re: DeLORME Earthmate PN-30

« on: August 04, 2009, 12:04:11 PM »

Garmin and Magellen are the big dogs.  Garmin is the biggest; everyone does Garmin protocol.

I use ExpertGPS for the GPS waypoint management, TopoFusion for its networking and track reduction, as well as imagery, and Topo for historical trip management and trip planning.

If you use any GIS software (or AutoCad, or I guess photoshop), that's what DeLorme is like.  Multiple layers of data you can turn on and off.  Very useful once you get used to it.  There is a steeper learning curve, but that's because it does more; most programs just work with one layer of data at a time.  I sometimes have 10 or more I'm working with.  It does have it's weaknesses, like any of the earlier mentioned programs.  When I want trip planning, delorme is fine.  When I want to go on the road, I take a Garmin.  Much better road updates in city/surburban areas, and even their rural areas are getting pretty good.  DeLorme has made a lot of good efforts to drag stuff into alignment, but in some lower-use areas, roads can still be 300 feet off.  (It's based off the US TIGER maps, visible in TopoFusion)

DeLorme also has a layer for map markups.  Text, callouts, lines, geometric shapes, etc.  Convert tracks to a draw-markup line and cut the map, put it on your GPS, and you can always view it, without using up a track slot to store it.  It's always "on"  (Which I suppose could be a problem if you want a track turned off.)  The bonus there is an infinite number of tracks, with notes, all displayed on your GPS screen.

When I'm 4x4ing in the Grand Canyon, I always take a laptop and a bluetooth GPS to run Topo.  Much bigger screen than any GPSr I've used, all my added roads, all my added notes.

• Draw layers are here:  http://forum.delorme.com/viewtopic.php?t=6941
• Grand Canyon example is here:  http://forum.delorme.com/viewtopic.php?t=9278
• Tucson Mtn Park (a simpler example with waypoints, tracks, and draw layer) is here: http://forum.delorme.com/viewtopic.php?t=15943

Good luck.

10

TopoFusion Pro / Re: DeLORME Earthmate PN-30

« on: August 04, 2009, 09:27:57 AM »

This program, and EasyGPS/ExpertGPS, do not have direct-connect ability with the PN-xx devices.  Apparently there is an issue with the protocol not being easy to work with.

To quote Dan Foster, creator of the Easy/Expert GPS:

Dan Foster: If I had to pick one company which seems to go out of its way to make its products not work with others, I'd pick Delorme. That being said, if they give you the interface specs, or a description of the file format used by the waypoints/routes/tracks, please let me know. I'll purchase a PN-20 at that point and give it a go. It looks like a great GPS receiver.
http://forums.topografix.com/index.php?showtopic=147&hl=DeLorme]

Dan bought the GPS, DeLorme published the specs, yet he still didn't implement the conversion.  The question then becomes why?  From a little farther down that page:

Dan Foster: After extensive testing with a Delorme PN-20, we've decided not to implement support for this GPS at this time. It uses a real-time USB interface that would require significant changes to our software. If they release further products based on this interface, or if their market share increases significantly, we'll revisit this decision. The good news is that Delorme's software finally supports GPX, so you can exchange GPX files between their software and any TopoGrafix product.

There is also more information here:
http://forums.topografix.com/index.php?showtopic=804

Another option is to put pressure from to other end. Go to DeLorme's forum and throw into their PN-xx suggestion page that DeLorme make their next generation of GPSr's easier for 3rd parties to work with.

This DeLorme thread is for the PN-20, but overall it's probably the best post to make the request in. The July 11, 2009 post asks now that the standard is out and that 3rd party programs (TopoGrafix Easy/ExpertGPS, TopoFusion) have had some problems with it, to make it easier to work with in the future.
http://forum.delorme.com/viewtopic.php?t=9361

11

TopoFusion Pro / Track tool: How do I draw tracks on current layer

« on: August 01, 2009, 07:58:25 PM »

Suggestion:
I know it pops up on the screen, but in the web based help file please include:
- To stop drawing tracks, right-click and select Save As.  It will save as a new track layer.

Question:
I created a combined track layer; the algorithm did a great job of reducing my sabino canyon tracks into a new layer with multiple tracks and waypoints.

Using the aerial maps, I wanted to draw in a few more trails to exchange with my GPSr so I could know where to go hiking later.

How do I draw a new track (or place a new waypoint) on the current layer?

12

Feature Requests / Re: Simplification for multiple tracks

« on: July 27, 2009, 01:38:15 PM »

Just to tie them together, that's effectively a seconding of a suggestion here
• Track Reduction - multiple suggestions

The above thread includes a short discussion on the issue, before I drag it off topic.

13

TopoFusion Pro / Re: Map Cache Percent is odd

« on: July 26, 2009, 06:08:43 PM »

All these years of tech support saying RTFM.....and here I went and did it   

You need to bike more, this stuff will wait until you get back.

I took 9 months off after graduation and before work; now my cubical gets smaller and smaller (literally) ever time my office is relocated, and I'm forced to live vicariously through your pictures.

14

TopoFusion Pro / Map Cache Percent is odd

« on: July 26, 2009, 03:52:38 PM »

I don't understand the map cache size.  The manual didn't help me understand, either.
http://www.topofusion.com/manual.php

It used to be called Tile Cache Size, now it's Map Cache Size
I am assuming the "Directory for Map Data" is where map tiles/map cache is stored.
If I understand the info right, the slider should adjust the size of the Map Data directory.
It appears to have a limit of 2 gig, but the slider bar only goes up to 50% (1 Gig)

Is there a goof somewhere, or am I not understanding?
Thanks, Wayne

15

Feature Requests / Re: Any progress on the load maps tool?

« on: July 26, 2009, 03:43:05 PM »

Larry -- load maps is next up on the list for sure.  I've been out riding and experimenting with sleep deprivation.

Sorry it took me a while to respond to that comment, but I was busy trying to stem the flow from my fleeding heart.  I had to do it one-handed, as the other was busy playing tiny violins!    ;-)

I've been following your fun on the diary; good stuff.   The pictures are great.  I took 9 months off after school / before starting a job to go backpacking.  I'm just jealous as my cubical gets smaller every year (literally).

16

User Projects / Re: Arizona Trails

« on: June 24, 2009, 02:43:07 PM »

Topofusion has actually changed the way I hike/bike. 

I now make an effort to wander to both sides of the tail now and then when I hike to ensure my recorded track logs cross each other to ensure good averaging. 

When I see a new road I want to explore later, I make certain I go at least 30 feet down the road so the setting I use in TopoFusion's stub reduction doesn't eliminate it.

17

User Projects / Arizona Trails

« on: June 22, 2009, 07:10:04 PM »

This isn't as exciting or useful as the other posts, but I do have some good examples of Topofusion use.

Here is the method I used, whether driving, riding, or hiking:

Started with GPS track logs (recording every 10 feet)
- Imported GPS tracks to DeLorme Topo
- Clipped off extra bits driving to trails,
- Made little "x" on the end of trails to make sure they averaged
- Exported tracks as GPX.

Opened the GPX in TopoFusion and used the Network function to automatically:
- Average tracks where I used the same road/trail more than once
- Remove stubs where I pulled down a road/trail for a second then got back on.

One example:  Doing this reduced a GPX file from 1.3 meg (11,000 points) to 1.1 meg (7,300 points) and made multiple-track roads more accurate due to averaging.  But I want to go smaller so I have room for more tracks on the GPS.

I then used the Simplify function where you can specify how many final points to have.

Offroad Hiking/Mountain Biking
- Divide by 2 (50% of original size) and it's near perfect to the original track, but 1/2 the size.  This gives one point about every 20 feet but intelligently reduced to give more points on curves, less on straights.
- Divide by 3 (33% of original size) and both the reduced track is nearly indistinguishable, even at very high zooms.

Offroad 4x4
- Divide by 5 (20% of original size) and it's virtually indistinguishable from original tracks except at high zoom. Even looks good on switchbacks.
- Divide by 7 good on curvy roads, overall pretty good representation for zoom 15.
- Divide by 9 decent for general use. Use when memory is at a premium or you don't need a perfect map.

I then saved the new GPX file, imported back to Topo, applied colors, thickness, and some notes.

• I rode (mountain bike) most of the Tucson Mountain park and used/combined those trails.  The files are in DeLorme Topo format here:
http://forum.delorme.com/viewtopic.php?t=15943

• I hiked/rode all around the Grand Canyon / Little Grand Canyon area.  Those files are in DeLorme Topo format here:
http://forum.delorme.com/viewtopic.php?t=9278

If someone really wants them in GPX format, let me know.  Mostly I wanted to put up another example of how I use Topofusion.  I'm not good with all the other features and am slowly learning more.  The track average and track reduction are really the sole reason I bought the program, and they work great.

18

Feature Requests / Upoad Network to track

« on: November 17, 2008, 07:22:15 AM »

In this suggestion post I mention that  TF lets you upload to your active log (at least on my Garmin 76CS).

As the active log is 10k points vs the 500 points in each saved track, you can use reduce networks to 7500 points and upload them to the active memory.  It will display, and you have 2500 points left over for new logging.

Assuming you loaded and run the trail start to finish, the points you least need will be erased and overwritten with your new track.

19

Feature Requests / Track Reduction - multiple suggestions

« on: November 17, 2008, 07:16:32 AM »

That two half example might not have been the beste.

You effectively have layers, but what if one of those layers has 100 closely grouped pieces?

Just a thought; I love it in autocad and GIS type programs, it's not as critical here.  Just a nice little plus.

Modifier keys could do the same;
- Click and drag = grab only what the select box completely surrounds
- Shift-Click and drag = grab everything in select box, as well as anything it touches a segment of.

20

Feature Requests / Track Reduction - multiple suggestions

« on: November 13, 2008, 05:34:18 AM »

If you make a trail network out of an east region and a west region that overlap each other slightly, and the east region has already been reduced.

Depending on the dirction TF had full inclusion set at (left or right)
- Dragging with "full inclusion" would make it so you could go just past the joined region, and you would only grab the new trails; maybe one or two of the old ones that could be de-selected from the group.
- Dragging with "touch only" would make it so that you could stop just shy of the overlap region, and you would still have the entire west side.

It's not critical, just something to rattle around as an idea.  I know you can get away with it now by just using one method.  It's hard to explain, but ask anyone that uses autocad if they would be happy if that feature went away.  It's one of those things (like a two-button mouse) that once you get used to it, you never want to go back and you wonder how everyone else does it.

That being said, you would be the only  mapping program I know that has it.  I often curse one other one that  has GIS-type features (layering and data types) but does not have a that select feature.

21

Feature Requests / Track Reduction - multiple suggestions

« on: November 12, 2008, 09:08:07 PM »

To go along with Suggestion 2(a)

This is a neat select trick seen in a few programs:

Click-drag to upper/lower right = select all objects that are entirely within the select-rectangle area

Click-drag to the upper/lower left = select all objects that are touched by the select-rectangle area.

[Suggestion 1:]

22

Feature Requests / Track Reduction - multiple suggestions

« on: November 11, 2008, 09:58:35 PM »

When you take multiple rides and make a trail network, it combines/averages out multiple tracks into a single track.  This is a great function, and I usually do it first.  The Trail Network function also takes long tracks and breaks them into pieces where two tracks cross.  Thus 8 rides (with overlap on several of the trails to be averaged together) can turn into 120 track pieces.

Topofusion also offers an intelligent trackpoint reduction tool that can take a detailed track (ex: points every 10 feet) and intelligently reduce it by selecting the final number of points desired.  Thus you can reduce a track to  20% of it's original size while maintaining a very high-quality representation of the trail.

I like to perform the Reduction function on the averaged track.  Unfortunately, those 8 original tracks were networked into 120 pieces, making a lot of work to right click on them, and to calculate what 20% of each track piece length is.

Suggestion 1:  Allow a percentage option instead of a final point number (or both).  Sliding either the percentage or changing the final number of points will update the other option.

This would let me set a percentage consistently based on my use.
Ex:  If I have track points every 10 feet, I would reduce to 33-25% of original for hiking, and reduce to 15-20% of the original size for vehicle off-roading, 15% for paved roads/highways.  Right-clicking on each track piece would default to the correct number of points based off the prior-set percentage.

Suggestion 2:  Another suggestion that piggy-backs the above suggestion:
(a) Allow me to select a series of tracks, or an area (that would select all tracks within it), or both options.
(b) Create a universal (all tracks) reduction option that would allow me to reduce all tracks by "xx percent" in one step.

That saves me about 120 right-clicks in my Tucson Mountain Park trail network.

23

Archived Support / Mis-aligned maps

« on: September 05, 2007, 06:22:19 AM »

I noticed an area like that in Tucson, AZ.
The President of TopoZone was nice enough to explain why this occurs.

The full discussion, with pictures of the alignment problem, is located here.
====================================
From Ed McNierney:
I'm not certain about this location, but this is likely a datum error. Many of the DRGs distributed by the USGS were labeled with the wrong datum; GeoTIFFs labeled as NAD27 were actually NAD83 and vice versa. For TopoZone we spent a huge amount of time finding and fixing these errors. If they're not corrected they produce a similar effect to what you show here.

A DRG is an image of the entire quad sheet, with the map collar (margin) included. You need to clip off that collar to mosaic the DRGs together. You know that a given quad covers a rectangular area from, say, 30.125 to 30.25 latitude, and -80.5 to -80.375 longitude. You clip that rectangle, containing only the map image, out from the entire DRG. By doing so you get exactly the map image, and only the map image. This process is considerably complicated by the fact that the DRG is in the UTM projection and those boundaries are not a rectangle!

But you need to know what datum you're talking about, and there are two datums involved. There's the datum used for the original printed map sheet, and the datum used for the digital DRG image file; they are not necessarily the same. If you have a DRG and you think it's a NAD83 image but it's really georeferenced to NAD27, your clipping rectangle will be off by a few hundred feet or so. When you clip out the map area you won't get exactly the map area inside the margins - you'll miss a bit and include a few hundred feet of white map margin where the map's supposed to be. That looks like what is happening here.

There's another possibility but I don't think it's pertinent here. If the USGS updates a quad/DRG the new quad will be produced in NAD83. If it is adjacent to an older quad (not updated) using NAD27, it is possible that there will be a gap in between the maps and that's NOT an error - there's no map there! If the boundary between two quads is 30 degrees North latitude, and one map ends at 30.0000 (NAD83) and the other starts at 30.0000 (NAD27), those two lines are not in the same place and there will be empty, unmapped space, in between.

24

Archived - Feedback and Comments / Feedback on GlobalSat BU 353 & TF

« on: September 05, 2007, 06:14:59 AM »

I use the US Globalsat Bluetooth 359.
It's just as good (SiRF III), and no wires (my laptop has built in bluetooth). The charge lasts over 10 hours, if you use a cig lighter to usb adapter you can charge it on the dash while running.  The nice thing about US GlobalSat--the batteries they use are from popular Nokia cell phones.  If your battery goes bad, it's easy to replace, unlike some other manufacturers who use custom batteries.

I place it in my sunroof and it works anywhere in the SUV.

Ignore the price here, you can find it half this price or less online.  US Globalsat BT359

Overall, just find what works best for you, and realize not everyone's "best answer" is the same.

[Offroad 4x4 driving. Take original track and….]

25

Archived Support / Track Point Reduction

« on: August 14, 2007, 04:34:27 PM »

As an FYI, this is reduction function.  This is what I do when logging is set to high resolution while gathering track points.  High resolution to me means:
- point every 10 feet
- point every 2 seconds
I run the reduction after I average the tracks.  (and usually after I re-join tracks that form a line end-to-end)

Offroad 4x4 driving.  Take original track and….  (% of original track points)
• Div by 9 (11%) decent for general use.  Use when memory is at a premium or you don't need a perfect map.
• Div by 7 (14%) good on curvy mountain roads, overall pretty good representation for high zoom (Zoom 15 in DeLorme Topo)
• Div by 5 (20%) virtually indistinguishable from original tracks at zoom 15, during 'regular' dirt roads.  Is great on switchbacks.  When going to zoom 16 and 17, it's still very good.

Mountain Biking / Hiking  (% of original track points)
If there aren't a lot of side trails (low trail density) you can obviously use the greater reductions above.  If there are a lot of trails, you probably want greater resolution so you can more quickly figure out if you took the correct fork in the trail.
• Div by 3 (33%) and it's nearly indistinguishable from the original even at the highest zooms.
• Divide by 2 (50%) and it's near perfect to the GPL.  This gives one point about every 20 feet but intelligently reduced to give more points on curves, less on straights.  I would question even using this resolution, however, although it does cut track sizes in half.  This is the "compulsive-attentive" level of logging (unless you count not reducing track sizes at all).

As a reference, I was in the Blue Spring/Cape Solitude area of the Grand Canyon.  I had the "in" track and the "out" track, along with some other tracks from exploring and turning the GPS on and off.

I started with DeLorme track logs  >> Saved to GPX.  (Saves point every 2 seconds, even when not moving)

Opened GPX in TopoFusion and used the Network function to automatically:
- Average tracks where I drove the same road twice.
- Remove stubs where I pulled down a road/trail for a second then got back on.
- Doing this reduced the GPX file from 1.3 meg to 1.1 meg and made multiple-track roads more accurate.

I then used the reduction function where you can specify how many final points to have.  Since it was for off-road driving use, but not in an area with much confusion over rods, I used "Divide By 7"

Final file size was 232k and was virtually identical to the 1.3 meg original.  Unfortunately, I didn't note the starting and ending number of track log points.

26

Archived Support / Combining multiple tracks into one?

« on: August 14, 2007, 04:23:30 PM »

This post might help.  It has my experiences with averaging.
Averaging Tracks

Sorry for the multiple posts in that other thread--I forgot about the wait!

27

Archived Support / Network:  Reduction strength

« on: August 14, 2007, 04:18:15 PM »

I've gotten more of the hang of it.  I do things like make certain I drag and "twist" ends together to make certain they merge/average.

Please forgive the mis-spellings; I didn't want to go through the work of re-grabbing and re-editing, then rehosting the picture.

What I'm trying to say on Picture 1 is that I drag the track points to make a triangle (which is why the red trails are so perfectly on top of each other), then I lower the track reduction strength until it doesn't eliminate triangles.  I don't mind small triangles getting flattened (this one isn't a large one; I don't mind if it goes away) but the larger ones I like to keep.

28

Feature Requests / Network Options

« on: May 13, 2007, 08:57:50 PM »

The current default Network Analysis function works great for me when I 4x4, and for Krein when he mountain bikes on long trails.

I like to map out every little trail, and sometimes get off my bike to hike.  The default settings (based off Krein's usage where I'm assuming you take long rides and few short paths) doesn't work for me in this situation.  It turns short hikes into stubs, and combines things that are parallel trails.

For example:
Me in Tucson Mtn Park on bike and foot:
- Reduction strength: 29
- Construction strength: 11

Me when I 4x4: (defaults--also works for long bike rides)
- Reduction strength: 76
- Construction strength: 45

Let us have a pulldown saving several sets of usage.  I sent you my Tucson Mtn Park GPX already; it's only getting more crowded as I explore the smaller trails.

Note:  I stay off any trails that are marked off, and if you see me wander onto one of the closed trails, please let me know as I'm going to put this GPX on the web later.

29

Feature Requests / APRS Functionality

« on: May 13, 2007, 11:32:52 AM »

DeLorme Street Atlas used to have this capability, and 3rd party programmers built up around it.

Then DeLorme removed it.  People still hold onto (or search for) the older, compatible hardware/software.

I know this is way out of what TopoFusion is aimed at, but I wouldn't mind seeing it added, either.

30

Archived Support / Screen contrast changes

« on: May 13, 2007, 10:15:08 AM »

This is going to be embarrassing, but in case anyone else has this issue, here's what I screwed up:

The keypad +/- will increase/decrease the zoom level.
I had been hitting the keyboard (over the enter key) +/-, which I didn't realize affected my contrast.  I didn't notice it until I came back and restarted later.

31

Archived Support / Multiple Monitors

« on: May 13, 2007, 10:11:50 AM »

Yes, latest drivers.
Monitor 1 (on right): 1680x1050 digital
Monitor 2 (on left): 1024x1280 analog, rotated to long edge is vertical (like a regular piece of paper).

32

Archived Support / Screen contrast changes

« on: May 13, 2007, 09:34:49 AM »

That's what I get for reading help.
Yes, it was incredibly obvious.
Window >> Image Processing >> Reset to default.

Brightness was all the way down.  I didn't find it last night.

No "dope slap" smiley?

33

Archived Support / Screen contrast changes

« on: May 12, 2007, 09:37:57 PM »

Here's a weird thing--I've got the preview on the left, flicker photo on the right (same monitor--it's an HP f2105 widescreen) and it's lighter looking in your forum than the original in Flickr.

See my other post (not approved yet--can't hot link to it.  What, do you sleep, too?  ) for the TopoFusion vs original on Flicker.

34

Archived Support / Multiple Monitors

« on: May 12, 2007, 09:35:48 PM »

TopoFusion version 3.07
I'm using a NVidia chipset, GeForce 6600.
This is how my tracks appear on my main monitor (digital)



This is what happens when I drag off to the left, on my Analog monitor (my card has 2 connections)



Any reason it doesn't work on a second monitor?

Here's a weird thing--I've got the preview on the left, flicker photo on the right (same monitor--it's an HP f2105 widescreen) and it's lighter looking in your forum than the original in Flickr.
Here's the original if you want to see how dark it is.
http://www.flickr.com/photos/sanaghan/495668990/

35

Archived Support / Screen contrast changes

« on: May 12, 2007, 09:09:49 PM »

Version 3.07 is much, much darker than 3.05.  I don't know the card, but I have the NVidia GeForce 6600 chipset.  I was unable to find an adjustment in Topofusion that let me adjust the contrast/brightness (except in Combo mode)

Let's see if Flikr will let me hot link.

The checkmark background used to be white...like the text box I put in there.



The Aerial map is very dark; felt like i was looking at it at night.

[Quote]

36

Archived Support / Network:  Reduction strength

« on: May 07, 2007, 06:02:26 PM »

Quote (Krein @ May 07 2007,6:50)

Yes, it really is 76 meters.  Note, however, that it is the maximum distance that the tracks can be apart -- meaning that at all times they must been within 76 meters or less.

As in "There is a tube around the tracks; at all points in that tube they must be 76 meters or closer.  The start and finish points can be farther than 76 meters."

Very good information to know.  I'm amazed more of my tracks didn't get pulled together.  I'm amazed how well it works.  I'm going to start breaking tracks up before I network them, and tighten that grouping way down to see if I can get rid of some goofieness; or maybe run it first then play with the tracks and run it again.

From the picture I sent you, two tracks have a long parallel stretch, but then diverge as I go down separate trails.  I have to make certain the two tracks are broken at the point where I separate for the network function to work correctly.

That also explains some of the goofy connections I get.

37

Archived Support / multiple track segment selection

« on: May 07, 2007, 03:16:57 PM »

>Wayne, can you describe what you mean by 'end to end'?

Pictures emailed.

For others, I tried doing it with text but the board reduces multiple ___ or --- even using the Code command.  Sorry, no way to do it with text.

38

Archived Support / Network:  Reduction strength

« on: May 07, 2007, 02:54:50 PM »

I fall too much; I'm very much a poor rider.  I curse the clips at times.

You nailed it on the road--I have two long stretches that run as parallel crescents, where I rode up the road on the right, and rode back down on the other right.  They cross once, up at the trail head.  I will drag two points and make them cross.  You can probably ignore the 2nd picture I just sent where my "ah-ha" moment now seem like a "wow, what a bad guess" moment.

I still don't get the reduction strength--is the default really 76 meters?  Or is that incorrect?

39

Archived Support / Track Point Reduction

« on: May 07, 2007, 02:49:28 PM »

Although it's probably clear from the above, my track lengths are wildly different in size, which is why I like the percentage.

Reducing a 10,000 point track to 500 points is not the same as reducing a 750 point file to 500 points.

Thanks for looking into it / adding in the future.

40

Archived Support / multiple track segment selection

« on: May 07, 2007, 07:46:38 AM »

Additional thought--in your on-line help document, if you search the page on the word "join" this option/ability does not come up.  In fact, the word "Join" is nowhere on the page.

It would be a good addition.

Click here to jump to manual web page

41

Archived Support / Track Point Reduction

« on: May 07, 2007, 07:44:57 AM »

Right now, you right click on a track and you can reduce it.  I love the function as it lets me take detailed measurements in the field (every 10 feet) then get a great representation after reduction, and it's much smaller when pushing back into a limited memory GPS.

In general, this is what I've found for 4x4 use:
Div by 9 (11.1% of original) decent for general use.  Use when memory is at a premium.      
Div by 7 (14.3% of original) good on curvy roads, overall pretty good representation for zoom 15.      
Div by 5 (20.0% of original) virtually indistinguishable from original tracks at zoom 15, great even on switchbacks.  Very good even at zoom 16 and 17.      

My suggestions are:
- Right now I use a spreadsheet for the math.  I have to right click the track, see how many points, do the division, and then type the answer in and have TF reduce the track.  Have a universal "divide by" operator so I don't have to do this.  I can default it to "5" or "9" (the program will remember this) and the track suggested size will be 1/5 of the original.

- Allow me to use an arrow to select a group of tracks (or if it's easier, just apply to all tracks) and let me reduce all selected tracks at once.

- Put it up on the Analysis toolbar and let me reduce all tracks in the open GPX document at once, without having to select a single or group of tracks.

42

Archived Support / Leave the "moderator approved" message up longer

« on: May 07, 2007, 07:36:48 AM »

Yeah, it looks like you're doing it now--that last message popped up for just 1 second or less!

43

Archived Support / Leave the "moderator approved" message up longer

« on: May 07, 2007, 07:36:10 AM »

Further analysis:  It's between 2-3 seconds now.  Even 5 would be better.

44

Archived Support / multiple track segment selection

« on: May 07, 2007, 07:35:09 AM »

I agree with the above--you have a "select point" tool, include a "select track" tool.  I don't need the analysis pop-up and the runner/animation every time.

I would also like the option to merge end-to-end. I keep getting a "double-back" due to time/date stamps, I'm assuming, after the network was created.

I would also like the track to be merged in situ, instead of having to export the track, then re-import.

Thanks.

45

Archived Support / Leave the "moderator approved" message up longer

« on: May 07, 2007, 07:04:32 AM »

Sorry about the double post, the "post is in, will be moderator approved" went by too quick.

When I didn't see it pop up in the forum list, a closer look let me see what the issue was.

Leave that message up about 10 seconds before it pops, or remove the auto-bounce back to the forum--give us a chance to read it, then make us click "return to forum"

[Quote]

46

Archived Support / Network:  Reduction strength

« on: May 07, 2007, 07:01:34 AM »

I searched on "reduction strength" first and came up with 0 hits. I know I can't be the first to ask about this feature.

I've been riding Tucson Mtn Park.  For the record, despite the picture at the top, I will not believe you actually rode up Krein trail to the peak.  That was steeper than anticipated.  I walked the bike up, and then walked it back down the other side.

I'm using a "Gen 2" gps; in simple terms it's a DeLorme PN-20 with an STMicro chipset that's more or less equivalent to SiRF III.  The satellites have general drift, and even with WAAS, I've noticed my tracks over time wind up a maximum of 30 feet (mostly 25 feet) apart on the wider trails.

I ran the Network Analysis on default to reduce my tracks, and it didn't work, in particular I noticed it on two parallel tracks that are 25 feet (9 meters) apart.

I looked at the docs and saw this:

Quote

Reduction strength is a measure (in meters) how how close parallel tracks must be to each other in order for them to be considered the same trail. They are then reduced to one track.

I looked at the default in TopoFusion and saw it was set at a whopping 76 meters.  That should have combined a lot more of my tracks.

Without experimentation, my guess is that may supposed to be 7.6 meters?

Can you please clarify this, or explain what I'm doing wrong?  Thanks, Wayne

47

Feature Requests / Trackpoint Reduction Tool

« on: February 27, 2007, 03:02:59 PM »

I wanted to report back that now that I've found and used the track reduction tool (where's the "I'm a dope" smilie?)

• It makes sense to right-click because you perform the operation to one track at a time.  However, you might make a tools menu and include just the tools (like track network), including a menu item for Reduction.  Reduction could have a pop-up box saying "select track (or right click on a track at any time)"  Not an elegant solution, but a little more obvious for new users and would point them to the easier selection.  I don't care so much now that I know where it is.

• The reduction worked great.  I experimented with dividing DeLorme GPL logs by 10 to 3.  I settled on divide by 5 for offroad 4x4 use.  This reduced tracks to 20% of their original size, while maintaining near perfect mapping data at high zoom.

Offroad 4x4
- Div by 9 decent for general use where memory is scarce.
- Div by 7 very good for curved roads, very good at zooms up to 15.   
- Div by 5 virtually indistinguishable at zoom 15, great even on switchbacks.  Very good even at zoom 16 and 17 (max).   

When combined with the Average/Network tool to average out where I went the same place twice, your outstanding tools reduced track sizes to about 10-15% of original size (depending on how many times I backtracked), with no loss in quality.

This lets me store more locations on my GPS, and speeds up 3D rendering on my computer.

Great job, and thanks for the help.

48

Archived - Feedback and Comments / National Geographic TOPO Conversion

« on: February 22, 2007, 12:34:13 PM »

I've got DeLorme Topo and it doesn't "save" to GPX, but it does Export to GPX.

See if you have an export option.  If you do, you will be able to find it by searching your help file.

TopoFusion opens GPX.

49

Archived Support / Networked tracks go fuzzy

« on: February 21, 2007, 10:30:25 PM »

Just to be clear:  The bug only occured in TF 3.00 Demo.

TF 3.00 Pro never made a fuzzy track even after several tries.

Thanks for the update.

50

Archived Support / Networked tracks go fuzzy

« on: February 21, 2007, 08:41:14 PM »

Glad you found it.
I quit the program and restart, the program fuzz is gone and it's the correct display.

I have not installed the regular (non-demo) Pro version at home yet; this is all with the demo-Pro version.

Here's a zoom on the blue line, since I already made it: