Yes, we are talking about the Table Joining Service specification. We have been implementing all the interfaces of the specification, with some limitations, and a management console. Now we are working with Geoserver 2.2.4. Some little changes to Geoserver core where required, specifically to packages main and wms. In main package add a method setWebMapServer to ResourcePool class. With this change we can set our own inherited implementation of this class. Also the implementation allows to apply styles in SLD format (with rules on datasets fields). In the package wms the method checkStyle was lightly changed in the class GetMapKvpRequestReader to avoid a exception when applying styles to a cascaded WMS layer.
And other bigger changes are needed in order to guarantee consistency when geoserver catalog’s objects are deleted or modified.
In this mail I’m attaching some slides where the list members can evaluate the implementation degree.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
(attachments)
TJS Geoserver Slides.pptx (903 KB)
Hey Rafael, it sounds like a great contribution to GeoServer. One project I work on (http://mapstory.org) actually could probably make great use of this.
Do you have the code up on github? Would be great to see what the core changes are. The first step is definitely to get on github, and then after that to get a community module in the main repo. And hopefully we can work to incorporate the core changes needed.
···
On Fri, May 10, 2013 at 11:31 AM, Rafael Cruz <rcruz@anonymised.com> wrote:
Yes, we are talking about the Table Joining Service specification. We have been implementing all the interfaces of the specification, with some limitations, and a management console. Now we are working with Geoserver 2.2.4. Some little changes to Geoserver core where required, specifically to packages main and wms. In main package add a method setWebMapServer to ResourcePool class. With this change we can set our own inherited implementation of this class. Also the implementation allows to apply styles in SLD format (with rules on datasets fields). In the package wms the method checkStyle was lightly changed in the class GetMapKvpRequestReader to avoid a exception when applying styles to a cascaded WMS layer.
And other bigger changes are needed in order to guarantee consistency when geoserver catalog’s objects are deleted or modified.
In this mail I’m attaching some slides where the list members can evaluate the implementation degree.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
Learn Graph Databases - Download FREE O’Reilly Book
“Graph Databases” is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Hi Chris:
We don’t have any previous experience about collaborating and will start publishing the code on GitHub. Once the project is there, we’ll notify to the list.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
···
On Fri, May 10, 2013 at 11:31 AM, Rafael Cruz <rcruz@anonymised.com> wrote:
Yes, we are talking about the Table Joining Service specification. We have been implementing all the interfaces of the specification, with some limitations, and a management console. Now we are working with Geoserver 2.2.4. Some little changes to Geoserver core where required, specifically to packages main and wms. In main package add a method setWebMapServer to ResourcePool class. With this change we can set our own inherited implementation of this class. Also the implementation allows to apply styles in SLD format (with rules on datasets fields). In the package wms the method checkStyle was lightly changed in the class GetMapKvpRequestReader to avoid a exception when applying styles to a cascaded WMS layer.
And other bigger changes are needed in order to guarantee consistency when geoserver catalog’s objects are deleted or modified.
In this mail I’m attaching some slides where the list members can evaluate the implementation degree.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
Learn Graph Databases - Download FREE O’Reilly Book
“Graph Databases” is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Sounds great. The ideal thing to do to ‘fork’ the repo, see https://help.github.com/articles/fork-a-repo
So you have your own version of GeoServer. Then apply all your changes to your fork. And then if you ‘push’ your local changes to your github repository they will be online for all GeoServer developers to check out. And after review if things are ok to merge it’s just really easy, just a few commands, instead of looking over a big patch of changes or a bunch of new files.
best regards,
Chris
···
On Mon, May 13, 2013 at 3:05 PM, Rafael Cruz <rcruz@anonymised.com> wrote:
Hi Chris:
We don’t have any previous experience about collaborating and will start publishing the code on GitHub. Once the project is there, we’ll notify to the list.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
-----Original Message-----
From: Chris Holmes <cholmes@anonymised.com>
To: Rafael Cruz <rcruz@anonymised.com>
Cc: “geoserver-devel@lists.sourceforge.net” <geoserver-devel@lists.sourceforge.net>, Jose Luis Capote Fernandez <capote@anonymised.com>
Date: Sat, 11 May 2013 11:23:32 -0400
Subject: Re: [Geoserver-devel] Yes, Table Joining Service implementation
Hey Rafael, it sounds like a great contribution to GeoServer. One project I work on (http://mapstory.org) actually could probably make great use of this.
Do you have the code up on github? Would be great to see what the core changes are. The first step is definitely to get on github, and then after that to get a community module in the main repo. And hopefully we can work to incorporate the core changes needed.
On Fri, May 10, 2013 at 11:31 AM, Rafael Cruz <rcruz@anonymised.com> wrote:
Yes, we are talking about the Table Joining Service specification. We have been implementing all the interfaces of the specification, with some limitations, and a management console. Now we are working with Geoserver 2.2.4. Some little changes to Geoserver core where required, specifically to packages main and wms. In main package add a method setWebMapServer to ResourcePool class. With this change we can set our own inherited implementation of this class. Also the implementation allows to apply styles in SLD format (with rules on datasets fields). In the package wms the method checkStyle was lightly changed in the class GetMapKvpRequestReader to avoid a exception when applying styles to a cascaded WMS layer.
And other bigger changes are needed in order to guarantee consistency when geoserver catalog’s objects are deleted or modified.
In this mail I’m attaching some slides where the list members can evaluate the implementation degree.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
Learn Graph Databases - Download FREE O’Reilly Book
“Graph Databases” is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
We also have some info about using git in our developer guide.
http://docs.geoserver.org/stable/en/developer/source.html
···
On Mon, May 13, 2013 at 12:16 PM, Chris Holmes <cholmes@anonymised.com> wrote:
Sounds great. The ideal thing to do to ‘fork’ the repo, see https://help.github.com/articles/fork-a-repo
So you have your own version of GeoServer. Then apply all your changes to your fork. And then if you ‘push’ your local changes to your github repository they will be online for all GeoServer developers to check out. And after review if things are ok to merge it’s just really easy, just a few commands, instead of looking over a big patch of changes or a bunch of new files.
best regards,
Chris
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Mon, May 13, 2013 at 3:05 PM, Rafael Cruz <rcruz@anonymised.com> wrote:
Hi Chris:
We don’t have any previous experience about collaborating and will start publishing the code on GitHub. Once the project is there, we’ll notify to the list.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
-----Original Message-----
From: Chris Holmes <cholmes@anonymised.com>
To: Rafael Cruz <rcruz@anonymised.com>
Cc: “geoserver-devel@lists.sourceforge.net” <geoserver-devel@lists.sourceforge.net>, Jose Luis Capote Fernandez <capote@anonymised.com>
Date: Sat, 11 May 2013 11:23:32 -0400
Subject: Re: [Geoserver-devel] Yes, Table Joining Service implementation
Hey Rafael, it sounds like a great contribution to GeoServer. One project I work on (http://mapstory.org) actually could probably make great use of this.
Do you have the code up on github? Would be great to see what the core changes are. The first step is definitely to get on github, and then after that to get a community module in the main repo. And hopefully we can work to incorporate the core changes needed.
On Fri, May 10, 2013 at 11:31 AM, Rafael Cruz <rcruz@anonymised.com> wrote:
Yes, we are talking about the Table Joining Service specification. We have been implementing all the interfaces of the specification, with some limitations, and a management console. Now we are working with Geoserver 2.2.4. Some little changes to Geoserver core where required, specifically to packages main and wms. In main package add a method setWebMapServer to ResourcePool class. With this change we can set our own inherited implementation of this class. Also the implementation allows to apply styles in SLD format (with rules on datasets fields). In the package wms the method checkStyle was lightly changed in the class GetMapKvpRequestReader to avoid a exception when applying styles to a cascaded WMS layer.
And other bigger changes are needed in order to guarantee consistency when geoserver catalog’s objects are deleted or modified.
In this mail I’m attaching some slides where the list members can evaluate the implementation degree.
Best regards,
Rafael Cruz Iglesias
GeoMIX Office Director
GeoSí Enterprise
Learn Graph Databases - Download FREE O’Reilly Book
“Graph Databases” is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel