Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`geolocate_polygon()`'s "too many polygons" doesn't always work

Open Beginner friendly
#308 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
r
Domain
data

Research direction

The check for too many polygons in geolocate_polygon() and geolocate() assumes the sf geometry column is named geometry. Read the suggested fix in pull request #306, which the issue links, then find where the polygon count check reads the column. Done when the check works for a geometry column with any name and a test covers a non-default column name.

Written by the indexing model from the issue text.

Description

bug

According to wilmund here, the current way to check for too many polygons supplied to geolocate() depends on the geometry column being named geometry. The suggested fix by wilmund is very low impact and should be pretty easy to implement.

Dominant language
R
Stars
49
Forks
5
Avg merge
1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AtlasOfLivingAustralia/galah-R

All issues in AtlasOfLivingAustralia/galah-R

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.