[GeoMoose-users] Doc, etc on Supported Protocols

[Brent Fraser]

Hi Eli,

Thanks for the feedback!   
1.  I may just pick one the variations for my next documentation challenge (maybe legends).
2.  I think we should add a link to the "Protocol Test" on the Demos page of GeoMoose.org, since it already has Full, Lite, and Editing links
https://demo.geomoose.org/3.x/desktop?mapbook=test
3. I may just start with one Selenium-based interactive test and commit that.  Then add if we think it is useful.

Thanks again!
Brent

----------------------------------------
From: "Eli Adam" <eadam at co.lincoln.or.us>
Sent: 12/22/22 11:50 AM
To: "bfraser at geoanalytic.com" <bfraser at geoanalytic.com>
Subject: Re: [GeoMoose-users] Doc, etc on Supported Protocols

Hi Brent, 

This is great stuff!

- The tables look good.  Seeing them in the doc might lead to a few refinement suggestions.  Your Issue 730 comments are spot on, there are MANY factors and combinations
- I didn't know that the mapbook test was available on the demo site.  I might need some URL examples or tips of how to access that.  Thinking back to table improvements, maybe a few links from the table to the map book test so that people know they can directly test.  
- I'm not sure on automated testing.  I'm generally in favor of automated testing.  I've made previous efforts at this in 2.x series and while effective, it was a lot of work and a lot of work to keep up with.  I think exposing manual testing as in 2. above, is a good compromise or a good start.  It makes it available to anyone without having to build something different and set it up yourself.  
Thanks for all the great documentation.  

Best regards, Eli 

----------------------------------------
From: GeoMoose-users <geomoose-users-bounces at lists.osgeo.org> on behalf of Brent Fraser <bfraser at geoanalytic.com>
Sent: Tuesday, December 13, 2022 10:46 AM
To: GeoMoose Users <geomoose-users at lists.osgeo.org>
Subject:[GeoMoose-users] Doc, etc on Supported Protocols 

Hi All!,

Our recent Project Steering Committee meetings have inspired me to do some work on the Protocol Table.  My intent is to move it from a debugging aid embedded in a issue [#547] to a guide in the GeoMoose user documentation.

I've made some progress, but I'd like your opinion on:

1. Any additions (or improvements) to the table(s) you'd like to see?

As I mentioned in Issue #730 the current table is really just a  start.  Other potential additional topics are supported projections, legends, query formats, returned data formats.

2. How to deliver a working app covering the supported protocols?

The companion to the Protocol Table is the mapbook-test-servers.xml mapbook; I've found it invaluable in clarifying my understanding for the protocol support.  I really appreciate the work others have put into making the mapbook-test-servers.xml available on the demo site.

Writing a mapbook for displaying, identifying, and selecting data for all the various protocols is not too bad (easily used by adding mapbook=test in the URL), but Select operations are a different story.  They currently required adding code in the app.js, or using a different app.js (which would imply a different index.html adding complexity).  Any suggestions?  One idea is to implement a simplified/default search in GeoMoose not requiring any code in the app.js.

3. Should we include automated testing of the protocols?

While reviewing/confirming the content of the Protocol Table I think I've found a case that is a regression bug (Selecting, Searching GeoJSON data).  It might be useful to use Selenium to automate high level testing of the query operations on the different protocols.  But it might be a big effort to maintain the tests.

Thanks for your attention!

Best Regards,
Brent Fraser

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20221222/aba9fec0/attachment-0001.htm>