Rename shapely.apply to shapely.transform

[jorisvandenbossche]

xref #1276 about naming inconsistencies

Shapely uses "transform" for what is called apply for the vectorized functions (merged from pygeos). This PR renames apply() to transform().

I personally think both names are fine, so this change keeps it a bit more consistent in shapely.

(I might actually even like "transform" a bit more, as it signals more that the geometry coordinates are only transformed, keeping the exact structure. While applying a function in general could return something else as geometries. For example, in pandas, there is a more generic "apply" (that can basically return anything) vs more specific "transform" (which is guaranteed to keep the same shaped output))

[coveralls]

Pull Request Test Coverage Report for Build 2524317425

• 5 of 5 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 84.242%

---

Totals
Change from base Build 2523812064:	0.0%
Covered Lines:	2133
Relevant Lines:	2532

---

💛 - Coveralls

[mwtoews]

Yes to "transform" for this type of operation.

A new GEOS 3.11 feature is GEOSGeom_transformXY (and GEOSTransformXYCallback). This functionality has not yet made it into Shapely yet, although I can see that it would be useful optimization for "(N, 2)->(N, 2)" cases within shapely.coordinates.transform().

[brendan-ward]

+1 on the name change

[caspervdw]

The docstring should also be adjusted. And maybe also change the names all the way down to C?

[jorisvandenbossche]

Updated the docstring

[jorisvandenbossche]

And maybe also change the names all the way down to C?

The method currently only lives on the python side (the actual C funcs being called here are get_coordinates and set_coordinates, apply/transform being a python wrapper around those with calling the transform func in the middle)