Difference between revisions of "GeoConnexion Column"

Revision as of 08:24, 31 August 2009

This is the home page for "Open Sources", the OSGeo column in GeoConnexion magazine. Contact mpg if you're interested in helping out.

(5) "The Gift Economy Ain't Free: Getting Help with Open Source Software" (Howard Butler and Chris Schmidt)
- published, October (or November?) 2007 PDF

(6) OpenLayers + TileCache (Schuyler Erle)
- published, December 2007/January 2008 PDF

(12) deegree and Spatial Data Infrastructues using FOSS (Markus Lupp and Jens Fitzke)
- published, July/August 2008 PDF

(13) "MapWindow GIS: Developer Tools for the .NET Platform" (Daniel P. Ames)
- published, September 2008 PDF

(14) "GeoDjango: A synergy of python, geospatial, and the web" (Dane Springmeyer)
- published, October 2008 PDF

(15) "OpenLayers: bringing maps to the web with JavaScript" (Chris Schmidt)
- published, November 2008 PDF

(18) "Obama Campaign Mapping Voters with MapServer, PostGIS, and OpenLayers" (Karsten Vennemann)
- published, Mar 2009 PDF

(22) "The Toronto Code Sprint" (Michael P. Gerlek)
- published, July/August 2009 PDF

(23) "OpenGeoBI: Spatially Enabling the Business Intelligence Suite" (Fabio D'Ovidio)
- to appear, October 2009

The following guidelines are from the GeoConnexions Editor (currently Roger Longhorn).

You'll need to include an headshot/passport-style picture of yourself and a short bio.

Images are good. We like images. But images are a big issue for hardcopy print, especially computer images because they are only 72 dpi usually. Print quality is 300 dpi. That means 300 pixels per square inch for the print process. Most screen captures are reduced to 1/5th their original size when printed - usually causing us to throw them out because they represent the content poorly. Stretching a 72 dpi image to resize it means one still ends up with a 72 dpi image, only bigger. Please aim for 300 dpi if submitting images.

Content - My policy is to support expression. Someone writes it, I'll support it. I only edit for spelling, grammar and what I consider to be outright libelous. The writer should stand behind their expression. As I mentioned earlier, I am not a programmer. I need your help to peer review programming content (which is why the 'contact point' ) will work well. Ultimately everything in the column will reflect on OSGeo. It's your column, you choose the content. Our Media Pack describes Themes for issues by edition throughout the year. I use these as a guideline.

Reprint - I am a supporter of the creator maintaining all rights. Whomever submits material owns it as far as I am concerned. All I ask is that we have first right to print (we compete on the basis originality). Once printed, you may do whatever you wish with the material, you own it. We usually archive it online and columns are available for distribution online. Since hardcopy prints are a fixed cost, they can be purchased if anyone wants a few hundred. I don't know the cost, a marketing person can help if needed. Our Media Pack is here.

Timeline - I am usually working 90-100 days ahead of time. Be aware that there is delay in hardcopy and get material in early. On the flip side, we publish our articles to online almost immediately after hardcopy production.

@@ Line 71: / Line 71: @@
 * (23) "OpenGeoBI: Spatially Enabling the Business Intelligence Suite" (Fabio D'Ovidio)
-** ''to appear, September 2009''
+** ''to appear, October 2009''
 == Future Columns ==
+* (24) "Marine Map" (Tim Welch)
+** ''to appear, November 2009''
+* (25) ?
+** ''copy due Oct 15th''