Rob Atkinson wrote: > There is an underlying thread here - Geoserver needs to leverage > deployed infrastructures to be most useful. > > 1.7 is (quite sensibly) about the most prevalent infrastructures - > Google (and other) environments that provide base maps, mash-ups with > existing data stores, and to a certain extent REST-based exploitation. > Lets call this SDI-for-viewing > > IMHO Version 2 should be aimed at what INSPIRE aims to achieve, which > is SDI-for-data (and brings us back full-circle to the original > geoserver vision). This should not preclude the viewing function, but > will require closer attention to metadata transparency, and in > particular the ability to synchronise remote data stroes from an > authoritative source without loss of information. > Yeah, this makes a lot of sense to me. I've always felt we should nail the compelling technologies so we can bring the great standards stuff in without people even noticing.
> emphasis on viewing = convienience and speed. Emphasis on data = > transmission reliability. > > As a basic structure, this might provide a coherent high level road > map that the end user community could understand? > OpenGeo's interest in 2.0 is primarily for the long needed UI upgrade, to bring GeoServer to be more of a platform for most anything spatial. We've got a nice module / extension structure, and this should extend to UI for plugins. And our longer term interest is workflows and editing, collaborative mapping stuff. But I'm really excited for the GeoServer vision to not be driven by OpenGeo, and I'd agree to the data / SDI story being the main one for 2.0, as long as the community comes up with the resources to execute, which looks to be happening, which is great to see. Chris > Rob A > > On Fri, Dec 12, 2008 at 4:07 AM, Chris Holmes <[email protected]> wrote: >> Hey all, sorry for sounding in late on this thread. >> >> GeoSearch as a core module is the top of my list. And after that getting >> RestConfig as a core module - we hit it pretty heavily recently, flushed out >> some bugs, so it should be pretty good. I'm super psyched on the Styler >> stuff, and a basic version should be easy from a GeoServer perspective (and >> depends on restconfig). We should think about how we want better >> integration. Directory datastore would also be really nice to have. And >> ogr output for wfs would be a nice win, especially since we already have the >> gdal stuff, so people will be more used to the platform specific stuff. >> >> I just yesterday got a chance to check out the 1.7.1 release. It feels >> really awesome, super tight in most every way. And the mac installer is >> great. There are a few things from a 'product' perspective that I think can >> make the next release even better. I'm happy to file the jira issues, but I >> think some may already exist in some form, so let me know if they do and I >> can just comment there (and I want to get this out sooner rather than >> later). >> >> * Better google earth templates for our demo layers. Great job on cleaning >> up the metadata for this release, it makes things feel a lot more tight. >> And the KML preview with super overlays is awesome. But when you click on >> most of the layers it doesn't show off the cool stuff we can do with >> templates. >> >> * When GeoSearch per layer about pages are in, we should be sure to link to >> them from the preview page. >> >> *GeoWebCache integration feedback* >> It's really great we have GWC as a part of things. I think we should work >> on both making it more obvious that users can use it, and to integrate it >> more directly >> >> * GWC options in openlayers preview. At the very least the drop down should >> be 'single tile, tiled, and cached'. Ideally we would also have buttons in >> there to 'truncate cache' (for when a user changes a style), and even 'seed >> the cache'. >> >> * More prominent links to GWC from admin console - perhaps on the front >> page, along with the capabilities links. And perhaps links from the demo >> page. >> >> * Real tiling integration - right now we make an in memory tile cache when >> tile requests come in. Better would be to check the GWC cache to see if a >> tile is already there. And to add it if it's not. Then GeoServer would >> have seamless caching whenever tiling clients are used. For this to work >> really well we'd need GWC listening to styling config changes and >> transactions (and anything else that may affect rendering), so that people >> don't change styles and continue to see the old. But we also could just >> have a useCache param or something in the wms request? >> >> * KML super overlays to use gwc. Right now it looks like the preview kml >> stuff doesn't use the caching? That's probably how people are going to be >> referencing their kml layers? We should make the docs encourage caching >> stuff. And eventually do the same as above - smart caching that updates on >> changes. >> >> *Installers* >> >> The mac installer is now way better than the others. We should step up on >> the others. >> >> * Linux installers - be able to do debian/ubuntu apt-get and redhat rpm >> >> * Better windows installer - run as a service. There should be lots of good >> examples that we can use now, with nice console and stop/start windows. >> >> *Docs* >> >> Really, from a product perspective, this should probably be the highest >> priority. Our tech is kicking major ass, we need to make it more obvious to >> people how to use it. The RestConfig stuff in particular will need a lot of >> documentation and examples and sample scripts. But we've known for awhile >> that most of the docs could use some love. I'd like us to make a commitment >> to being the best document geospatial server, open source or otherwise. >> >> But in general things are feeling pretty awesome. I have a bit more, but >> I'll send another email about that stuff. >> >> best regards, >> >> Chris >> >> Rob Atkinson wrote: >>> In the medium term, (targetting 2.0) CSIRO is resourcing >>> >>> http://jira.codehaus.org/browse/GEOS-552 >>> >>> in the short term, IMHO it would be very useful to support GML3.2, as >>> INSPIRE (a bigger market for WFS than everything that has gone before) >>> will mandate this. >>> >>> http://jira.codehaus.org/browse/GEOS-2378 >>> >>> I'd be interested in seeing what else is targeted for 2.0 in the >>> emerging roadmap, and what it's big announcement is. Meeting basic SDI >>> requirements seems a pretty good reason, and we cant begin to claim >>> this until we land these issues. >>> >>> Rob Atkinson >>> >>> >>> On Wed, Dec 10, 2008 at 1:49 PM, Justin Deoliveira <[email protected]> >>> wrote: >>>> Thanks for starting things off Andrea. As per discussion in IRC i would >>>> like to continue things along as well as encourage others to chime in >>>> with things they want to see. >>>> >>>> Things I want to see in the near future: >>>> >>>> * Move geosearch module to core distribution >>>> http://jira.codehaus.org/browse/GEOS-2496 >>>> >>>> * Integrate GeoExt based styler >>>> http://jira.codehaus.org/browse/GEOS-2498 >>>> >>>> * move restconfig to core module >>>> http://jira.codehaus.org/browse/GEOS-2497 >>>> >>>> -Justin >>>> >>>> Andrea Aime wrote: >>>>> Hi, >>>>> following yesterday discussion during the GeoServer IRC meeting >>>>> I've been looking into Jira for "New Feature", "Improvement" or "Task" >>>>> issues that are scheduled for 1.7.2. Actually yesterdays we talked >>>>> only about "New Feature", but since the issue type has not been >>>>> used consistently in the past, I thought to expand a bit the >>>>> search: >>>>> >>>>> >>>>> http://jira.codehaus.org/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?fixfor=14681&type=4&type=2&type=3&type=5&pid=10311&resolution=-1&sorter/field=priority&sorter/order=DESC&tempMax=1000 >>>>> >>>>> Wow, there are 53. >>>>> It's not like these are the real new features scheduled >>>>> for 1.7.2, as being there is more of a side effect of having >>>>> been scheduled by someone for some 1.6.x or 1.7.x release and >>>>> have been moved forward ever since. >>>>> >>>>> So ok, the idea of the roadmap was to present a few compelling >>>>> new features making up the theme of a release. >>>>> >>>>> Here is what I would like to see in 1.7.2 (but I have no funding >>>>> for those atm, thought I could pour some of my personal time into >>>>> some of these during the holidays should OpenGeo decide not >>>>> to sponsor these directly): >>>>> >>>>> * http://jira.codehaus.org/browse/GEOS-2288 >>>>> Directory datastore. This is an old issue actually, we looked >>>>> into integrating that datastore in the past already (1.5.x >>>>> something). The thin is that the datastore as it stands >>>>> is not usable, but a rewrite is easy and I have some ideas >>>>> coming togheter already. >>>>> * http://jira.codehaus.org/browse/GEOS-665 >>>>> From the "I love low effort big gain" department, here is >>>>> one that would multiply WFS output format count by 10 >>>>> at the least and there is also a patch that could be used >>>>> as a started >>>>> * http://jira.codehaus.org/browse/GEOS-2296 >>>>> This one is from "pain in the axe" ;-) department, I keep >>>>> on hearing people asking for ECW support, and Frank at >>>>> FOSS4G suggested a way out, but it requires rebuilding >>>>> all of the GDAL native parts so that ECW is turned >>>>> into a plugin. I guess this one would need some GeoSolutions >>>>> work, so take it just as a Christmas wish, would you? :) >>>>> * http://jira.codehaus.org/browse/GEOS-2433 >>>>> This is almost done, so why not? >>>>> * http://jira.codehaus.org/browse/GEOS-1783 >>>>> This one I already coded, but requires a small change in the >>>>> (sigh) unmantained refererencing subsystem. A small gift >>>>> to all italian people getting crazy because GeoServer reprojects >>>>> data 100m away only because it's using the Sardinia ellipsoid >>>>> parameters whilst most of the data of course resides somewhere >>>>> else >>>>> * http://jira.codehaus.org/browse/GEOS-2386 >>>>> This one I have already in progress as well, and it's a nice >>>>> new one for people with huge data sets and a need to serve >>>>> them with WFS >>>>> >>>>> Well, that's sort of my personal wish list out of those >>>>> 53 issues (and as I said, I can probably sponsor personally >>>>> one or two or these, the others need OpenGeo/someone else's >>>>> get go) >>>>> Anybody else? >>>>> >>>>> Cheers >>>>> Andrea >>>>> >>>>> >>>> -- >>>> Justin Deoliveira >>>> OpenGeo - http://opengeo.org >>>> Enterprise support for open source geospatial. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, >>>> Nevada. >>>> The future of the web can't happen without you. Join us at MIX09 to help >>>> pave the way to the Next Web now. Learn more and register at >>>> >>>> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ >>>> _______________________________________________ >>>> Geoserver-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>> >>> >>> ------------------------------------------------------------------------------ >>> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, >>> Nevada. >>> The future of the web can't happen without you. Join us at MIX09 to help >>> pave the way to the Next Web now. Learn more and register at >>> >>> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ >>> _______________________________________________ >>> Geoserver-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> -- >> Chris Holmes >> OpenGeo - http://opengeo.org >> Expert service straight from the developers. >> > > ------------------------------------------------------------------------------ > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. > The future of the web can't happen without you. Join us at MIX09 to help > pave the way to the Next Web now. Learn more and register at > http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Chris Holmes OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
