Talk:OSGeo Cartographic Engine - Revision history

Wiki-HamishBowman: svg

2010-03-08T07:52:55Z

svg

Tmitchell: Talk:OSGeo Cartographic Library moved to Talk:OSGeo Cartographic Engine: clarifying project by changing name :)

2010-03-07T23:11:30Z

Talk:OSGeo Cartographic Library moved to Talk:OSGeo Cartographic Engine: clarifying project by changing name :)

Wiki-Nick Lawrence at 23:08, 8 April 2008

2008-04-08T23:08:20Z

Tmitchell: New section: Configuration Files

2008-04-07T18:56:10Z

New section: Configuration Files

Wiki-Dsampson: removed my discussion post. All content hacked into wiki

2008-04-07T15:27:49Z

removed my discussion post. All content hacked into wiki

Wiki-Dsampson: New page: ~~~~ Currently I am working to get a Search and Rescue (SAR) volunteer group into some OS geo for their field operations. One of their biggest needs is the ability to print maps off in t...

2008-04-07T13:49:54Z

New page: ~~~~ Currently I am working to get a Search and Rescue (SAR) volunteer group into some OS geo for their field operations. One of their biggest needs is the ability to print maps off in t...

New page

[[User:Dsampson|Dsampson]] 09:49, 7 April 2008 (EDT)

Currently I am working to get a Search and Rescue (SAR) volunteer group into some OS geo for their field operations.

One of their biggest needs is the ability to print maps off in the field from a regular printer (8.5x11in or 11x14in) sheets.

I am of course using GRASS and QGIS and some basic carto features we would be able to use are

1. Printing from a georefed PDF or GeoTiff 
2. Miniature maps with borders, scale, UTM Grid 
3. Printing from vector and raster combined data 
4. Simple color schemes 
5. Printing to "recreation paper" (eg Tyvek) 

[[User:Dsampson|Dsampson]] 09:49, 7 April 2008 (EDT)

Two things to consider include how the data is represented and how the style rules are stored.

These questions might influence the model for designing the cartographic library. For instance should we consider separating the geographic representation from the cartographic representation. This may be similar as to ESRI's cartographic layer. A great concept. This way multiple clients or uses can be achieved from the same growing and changing data sources.

Furthermore, for the representations there is also the layout (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13). Perhaps we can learn lots from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus vcould allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

Second, is the rule based approach. Natural Resource Canada (NRCAN)publishes their Cartographic Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf). Could these be stored in a database or XML format that can be applied to multiple maps?

← Older revision		Revision as of 07:52, 8 March 2010
Line 10:		Line 10:
	It is written in Delphi, but is fairly stable.		It is written in Delphi, but is fairly stable.
	--nick		--nick
		+
		+	== Preliminary steps ==
		+
		+	Projects can start now by moving towards SVG symbols internally.
		+	-- Hamish

← Older revision		Revision as of 23:08, 8 April 2008
Line 3:		Line 3:
	I picture a configuration file to be very similar to the MapServer map file - with pointers to the input layers but to also have layout and more complex styling. How much of this can be done using existing standards like Web Map Context, SLD and GML. I assume this does not address layout needs?		I picture a configuration file to be very similar to the MapServer map file - with pointers to the input layers but to also have layout and more complex styling. How much of this can be done using existing standards like Web Map Context, SLD and GML. I assume this does not address layout needs?
	-- Tyler		-- Tyler
		+
		+	== AutoREALM ==
		+
		+	There is a open-source application called [http://autorealm.sourceforge.net AutoREALM] that is for making maps & cartographic output.
		+
		+	It is written in Delphi, but is fairly stable.
		+	--nick

← Older revision	Revision as of 18:56, 7 April 2008
Line 1:	Line 1:
	+	== Configuration Files ==

	+	I picture a configuration file to be very similar to the MapServer map file - with pointers to the input layers but to also have layout and more complex styling. How much of this can be done using existing standards like Web Map Context, SLD and GML. I assume this does not address layout needs?
	+	-- Tyler

← Older revision		Revision as of 15:27, 7 April 2008
Line 1:		Line 1:
−	~~[[User:Dsampson\|Dsampson]] 09:49, 7 April 2008 (EDT)~~

−	~~Currently I am working to get a Search and Rescue (SAR) volunteer group into some OS geo for their field operations.~~
−
−	~~One of their biggest needs is the ability to print maps off in the field from a regular printer (8.5x11in or 11x14in) sheets.~~
−
−	~~I am of course using GRASS and QGIS and some basic carto features we would be able to use are~~
−
−	~~1. Printing from a georefed PDF or GeoTiff <br>~~
−	~~2. Miniature maps with borders, scale, UTM Grid <br>~~
−	~~3. Printing from vector and raster combined data <br>~~
−	~~4. Simple color schemes <br>~~
−	~~5. Printing to "recreation paper" (eg Tyvek) <br>~~
−
−
−	~~[[User:Dsampson\|Dsampson]] 09:49, 7 April 2008 (EDT)~~
−
−	~~Two things to consider include how the data is represented and how the style rules are stored.~~
−
−	These questions might influence the model for designing the cartographic library. For instance should we consider separating the geographic representation from the cartographic representation. This may be similar as to ESRI's cartographic layer. A great concept. This way multiple clients or uses can be achieved from the same growing and changing data sources.
−
−	Furthermore, for the representations there is also the layout (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13). Perhaps we can learn lots from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus vcould allow for auto generation of some layout features and text such as changing declination, Projection info, and others.
−
−	Second, is the rule based approach. Natural Resource Canada (NRCAN)publishes their Cartographic Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf). Could these be stored in a database or XML format that can be applied to multiple maps?

← Older revision	Revision as of 23:11, 7 March 2010
(No difference)