{ "id": "geonode-vs-geonetwork", "ids": [ "geonode", "geonetwork" ], "title": "GeoNode vs GeoNetwork: geospatial portals and metadata discovery", "heading": "GeoNode vs GeoNetwork", "kicker": "GIS and analysis software comparison", "deck": "GeoNode suits a broader geospatial publishing and sharing portal. GeoNetwork focuses on metadata catalogue management and discovery. Choose according to whether users need to publish and manage geospatial content itself or catalogue resources hosted elsewhere.", "description": "Compare GeoNode vs GeoNetwork for geospatial portals and metadata discovery.", "answerHeading": "Which option fits the requirement?", "answer": "GeoNode suits a broader geospatial publishing and sharing portal. GeoNetwork focuses on metadata catalogue management and discovery. Choose according to whether users need to publish and manage geospatial content itself or catalogue resources hosted elsewhere.", "checkedAt": "2026-10-25", "researchTag": "Deployment, compatibility and cost scope", "researchLimit": "Official product material reviewed. Acceptance checks are proposed exercises, not completed product trials, performance measurements or reliability guarantees.", "datasetDescription": "Seven technical differences and four proposed acceptance checks for GeoNode vs GeoNetwork.", "type": "workflow-buying", "sharedBuyingNeed": "Evaluate alternative approaches to geospatial portals and metadata discovery.", "rows": [ [ "Product role", "Geospatial content sharing platform", "Spatial metadata catalogue application" ], [ "Operating model", "Open-source platform operated by your team", "Open-source catalogue deployment" ], [ "Information managed", "Geospatial content and associated metadata", "Metadata records and resource references" ], [ "Discovery context", "Portal-based publication and discovery", "Metadata search, editing and discovery" ], [ "Publication boundary", "Platform services and data access need configuration", "Referenced services keep their own access controls" ], [ "Evaluation focus", "Content publication, permissions and portal operations", "Metadata profiles, harvesting and search behaviour" ], [ "Cost components", "Hosting, integration, maintenance and support", "Hosting, metadata work, maintenance and support" ] ], "scenarios": [ { "name": "Record migration", "question": "Can the team import copied metadata records with known identifiers and resource links?", "left": "With GeoNode, import copied metadata records with known identifiers and resource links.", "right": "With GeoNetwork, import copied metadata records with known identifiers and resource links.", "note": "Required fields, identifiers and links remain valid." }, { "name": "Discovery task", "question": "Can the team search for a specified dataset using its title, topic and spatial extent?", "left": "With GeoNode, search for a specified dataset using its title, topic and spatial extent.", "right": "With GeoNetwork, search for a specified dataset using its title, topic and spatial extent.", "note": "The intended users can find the correct record." }, { "name": "Access separation", "question": "Can the team publish a public record referencing a restricted test resource?", "left": "With GeoNode, publish a public record referencing a restricted test resource.", "right": "With GeoNetwork, publish a public record referencing a restricted test resource.", "note": "Catalogue discovery does not grant unintended data access." }, { "name": "Harvest update", "question": "Can the team change an authorised source record and run a test harvest?", "left": "With GeoNode, change an authorised source record and run a test harvest.", "right": "With GeoNetwork, change an authorised source record and run a test harvest.", "note": "The update is traceable without unexpected duplicates." } ], "exampleTable": { "caption": "Proposed checks using authorised copies of representative datasets, projects or models. Record software versions, required licences, dependencies, configuration and observed results.", "headers": [ "Requirement", "Proposed exercise", "Accept when" ], "rows": [ [ "Record migration", "Import copied metadata records with known identifiers and resource links.", "Required fields, identifiers and links remain valid." ], [ "Discovery task", "Search for a specified dataset using its title, topic and spatial extent.", "The intended users can find the correct record." ], [ "Access separation", "Publish a public record referencing a restricted test resource.", "Catalogue discovery does not grant unintended data access." ], [ "Harvest update", "Change an authorised source record and run a test harvest.", "The update is traceable without unexpected duplicates." ] ] }, "sections": [ { "id": "scope-and-architecture", "navLabel": "Architecture", "title": "Scope and architecture", "paragraphs": [ "GeoNode suits a broader geospatial publishing and sharing portal. GeoNetwork focuses on metadata catalogue management and discovery. Choose according to whether users need to publish and manage geospatial content itself or catalogue resources hosted elsewhere.", "A metadata catalogue describes and helps discover resources; it does not necessarily host, edit or grant access to the underlying data. GeoNode includes a broader geospatial sharing platform, while metadata-focused products can sit alongside existing data services." ], "links": [ { "url": "https://geonode.org/", "label": "GeoNode product information" }, { "url": "https://geonetwork-opensource.org/", "label": "GeoNetwork product information" } ] }, { "id": "cost-and-migration", "navLabel": "Costs & migration", "title": "Cost and migration planning", "paragraphs": [ "For GeoNode, include hosting, integration, maintenance and support. For GeoNetwork, include hosting, metadata work, maintenance and support. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration.", "Move a small authorised set of metadata records, preserve resource links and access restrictions, and test harvesting and search. Confirm metadata profiles and the ownership of each referenced dataset before moving a catalogue." ] } ], "faqs": [ { "question": "How should we choose between GeoNode and GeoNetwork?", "answer": "GeoNode suits a broader geospatial publishing and sharing portal. GeoNetwork focuses on metadata catalogue management and discovery. Choose according to whether users need to publish and manage geospatial content itself or catalogue resources hosted elsewhere." }, { "question": "Which costs belong in the comparison?", "answer": "For GeoNode, include hosting, integration, maintenance and support. For GeoNetwork, include hosting, metadata work, maintenance and support. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration." }, { "question": "What should we validate before a production move?", "answer": "Move a small authorised set of metadata records, preserve resource links and access restrictions, and test harvesting and search. Confirm metadata profiles and the ownership of each referenced dataset before moving a catalogue." } ], "sources": [ { "url": "https://geonode.org/", "facts": "Official product scope, deployment and integration context used for geospatial portals and metadata discovery." }, { "url": "https://geonetwork-opensource.org/", "facts": "Official product scope, deployment and integration context used for geospatial portals and metadata discovery." } ], "relatedLinks": [ { "path": "/categories/gis-geospatial/", "title": "Gis Geospatial software" }, { "path": "/guides/software-buying-checklist/", "title": "Software buying checklist" } ] }