SLD SERVICE RESTLET PROPOSAL!
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
SLD SERVICE RESTLET PROPOSAL!
by kappu
::
Rate this Message:
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 |
|
|
Re: SLD SERVICE RESTLET PROPOSAL!
by Carlos Fernando Gonçalves
::
Rate this Message:
Hi Andrea Cappugi.
I think a good idea and has my support. I am developing a system for an institution here in Brazil and really have difficulties to implement the solutions that the user wants with the legends and styles of maps. Congratulations on your initiative and I hope it is successful in the GeoServer. I think many will like to have this resource in GeoServer. Best regards, Carlos Fernando Gonçalves 2007/11/9, Andrea Cappugi <kappu72@...>: Hi all, -- Carlos FG ------------------------------------------------------------------------- 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 |
|
|
Re: SLD SERVICE RESTLET PROPOSAL!
by Chris Holmes
::
Rate this Message:
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 |
|
|
Re: SLD SERVICE RESTLET PROPOSAL!
by Chris Holmes
::
Rate this Message:
Oh, right. And the next step is to make a wiki page describing the
module, you could start by mostly just copying the email you wrote and adding a bit of background. Add it as a subpage here: http://docs.codehaus.org/display/GEOSDOC/Community Let me know if you have trouble, as Mauro wasn't able to add stuff to GEOSDOC, had to do it in GEOS. Once that's there we can get you set up to commit the module. Chris Chris Holmes wrote: > 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 |
|
|
|
|
|
Re: SLD SERVICE RESTLET PROPOSAL!
by aaime
::
Rate this Message:
Andrea Cappugi ha scritto:
> 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! Hi Andrea, first of all, sorry for the very very late answer. The idea of serving SLD piece wise to a javascript client seems interesting, and the implementation you're proposing is ok. I see a few issues thought: * a client might want to grab a full subtree without having to do 50 calls. If the SLD is big, there is a trade off between the amount of data you can deal with in a javascrict client, and the amount of network delay one has to pay for each call. I'd suggest to stop the splitting at the rule level, and to allow full download on the upper levels by using a parameter (for example, &content=full) * the idea of having services generate resources server side seems fine, thought the url does not look right to me. Given that you're calling an algorithm, the url should be something like: http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}?quantileclassification&property={property}&classNum={num} I'm also not sure about the type of method, but since it's creating resources I guess it should be a POST * the split does work well on the read side, but seems to fall on the write side. When you create an SLD server side it must be valid, not an incomplete document. So I'd say writing wise: * the creation of a new sld is a put or a post that specifies a valid SLD * each item can be modified using PUT * new elements can be added dynamically using either POST or PUT, but each time this occurs the element must be complete and valid (think adding a rule or a feature type style) What do you think? Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@... https://lists.sourceforge.net/lists/listinfo/geoserver-devel |
|
|
Re: SLD SERVICE RESTLET PROPOSAL!
by kappu
::
Rate this Message:
> Hi Andrea, > first of all, sorry for the very very late answer. > Hi Andrea, I have to apologize too for my very very very late answer. > I'd suggest to stop the splitting at the rule level, and > to allow full download on the upper levels by using a parameter > (for example, &content=full) I agree, but I think is better to avoid the use of parameters in restlet We can find a different url mapping this request. Maybe we can return all the content rules excluded at -> http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID} > * the idea of having services generate resources server side > seems fine, thought the url does not look right to me. Given > that you're calling an algorithm, the url should be something > like: > http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}?quantileclassification&property={property}&classNum={num} > I'm also not sure about the type of method, but since it's > creating resources I guess it should be a POST As before, I'm not a great expert of Rest but I think that in a Rest architecture we have to avoid the use of parameters, but I'm not sure. :-) * the split does work well on the read side, but seems to > fall on the write side. When you create an SLD server side > it must be valid, not an incomplete document. is an SLD domcunmet without any rule a valide one? Thanks for your comments kappu ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list Geoserver-devel@... https://lists.sourceforge.net/lists/listinfo/geoserver-devel |
|
|
Re: SLD SERVICE RESTLET PROPOSAL!
by aaime
::
Rate this Message:
Andrea Cappugi ha scritto:
... >> * the idea of having services generate resources server side >> seems fine, thought the url does not look right to me. Given >> that you're calling an algorithm, the url should be something >> like: >> http://domain:8080/geoserver/sldservice/{featureType}/{UserStyleID}/{FeatureTypeStyleID}?quantileclassification&property={property}&classNum={num} >> I'm also not sure about the type of method, but since it's >> creating resources I guess it should be a POST > As before, I'm not a great expert of Rest but I think that in a Rest > architecture we have to avoid the use of parameters, but I'm not sure. :-) That's not my understanding, you have to avoid them to refer to resources, but you have to use them when calling algorithms server side. Someone suggest its usage for format specification too: http://groups.google.com/group/geo-web-rest/browse_frm/thread/b75e831aaaedc7a3 Cheers Andrea ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geoserver-devel mailing list Geoserver-devel@... https://lists.sourceforge.net/lists/listinfo/geoserver-devel |
| Free embeddable forum powered by Nabble | Forum Help |
