Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve management command docs #212

Open
pvgenuchten opened this issue Jan 20, 2022 · 1 comment
Open

improve management command docs #212

pvgenuchten opened this issue Jan 20, 2022 · 1 comment

Comments

@pvgenuchten
Copy link
Contributor

While reading https://docs.geonode.org/en/master/admin/index.html#geonode-management-commands, it is not clear why all calls to python are prepended with DJANGO_SETTINGS_MODULE=geonode.settings. Can you add an intro to the section to explain how management commands can be invoked?

DJANGO_SETTINGS_MODULE=geonode.settings python manage.py updatelayers --help

For the management command update-layers can you add a section to explain what is the actual procedure?

  • Does the procedure update all layers, or only the layers which are not present yet
  • Does the procedure update also the metadata (update bounds, if bounds have changed on geoserver), update title/abstract/keywords, if they have changed on geoserver.
  • Does the procedure remove layers from geonode if they are no longer available on geoserver
  • Does geonode also update the geoserver config, to add a back-linkage to pycsw metadata url?

For the import-layers command can you add a section in the doc on how metadata is imported,

  • Does geonode import a file.shp.xml as metadata if included on the shapefile? Should the file have a specific metadata format (iso19139?). Or is minimal metadata generated from a template?
  • Does the import-layers command go into subfolders?
  • What filetypes are supported?

Thank you!

@pvgenuchten
Copy link
Contributor Author

update-layers

  • Does the procedure update all layers, or only the layers which are not present yet? A configuration parameter exists for this --skip-geonode-registered

  • Does the procedure update also the metadata (update bounds, if bounds have changed on geoserver), update title/abstract/keywords, if they have changed on geoserver? Yes, new metadata is created for each of the layers

  • Does the procedure remove layers from geonode if they are no longer available on geoserver? A configuration option exists for this --remove-deleted

  • Does geonode also update the geoserver config, to add a back-linkage to pycsw metadata url? Afaik, no.

import-layers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant