Hi Bob,<br><br>I don't think that it would be appropriate to allocate a mind map branch to each OSGeo project, as:<br><br>- it would be better to keep the mind map as an independent high level architectural assessment.<br>
<br>- not all projects listed are OSGeo Projects.<br><br><br><br>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.<br><br><br><br><br><br>
That said, I see this mind map as just the beginning of the 'Current State Architecture' of Open Source spatial. <br><br>I undertook the work, because I was trying to get the 'big picture' of what was happening.<br>
<br><br>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.<br><br><br>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:<br>
<br>- (with broad consultation) Work out a broad strategic direction for the next five years, including:<br><br> + what are the key OSGeo projects to focus on.<br><br> + what non-OSGeo projects should be encouraged into the fold.<br>
<br> + what new projects are desirable.<br><br> + define OSGeo policy requirements for applications, e.g.: OGC Services support;<br> a standard interface layout so that users can switch between applications<br> without undue re-learning; a standard configuration process; common branding; etc.<br>
<br> + define desirable OSGeo integration functionality for individual OSGeo Project<br> Contral Boards to target their development against.<br><br> + define and continue development of core OSGeo supportive projects e.g.<br>
cartographic and GUI symbol libraries.<br><br> + etc<br><br><br>- Defining a roadmap with indicative timelines to get from our 'current state' to<br> our 'future state' (i.e. a more co-ordinated and well integrated suite of OSGeo applications).<br>
<br><br>Just a thought.<br><br> <br>Bruce Bannerman<br><br><br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> -----Original Message-----<br>
> From: <a href="mailto:discuss-bounces@lists.osgeo.org">discuss-bounces@lists.osgeo.org</a><br>
</div><div class="im">> [mailto:<a href="mailto:discuss-bounces@lists.osgeo.org">discuss-bounces@lists.osgeo.org</a>] On Behalf Of Bob Basques<br>
> Sent: Thursday, 15 October 2009 3:16 AM<br>
> To: <a href="mailto:discuss@lists.osgeo.org">discuss@lists.osgeo.org</a><br>
> Subject: Re: Fwd: [OSGeo-Discuss] Mind Map - Open Source<br>
> Spatial Projects<br>
><br>
</div>> A thought here . . . .<br>
><br>
><br>
> How would you see something like this working from a Project<br>
> meta-data perspective. I'm wondering about the possibilty of<br>
> each OSGEO project handling their own branch of the MindMap<br>
> diagram. Is there a way to link branches together?<br>
><br>
><br>
> Another piece that is nagging at me somewhat is how to handle<br>
> things that might need to be cross indexed (if possible),<br>
> GeoMoose might (will??) have items that related to more than<br>
> one other project, it's now utilizing the OpenLayers display<br>
> LIBs for example. And I know of a couple of other projects<br>
> that may end up as connectors.<br>
><br>
><br>
> Just wondering (or muttereing) out loud. . . .<br>
<div class="im">><br>
><br>
> bobb<br>
><br>
><br>
><br>
><br>
> >>> Bruce Bannerman <<a href="mailto:bruce.bannerman.osgeo@gmail.com">bruce.bannerman.osgeo@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> ><br>
</div><div class="im">> > It would be great if you could add in the MapWindow project.<br>
> > MapWindow GIS Desktop Application is a C#/.NET desktop GIS that is<br>
> > completely open source and has about 6000 downloads per month from<br>
> > <a href="http://www.MapWindow.org" target="_blank">www.MapWindow.org</a>.<br>
> ><br>
> > Also, under your library/developer tools, we the project<br>
> also includes<br>
> > a set of .NET libraries and a COM C++ ActiveX component<br>
> based on both<br>
> > NTS and GDAL.<br>
> ><br>
> > - Dan<br>
><br>
><br>
</div>> done<br>
<div class="im">><br>
><br>
><br>
><br>
><br>
> ><br>
> > OpenScales is a user-friendly and fast interface written in<br>
> > ActionScript3/Flex/AIR designed to visualize and manipulate spatial<br>
> > data.<br>
> ><br>
> > OpenScales is open source with an LGPL license.<br>
> ><br>
> ><br>
> ><br>
</div>> > Aurélien Barbier-Accary<br>
><br>
><br>
> done<br>
><br>
><br>
><br>
> Bruce<br>
><br>
><br>
><br>
> </blockquote></div><br>