1. Regarding the problems with the hydrologic soil group coverages. On a
whim, I removed the global hydrologic soil group layer and recreated it
with a slightly different name (changing "soils" to "soil"). This fixes
the problem for both the global and puget coverages. Apparently one is
not allowed to have two coverage stores with the same name, even if they
are in different workspaces? I have put a comment in the jira issue to
the effect that it would be nice if the geoserver user interface tested
for this and told the user to choose a different name.
2. On the geoserver keyword batch update front, I took a detour to look
at the java classes restconfig-client that are distributed with
geoserver, but they had serious problems both in the implementation and
the approach, all of which was discussed on the geoserver-devel mailing
list and may possibly lead to some improvements in the future. But for
now, I plan to go back to my original approach of using php scripts and
the cURL library, which would be robust to modifications in the
geoserver Rest schema (which is the main problem with the approach taken
in the java client).
Thats it on the geoserver front.
Ciao, Tara
--
Tara Athan
Owner, Athan Ecological Reconciliation Services
tara_athan at
alt2is.com
707-272-2115 (cell, preferred)
707-485-1198 (office)
249 W. Gobbi St. #A
Ukiah, CA 95482
--
Subscription settings:
http://groups.google.com/group/aries-project/subscribe?hl=en