Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Mike Saunt
I think this is a good idea.   We're using basecamp for FOSS4G 2013 so lots
of details will be recorded there.  I would think conference post mortems
would work too...

sent from mobile which isn't an iPhone
On Sep 5, 2012 11:34 PM, Cameron Shorter cameron.shor...@gmail.com
wrote:

 In analysing the downfall of FOSS4G 2012 [1] one of the key lessons that
 became apparent to me is that we are not very efficient at passing on
 Lessons Learned from one conference to the next.

 Could we do a better job of knowledge transfer by building an OSGeo
 Conference Body of Knowledge? Something like a FOSS4G Cookbook [2]?

 If so, what should be the scope of the cookbook? Should it only be for the
 international FOSS4G event? Should it cover regional conferences too?
 Should it also cover FOSS4G steams in other conferences?

 Who thinks this idea is important enough that you would like to help write
 sections of the Cookbook, or help with editing?

 What format should we use to write the Cookbook? Maybe a wiki?

 I'm interested to help push this idea forward if we as a community think
 that there will be value in such a collaboratively edited document.

 If you have an interest, please respond on the OSGeo conference_dev email
 list (rather than OSGeo Discuss)

 [1] http://cameronshorter.**blogspot.com.au/2012/08/**
 analysing-downfall-of-foss4g-**2012.htmlhttp://cameronshorter.blogspot.com.au/2012/08/analysing-downfall-of-foss4g-2012.html
 [2] 
 http://wiki.osgeo.org/wiki/**FOSS4G_Cookbookhttp://wiki.osgeo.org/wiki/FOSS4G_Cookbook
 [3] 
 http://lists.osgeo.org/**mailman/listinfo/conference_**devhttp://lists.osgeo.org/mailman/listinfo/conference_dev

 --
 Cameron Shorter
 Geospatial Solutions Manager
 Tel: +61 (0)2 8570 5050
 Mob: +61 (0)419 142 254

 Think Globally, Fix Locally
 Geospatial Solutions enhanced with Open Standards and Open Source
 http://www.lisasoft.com

 __**_
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/**mailman/listinfo/discusshttp://lists.osgeo.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Research - Reg

2012-09-06 Thread shri vinoth
Thanks Markus,.
Can you please tell me what are the 'Datum' needed for locating new
prospective areas of groundwater wells using GRASS GIS..

Regards,
Shri.

On 9/4/12, Markus Neteler nete...@osgeo.org wrote:
 On Tue, Sep 4, 2012 at 7:59 AM, shri vinoth vinoths...@gmail.com wrote:
 Hi evryone,
This is Shri. I'm new to this field. I mean GIS. I've taken up
 a
 project on GIS in which my work is to delineate a watershed and locating
 new
 prospective areas of groundwater wells. I need help. So, please let me
 know
 which GIS software would be better for this project and what are all the
 datum needed. Thank you.

 Welcome here!

 Please take a look at GRASS GIS:
 http://grass.osgeo.org/wiki/Hydrological_Sciences

 It offers many sophisticated tools including groundwater flow.

 Best regards
 Markus



-- 
Er. Shrimani. C.
M.Tech. (SWCE)
TNAU
09952828347
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Seven (aka Arnulf)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
we discuss this every year but it never happens. So I picked it up at
yesterday's UK Local Chapter meeting to start an outline based on what
we did over the past years. Once we have a framework I'll ping this
list and then move the thread to OSGeo Conf list and keep FOSS4G 2013
in the loop. It will all happen in the OSGeo Wiki under it's own
namespace.

Cheers,
Arnulf

On 09/06/2012 10:55 AM, Mike Saunt wrote:
 I think this is a good idea.   We're using basecamp for FOSS4G 2013
 so lots of details will be recorded there.  I would think
 conference post mortems would work too...
 
 sent from mobile which isn't an iPhone
 
 On Sep 5, 2012 11:34 PM, Cameron Shorter
 cameron.shor...@gmail.com mailto:cameron.shor...@gmail.com
 wrote:
 
 In analysing the downfall of FOSS4G 2012 [1] one of the key
 lessons that became apparent to me is that we are not very
 efficient at passing on Lessons Learned from one conference to the
 next.
 
 Could we do a better job of knowledge transfer by building an
 OSGeo Conference Body of Knowledge? Something like a FOSS4G
 Cookbook [2]?
 
 If so, what should be the scope of the cookbook? Should it only be 
 for the international FOSS4G event? Should it cover regional 
 conferences too? Should it also cover FOSS4G steams in other 
 conferences?
 
 Who thinks this idea is important enough that you would like to
 help write sections of the Cookbook, or help with editing?
 
 What format should we use to write the Cookbook? Maybe a wiki?
 
 I'm interested to help push this idea forward if we as a community 
 think that there will be value in such a collaboratively edited 
 document.
 
 If you have an interest, please respond on the OSGeo
 conference_dev email list (rather than OSGeo Discuss)
 
 [1] 
 http://cameronshorter.__blogspot.com.au/2012/08/__analysing-downfall-of-foss4g-__2012.html

 
http://cameronshorter.blogspot.com.au/2012/08/analysing-downfall-of-foss4g-2012.html
 [2] http://wiki.osgeo.org/wiki/__FOSS4G_Cookbook 
 http://wiki.osgeo.org/wiki/FOSS4G_Cookbook [3]
 http://lists.osgeo.org/__mailman/listinfo/conference___dev 
 http://lists.osgeo.org/mailman/listinfo/conference_dev
 
 -- Cameron Shorter Geospatial Solutions Manager Tel: +61 (0)2 8570
 5050 tel:%2B61%20%280%292%208570%205050 Mob: +61 (0)419 142 254
 tel:%2B61%20%280%29419%20142%20254
 
 Think Globally, Fix Locally Geospatial Solutions enhanced with Open
 Standards and Open Source http://www.lisasoft.com
 
 _ Discuss mailing
 list Discuss@lists.osgeo.org mailto:Discuss@lists.osgeo.org 
 http://lists.osgeo.org/__mailman/listinfo/discuss 
 http://lists.osgeo.org/mailman/listinfo/discuss
 
 
 
 ___ Discuss mailing
 list Discuss@lists.osgeo.org 
 http://lists.osgeo.org/mailman/listinfo/discuss
 


- -- 
Seven of Nine
http://arnulf.us/Seven
Exploring Body, Space and Mind
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBIh0QACgkQXmFKW+BJ1b1bqgCfeiPA1EQ2xIu7yWm+OPQsv8ON
2+AAn0jeUvsr1RF4X4/MGd7b6sMx+2st
=vp69
-END PGP SIGNATURE-
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


[OSGeo-Discuss] uDig 1.3.2 Released

2012-09-06 Thread Jody Garnett
UDIG 1.3.2 RELEASED


The uDig Community is pleased to announce the release of the uDig 1.3.2.
This point release packs significant new functionality. Thanks to our Google 
Summer of Code students for taking part in this years program. Macro Foi 
completed his work porting the advanced edit tools into this release.
There are a large number of people to thank for the nuts and bolts of this 
release. Cliff Broadbent and Sam Guymer transitioning the project to the tycho 
build system. Andrea Antonello setup the dropins folder for easy plugin 
installation. Jody Garnett and Frank Gasdorf ported the documentation and 
walkthroughs into Restructured Text resulting in a nice clean look.
This release is made in conjunction with GeoTools 8.1.
RELEASE DETAILS
Download the package appropriate to your platform, install (or unzip) and run:
uDig Downloads (http://udig.refractions.net/download/) (with archives and 
installers for Mac, Linux and Windows)
Release Notes (http://udig.refractions.net/files/downloads/udig-1.3.2.html)
Issue Tracker Change Log 
(https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10600version=18235)

ABOUT UDIG 1.3.2
The 1.3.2 release showcases active assistance when writing CQL expressions and 
filters. This technology will be used to making editing styles a more rewarding 
and dynamic experience.
The 1.3 series features some great usability improvements with a new tool 
palette and easy to access tool options. For developers the uDig platform 
provides access to the latest open source libraries from an Eclipse RCP 
environment.
Here are some new features you can look forward to:
Import SLD 1.1 Styles
Edit Tools included - no longer require a separate download
Area - define your area of interest based on CRS, current screen or a bookmark. 
You can use the area of interest to filter a Map Layer or just the Table view. 
This is a great way to focus on just the content you are interested in.
Query Layers using a dynamic filter editor, there is also a checkbox to filter 
using the area of interest. Can be used to answer simple feature containment 
questions.
Powerful data processing with the Transform operation. Use a dynamic expression 
editor to generate new datasets.
Provide an expression to label features, allowing the Information view to list 
features by name.
Updated Info and Profile tools for raster data
Teradata support
Spatial Toolbox view allowing access to OMS3 processing; with tutorial!
New import and export formats: CSV and KML.
For details on these and other features check out the What is new 
(http://udig.github.com/docs/user/What%20is%20new.html)!

Usability
Active assistance when editing CQL Filters and Expressions
Tool Palette with easy to use Tool Options for quick access to preferences 
(blog (http://udig-news.blogspot.com/2011/10/tool-palette-and-options.html))
Cheatsheets offering guided assistance for new users (blog 
(http://udig-news.blogspot.com/2011/10/adding-cheatsheets-interactive-help-to.html))
Control Tool interaction with your layers with the ability to mark background 
layers

Documentation:
Includes a revitalised User Guide a new clean look (available online 
(http://udig.github.com/docs/user/index.html))
Extensive update to online help including Quickstart 
(http://udig.github.com/docs/user/Quickstart.html) and uDig Overview 
(http://udig.github.com/docs/user/uDig%20Overview.html)
Updated Walkthrough 1 (http://udig.github.com/docs/user/Walkthrough%201.html) 
and Walkthrough 2 (http://udig.github.com/docs/user/Walkthrough%202.html) 
covering the use of the tool palette.
Step by step Introduction to Spatial Toolbox 
(http://udig.github.com/docs/user/Introduction%20to%20the%20Spatial%20Toolbox.html)
Reorganised the Tasks (http://udig.github.com/docs/user/Tasks.html) section 
with step by step instructions for using new features

For developers:
Latest GeoTools 8.1 release
Latest JTS 1.12
Latest ImageIO-EXT 1.1.4


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Jeff McKenna
Hello Cameron,

Making sure that a transfer of knowledge happens from one FOSS4G local
committee to the next is something that I've championed for a very long
time now - it is a thankless invisible task that not many are aware is
happening (archiving documents, pinging committee members over and over
to openly archive documents and logos and files, making sure such
critical parts of FOSS4G are kept - ribbon in logo, t-shirts for
attendees, hands-on workshops - to the point that local committees kind
of become annoyed with me).

My vision of FOSS4G (credit here to original FOSS4G Heroes such as
Venka and Markus of course) has always been very simple: to spread the
Open Source Geospatial passion all around the world.  It has not been
about money or politics.  The result has been FOSS4G local committees
are free to take this passion and mold it into their own vision.  Events
such as FOSS4G Cape Town in 2008 are proof of this.

I worry that such a 'cookbook' will hinder this open passion and vision
for a local committee.

The first drafts of such a cookbook came many years ago from Paul
Ramsey, from his 2007 experiences.  Since then I've heard rumblings from
Arnulf, Cameron and others.

I guess it is time for such guidelines.  For sure we need a conference
Content Management System internal to OSGeo that is required for all
FOSS4G local committees to use (not external systems such as Basecamp);
this is critical.


-jeff





On 12-09-05 7:34 PM, Cameron Shorter wrote:
 In analysing the downfall of FOSS4G 2012 [1] one of the key lessons that
 became apparent to me is that we are not very efficient at passing on
 Lessons Learned from one conference to the next.
 
 Could we do a better job of knowledge transfer by building an OSGeo
 Conference Body of Knowledge? Something like a FOSS4G Cookbook [2]?
 
 If so, what should be the scope of the cookbook? Should it only be for
 the international FOSS4G event? Should it cover regional conferences
 too? Should it also cover FOSS4G steams in other conferences?
 
 Who thinks this idea is important enough that you would like to help
 write sections of the Cookbook, or help with editing?
 
 What format should we use to write the Cookbook? Maybe a wiki?
 
 I'm interested to help push this idea forward if we as a community think
 that there will be value in such a collaboratively edited document.
 
 If you have an interest, please respond on the OSGeo conference_dev
 email list (rather than OSGeo Discuss)
 
 [1]
 http://cameronshorter.blogspot.com.au/2012/08/analysing-downfall-of-foss4g-2012.html
 
 [2] http://wiki.osgeo.org/wiki/FOSS4G_Cookbook
 [3] http://lists.osgeo.org/mailman/listinfo/conference_dev
 

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Stephen Woodbridge

Hello,

I think the 'cookbook' is a great idea! It is about capturing our 
collective knowledge and experience, it not about limiting creativity or 
change. Just like in software when you have an individual contributor 
that has passion, vision and drive can create wonderful things, you also 
have to help the other contributors that are not so visionary to do a 
good job. The 'cookbook' gives us a recipe for success, it is the basic 
stuff that you need to know to get the job done successfully. To 
continue with the analogy a visionary chef looks at the recipe and 
changes it to suit his creative talents.


So it all depends on whether we require people to only follow the 
recipe or we use it as a guideline for people that are volunteering to 
help but may not have had past experience to get things done correctly.


The cookbook is a great idea in my opinion.

-Steve W

On 9/6/2012 10:14 AM, Jeff McKenna wrote:

Hello Cameron,

Making sure that a transfer of knowledge happens from one FOSS4G local
committee to the next is something that I've championed for a very long
time now - it is a thankless invisible task that not many are aware is
happening (archiving documents, pinging committee members over and over
to openly archive documents and logos and files, making sure such
critical parts of FOSS4G are kept - ribbon in logo, t-shirts for
attendees, hands-on workshops - to the point that local committees kind
of become annoyed with me).

My vision of FOSS4G (credit here to original FOSS4G Heroes such as
Venka and Markus of course) has always been very simple: to spread the
Open Source Geospatial passion all around the world.  It has not been
about money or politics.  The result has been FOSS4G local committees
are free to take this passion and mold it into their own vision.  Events
such as FOSS4G Cape Town in 2008 are proof of this.

I worry that such a 'cookbook' will hinder this open passion and vision
for a local committee.

The first drafts of such a cookbook came many years ago from Paul
Ramsey, from his 2007 experiences.  Since then I've heard rumblings from
Arnulf, Cameron and others.

I guess it is time for such guidelines.  For sure we need a conference
Content Management System internal to OSGeo that is required for all
FOSS4G local committees to use (not external systems such as Basecamp);
this is critical.


-jeff





On 12-09-05 7:34 PM, Cameron Shorter wrote:

In analysing the downfall of FOSS4G 2012 [1] one of the key lessons that
became apparent to me is that we are not very efficient at passing on
Lessons Learned from one conference to the next.

Could we do a better job of knowledge transfer by building an OSGeo
Conference Body of Knowledge? Something like a FOSS4G Cookbook [2]?

If so, what should be the scope of the cookbook? Should it only be for
the international FOSS4G event? Should it cover regional conferences
too? Should it also cover FOSS4G steams in other conferences?

Who thinks this idea is important enough that you would like to help
write sections of the Cookbook, or help with editing?

What format should we use to write the Cookbook? Maybe a wiki?

I'm interested to help push this idea forward if we as a community think
that there will be value in such a collaboratively edited document.

If you have an interest, please respond on the OSGeo conference_dev
email list (rather than OSGeo Discuss)

[1]
http://cameronshorter.blogspot.com.au/2012/08/analysing-downfall-of-foss4g-2012.html

[2] http://wiki.osgeo.org/wiki/FOSS4G_Cookbook
[3] http://lists.osgeo.org/mailman/listinfo/conference_dev



___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss



___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Basques, Bob (CI-StPaul)
All,

Related to this, I've been wondering about how to go about setting up a 
business specific LiveDVD.  Is there a possible synergy to be had with a recipe 
derived DVD (collection?) ??.

Bobb



  -Original Message-
  From: discuss-boun...@lists.osgeo.org [mailto:discuss-
  boun...@lists.osgeo.org] On Behalf Of Stephen Woodbridge
  Sent: Thursday, September 06, 2012 9:43 AM
  To: discuss@lists.osgeo.org
  Subject: Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?
  
  Hello,
  
  I think the 'cookbook' is a great idea! It is about capturing our
  collective knowledge and experience, it not about limiting
  creativity or change. Just like in software when you have an
  individual contributor that has passion, vision and drive can
  create wonderful things, you also have to help the other
  contributors that are not so visionary to do a good job. The
  'cookbook' gives us a recipe for success, it is the basic stuff
  that you need to know to get the job done successfully. To
  continue with the analogy a visionary chef looks at the recipe
  and changes it to suit his creative talents.
  
  So it all depends on whether we require people to only follow
  the recipe or we use it as a guideline for people that are
  volunteering to help but may not have had past experience to get
  things done correctly.
  
  The cookbook is a great idea in my opinion.
  
  -Steve W
  
  On 9/6/2012 10:14 AM, Jeff McKenna wrote:
   Hello Cameron,
  
   Making sure that a transfer of knowledge happens from one
  FOSS4G local
   committee to the next is something that I've championed for a
  very
   long time now - it is a thankless invisible task that not many
  are
   aware is happening (archiving documents, pinging committee
  members
   over and over to openly archive documents and logos and files,
  making
   sure such critical parts of FOSS4G are kept - ribbon in logo,
  t-shirts
   for attendees, hands-on workshops - to the point that local
  committees
   kind of become annoyed with me).
  
   My vision of FOSS4G (credit here to original FOSS4G Heroes
  such as
   Venka and Markus of course) has always been very simple: to
  spread the
   Open Source Geospatial passion all around the world.  It has
  not been
   about money or politics.  The result has been FOSS4G local
  committees
   are free to take this passion and mold it into their own
  vision.
   Events such as FOSS4G Cape Town in 2008 are proof of this.
  
   I worry that such a 'cookbook' will hinder this open passion
  and
   vision for a local committee.
  
   The first drafts of such a cookbook came many years ago from
  Paul
   Ramsey, from his 2007 experiences.  Since then I've heard
  rumblings
   from Arnulf, Cameron and others.
  
   I guess it is time for such guidelines.  For sure we need a
  conference
   Content Management System internal to OSGeo that is required
  for all
   FOSS4G local committees to use (not external systems such as
   Basecamp); this is critical.
  
  
   -jeff
  
  
  
  
  
   On 12-09-05 7:34 PM, Cameron Shorter wrote:
   In analysing the downfall of FOSS4G 2012 [1] one of the key
  lessons
   that became apparent to me is that we are not very efficient
  at
   passing on Lessons Learned from one conference to the next.
  
   Could we do a better job of knowledge transfer by building an
  OSGeo
   Conference Body of Knowledge? Something like a FOSS4G Cookbook
  [2]?
  
   If so, what should be the scope of the cookbook? Should it
  only be
   for the international FOSS4G event? Should it cover regional
   conferences too? Should it also cover FOSS4G steams in other
  conferences?
  
   Who thinks this idea is important enough that you would like
  to help
   write sections of the Cookbook, or help with editing?
  
   What format should we use to write the Cookbook? Maybe a wiki?
  
   I'm interested to help push this idea forward if we as a
  community
   think that there will be value in such a collaboratively
  edited document.
  
   If you have an interest, please respond on the OSGeo
  conference_dev
   email list (rather than OSGeo Discuss)
  
   [1]
   http://cameronshorter.blogspot.com.au/2012/08/analysing-
  downfall-of-f
   oss4g-2012.html
  
   [2] http://wiki.osgeo.org/wiki/FOSS4G_Cookbook
   [3] http://lists.osgeo.org/mailman/listinfo/conference_dev
  
  
   ___
   Discuss mailing list
   Discuss@lists.osgeo.org
   http://lists.osgeo.org/mailman/listinfo/discuss
  
  
  ___
  Discuss mailing list
  Discuss@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/discuss


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


[OSGeo-Discuss] Supporting Standards

2012-09-06 Thread Seven (aka Arnulf)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Folks,
one item on the OGC Architecture Board meeting agenda today was to
look at this web site:
http://open-stand.org/principles/

- From my perspective the principles listed here are very much aligned
with our goals and nicely worded. So my suggestion is to support this
initiative as an organization [1]. Let's have a dialog here and if we
come to the conclusion that we want to officially endorse this submit
a motion to the board for their next meeting.

Cheers,
Arnulf

[1] http://open-stand.org/stand-with-us/

- -- 
Seven of Nine
http://arnulf.us/Seven
Exploring Body, Space and Mind
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBIwMAACgkQXmFKW+BJ1b3aBwCfbLsyPwZ1r7f3CzcPsRbumh2v
MlAAn0ajzfp0nB/oxjbxi5WwyNXME9Cv
=zr31
-END PGP SIGNATURE-
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Supporting Standards

2012-09-06 Thread Stefano Costa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Il 06/09/2012 17:26, Seven (aka Arnulf) ha scritto:
 Folks, one item on the OGC Architecture Board meeting agenda today
 was to look at this web site: http://open-stand.org/principles/
 
 - From my perspective the principles listed here are very much
 aligned with our goals and nicely worded. So my suggestion is to
 support this initiative as an organization [1]. Let's have a dialog
 here and if we come to the conclusion that we want to officially
 endorse this submit a motion to the board for their next meeting.

I'm a bit worried by the vague wording of those principles.

More in detail, point 4 is crucial, stating that:

fair terms may vary from royalty-free to fair, reasonable, and
non-discriminatory terms (FRAND).

See http://www.gnu.org/philosophy/words-to-avoid.html#RAND for some
background of why this is problematic for free and open source
software (our mission, I believe).

Ciao
steko
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJQSMbAAAoJEDBz7sDeHMxYmdMP/RKaJVCdeYp9JV87uG7B7cev
iOxF2nNt8G3Jhc+Yd4G3riiMxs+RTKiA1aDAjKnpuo3udBTTcVuuwB02b9oVKikX
hb178cFC3vI0AAKAmMeOZEXpMF74L8H6IOwrz4XxaOesYxjL/Cxx59GeNO//pSIb
zC0PvYI1lharjaLNKFLG1/dkobFEq6/6Qj6iTRPpOCryGcXwg95H4sWdP2mK+Cyr
MD43/ycHag2GpWoYrov4OxjX6MSQnFYSs9H6pkibEQAMYz3PxSiCpdxNSjrp+uk5
6L9wbOeWLW2tJJcFZSkzxa7GZrwrKsyzSS8+TAsPHs556HCkqQNHIzwDlKLVzZa2
Y32CaLVqrhSoP4k6xvw+B3ZbcvQ+nz5yaxt7Q/Kue0+rEepmcdduoIultv48Y9dI
+8mgHGl5TFpeB2Y6JeiqlokcJw7uflZxUFYflgylkwn34C1x3qSvk9VdFfdL8pII
3ErbAWLOmKAcT44+7Q4O6ubacrLLJhLzhkbuvOWscBDGMTr5SsGHjPYmwOHhW707
kUQ6rKZfVWcmCYX6ip7RhM52HMKxpVcFwucCNzsn+f+cIEzsIgplO+ymgjOcparF
vPMmZy4SauRZBtpZkiOEAxy5y2/jd2xQyWbAZQrarqJ6gwULdb/hyO5jmomVmBnh
zBkMdeA3tLCyxI52CQjO
=vBan
-END PGP SIGNATURE-
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Research - Reg

2012-09-06 Thread Mohammed Rashad
depends on your data. there is no datum for ground water Different data
have a different datum

some of them are WGS84[1] NAD83

for theory part you can scan on [2] and [3]

[1]http://wiki.gis.com/wiki/index.php/WGS84
[2]http://en.wikipedia.org/wiki/Datum_(geodesy)
[3]http://www.colorado.edu/geography/gcraft/notes/datum/datum_f.html



On Thu, Sep 6, 2012 at 3:36 PM, shri vinoth vinoths...@gmail.com wrote:

 Thanks Markus,.
 Can you please tell me what are the 'Datum' needed for locating new
 prospective areas of groundwater wells using GRASS GIS..

 Regards,
 Shri.

 On 9/4/12, Markus Neteler nete...@osgeo.org wrote:
  On Tue, Sep 4, 2012 at 7:59 AM, shri vinoth vinoths...@gmail.com
 wrote:
  Hi evryone,
 This is Shri. I'm new to this field. I mean GIS. I've taken
 up
  a
  project on GIS in which my work is to delineate a watershed and locating
  new
  prospective areas of groundwater wells. I need help. So, please let me
  know
  which GIS software would be better for this project and what are all the
  datum needed. Thank you.
 
  Welcome here!
 
  Please take a look at GRASS GIS:
  http://grass.osgeo.org/wiki/Hydrological_Sciences
 
  It offers many sophisticated tools including groundwater flow.
 
  Best regards
  Markus
 


 --
 Er. Shrimani. C.
 M.Tech. (SWCE)
 TNAU
 09952828347
 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss




-- 
Regards,
   Rashad
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Cameron Shorter

Jeff,
I think Stephen summarises the intent of the cookbook well as a guide 
rather than a mandate.
I see it also as a way to expand what you have been doing individually 
(collecting collective knowledge) into a self help which is not limited 
by the time constraints of one person. Initially when there was only 1 
foss4g event per year it was possible for one person to be the core 
driver, but we now have scores of events per year.


Bob,
I'd anticipate there being subheading in the Cookbook for using the 
LiveDVD at FOSS4G events.


On 7/09/2012 1:00 AM, Basques, Bob (CI-StPaul) wrote:

All,

Related to this, I've been wondering about how to go about setting up a 
business specific LiveDVD.  Is there a possible synergy to be had with a recipe 
derived DVD (collection?) ??.

Bobb




  -Original Message-
  From: discuss-boun...@lists.osgeo.org [mailto:discuss-
  boun...@lists.osgeo.org] On Behalf Of Stephen Woodbridge
  Sent: Thursday, September 06, 2012 9:43 AM
  To: discuss@lists.osgeo.org
  Subject: Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?
  
  Hello,
  
  I think the 'cookbook' is a great idea! It is about capturing our

  collective knowledge and experience, it not about limiting
  creativity or change. Just like in software when you have an
  individual contributor that has passion, vision and drive can
  create wonderful things, you also have to help the other
  contributors that are not so visionary to do a good job. The
  'cookbook' gives us a recipe for success, it is the basic stuff
  that you need to know to get the job done successfully. To
  continue with the analogy a visionary chef looks at the recipe
  and changes it to suit his creative talents.
  
  So it all depends on whether we require people to only follow

  the recipe or we use it as a guideline for people that are
  volunteering to help but may not have had past experience to get
  things done correctly.
  
  The cookbook is a great idea in my opinion.
  
  -Steve W
  
  On 9/6/2012 10:14 AM, Jeff McKenna wrote:

   Hello Cameron,
  
   Making sure that a transfer of knowledge happens from one
  FOSS4G local
   committee to the next is something that I've championed for a
  very
   long time now - it is a thankless invisible task that not many
  are
   aware is happening (archiving documents, pinging committee
  members
   over and over to openly archive documents and logos and files,
  making
   sure such critical parts of FOSS4G are kept - ribbon in logo,
  t-shirts
   for attendees, hands-on workshops - to the point that local
  committees
   kind of become annoyed with me).
  
   My vision of FOSS4G (credit here to original FOSS4G Heroes
  such as
   Venka and Markus of course) has always been very simple: to
  spread the
   Open Source Geospatial passion all around the world.  It has
  not been
   about money or politics.  The result has been FOSS4G local
  committees
   are free to take this passion and mold it into their own
  vision.
   Events such as FOSS4G Cape Town in 2008 are proof of this.
  
   I worry that such a 'cookbook' will hinder this open passion
  and
   vision for a local committee.
  
   The first drafts of such a cookbook came many years ago from
  Paul
   Ramsey, from his 2007 experiences.  Since then I've heard
  rumblings
   from Arnulf, Cameron and others.
  
   I guess it is time for such guidelines.  For sure we need a
  conference
   Content Management System internal to OSGeo that is required
  for all
   FOSS4G local committees to use (not external systems such as
   Basecamp); this is critical.
  
  
   -jeff
  
  
  
  
  
   On 12-09-05 7:34 PM, Cameron Shorter wrote:
   In analysing the downfall of FOSS4G 2012 [1] one of the key
  lessons
   that became apparent to me is that we are not very efficient
  at
   passing on Lessons Learned from one conference to the next.
  
   Could we do a better job of knowledge transfer by building an
  OSGeo
   Conference Body of Knowledge? Something like a FOSS4G Cookbook
  [2]?
  
   If so, what should be the scope of the cookbook? Should it
  only be
   for the international FOSS4G event? Should it cover regional
   conferences too? Should it also cover FOSS4G steams in other
  conferences?
  
   Who thinks this idea is important enough that you would like
  to help
   write sections of the Cookbook, or help with editing?
  
   What format should we use to write the Cookbook? Maybe a wiki?
  
   I'm interested to help push this idea forward if we as a
  community
   think that there will be value in such a collaboratively
  edited document.
  
   If you have an interest, please respond on the OSGeo
  conference_dev
   email list (rather than OSGeo Discuss)
  
   [1]
   http://cameronshorter.blogspot.com.au/2012/08/analysing-
  downfall-of-f
   oss4g-2012.html
  
   [2] http://wiki.osgeo.org/wiki/FOSS4G_Cookbook
   [3] http://lists.osgeo.org/mailman/listinfo/conference_dev
  
  
   ___
   

Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Jeff McKenna
On 12-09-06 5:22 PM, Cameron Shorter wrote:
 Jeff,
 I think Stephen summarises the intent of the cookbook well as a guide
 rather than a mandate.
 I see it also as a way to expand what you have been doing individually
 (collecting collective knowledge) into a self help which is not limited
 by the time constraints of one person. Initially when there was only 1
 foss4g event per year it was possible for one person to be the core
 driver, but we now have scores of events per year.
 


Well said Cameron, this is a great problem to have.

In fact I've heard through Twitter that the first local committee
meeting for FOSS4G Buenos Aires 2013 is happening today.  It's spread
all over the world.

Have a good Friday all.

-jeff



___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Should we write a FOSS4G Cookbook?

2012-09-06 Thread Cameron Shorter
FYI, I'm switching the remainder of this discussion over to the OSGeo 
Conference email list.

Please subscribe if you wish to follow along.
http://lists.osgeo.org/mailman/listinfo/conference_dev


--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] Supporting Standards

2012-09-06 Thread Michael P. Gerlek
[added standards mailing list back to the distribution list]

Quoting all of item 4, to put Stefano's quote in context:

Standards specifications are made accessible to all for implementation
and deployment. Affirming standards organizations have defined
procedures to develop specifications that can be implemented under
fair terms. Given market diversity, fair terms may vary from 
royalty-free
to fair, reasonable, and non-discriminatory terms (FRAND).

I'm pretty pragmatic about this stuff, so I see this as a perfectly reasonable 
position for an organization to take.

-mpg



On Sep 6, 2012, at 8:52 AM, Stefano Costa st...@iosa.it wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 Il 06/09/2012 17:26, Seven (aka Arnulf) ha scritto:
 Folks, one item on the OGC Architecture Board meeting agenda today
 was to look at this web site: http://open-stand.org/principles/
 
 - From my perspective the principles listed here are very much
 aligned with our goals and nicely worded. So my suggestion is to
 support this initiative as an organization [1]. Let's have a dialog
 here and if we come to the conclusion that we want to officially
 endorse this submit a motion to the board for their next meeting.
 
 I'm a bit worried by the vague wording of those principles.
 
 More in detail, point 4 is crucial, stating that:
 
fair terms may vary from royalty-free to fair, reasonable, and
non-discriminatory terms (FRAND).
 
 See http://www.gnu.org/philosophy/words-to-avoid.html#RAND for some
 background of why this is problematic for free and open source
 software (our mission, I believe).
 
 Ciao
 steko

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss