Regina Obe

If people are interested I'm willing to tackle adding view support to this function and suspect it is a fairly trivial change. The only question is whether to backport that...

I was thinking of isolating the view change to just pgr_nodeNetwork, but then it occurred to me that it doesn't make much sense for _pgr_getTableName to just look at tables...

Another thought have the _pgr_getTableName also return the table_type so a function can decide whether to use it or not if it absolutely needs to work on a real table.

Probably not worth the effort. The reason PostGIS does that is to satisfy SQL/MM convention (and then we said might as well make all our functions that way even if...

@JamesMilnerUK I'm wondering if you have multiple versions of PostgreSQL and brew installed into a different location. I thought brew installed PostgreSQL in something like Cellar, which doesn't seem to...

Haven't read thru the thread - but I'd go with name pgr_pickupDelivery. Definitely something with pgr in it, since they all float together and you know it's a pgRouting function....

The function is ST_3DDistance :)

I don't see a pgr_findClosestEdge function. I see a .pgr_pointToEdgeNode.

This is still a problem. All the above issues. In addition, pgRouting 2.5 has paths wrong to static content and build environment assumes the build folder is a subfolder of...

Just a heads up. In PostGIS 3.3.0 ST_ConcaveHull is being done to use GEOS functionality. This new version will be exposed for those running GEOS 3.11+ (not out yet). postgis_sfcgal...