Messages

not really either will definitely work.  Originally the 4 smaller segments were a little faster to download with multiple computers than the one single.

I am looking into how to do it.

I don't currently have fast enough internet where I am based for the next couple weeks to download all the data.  If I can open all the source files of the above cali map I should be able to split them

The other guy, David (IndyJpr) was working on a new map but I'm not sure how far he got; he's been pretty busy lately.

I will be able to let you know how the splitting goes during the weekend.

Mississippi will be up by this weekend.  It'll compile each night this week and probably take 2-3 nights to compile.

It is sad that it takes Garmin so long but I still can't do routing.

I used this in my Mississippi map.

I wrote some queries for postgis that got rid of a lot of the points and kept ones I could find garmin types for:

Code Select Expand

ALTER TABLE fs_pts ADD COLUMN mp_type character varying(50);
ALTER TABLE fs_pts ALTER COLUMN mp_type SET STORAGE EXTENDED;
UPDATE fs_pts SET mp_type = '0x2B03' WHERE cff='36' or cff='37' or cff='38';
UPDATE fs_pts SET mp_type = '0x5200' WHERE cff='46' or cff='47';
UPDATE fs_pts SET mp_type = '0x5904' WHERE cff='61' or cff='62';
UPDATE fs_pts SET mp_type = '0x4800' WHERE cff='63' or cff='64'or cff='924' or cff='925';
UPDATE fs_pts SET mp_type = '0x6410' WHERE cff='166' or cff='167';
UPDATE fs_pts SET mp_type = '0x6404' WHERE cff='168' or cff='169';
UPDATE fs_pts SET mp_type = '0x640C' WHERE cff='183' or cff='184' or cff='185' or cff='186';
UPDATE fs_pts SET mp_type = '0x6414' WHERE cff='194' or cff='426';
UPDATE fs_pts SET mp_type = '0x6403' WHERE cff='213';
UPDATE fs_pts SET mp_type = '0x4A00' WHERE cff='256' or cff='530';
UPDATE fs_pts SET mp_type = '0x4900' WHERE cff='257';
UPDATE fs_pts SET mp_type = '0x6509' WHERE cff='461';
UPDATE fs_pts SET mp_type = '0x6412' WHERE cff='921';
UPDATE fs_pts SET mp_type = '0x2c06' WHERE cff='926';
DELETE FROM fs_pts WHERE mp_type IS NULL;

I have the major parts done.  I just need federal lands.  I'm actually working on it right now so I'll have a better ETA in a few hours.

Yea, the geotiff is 1 file that is over 200mb.

I'm glad you like it.  definitely keeps me motivated to keep working on it

Hopefully people learn from the hard lessons I've learned and thus that makes GPS's better for everyone.

Yea, sorry military took me away.  The next segments are coming.  I also created a program that will do the contours pretty quickly for those that don't have Global Mapper and its a little faster and works better with large areas than Dem2Topo.

Also, I learned its not necessarily the size of the map but the number of elements.  For example for my 0 level I have upwards of 200,000 lines and that takes a long time.  If I had that in the 1 level it would take a lot longer to process the map than if only 10k of the lines were in the 1 level.

Glad to know it works since I'm not in Arizona right now.

22 hours does seem a little bit long.  50% cpu is right though because cgpsmapper is not a dual-core friendly program.

The map has been updated.  Lots of pretty major updates.
Version 1.1 (16 Jun 08)

* Updated to 2007 National Tiger Road Data
* Updated to 2007 National Tiger Railroad Data
* Added major powerlines
* Included airport runways (2007 Tiger Data)
* Included Native American Reservations
* Updated Grand Canyon Trails (removed duplicates)
* Fixed trails marked as roads
* Fixed road locations in Pima County

http://www.gpsfiledepot.com/maps/view/1/

Well, it worked but it didn't appear to have any trails for the forest I tried (Tonto).

Well, you're right.  I have no idea how to convert the tif file into a vector file.  Global Mapper can't do it.

Steve,

Have you completed the contours.  I have written a program that creates contours from tif files.  Its not fully complete but its good enough that if you wanted to use it to not have this problem with the long problem lines it could help you with that.

Dan