GM contours

[rickvr]

Once GM completes contours how do I determine which are minor,intermediate or major? Or does it matter in the end product?

Also, how can I trim a map to get rid of overlapping data?

[-Oz-]

Continue following the tutorial; postgis will be used for major, minor, int.  Definitely matters in the end product for zoom levels.

And to trim a map is much more complicated.  First, get a state, convert to a polygon and load it into postgis.  Then, load you data into postgis. 

Use these queries to cut it out (i called my state "state"):

Code Select Expand

SELECT i.gid, i.name, i.layer, i.marine, i.levels, i.datalevel, i.mp_type, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO cut_federal_land
FROM state INNER JOIN federal_land i ON ST_Intersects(state.the_geom,
i.the_geom)

SELECT i.gid, i.aiannhce, i.aiannhns, i.aiannhid, i.layer, i.name, i.namelsad, i.lsad, i.mp_type, i.comptyp, i.classfp, i.aiannhr, i.mtfcc, i.funcstat, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO cut_reservations
FROM state INNER JOIN reservations i ON ST_Intersects(state.the_geom,
i.the_geom)

//NPS Boundary
SELECT i.gid, i.name, i.layer, i.gis_loc_id, i.unit_code, i.group_code, i.unit_name, iunit_type, i.meta_midf, i.lands_code, i.date_edit, i.gis_notes, i.mp_type, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO cut_nps
FROM state INNER JOIN nps i ON ST_Intersects(state.the_geom,
i.the_geom)

SELECT i.gid, i.comid, i.fdate, i.resolution, i.gnis_id, i.name, i.areasqkm, i.elevation, i.ftype, i.fcode, i.shape_leng, i.shape_area, i.mp_type, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO state_nhdarea
FROM state INNER JOIN nhd_area i ON ST_Intersects(state.the_geom,
i.the_geom)

SELECT i.gid, i.comid, i.fdate, i.resolution, i.gnis_id, i.name, i.lengthkm, i.reachcode, i.flowdir, i.wbareacomi, i.ftype, i.fcode, i.shape_leng, i.enabled, i.mp_type, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO state_nhdflowline
FROM state INNER JOIN nhd_flowline i ON ST_Intersects(state.the_geom,
i.the_geom)

SELECT i.gid, i.comid, i.fdate, i.resolution, i.gnis_id, i.name, i.areasqkm, i.elevation, i.reachcode, i.ftype, i.fcode, i.shape_leng, i.shape_area, i.mp_type, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO state_nhdwaterbody
FROM state INNER JOIN nhd_waterbody i ON ST_Intersects(state.the_geom,
i.the_geom)

//for global mapper contours
SELECT i.gid, i.name, i.layer, i.elevation, i.gm_layer, i.gm_type, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO state_contours
FROM state INNER JOIN contours i ON ST_Intersects(state.the_geom,
i.the_geom)

//for fwtools contours
SELECT i.gid, i.id, i.elev, i.mp_type, i.name, i.tmp, ST_Intersection(state.the_geom, i.the_geom)  As the_geom
INTO cut_contours
FROM state INNER JOIN contours i ON ST_Intersects(state.the_geom,i.the_geom);

[rickvr]

Looks like I've gone as far as I can with making maps. I still haven't been able to install postgresql and postgis on my computer (vista). Thanks for the help.

[-Oz-]

which error were you getting for postgresql

[Boyd]

Once GM completes contours how do I determine which are minor,intermediate or major? Or does it matter in the end product?

I honestly don't think it matters. When you export the contours as an .mp file they will be properly flagged by Global Mapper. Have you seen their tutorial here?

http://cgpsmapper.com/download/GM8DocV2.pdf

Note how the major and minor intervals appear in the screenshots from both Global Mapper and the GPS itself on pages 21 and 25. I would not get discouraged by the postgis issue. I'm making my own maps and have not needed it. The only thing which may be an issue is processing POI data from the census bureau.

But Global Mapper can do almost everything else for you using the powerful search function and the MP_TYPE field which gives you control over what kind of lines/points/polygons will be used on the GPS; this is also covered in the tutorial at the above link.

[rickvr]

-OZ- The error I got was with postgis. I don't remember exactly, something about writing to a .dll, I posted it earlier under "postgis subject".

boyd - Thanks for the info, GM has turned out to be more complex than I first though it's going to take some time to figure it all out.

one more question: in cgpsmapper, what does this mean. "warning w024:element should not be 0"