How Should a GIS Developer in Spain Combine QGIS Plug-ins, Web Maps, and Licensed Datasets?

A GIS developer should organise the portfolio around distinct spatial products, name the map or pipeline's purpose and their contribution, and link only to demos, repositories, documentation, or imagery that the data licence and client permit.

A beautiful map is not enough if a reviewer cannot tell whether you built the data pipeline, analysis, QGIS plug-in, frontend, cartography, or deployment. At the same time, cadastral, mobility, environmental, commercial, or client datasets may have attribution, access, or redistribution limits that a public portfolio must respect.

Which GIS projects deserve separate entries?

Create separate entries for spatial products with different users, evidence, or maintenance paths, such as a QGIS plug-in, web map, geoprocessing pipeline, field tool, or published dataset.

State the user question, source category, processing responsibility, output, and your role. Name relevant technology only when it clarifies the work; a stack list without the spatial decision does not explain the project.

Keep one web map and its supporting pipeline together when they form a single product. Split a reusable plug-in or maintained dataset when it has an independent audience and canonical destination.

Interactive map: public URL with accessible fallback if available.
QGIS plug-in: official listing or repository.
Private analysis: approved case with safe static output.
Restricted dataset: describe provenance and licence, never republish it.

What is the fast way to build the GIS portfolio with IndieShow?

The fast way is to make one IndieShow card per spatial product, label its current status, and choose the strongest destination a reviewer can open without credentials.

Use the description for audience, geographic problem, artifact, and contribution; use the tag for GIS, QGIS, remote sensing, web mapping, or another useful domain. The optional metric is suitable only for a defined, permitted figure, not an estimate of coverage or impact.

Order projects for the target role and use the preview to check every card on desktop and mobile. Maps can stay on specialist hosts while the personal IndieShow URL provides the readable overview.

Build your IndieShow pageClaim your handle, organise the projects in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.

How should licensed or confidential geodata be handled?

Handle restricted geodata by publishing only what the licence, consent, and client agreement allow, with required attribution and a synthetic or aggregated substitute when raw features cannot be shown.

Do not assume that public availability means unrestricted redistribution. Check the dataset's licence, attribution, derivative-work terms, privacy risk, and whether combining layers exposes sensitive locations.

For private projects, describe the geographic task and technical method at a safe level. Never expose precise personal locations, critical infrastructure, customer assets, API keys, private tiles, or download endpoints.

What should each map or plug-in link prove?

Each link should prove the most important claim in the card: usable interaction, maintained code, documented installation, a published method, or an approved result.

Test web maps while signed out, on a narrow screen, and with the browser console closed to privileged tokens. Replace dead tile services or stale demos and state when a project is a historical snapshot.

For team maps, credit cartography, data engineering, frontend, analysis, and domain work accurately. A project card should narrow your contribution rather than claiming an entire public-sector or research programme.

How does IndieShow support a maintained GIS portfolio?

IndieShow supports a maintained GIS portfolio by giving every plug-in, map, pipeline, and archived analysis a consistent card and one stable personal route.

Update the link, description, tag, status, logo, and optional metric as hosting or licences change. Move unsupported tools to Archived instead of leaving a broken map framed as live work.

IndieShow closes the page as a clear index; QGIS listings, map hosts, repositories, papers, and approved case studies remain the sources of detailed geospatial proof.