Should we add a tools section?
Some things that come to mind are:

• Erase (ArcGIS) -> Difference (QGIS)
• Create Multipart -> Dissolve (kind of... with selections -- very important if uploading to ESF)

There are probably others but I don't know them all.

This issue is a kind reminder that your repository has been inactive for 181 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

The QGIS layer library full file path is not listed in gis-pantry/docs/getting-started-with-QGIS/doc/data.md and some people have different W: drive locations. This could cause some confusion for people that don't already know the full path to the layer library and have a different drive mapped to W:

Add meta to the root README.md to make the contents more searchable.

In the Editing section the "Topological Editing" section is duplicated at the bottom.
Also, there should be a hyperlinked table of contents to skip down to different sections of the page.

I think the location of the coding standards doc should be moved to a more obvious location. currently, it is in Docs/GIS pantry intro docs/Template/References

A good place may be just in GIS pantry intro docs.

The home link doesn't work in this page

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

There is a point for 'symbolizing your layers' but there is no section for that (only advanced symbology)
Maybe we should link to https://docs.qgis.org/3.16/en/docs/training_manual/basic_map/symbology.html

The "Home" links at the top of each page of the QGIS documentation are broken.

Would be good to link to SLYR md from the Adding Layer Library data section of this page

Would this be an appropriate addition to the pantry? It doesn't really need its own repo.
https://github.com/smnorris/bcelev

Edits for the "Adding and Working with data" page:

• Oracle Image is broken in the "Adding Oracle data via browser panel" and "Adding Oracle data via DB manager" sections
• "Virtual Oracle SQL Layer" image is broken in the "Add Oracle data via DB manger" section
• "Create New Vector Layers" section: Add some text to make it more descriptive instead of just a link to QGIS documentation: "See the QGIS Documentation link for directions on creating new vector layers in various formats (Geopackage, Shapefile, SQLite, etc).

Python-console-icon image has a broken link and does not display

https://github.com/bcgov/gis-pantry/blob/master/recipes/bcelev/get_terraintiles.py can be replaced by a terraincache command

eg, from terraincache README
https://github.com/smnorris/terraincache

terraincache \
  --bounds "336637.5, 1597112.5, 346637.5, 1607112.5" \
  --bounds-crs EPSG:3005 \
  --zoom 11 \
  -tr 25 \
  -r bilinear \
  -o dem.tif

Add raster section to advanced symbology

can we have a template to show users what's expected for submissions to the three folders? or a template for each folder?

The Expressions & Filter Queries section needs some a table of contents at the top - hyperlinks to lead you to each sub-section

Index link for raster calculator tool doesn't work/is broken

The Geopackage and other data formats page:

• some images are broken
• Should be linked from the home page or other section (I don't think it currently is)

broken page

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Perhaps this section:
https://github.com/bcgov/gis-pantry/blob/master/docs/getting-started-with-QGIS/doc/setup-best-practice.md

Service URL: https://tiles.arcgis.com/tiles/ubm4tcTYICKBpist/arcgis/rest/services/BC_BASEMAP/VectorTileServer
Style URL: https://www.arcgis.com/sharing/rest/content/items/b1624fea73bd46c681fab55be53d96ae/resources/styles/root.json?f=pjson
Min Zoom: 0
Max Zoom: 16

Editing vector data is in the index twice as list number 8 (not working) and 17 (working). As are list items 9-16.

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Create a documentation guideline/style guidance
Common gif sizes

L = 900x650
M
S