The ckanext-geonode extension provides a dedicated harvester for CKAN that retrieves metadata and resources from GeoNode instances. Unlike generic CSW harvesters, it leverages GeoNode's internal API to access richer information, including maps and documents, which might not be available through CSW records alone. This ensures a more complete and detailed synchronization of GeoNode resources within CKAN. Key Features: GeoNode API Harvesting: Uses GeoNode's own API for more complete data retrieval, going beyond standard CSW metadata. Resource Subtype Filtering: Allows selective harvesting of specific resource subtypes (layers, maps, documents) via the import configuration option. This enables focused harvesting, improving efficiency and relevance. Dynamic Metadata Mapping: Implements a flexible system for dynamically mapping GeoNode resource properties to CKAN dataset fields (tags, extras, groups). This customization allows alignment of metadata structures between systems. Rule-Based Mapping: Utilizes a rules engine with filters and actions to control how GeoNode resource data is mapped to the CKAN dataset. Rules consist of JMESPath filters and actions that define how properties from GeoNode will be applied to the CKAN dataset’s properties. Technical Integration: The extension integrates with CKAN as a plugin, enabled through the ckan.plugins configuration option in the CKAN ini file (ckan.plugins = [...] harvest [...] geonode_harvester). It extends the CKAN harvesting framework, providing a specific harvester type for GeoNode instances. Configuration is managed through the harvester instance settings. Benefits & Impact: The primary benefit is richer and more seamless synchronization of GeoNode resources with CKAN, enabling organizations to centrally manage and discover geospatial data. Dynamic mapping allows the adoption of different organization schemas between GeoNode and CKAN. The selective importing of resource subtypes helps to control the information harvested based on the organization's needs.
This zipped file includes the presentation, exercises and corresponding data for the training for non GIS Experts. You can download the data and make the training in the specialized training platform of WFP GeoNode: http://training.geonode.wfp.org/
REQUIRED: A brief narrative summary of the data set.
EbolaGeonode was a partnership platform for sharing geospatial data, analysis and maps related to the Ebola emergency response. The platform was intended to minimize the time that GIS analysts spend locating up-to-date data. Users were able to make maps on the fly, view metadata, and access the reports behind GIS layers. Curators worked to ensure that the layers were recent, clean, useful, and legally and technically open.
Worldwide Country names to be used with the Wrold International Boundaries layer (https://geonode.wfp.org/layers/geonode%3Awld_bnd_admin0_l_unmap_2019#more)
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
A 40-minute tutorial to use OGC webservices offered by the Mission Atlantic GeoNode in your data analysis. The workshop makes use of Python Notebooks and common GIS Software (ArcGIS and QGIS), basic knowledge of Python and/or GIS software is recommended. • Introduction to OGC services • Search through metadata using the OGC Catalogue Service (CSW) • Visualize data using OGC Web Mapping Service (WMS) • Subset and download data using OGC Web Feature and Coverage Services (WFS/WCS) • Use OGC services with QGIS and/or ArcGIS
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is an extraction of roads from OpenStreetMap data made by WFP following UNSDI-T standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include streets and pathways that have been published on a separate dataset (streets and pathways).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
No abstract provided
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
No abstract provided
No abstract provided
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is an extraction of roads from OpenStreetMap data made by WFP following UNSDI-T standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include streets and pathways that have been published on a separate dataset (streets and pathways).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
This dataset is an extraction of streets and pathways from OpenStreetMap data made by WFP that follow UNSDIT standards. The data is updated in near-real time from OSM servers and include all latest updates. NOTE: this dataset doesn't include main roads that have been published on a separate dataset (main roads).
More documentation on the whole process for extracting OpenStreetMap roads can be found here: http://geonode.wfp.org/documents/6823/download
Proyecto"Atlas de vulnerabilidad hidroclimática de la cuenca amazónica"
No abstract provided
The ckanext-geonode extension provides a dedicated harvester for CKAN that retrieves metadata and resources from GeoNode instances. Unlike generic CSW harvesters, it leverages GeoNode's internal API to access richer information, including maps and documents, which might not be available through CSW records alone. This ensures a more complete and detailed synchronization of GeoNode resources within CKAN. Key Features: GeoNode API Harvesting: Uses GeoNode's own API for more complete data retrieval, going beyond standard CSW metadata. Resource Subtype Filtering: Allows selective harvesting of specific resource subtypes (layers, maps, documents) via the import configuration option. This enables focused harvesting, improving efficiency and relevance. Dynamic Metadata Mapping: Implements a flexible system for dynamically mapping GeoNode resource properties to CKAN dataset fields (tags, extras, groups). This customization allows alignment of metadata structures between systems. Rule-Based Mapping: Utilizes a rules engine with filters and actions to control how GeoNode resource data is mapped to the CKAN dataset. Rules consist of JMESPath filters and actions that define how properties from GeoNode will be applied to the CKAN dataset’s properties. Technical Integration: The extension integrates with CKAN as a plugin, enabled through the ckan.plugins configuration option in the CKAN ini file (ckan.plugins = [...] harvest [...] geonode_harvester). It extends the CKAN harvesting framework, providing a specific harvester type for GeoNode instances. Configuration is managed through the harvester instance settings. Benefits & Impact: The primary benefit is richer and more seamless synchronization of GeoNode resources with CKAN, enabling organizations to centrally manage and discover geospatial data. Dynamic mapping allows the adoption of different organization schemas between GeoNode and CKAN. The selective importing of resource subtypes helps to control the information harvested based on the organization's needs.