Messages

savage, would you be interested in code to cut the shapefiles to the state border exactly?

I do not know. I was thinking merging several NE maps into a larger one instead?

Fantastic work, 3 down! Do you have plans to do other states in the NE?

I do not know which one I will do next. Maybe New York state but that is not NE

There is a new version of the Maine topo map available here: http://www.gameandfishnetwork.com/News/article/sid=14.html

And this one was not an easy one to do. Let me know if there are bugs.

True, but I am not going to pay for a software that is extremely slow to the point of being unusable.

My Maine map is still being compiled. I have been stuck in the cgpsmapper for more than 9 hours at the 1% mark. I went to 30% in less than 15 minutes!

Should we contact the developer of cgpsmapper? I will be happy to give them my MP file.

It finally got the quad done, it took 27 hours but it compressed that 300mb behemoth down to a 10.2 mb file. Now processing the next quad. One down 39 to go....

The map looks great!!!!
Thanks Oz and Savage for all the help Can't wait to finish the set so I can upload it all.

-Erik

Good job and I have Maine still running. Hopefully it should be ready this week-end unless something unexpected happens.

I have an idea (probably a bad one but we are amongst friends here) why cgpsmapper is so slow.
This morning I looked at my computer and cgpsmapper was running but not making any progress for more than 8 hours. I wanted to kill it. I went to the DOS CMD window to check it out and suddenly the % of completion that was stuck at 2 is now incrementing nicely, currently at 10%.

Is it possible something could be blocking the DOS output? Maybe when I checked it out last night before going to bed?

I think the problem is not the map not covering all the rectangles is that some of the rectangles are outside the US territory and have no or very little elevation data.

Here is the problem:

When I generate the .MP files the map is split into zones:

A1 A2 A3 A4 A5 A6
B1 B2 B3 B4 B5 B6
...
G1 G2 G3 G4 G5 G6

The problem is the state does not cover all the rectangles. For the northern rows we have:

xx xx A3 A4 A5 xx
xx B2 B3 B4 B5 xx

And in the case of ME, the xx falls outside the border of the US and very little elevation data is available. Therefore removing those rectangles is OK.

I think the bug could be traced to the topoprocess I used to create the elevation. In my previous map of ME I used GM to do the elevation.

Glad to know I am not the only one with elevation problems!

As predicted the cgpsmapper crashed on the MP files at the edge of the map.

OK, A3 completed and it is now doing A4. I think ignoring the error(s) (I think there will be more) is probably OK but it would be nice to go to the bottom of this thing.

I removed the layer I did not need, but I still get the same error on the A2 file. The new A2 file is about 1/2 the size of the previous file. The weird thing is that use to work but I regenerated the contour line using the topoprocess instead of GM and I also updated some data.

Here is the cgpsmapper doc:

E024 Top layer detail level too
high to cover entire map -
decrease detail level of the
less detail layer (use higher
Level#).
This error needs a little more explanation since it is
often a source of confusion.
The last layer (the empty one) must always have
one 'tre region'. The maximum size of this region is
65535/2 * resolution (grid). If the map covers a
large area, the selected grid may be too low to
allow the desired 'tre region' to be created.
The maximum size of any object strictly depends
on the bit resolution. For resolution 24, the
maximum size ≈ 1.5 metre * 65535. Similarly, for
resolution 23, the maximum size ≈ 3 meter *
65535. This means that if the object is too big to fit
into the given layer of the map, the bit resolution of
this layer needs to be decreased so the layer can
accept bigger objects.


This is really strange because there are no large objects in A2. There are just few single points.
Currently cgpsmapper is running on A3 but it looks like I have few MP files similar to A2 that are on the edges of the MAP. Maybe I can just ignore the error?

I included a layer that should not have been included. The new A2 file is now smaller but still has the same weird points (as opposed to lines)

I will let you know how it goes.

I saw that. I probably included something I did not want to include. I will investigate.
Thanks

On average cGPSMapper produces 1 .img per hour on my machine using the same parameters suggested in the tutorial. But I have also seen .img taking more than 5 hours!