I would guess that the average user wouldn't download and go through the trouble of learning how to install that mapset.
I asked OZ and he said go ahead and make state maps for the central and eastern states. A day or so after I uploaded the first one, he added did the PC installer and graphic, then added the Mac version. Then continued doing so as I uploaded the other states. I asked him about OR and CA - he did not say no, but did not say yes either. I then redid the AR topo as USGS replaced the NED data for the entire state, the WV overlay contour using the USGS 3m grid from LIDAR data, CO with contour interval matching the printed 7 1/2 quads, and a PA topo/plan - plan where an older NED production method was used and the resulting contours do not match those on the printed topos. He did not do anything with the WV overlay, CO toc, or PA t/p mapsets and I never asked him to as they were somewhat one of a kind 'test of concept' mapsets.
Just my opinion.
Greatly appreciated. Thanks.
Have you received any feedback on that mapset? I think if it were me, I'd make a PC installer, and convert a Mac version and actively seek feedback.
One comment within a few days on the CO mapset asking if more detailed boundaries for Forest Service lands could be used which would show the private inholdings. Nothing about the CI and nothing on the WV nor PA mapsets. Specifically asked for comments in the CO & PA mapsets. I expect the users do not read much of the info provided - with that in mind, I never uploaded the AK mapset because of issues with ocean/island polygons (no comments on that issue when asked on the forums). I have asked for feedback on the forums on some issues, usually do not get any - but at times my level of concern is fairly deep for even mapauthors.
I have some mapsets that have meter next to feet and it isn't a problem.
I would not expect it to be for you, but for others, me included, it might be a minor issue.
you can easily change the units in the GPS to match the printed quad to match up the number format.
I have never tired that. In a current project, the land elevations are in feet and the ocean in meters in the name field. When GlobalMapper makes the .mp files it converts the meter values to their value in feet. - would be nice if there was a way to make GM leave ones data alone.
There isn't a beet all, end all map that can be produced, and fit everyone's use.
I agree. Where in the spectrum of use/needs is the best balance point? I and some posters find it hard to see hydro and contours when a land ownership/use polygon is used; for others it is critical; in my CO toc mapset I tried a compromise.
... 24k/25K sets ... they don't work well with limited memory, such as with a Venture HC or older 8MB units. That's the battle between coverage and detail.
I was refering more to the overcontouring (20 versus 40 or 80) than 24k itself. I used a variable quad size in my state mapsetes to keep the average file/tile size to around 1.1Mb. Also no special typ file. Capabilities of older versus newest units, what to design for? With software for many units now supporting 4Gb, but still a 2025 file limit, 2+-Mb might be a better choice for an average file size. Oz once mentioned he prefers 8-10Mb files for his own use to somewhat balance all those 100+k files he also uses. I am considering a type file with a dashed contour line to be used in areas where the NED data does match the printed contours.
Also a blue dashed line for intermittent streams. I do not know what effect this will have on older units which do not support custom feature types, but how long should these enhancements be kept from newer units that do?
On some 'presentation methods', one person comments that s/he would like to see it a little different, but there have been thousands of downloads. Did the others like it and not comment, did not like it and did not comment, or not even use it? Should it be changed and risk x number of people then not liking it? I am open to suggestions as GPSr mapauthoring has it own unique set of limitations and parameters compared to the standards used on printed topo maps.