Suite 4.7 Feedback from GeoServer workshop

[jodygarnett]

Consistent GeoServer/Suite 4.7 issues:

• When importing meterors.zip the incorrect store was selected by default (we would like it to defaul to create new when importing a shapefile).

  Importer: imported "store" is consistently wrong - want it to default to "create new" and it is defaulting to the last used store (on Chrome at least).

  This issue was encountered multiple times and may be a GeoServer regression.

• When importing the cites.sld the default name was generated as "C:\styles\cities.sld" on one machine producing wicket error (another case where we need better name checking).

Documentation glitches:

• Documentation mistake: setting up shapefile store - field is called "Shapefile location" (not URL as documented)

• Documentation assumes opengeo suite ships with "medford" postgresql database - but that has not been true for a long time. We can either reword this section to be general, make the example uses "nyc" (from the postgresql workshop), or provide instructions for loading medford.

• Layergroup page incorrectly shows city names in the screen capture, no style has been defined yet so text labels are not yet generated.

• Importing styles, countries already existed (it is a default dataset).

  We will need to choose a new name (countries2.sld) and update subsequent steps? Or add logic to GeoServer prevent duplicate name.

  This issue was encountered by several individual, each managed to wreck the default countries.sld style, and break their existing opengeo:countries layer in the process.

Recommendations:

• Importing styles, we should take a moment to mention legend preview (new features).
• Remove GeoExplorer section (not sure if if it can be replaced with a simple SDK app, or just removed)
• Update KML section to use google maps or cesium or similar (google earth is dead)