<div dir="ltr">All new features are in the refactor branch:<div><a href="http://svn.featureserver.org/branches/refactor">http://svn.featureserver.org/branches/refactor</a></div><div><br></div><div>Please use this instead of the trunk ...</div>
<div><br></div><div>Chris - what do you think about adding a note to the <a href="http://featureserver.org">featureserver.org</a> site noting the recommended svn location for most recent features?</div><div><br></div><div>
-Josh<br><br><div class="gmail_quote">On Wed, Oct 15, 2008 at 9:35 AM, Roald de Wit <span dir="ltr"><<a href="mailto:roald.dewit@lisasoft.com">roald.dewit@lisasoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Christopher and list,<br>
<br>
Could it be that the new features described below are not in SVN trunk<br>
yet? If so, would it be a good idea to add them? That could help us,<br>
users play with it and maybe discover bugs and/or provide patches.<br>
<br>
I'm very interested in using the WPS-like functionality within FS.<br>
<br>
Thanks, Roald<br>
<br>
<br>
On Wed, 2008-05-21 at 13:48 +0930, Christopher Schmidt wrote:<br>
> This weekend, at Wherecamp, Myself, jlivni, and brentp took on the task<br>
> of refactoring a significant chunk of FeatureServer.<br>
><br>
> The result, which I've been referring to as FeatureServer 2.0, will<br>
> likely be a significant step forwards, and although I expect it won't be<br>
> significantly different to operate, there are enough changes that I'd<br>
> like to call it '2.0', and stop further development of the 1.x line.<br>
><br>
> Major new feature:<br>
> * Improved support for attribute queries: Now supporting comparisons<br>
> like greaterthan, lessthan, etc. using django-like URL filters, on<br>
> datasources which support them.<br>
><br>
> * Support for processing actions on output. Any datasource can now<br>
> define a list of 'processes', which will then be applied to the<br>
> features after they are loaded from the dataset and before they are<br>
> returned to the user.<br>
><br>
> <a href="http://featureserver.org/refactor/doc/Processes.html" target="_blank">http://featureserver.org/refactor/doc/Processes.html</a> has more<br>
> information.<br>
><br>
> As a demo:<br>
> <a href="http://featureserver.org/refactor/featureserver.cgi/scribble/17.html" target="_blank">http://featureserver.org/refactor/featureserver.cgi/scribble/17.html</a><br>
> Complex Line.<br>
><br>
> <a href="http://featureserver.org/refactor/featureserver.cgi/scribble_simplify/17.html" target="_blank">http://featureserver.org/refactor/featureserver.cgi/scribble_simplify/17.html</a><br>
> Somewhat simplified line. Not visibly so: the default of .1 at this<br>
> zoom shows little degredation.<br>
><br>
> <a href="http://featureserver.org/refactor/featureserver.cgi/scribble_simplify/17.html?process_simplify_tolerance=10" target="_blank">http://featureserver.org/refactor/featureserver.cgi/scribble_simplify/17.html?process_simplify_tolerance=10</a><br>
> Very simplified line.<br>
><br>
><br>
> New Properties:<br>
> * Feature model and serialization/deserialization is handled by<br>
> a seperated chunk of code, currently called vectorformats.<br>
> vectorformats is a lightweight OGR-like data converter in Python,<br>
> designed for the purpose of things like FeatureServer. (It will also<br>
> work well for other Python projects which need to serialize geometry<br>
> + attributes.)<br>
><br>
> * Refactored web serving to seperate code common to TileCache,<br>
> FeatureServer, WPServer.<br>
><br>
> * Updated internal geometry model to current GeoJSON specs<br>
><br>
> One thing that I'm thinking seriously about doing is changing the<br>
> 'default' format/service from GeoJSON to HTML (and, correspondingly,<br>
> improving the HTML to work in more places/support a wider set of<br>
> depandancies as options). The upshot of this would be:<br>
> * The default view is broser-oriented.<br>
> * Crawling from services like Google or other web services<br>
> would be more likely.<br>
> * It's easier to link from HTML to other services than the other way<br>
> around.<br>
><br>
> Downsides:<br>
> * Applications which expect a GeoJSON file based on a no-extension,<br>
> no-content type request will get screwed.<br>
><br>
> That downside seems an appropriate step to take at a 2.0, assuming that<br>
> the default setup can be made to fall back to something else which is<br>
> sensible if HTML support is not available.<br>
><br>
> At the moment, the work is in the 'refactor' branch. If there's<br>
> something about FeatureServer that has been bothering you, but it seemed<br>
> like an API change, now might be a good time to mention it. My current<br>
> plan is to continue hacking / playing in refactor for another week or so,<br>
> mostly writing tests and so on, and then merge it back to trunk, at<br>
> which point trunk will become '2.0 prep' until we release 2.0.<br>
><br>
> If this seems likely to interfere with deadlines of yours, please let<br>
> the list know, and we can look at how to solve the problem.<br>
><br>
> Regards,<br>
> --<br>
> Christopher Schmidt<br>
> MetaCarta<br>
> _______________________________________________<br>
> Featureserver mailing list<br>
> <a href="mailto:Featureserver@openlayers.org">Featureserver@openlayers.org</a><br>
> <a href="http://featureserver.org/mailman/listinfo/featureserver" target="_blank">http://featureserver.org/mailman/listinfo/featureserver</a><br>
--<br>
Roald de Wit<br>
Software Engineer<br>
<a href="mailto:roald.dewit@lisasoft.com">roald.dewit@lisasoft.com</a><br>
<br>
Commercial Support for Open Source GIS Software<br>
<a href="http://lisasoft.com/LISAsoft/SupportedProducts/" target="_blank">http://lisasoft.com/LISAsoft/SupportedProducts/</a><br>
<br>
_______________________________________________<br>
Featureserver mailing list<br>
<a href="mailto:Featureserver@openlayers.org">Featureserver@openlayers.org</a><br>
<a href="http://featureserver.org/mailman/listinfo/featureserver" target="_blank">http://featureserver.org/mailman/listinfo/featureserver</a><br>
</blockquote></div><br></div></div>