Opened 13 years ago

Closed 13 years ago

#587 closed task (fixed)

[raster] SVN copy wkt raster code to PostGIS trunk

Reported by: pracine Owned by: jorgearevalo
Priority: critical Milestone: PostGIS 2.0.0
Component: raster Version: master
Keywords: Cc:

Description (last modified by pracine)

-SVN copy to keep the history

-Remove or merge old PostGIS files used by WKT Raster

-Remove any reference to "WKT". WKT Raster is now merely the PostGIS RASTER type.

-Make sure everything compile, make check and make post-install-check

Change History (12)

comment:1 by pracine, 13 years ago

Description: modified (diff)

comment:2 by jorgearevalo, 13 years ago

I suggest the following steps:
1.- Checkout the PostGIS sources from trunk
2.- Create a new folder named "raster" in the working copy
3.- SVN copy the contents of the /spike/wktraster folder to the new raster folder
4.- Modify autogen.sh, configure.ac and install.sh from working copy for adding the new raster options
5.- Other stuff I'm missing?

comment:3 by pracine, 13 years ago

Then you must add a line in the general postgis makefile to build the raster stuff.

It would also be great if you could, by the way, move all the .py files from the "script" folder to a "python" subfolder.

comment:4 by pracine, 13 years ago

Summary: [wktraster] SVN copy wkt raster code to PostGIS trunk[raster] SVN copy wkt raster code to PostGIS trunk

comment:5 by jorgearevalo, 13 years ago

Status: newassigned

comment:6 by jorgearevalo, 13 years ago

Do I have to merge PostGIS "configure.ac" with WKT Raster "configure.ac"? That's: is WKT Raster going to be compiled by default when compiling PostGIS?

  • If yes: I should merge both configure.ac scripts. Pay attention to the fact WKT Raster needs GDAL, and this can't be a constraint for normal PostGIS compiling.
  • If not: The user must execute "./configure & make & make install" both, in general PostGIS folder and in "raster" folder inside PostGIS one.

comment:7 by pracine, 13 years ago

What was decided was that PostGIS Raster will be compiled with PostGIS unconditionnaly. Even if this imply compiling GDAL. You could send a warning mail prior committing this change just to make sure people are ready…

comment:8 by jorgearevalo, 13 years ago

Ok, I was thinking about a "—with-raster" option (or a "—without-raster"). But I'll send a mail before committing the change.

comment:9 by robe, 13 years ago

I think having a —with-raster option would be best starting off. Eventually we'll take it out before final release. But it will allow people to continue testing PostGIS until they get the additional dependencies in order for rasteer. Besides we have to update the help to include that.

I suspect Kevin doesn't have hudson prepared to compile with GDAL yet, so if you make compiling with raster a requirement off the bat, it will send false warnings and break the Hudson build (which will break documentation build and tar ball generation for the PostGIS site).

comment:10 by mcayland, 13 years ago

+1. Let's have a —with-raster option to start with, and then we can switch the default when everything is bedded in.

comment:11 by pracine, 13 years ago

+1

comment:12 by jorgearevalo, 13 years ago

Resolution: fixed
Status: assignedclosed

Ticket closed. The raster code is now in trunk.

Note: See TracTickets for help on using tickets.