[OSGeo-Discuss] Mind Map - Open Source Spatial Projects

[Bruce Bannerman]

Hi Bob,

I don't think that it would be appropriate to allocate a mind map branch to
each OSGeo project, as:

- it would be better to keep the mind map as an independent high level
architectural assessment.

- not all projects listed are OSGeo Projects.



It is possible to link nodes on the mind map with lines (e.g. GeoMoose to
Openlayers), but this started to get messy, so I left it out.





That said, I see this mind map as just the beginning of the 'Current State
Architecture' of Open Source spatial.

I undertook the work, because I was trying to get the 'big picture' of what
was happening.


A potential future direction that we in OSGeo may (or may not) wish to take
is to get a more co-ordinated and well integrated suite of OSGeo
applications.


Borrowing from the Enterprise Architecture world, a potential way forward is
to get together a group of like minded people with the relevant experience
and:

- (with broad consultation) Work out a broad strategic direction for the
next five years, including:

  + what  are the key OSGeo projects to focus on.

  + what non-OSGeo projects should be encouraged into the fold.

  + what new projects are desirable.

  + define OSGeo policy requirements for applications, e.g.: OGC Services
support;
     a standard interface layout so that users can switch between
applications
     without undue re-learning; a standard configuration process; common
branding; etc.

  + define desirable OSGeo integration functionality for individual OSGeo
Project
     Contral Boards to target their development against.

  + define and continue development of core OSGeo supportive projects e.g.
     cartographic and GUI symbol libraries.

  + etc


- Defining a roadmap with indicative timelines to get from our 'current
state' to
  our 'future state' (i.e. a more co-ordinated and well integrated suite of
OSGeo applications).


Just a thought.


Bruce Bannerman





> > -----Original Message-----
> > From: discuss-bounces at lists.osgeo.org
> > [mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Bob Basques
> > Sent: Thursday, 15 October 2009 3:16 AM
> > To: discuss at lists.osgeo.org
> > Subject: Re: Fwd: [OSGeo-Discuss] Mind Map - Open Source
> > Spatial Projects
> >
> > A thought here . . . .
> >
> >
> > How would you see something like this working from a Project
> > meta-data perspective.  I'm wondering about the possibilty of
> > each OSGEO project handling their own branch of the MindMap
> > diagram.  Is there a way to link branches together?
> >
> >
> > Another piece that is nagging at me somewhat is how to handle
> > things that might need to be cross indexed (if possible),
> > GeoMoose might (will??) have items that related to more than
> > one other project, it's now utilizing the OpenLayers display
> > LIBs for example.  And I know of a couple of other projects
> > that may end up as connectors.
> >
> >
> > Just wondering (or muttereing) out loud. . . .
> >
> >
> > bobb
> >
> >
> >
> >
> > >>> Bruce Bannerman <bruce.bannerman.osgeo at gmail.com> wrote:
> >
> >
> >
> > >
> > > It would be great if you could add in the MapWindow project.
> > > MapWindow GIS Desktop Application is a C#/.NET desktop GIS that is
> > > completely open source and has about 6000 downloads per month from
> > > www.MapWindow.org.
> > >
> > > Also, under your library/developer tools, we the project
> > also includes
> > > a set of .NET libraries and a COM C++ ActiveX component
> > based on both
> > > NTS and GDAL.
> > >
> > > - Dan
> >
> >
> > done
> >
> >
> >
> >
> >
> > >
> > > OpenScales is a user-friendly and fast interface written in
> > > ActionScript3/Flex/AIR designed to visualize and manipulate spatial
> > > data.
> > >
> > > OpenScales is open source with an LGPL license.
> > >
> > >
> > >
> > > Aurélien Barbier-Accary
> >
> >
> > done
> >
> >
> >
> > Bruce
> >
> >
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/discuss/attachments/20091015/8c1bdd40/attachment-0002.html>