Topics

1

Feature Requests / Request to add National Geographic map tiles

« on: September 22, 2015, 08:23:58 AM »

I use a map app on my phone that allows me to view the very pretty National Geographic maps.   NatGeo does a great job of labeling features (mountain ranges, parks, basins, etc) at different zoom levels that other maps don't capture.

Can these map tiles be added to Topofusion?

http://mapmaker.education.nationalgeographic.com/

2

Feature Requests / Map list organizing

« on: September 12, 2015, 11:25:06 AM »

There are lots of maps, but its not the easiest to quickly identify what you want.
A little organization would make it a lot easier.  I made a horribly quick mock-up to demonstrate; just noticed I didn't get all the shortucts correct.

It might also be better if you put the shortcuts first before the name, so they were all in a vertical line together.

If you want to make it shorter, instead of "switch to xyz" you could make it:
Topo  Map -
Aerial Map -
Street Map -
Misc Map -

At the least, I suggest grouping maps by type.  Thank you.

[edit: spelling.  Logs of maps >> Lots]

3

TopoFusion Pro / Mapquest Maps: US vs England vs Other programs

« on: December 29, 2014, 01:37:44 PM »

I noticed a difference that's an odd one.
When I look at mapquest in the USA, the view is top down.
When I look at mapquest in the UK, the aerial view is always at an angle.

I use an android program from Codesector called Maverick that downloads Mapquest, I assume the same source.  In the UK, it displays the Mapquest from top down.  The program ExpertGPS also shows the same top-down view in the UK.

Is there a setting somewhere in Topofusion I'm missing, or is it a different map?

It might be a different map source despite both saying Mapquest.  The Mapquest version used in Maverick and ExpertGPS also lets me zoom out to a full world view, while the Mapquest in Topofusion cuts out and won't let me view a full state of Arizona.

Thank you.

4

TopoFusion Pro / Reading street names in OSM

« on: September 06, 2013, 01:01:09 PM »

I searched on "street names" and didn't see this brought up before.  The street names are much easier to read in the OSM web pages than they are in the TopoFusion program.

Is there a setting I can use to increase the text size of the street names?

5

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?

6

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?

7

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

8

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:

I start with GPS track logs (recording one point every 10 feet)
•  Sometimes use another program to make some manual cleaning--clip off unwanted trails recording before trails, etc.
• Made little "x" on the end of trails to ensure they average.
• Re-save 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:  A GPX file reduced 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 4x4 Take original track and (% of original track points)
• Div by 9 (11%) General track.  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).  You won't get lost.
• 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.

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

I then saved the new GPX file, imported back to Topo, applied colors, thickness, and 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

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.

[Suggestion 1:]

9

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.

10

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.

11

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/

12

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.

13

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]

14

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

15

Archived Support / Networked tracks go fuzzy

« on: February 21, 2007, 12:19:05 AM »

I went to build a network.  As I try to build the network (editing points inbetween attempts) about every 4th attempt, my network blows up.

I can use the 'select multiple track points' tool to select the underlying track, but I can't get rid of the color explosion.

Then I'll recalculate...and it comes out exploded somewhere else, or it's fine.

When I zoom in on the circle explosion, it turns looks like the longer, tubed shaped one.  I'd guess that the ends have fixed 'explosions' but the middle sections scale into them, turning a tube into a circle as you zoom out.

At high zoom, instead of a thin line for the track, it looks like a series of blue rectangles (with the lighter blue fuzzy coloring the screen around them)

What causes this, and how can I fix or prevent it?
Thanks.

16

Feature Requests / Trackpoint Reduction Tool

« on: February 20, 2007, 07:53:53 AM »

I made a post located here looking for definitions on the Network Dialog slider bars.  I have a suggestion for further expansion of the tool to include trackpoint reduction.

Many GPS's have a large track log, and smaller saved logs.  Ex: Garmin 76CS has a 10,000 point active log, but a 500 point saved log.  The GPS reduces the track size (with no user control) on save.  DeLorme's PN-20 lets you save full 10k unreduced track logs, but they take up a lot of memory with too much data.  (Yes, I can expand from a 2G to 4G card, but that's not my point, or the solution to every problem).

You seem to have some sort of a "reduce" function with the networks, but I'm suspecting (after playing with it) that it just reduces points based on overlapped routes, not a true "reduction" forumla.  I would like the ability of the tool expanded.  I'd like a way to better manage / average tracks. Examples:

• Track Reduction.  Active track logs can be reduced by using the reduction tool, little by little.  But the Garmin GPS (and others) have a saved-log limit of 500 points per saved log.  Allow me to say I want it reduced to "X" number of points, and TopoFusion will reduce the full tracklog from it's current size to 500 points via an intelligent mathematical function.  I know you have some of that already, but some suggestion are:
- When I travel in a straight line, you could eliminate most in-between points until there's movement in the perpendicular direction.
- When I stop and sit for a few minutes, I wind up with dozens of points that describe the same location. These could be reduced/eliminated.
- No two points withing "x" distance" of each other, even on turns. (When I import my 10k Garmin track log, it seems to make extremely descriptive low-speed turns, even while making less accurate descriptions on higher speed tighter turns).

• Allow me to remove "x" number of points. While the Garmin default method set on "Very High" logging produces many points, the DeLorme track logs (Street Atlas/Topo/PN-20 GPS) have many, many times more detail (and often too much detail, but I don't want to keep stoping and changing the logging method....and you can't change the logging method when you're 4x4ing with the laptop software version of the program).  This grows very large files. As a starter, I might remove every 1 of 2 points, or every 2 of 3 points, before I apply other advanced reduction methods.

[Quote]

17

Archived Support / Network Dialog question

« on: February 20, 2007, 07:45:40 AM »

I looked at the help for the Network Dialog box: TopoFusion Help.  I also searched this forum on "Network Dialog" and didn't find what I was looking for.

I know the method is proprietary, but can you explain what each individual sliders is?  You only have a joint explanation that makes sense when you know the answer already, but doesn't

Quote

The slider bars for reduction and contraction strength control how close or similar sections of tracks must be in order for them to be considered duplicates. Larger values will result in tracks being considered the same (and subsequently averaged together) when they are further apart.

I'm guessing here:
• Reduction:  How close two tracks have to be to each other to reduce them into a single track?  (NOT the reduction of total number of points)

• Contraction: How close single points have to be (without a lot of X-Y change) to reduce them to less points.
Ex: -  -  -  - - - -
could be contracted to:  - ____ -
with no loss of information.  (underscore added to keep spacing)

• Or I might be wrong and the program doesn't reduce points (except overlaps) at all.

Either way, a more detailed explanation of what each bar's function is would be appreciated.  Thanks.