Opened 11 years ago

Closed 6 years ago

#2752 closed defect (fixed)

raster && geometry, @ and ~ are undocumented

Reported by: strk Owned by: robe
Priority: medium Milestone: PostGIS 2.5.0
Component: documentation Version: 2.1.x
Keywords: Cc:

Description

The "raster && geometry" operator(s) are undocumented here: ​http://postgis.net/docs/RT_Raster_Intersect.html

And have no availability info in the sql source

When were they introduced ?

Change History (14)

comment:1 by strk, 11 years ago

r9372 seems to be the introducing commit, referencing ticket #1635

comment:2 by strk, 11 years ago

r12599 added availability information in the sql source for && and ~ — but I found we also have @@ which is stil undocumented and was added by r12107 for #2532

comment:3 by strk, 11 years ago

r12600 adds info about raster @ geometry and back + support functions.

Documentation still missing. Can you take care of that, Regina ? I dunno what's the correct way to do that (ie: NOTE ? More signatures ? It's already automatic ?)

comment:4 by strk, 11 years ago

r12601 forward-ports availability info to trunk

comment:5 by robe, 11 years ago

okay will take care of it later.

comment:6 by robe, 11 years ago

Component: raster → documentation
Owner: changed from dustymugs to robe
Summary: raster && geometry is undocumented → raster && geometry, @@ and ~ are undocumented

Done for trunk at r12603 (&&) Guess I still need to do for raster @ geometry. Will close once I backport to 2.1 and 2.0.

comment:7 by robe, 11 years ago

Summary: raster && geometry, @@ and ~ are undocumented → raster && geometry, @ and ~ are undocumented

comment:8 by robe, 11 years ago

Milestone: PostGIS 2.1.4 → PostGIS 2.0.7

Hey I just noticed you have in availability that geometry @ raster was introduced in 2.0.5. We technically should not be doing introducing new functions/operators in micro. Who did this? Guess its too late to roll back that change.

comment:9 by strk, 11 years ago

We probably had your blessing. Was technically a bug IIRC, read previous comments in this ticket,they should have all referencesto all revisions and tickets that brought to that conclusion.

comment:10 by pramsey, 9 years ago

Milestone: PostGIS 2.0.7 → PostGIS 2.0.8

comment:11 by pramsey, 7 years ago

Milestone: PostGIS 2.0.8 → PostGIS 2.2.6

comment:12 by pramsey, 7 years ago

Milestone: PostGIS 2.2.6 → PostGIS 2.2.7

comment:13 by robe, 7 years ago

Milestone: PostGIS 2.2.7 → PostGIS 2.5.0

comment:14 by komzpa, 6 years ago

Resolution: → fixed
Status: new → closed

2.0, 2.1 are EOL'd, so all supported versions got this fixed.

Note: See TracTickets for help on using tickets.