Looks good kappu. We are definitely interested in a javascript sld
editor as well (though lack funding for it right now). I think the main
thing I'd like to see in it is having set zoom levels that you can set
styles for, make a nice UI to tell which zooms you want your SLD apply to.
The service looks great, the one thing I wonder about is how it should
play with the REST configuration stuff Arne and David are working on.
Like it might make sense to just have one general resource location for
styles. Which I think would be as simple as adding to your stuff the
ability to just GET and PUT/POST the full SLD, in addition to just
portions (unless you already have that and I'm missing it), as an
alternate resource representation. I'm not sure which should be the
default...
But this doesn't have to happen immediately, just something to think
about, what our whole REST api picture should be.
best regards,
Chris
Andrea Cappugi wrote:
> Hi all,
> I'm developing a restlet service to manage sld, I would like to share
> with community (ideas and code).
> The idea is to develop a geoserver community module ables to serve an
> sld userStyle in a retfull way, (divided in multiple resource):
> Example:
>
http://domain:8080/geoserver/sldservice/{featureType}
> -> List of available styles in geoserver for a featuretype or coverage
> name link to resource
>
http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}
> -> UserStyle: Name Title Abstract IsDefault List of FeatureTypeStyle
> (only name, id and link to the resource)
>
http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}
> -> FeatureTypeStyle Name Title Abstract featureTypeName ruleslength
>
http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}/rules/
>
http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}/rules/{fisrtRuleId}/{lastRuleID}
> -> Rule list: As in sld spec. (using the first will return all rules)
> A live example is available at
>
http://test.ominiverdi.org:8080/geoserverSld/sldservice/topp:states (try
> also with other layers)
>
> I will add also the capabilities to generate rules based on
> classification system
> example:
>
http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}/quantileclassification/{property}/{classNum}
> -> Rule list generated server side
> (not yet added in the live example)
>
> Later I wish to develop a javascript sld editor,
> ables to work with a great number of rules and to create classified style.
> Any comments and ideas are welcome!
> Ciao kappu
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>
http://get.splunk.com/> _______________________________________________
> Geoserver-devel mailing list
>
Geoserver-devel@...
>
https://lists.sourceforge.net/lists/listinfo/geoserver-devel>
> !DSPAM:4005,47345498308313362379201!
>
[cholmes.vcf]
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;349 W. 12th Street, #3;New York;NY;10014;USA
email;internet:cholmes@...
title:Managing Director, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel