> I meant with 4 instead of 1.
> postgis-raster-topology
> postgis-noraster-topology
> postgis-raster-notopology
> postgis-noraster-notopology
Regardless how you dice it, option 1 or 2 you still have the same headache
without manually copying files.
a) a PostGIS that offers all modes - postgis
"Regina Obe" writes:
The proposals are:
>>>
>>> 1) Move raster to its own extension "postgis_raster"
>>> See https://trac.osgeo.org/postgis/ticket/3888
>
>> this gets us two extensions, and if we split into N, we will have N
>> extensions.
>
> Greg I'm missing something here. If you g
Hi,
I'm trying the use the new ST_AsMVT and ST_AsMVTGeom and I'm seeing an
error that I can't figure out:
SELECT ST_AsMVTGeom(ST_Transform(geom, 3857),
TileBBox(4, 9, 4), 4096, 256, TRUE)
FROM fin_adm4 WHERE name_3='Vaasa';
-- ERROR: Operation on mixed SRID geometr
>>> The proposals are:
>>
>> 1) Move raster to its own extension "postgis_raster"
>> See https://trac.osgeo.org/postgis/ticket/3888
> this gets us two extensions, and if we split into N, we will have N
extensions.
Greg I'm missing something here. If you go with this option you still have
"Regina Obe" writes:
>> The proposals are:
>
> 1) Move raster to its own extension "postgis_raster"
> See https://trac.osgeo.org/postgis/ticket/3888
this gets us two extensions, and if we split into N, we will have N
extensions.
> 2) Provide two versions of extension "postgis"
> See
On Mon, Oct 09, 2017 at 05:24:33AM -0400, Regina Obe wrote:
> SELECT postgis_full_version();
>
> Tells you exactly what version of everything you've got. It always will
> regardless of if raster is a separate extension or not.
As of r15937 (in trunk) you now also get information about
core bein
> So you either specify what you want (including version) or the behavior
depend on how the system postgis was built.
> Is that considered acceptable behavior for users ?
Nothing has changed strk and nothing will change even by breaking out
postgis_raster.
Users have always needed to do this i
On Mon, Oct 09, 2017 at 04:39:22AM -0400, Regina Obe wrote:
> I'm more worried about folks who do
>
> ALTER EXTENSION postgis UPDATE;
>
> And forget to do
> ALTER EXTENSION postgis_raster UPDATE;
>
> And as a result get all sorts of crazy issues.
We should recommend to always run `postgis_f
On Mon, Oct 09, 2017 at 04:26:36AM -0400, Regina Obe wrote:
> Sandro wrote:
> >
> > 1) Move raster to its own extension "postgis_raster"
> > See https://trac.osgeo.org/postgis/ticket/3888
> >
> > 2) Provide two versions of extension "postgis"
> > See https://trac.osgeo.org/postgis/ticket/
> No, but it could be done. Actually, it may make sense to *always* include
> rtpostgis_upgrade in the unpackaged--current upgrade script, or it could
> still fail, no ?
Give that a try. I suspect it might fail. I don't think unpackaged is
supposed to have anything but
ALTERE EXTENSION ...
> Could you elaborate on this ? It looks to me that:
> - How do users migrate to postgis that doesn't have raster ?
> proposal 1: ALTER EXTENSION postgis UPDATE TO 'noraster'
> proposal 2: DROP EXTENSION postgis_raster
> I think proposals are crossed here
>> The proposals are:
>>
>> 1)
On Mon, Oct 09, 2017 at 01:28:22AM -0400, Regina Obe wrote:
>
> > > - How users can upgrade from older versions of postgis
> > > p1: ALTER EXTENSION postgis UPDATE; CREATE EXTENSION
> > postgis_raster FROM unpackaged;
> >
> > The problem with this is you can't install postgis_raster from
>
On Sun, Oct 08, 2017 at 11:29:33PM -0400, Regina Obe wrote:
> Sandro Santilli > writes:
>
>> The proposals are:
>>
>> 1) Move raster to its own extension "postgis_raster"
>> See https://trac.osgeo.org/postgis/ticket/3888
>>
>> 2) Provide two versions of extension "postgis"
>> See https:/
13 matches
Mail list logo
