James Gaboardi

#### archive `legendgram` * [x] add note to `README` * [x] ~~https://github.com/pysal/legendgram/issues/24~~ * [x] close out or transfer remaining tickets * #6 * #8 * #21 * [x] close out...

#### prepare migration notebooks * [ ] `esda` * [ ] .... * [ ] .... * [ ] `giddy` * [ ] .... * [ ] .... * [...

`pycno.py` – Unused `fieldname` argument in `extract_values()`

1

* `pycno.py` – Unused `fieldname` argument in `extract_values()` ``` ARG001 Unused function argument: `fieldname` --> tobler/pycno/pycno.py:221:49 | 221 | def extract_values(pycno_array, gdf, transform, fieldname="Estimate"): | ^^^^^^^^^ 222 | """Extract raster...

`utils.py` – Unused `buffer` argument in `_to_hex()`

1

* `utils.py` – Unused `buffer` argument in `_to_hex()` ``` ARG001 Unused function argument: `buffer` --> tobler/util/util.py:183:54 | 183 | def _to_hex(source, resolution=6, return_geoms=True, buffer=True): | ^^^^^^ 184 | """Generate a...

standard CI envs dir & naming conventions

2

* https://github.com/pysal/submodule_template/issues/45#issue-1941064101 * https://github.com/orgs/pysal/discussions/1278#discussioncomment-13567804 * https://github.com/pysal/pysal/issues/1338

@JamesSaxon How do you feel about us cutting fresh release to include in the meta release? If so, I'm thinking `v1.1.10`. Thoughts?

2 kwargs unused in 3 functions - `fca.py`

1

Two keyword arguments not actually being used in three functions in `fca.py`. * keyword arguments * `supply_index="geoid"` * `normalize=False` * functions * `fca_ratio()` * `two_stage_fca()` * `three_stage_fca()` see #78

2 notebooks seem to not be functional (at least locally for me) * [`notebooks/How to Subset the Travel Cost Matricies.ipynb`](https://github.com/pysal/access/blob/main/notebooks/How%20to%20Subset%20the%20Travel%20Cost%20Matricies.ipynb) * [`notebooks/How to Read, Filter, and Convert Shapefiles to .geojson.ipynb`](https://github.com/pysal/access/blob/main/notebooks/How%20to%20Read%2C%20Filter%2C%20and%20Convert%20Shapefiles%20to%20.geojson.ipynb)

catch specific errors rather than bare exceptions

1

* catch specific errors rather than bare exceptions * for example [these 3](https://github.com/pysal/access/blob/29b043610c366873d4762b9a64aede2b24cfa0bb/access/raam.py#L181-L204) for declaring `travel_np`, `supply_np`, and `demand_np` – kind of error is expected to be raised here? *...

* Update PyPI release for trusted publishing * needs [proper workflow name listed in PyPI + proper permissions](https://github.com/pysal/access/issues/94#issuecomment-3647268519) * needs proper permissions/tokens in action itself – e.g., [here in `access`](https://github.com/pysal/access/blob/541de01eb01c36d4a3b3af4808dcc4c456488303/.github/workflows/upload_package.yml#L20-L22)...