| [geogig-dev] Geogig store in Geoserver 2.10.1 fails to find any repo data |
|
Dear list, Really pleased that Geogig has had a first full release! Here at British Antarctic Survey we have been looking to implement a versioned geospatial data repository for some time, and I am spending some time trying out Geogig 1.0 (downloaded
2017-01-13) to see if it meets our needs. I have an existing PostGIS database (non-versioned) whose data I’d like to import into a Geogig repository. I created a database ‘geogig’ within the same PostgreSQL 9.3 installation with a suitable user role, and then used the command: geogig pg import --all --repo 'postgresql://<server>/geogig/add/master?user=geogig&password=<password>' --host <server> --schema add7 --database magic --user add --password <password> on the workstation where I installed Geogig (the server is a different Centos Linux VM running PostgreSQL 9.3, within our local network). This command appeared to work correctly, giving feedback on the import process and completing without
errors. Running the command: geogig ls --repo 'postgresql://<server>/geogig/add/master?user=geogig&password=<password>' Resulted in the output: Root tree/ antarctic_elevations/ antarctic_contours_medium/ antarctic_coastline_line_high/ sub_antarctic_coastline_high_to30s/ antarctic_graticule/ antarctic_rock_outcrop_low/ antarctic_circle/ antarctic_lakes_high/ antarctic_seamask_medium/ antarctic_coastal_change/ sub_antarctic_coastline_low_to30s/ antarctic_streams/ antarctic_lakes_medium/ antarctic_seamask_high/ antarctic_ice_feature_catchments/ antarctic_bas_survey_points/ sub_antarctic_coastline_high/ antarctic_moraine_high/ antarctic_coastline_polygon_high/ antarctic_rock_outcrop_high/ antarctic_coastline_line_medium/ antarctic_coastline_polygon_low/ antarctic_contours_low/ antarctic_contours_high/ antarctic_landsat_rock/ antarctic_rock_outcrop_medium/ sub_antarctic_coastline_medium_to30s/ antarctic_moraine_medium/ antarctic_facilities/ antarctic_coastline_polygon_medium/ sub_antarctic_coastline_medium/ antarctic_seamask_low/ antarctic_historic_sites/ antarctic_coastline_line_low/ sub_antarctic_coastline_low/ antarctic_add_data_limit/ antarctic_lima_tile_grid/ So I’m assuming my data has imported correctly. I now want to expose the newly created repository via Geoserver 2.10.1 according to: http://geogig.org/docs/interaction/geoserver_ui.html So I downloaded the 2.10 extension, copied all the jars to WEB-INF/lib and restarted. Geoserver can now create Geogig stores. First I went to “Geogig repositories” in the admin GUI and selected “Import an existing repository”. I selected
PostgreSQL and entered the details. Now my master repo showed up in the list. I then tried to create a versioned data store based on this via Stores -> Add new store -> Geogig versioning data store. I entered name and description and checked “Enabled”,
then selected my repo from the drop-down list. I selected “master” from the branch drop-down as I don’t have a checked out branch at present. Clicking “Save” then brought up the “New layer” page. At this point the list of data layers capable of being published
from the repo is empty. I see no error output in geoserver_data/logs/geoserver.log or the Tomcat container logfile catalina.out.
I’m quite prepared to believe that I’m misunderstanding some aspect of Geogig operation as I’m new to the software. Can someone enlighten me as to why Geoserver appears to think my repository is empty, or can’t read it for some reason?
Any extra logging I can turn on to get more information? I’d be really grateful for any help. Many thanks, David Herbert Web GIS Developer British Antarctic Survey. This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. |