I was interested in getting feedback to see if this was something others would find valuable.
- More user friendly layer name/description in Google Earth. Layer titles and abstract are displayed as opposed to just the basic “workspace:name” for the network link names previously. Fallbacks are provided to ensure if any of this data is missing layers are not broken.
- New format option parameter “kmlrefresh” can be used to specify either a set interval in seconds or “expires” to utilize the cache expiration value specified in layer config. This will cause layers to automatically be refreshed without pan/zom when using kml refresh mode - useful for big-screen displays that must be regularly updated.
- New format option parameter “kmlvisible” can be used to set the initial state of all network links to be on or off. Useful if multiple layers are enabled and due to data volume it is desirable to not immediately request all layer data.
These are improvements I implemented into a custom build of GeoServer to support a client and thought they may be of value to the community. All unit tests and documentation have been updated to cover these changes.
Documentation added at the bottom of format options WMS section:
https://github.com/gisjon/geoserver/blob/kml-improvements/doc/en/user/source/services/wms/vendor.rst#format_options
Associated pull request:
https://github.com/geoserver/geoserver/pull/851
v/r,
···
Jonathan Meyer | Senior Software Engineer
Applied Information Sciences
Sounds like a neat bit of work Jonathan. Impressed that you have both documentation and unit tests.
Can you write up a quick proposal for the work? We are getting close to the code freeze.
I usually recommend writing a proposal prior to customer sign off. Either before starting work (to help confirm the design direction and minimize risk). You have already hit the usual gaps (documentation unit tests). A proposal is still useful to ensure our format options are consistent and to help schedule round release.
In the best case scenario this can identify potential collaborators (either developers to share workload, or users to donate QA testing).
···
On Tue, Jan 6, 2015 at 2:54 PM, Jonathan Meyer <jon@anonymised.com…4152…> wrote:
I was interested in getting feedback to see if this was something others would find valuable.
- More user friendly layer name/description in Google Earth. Layer titles and abstract are displayed as opposed to just the basic “workspace:name” for the network link names previously. Fallbacks are provided to ensure if any of this data is missing layers are not broken.
- New format option parameter “kmlrefresh” can be used to specify either a set interval in seconds or “expires” to utilize the cache expiration value specified in layer config. This will cause layers to automatically be refreshed without pan/zom when using kml refresh mode - useful for big-screen displays that must be regularly updated.
- New format option parameter “kmlvisible” can be used to set the initial state of all network links to be on or off. Useful if multiple layers are enabled and due to data volume it is desirable to not immediately request all layer data.
These are improvements I implemented into a custom build of GeoServer to support a client and thought they may be of value to the community. All unit tests and documentation have been updated to cover these changes.
Documentation added at the bottom of format options WMS section:
https://github.com/gisjon/geoserver/blob/kml-improvements/doc/en/user/source/services/wms/vendor.rst#format_options
Associated pull request:
https://github.com/geoserver/geoserver/pull/851
v/r,
Jonathan Meyer | Senior Software Engineer
Applied Information Sciences
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
–
Jody Garnett
Technical Lead | Boundless
jgarnett@anonymised.com
877-673-6436
@jodygarnett
I apologize for being uninformed on this process. Would this be the process outlined in the following doc:
http://docs.geoserver.org/latest/en/developer/policies/gsip.html
Thanks,
···
On Tue, Jan 6, 2015 at 6:42 PM, Jody Garnett <jgarnett@anonymised.com> wrote:
Sounds like a neat bit of work Jonathan. Impressed that you have both documentation and unit tests.
Can you write up a quick proposal for the work? We are getting close to the code freeze.
I usually recommend writing a proposal prior to customer sign off. Either before starting work (to help confirm the design direction and minimize risk). You have already hit the usual gaps (documentation unit tests). A proposal is still useful to ensure our format options are consistent and to help schedule round release.
In the best case scenario this can identify potential collaborators (either developers to share workload, or users to donate QA testing).
–
Jody
Jonathan Meyer
On Tue, Jan 6, 2015 at 2:54 PM, Jonathan Meyer <jon@anonymised.com> wrote:
I was interested in getting feedback to see if this was something others would find valuable.
- More user friendly layer name/description in Google Earth. Layer titles and abstract are displayed as opposed to just the basic “workspace:name” for the network link names previously. Fallbacks are provided to ensure if any of this data is missing layers are not broken.
- New format option parameter “kmlrefresh” can be used to specify either a set interval in seconds or “expires” to utilize the cache expiration value specified in layer config. This will cause layers to automatically be refreshed without pan/zom when using kml refresh mode - useful for big-screen displays that must be regularly updated.
- New format option parameter “kmlvisible” can be used to set the initial state of all network links to be on or off. Useful if multiple layers are enabled and due to data volume it is desirable to not immediately request all layer data.
These are improvements I implemented into a custom build of GeoServer to support a client and thought they may be of value to the community. All unit tests and documentation have been updated to cover these changes.
Documentation added at the bottom of format options WMS section:
https://github.com/gisjon/geoserver/blob/kml-improvements/doc/en/user/source/services/wms/vendor.rst#format_options
Associated pull request:
https://github.com/geoserver/geoserver/pull/851
v/r,
Jonathan Meyer | Senior Software Engineer
Applied Information Sciences
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
–
Jody Garnett
Technical Lead | Boundless
jgarnett@anonymised.com
877-673-6436
@jodygarnett
That is the one, you can see lots of other proposals here:
https://github.com/geoserver/geoserver/wiki/Proposals
No need to apologize - this is one of things we try to do to make it easier for consultants to work with GeoServer (and get paid for doing so).
···
On 6 January 2015 at 16:15, Jonathan Meyer <jon@anonymised.com> wrote:
I apologize for being uninformed on this process. Would this be the process outlined in the following doc:
http://docs.geoserver.org/latest/en/developer/policies/gsip.html
Thanks,
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Jody Garnett
Senior Software Engineer | Boundless
Jonathan Meyer
On Tue, Jan 6, 2015 at 6:42 PM, Jody Garnett <jgarnett@anonymised.com> wrote:
Sounds like a neat bit of work Jonathan. Impressed that you have both documentation and unit tests.
Can you write up a quick proposal for the work? We are getting close to the code freeze.
I usually recommend writing a proposal prior to customer sign off. Either before starting work (to help confirm the design direction and minimize risk). You have already hit the usual gaps (documentation unit tests). A proposal is still useful to ensure our format options are consistent and to help schedule round release.
In the best case scenario this can identify potential collaborators (either developers to share workload, or users to donate QA testing).
–
Jody
On Tue, Jan 6, 2015 at 2:54 PM, Jonathan Meyer <jon@anonymised.com> wrote:
I was interested in getting feedback to see if this was something others would find valuable.
- More user friendly layer name/description in Google Earth. Layer titles and abstract are displayed as opposed to just the basic “workspace:name” for the network link names previously. Fallbacks are provided to ensure if any of this data is missing layers are not broken.
- New format option parameter “kmlrefresh” can be used to specify either a set interval in seconds or “expires” to utilize the cache expiration value specified in layer config. This will cause layers to automatically be refreshed without pan/zom when using kml refresh mode - useful for big-screen displays that must be regularly updated.
- New format option parameter “kmlvisible” can be used to set the initial state of all network links to be on or off. Useful if multiple layers are enabled and due to data volume it is desirable to not immediately request all layer data.
These are improvements I implemented into a custom build of GeoServer to support a client and thought they may be of value to the community. All unit tests and documentation have been updated to cover these changes.
Documentation added at the bottom of format options WMS section:
https://github.com/gisjon/geoserver/blob/kml-improvements/doc/en/user/source/services/wms/vendor.rst#format_options
Associated pull request:
https://github.com/geoserver/geoserver/pull/851
v/r,
Jonathan Meyer | Senior Software Engineer
Applied Information Sciences
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
–
Jody Garnett
Technical Lead | Boundless
jgarnett@anonymised.com
877-673-6436
@jodygarnett
Swell. Thanks for the direction. I added a proposal for both the pull request discussed here and the other pull request I put in for relative time.
I did not attempt to add anything to the main proposal page as I assumed you or someone else added items there once it was determined what stage of the process they were in.
One other note of clarification, I proposed this for the next major release (2.7), but if there is allowance for inclusion into a sooner release (2.5/2.6?) that would be great. I assume that is somewhat dependent on the understood side-effects of the change.
https://github.com/geoserver/geoserver/wiki/GSIP-125—KML-Usability-Improvements
https://github.com/geoserver/geoserver/wiki/GSIP-124—WMS-WCS-Relative-Time-Support
Let me know if anything else is needed.
Cheers,
···
On Tue, Jan 6, 2015 at 7:59 PM, Jody Garnett <jgarnett@anonymised.com> wrote:
That is the one, you can see lots of other proposals here:
https://github.com/geoserver/geoserver/wiki/Proposals
No need to apologize - this is one of things we try to do to make it easier for consultants to work with GeoServer (and get paid for doing so).
Jody
Jonathan Meyer
–
Jody Garnett
Senior Software Engineer | Boundless
On 6 January 2015 at 16:15, Jonathan Meyer <jon@anonymised.com> wrote:
I apologize for being uninformed on this process. Would this be the process outlined in the following doc:
http://docs.geoserver.org/latest/en/developer/policies/gsip.html
Thanks,
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Jonathan Meyer
On Tue, Jan 6, 2015 at 6:42 PM, Jody Garnett <jgarnett@anonymised.com> wrote:
Sounds like a neat bit of work Jonathan. Impressed that you have both documentation and unit tests.
Can you write up a quick proposal for the work? We are getting close to the code freeze.
I usually recommend writing a proposal prior to customer sign off. Either before starting work (to help confirm the design direction and minimize risk). You have already hit the usual gaps (documentation unit tests). A proposal is still useful to ensure our format options are consistent and to help schedule round release.
In the best case scenario this can identify potential collaborators (either developers to share workload, or users to donate QA testing).
–
Jody
On Tue, Jan 6, 2015 at 2:54 PM, Jonathan Meyer <jon@anonymised.com> wrote:
I was interested in getting feedback to see if this was something others would find valuable.
- More user friendly layer name/description in Google Earth. Layer titles and abstract are displayed as opposed to just the basic “workspace:name” for the network link names previously. Fallbacks are provided to ensure if any of this data is missing layers are not broken.
- New format option parameter “kmlrefresh” can be used to specify either a set interval in seconds or “expires” to utilize the cache expiration value specified in layer config. This will cause layers to automatically be refreshed without pan/zom when using kml refresh mode - useful for big-screen displays that must be regularly updated.
- New format option parameter “kmlvisible” can be used to set the initial state of all network links to be on or off. Useful if multiple layers are enabled and due to data volume it is desirable to not immediately request all layer data.
These are improvements I implemented into a custom build of GeoServer to support a client and thought they may be of value to the community. All unit tests and documentation have been updated to cover these changes.
Documentation added at the bottom of format options WMS section:
https://github.com/gisjon/geoserver/blob/kml-improvements/doc/en/user/source/services/wms/vendor.rst#format_options
Associated pull request:
https://github.com/geoserver/geoserver/pull/851
v/r,
Jonathan Meyer | Senior Software Engineer
Applied Information Sciences
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
–
Jody Garnett
Technical Lead | Boundless
jgarnett@anonymised.com
877-673-6436
@jodygarnett