Remove the Geo-server component from Metacat

[taojing2002]

trafficstars

Geo-server is obsoleted in Metacat and we need to remove it. Those three parts we should get rid of :

• The geoserver war file in the metacat distribution
• The geoserver admin page on metacat configuration
• The related properties in the metacat.properties file

[yvanlebras]

Hi Jing! I am wondering if there is an interest to keep a link with GIS / OGC related standard proctol as geoserver was a manner to give access to a metacat data through WMS / WFS / WCS protocols ? Maybe this is not relevant, sorry ;)

[taojing2002]

Hi Yvan:

Thank you for your suggestion. However, the GeoServer part which we are removing is kind of different to your thought. It was used to build maps for displaying datasets. Now we use the Google map to replace it. Since it has some vulnerable jar files, we decided to remove it.

Thanks,

Jing

On Wed, Mar 16, 2022 at 3:35 AM Yvan Le Bras @.***> wrote:

Hi Jing! I am wondering if there is an interest to keep a link with GIS / OGC related standard proctol as geoserver was a manner to give access to a metacat data through WMS / WFS / WCS protocols ? Maybe this is not relevant, sorry ;)

— Reply to this email directly, view it on GitHub https://github.com/NCEAS/metacat/issues/1551#issuecomment-1068973920, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5QQDDTOHPHNB3YSAOQC6LVAG2NJANCNFSM5MIJLFUQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[artntek]

Additional info for removing: The related properties in the metacat.properties file

these properties include:

######## Spatial section              #########################################

spatial.runSpatialOption=false
spatial.regenerateCacheOnRestart=false
# Comma-seperated list of schemas containing spatial bounding boxes
# name corresponds to the docname stored in xml_documents table
spatial.spatialDocnameList=eml,fgdc,metadata
# XML paths to the four bounding coordinates
# These paths must be included in your indexPaths variable in build.properties
# Note the naming convention:
#   {docname}_{direction}BoundingCoordinatePath=.....
# Has not been tested with other schemas besides EML
spatial.eml_westBoundingCoordinatePath=geographicCoverage/boundingCoordinates/westBoundingCoordinate
spatial.eml_eastBoundingCoordinatePath=geographicCoverage/boundingCoordinates/eastBoundingCoordinate
spatial.eml_southBoundingCoordinatePath=geographicCoverage/boundingCoordinates/southBoundingCoordinate
spatial.eml_northBoundingCoordinatePath=geographicCoverage/boundingCoordinates/northBoundingCoordinate
spatial.fgdc_westBoundingCoordinatePath=spdom/bounding/westbc
spatial.fgdc_eastBoundingCoordinatePath=spdom/bounding/eastbc
spatial.fgdc_southBoundingCoordinatePath=spdom/bounding/southbc
spatial.fgdc_northBoundingCoordinatePath=spdom/bounding/northbc
spatial.metadata_westBoundingCoordinatePath=westbc
spatial.metadata_eastBoundingCoordinatePath=eastbc
spatial.metadata_southBoundingCoordinatePath=southbc
spatial.metadata_northBoundingCoordinatePath=northbc
spatial.docTitle=dataset/title

(but may include others)