Paul Ramsey | 1 Jul 07:01 2006
Picon

1.1.3 Release

As heard on postgis-devel, 1.1.3 is now available.  Downloads from <http://postgis.refractions.net/download/>

The 1.1.3 release includes numerous bug fixes and some new functionality. This release includes standard support for long transactions, which should be useful for a number of client applications.
  • NEW Long Transactions support.
  • Can run the regress tests with 'make check' now.
  • New regress test support for loader/dumper.
  • BUGFIX in pgsql2shp successful return code.
  • BUGFIX in shp2pgsql handling of MultiLine WKT.
  • BUGFIX in affine() failing to update bounding box.
  • WKT parser: forbidden construction of multigeometries with EMPTY elements (still supported for GEOMETRYCOLLECTION).
  • Added --with-proj-libdir and --with-geos-libdir configure switches.
  • JDBC:
    • Improved regression tests: MultiPoint and scientific ordinates
    • Fixed some minor bugs in jdbc code
    • Added proper accessor functions for all fields in preparation of making those fields private later
  • Support for build Tru64 build.
  • Use Jade for generating documentation.
  • NEW DumpRings() function.
  • BUGFIX in distance(poly,poly) giving wrong results.
  • NEW AsHEXEWKB(geom, XDR|NDR) function.
  • Don't link pgsql2shp to more libs then required.
  • Initial support for PostgreSQL 8.2.


_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
Stefano B. | 3 Jul 09:09 2006
Picon

1.1.3 compilation problem

Hi, when I compile postgis 1.1.3 on my freebsd 5.3 os I get the following:
 
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether ln -s works... yes
checking for iconv_open in -liconv... no
checking for libiconv_open in -liconv... no
checking for iconv_open in -lc... no
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking iconv.h usability... no
checking iconv.h presence... no
checking for iconv.h... no
checking build system type... i386-unknown-freebsd5.3
checking host system type... i386-unknown-freebsd5.3
checking for geos-config... /usr/local/bin/geos-config
checking for proj... /usr/local/bin/proj
checking for flex... /usr/bin/flex
checking for dllwrap... no
checking for dlltool... no
checking for bison... bison -y
checking for perl... /usr/bin/perl
checking for xsltproc... no
checking for pdfxmltex... no
checking for db2pdf... no
checking for jw... no
checking which template to use... freebsd
configure: creating ./config.status
config.status: creating Makefile.config
config.status: creating config.h
config.status: config.h is unchanged
 
 SUMMARY
 -------------------------------------------------------
 
 HOST_OS: freebsd5.3
 
   PGSQL: /usr/local/pgsql8.1/bin/pg_config
    GEOS: /usr/local/bin/geos-config (with C-API)
          (ldflags: -L/usr/local/lib)
    PROJ: prefix=/usr/local libdir=/usr/local/lib
   ICONV: 0
 
 PORTNAME: freebsd
   PREFIX: /usr/local/pgsql8.1
  EPREFIX: ${prefix}
      DOC: /usr/local/pgsql8.1/doc/contrib
     DATA: /usr/local/pgsql8.1/share/contrib
      MAN: /usr/local/pgsql8.1/man
      BIN: /usr/local/pgsql8.1/bin
      EXT: /usr/local/pgsql8.1/lib (\$$libdir)
 -------------------------------------------------------
 
gmake -C lwgeom
gmake[1]: Entering directory `/usr/src/smit/postgis-1.1.3/lwgeom'
bison -y -vd -p lwg_parse_yy wktparse.y
wktparse.y:40.14: parse error, unexpected ":", expecting ";" or "|"
wktparse.y:58.20-32: $3 of `geometry' has no declared type
wktparse.y:61.6-19: $1 of `geometry' has no declared type
wktparse.y:145.17: parse error, unexpected ":", expecting ";" or "|"
wktparse.y:232.14-31: $1 of `geom_multilinestring' has no declared type
wktparse.y:232.14-34: $2 of `geom_multilinestring' has no declared type
wktparse.y:235.20-37: $1 of `geom_multilinestring' has no declared type
wktparse.y:235.20-40: $2 of `geom_multilinestring' has no declared type
wktparse.y:235.20-43: $3 of `geom_multilinestring' has no declared type
wktparse.y:238.26-43: $1 of `geom_multilinestring' has no declared type
wktparse.y:238.26-46: $2 of `geom_multilinestring' has no declared type
wktparse.y:238.26-49: $3 of `geom_multilinestring' has no declared type
wktparse.y:238.26-52: $4 of `geom_multilinestring' has no declared type
gmake[1]: *** [wktparse.tab.c] Error 1
gmake[1]: Leaving directory `/usr/src/smit/postgis-1.1.3/lwgeom'
gmake: *** [liblwgeom] Error 2
gmake -C lwgeom
gmake[1]: Entering directory `/usr/src/smit/postgis-1.1.3/lwgeom'
bison -y -vd -p lwg_parse_yy wktparse.y
wktparse.y:40.14: parse error, unexpected ":", expecting ";" or "|"
wktparse.y:58.20-32: $3 of `geometry' has no declared type
wktparse.y:61.6-19: $1 of `geometry' has no declared type
wktparse.y:145.17: parse error, unexpected ":", expecting ";" or "|"
wktparse.y:232.14-31: $1 of `geom_multilinestring' has no declared type
wktparse.y:232.14-34: $2 of `geom_multilinestring' has no declared type
wktparse.y:235.20-37: $1 of `geom_multilinestring' has no declared type
wktparse.y:235.20-40: $2 of `geom_multilinestring' has no declared type
wktparse.y:235.20-43: $3 of `geom_multilinestring' has no declared type
wktparse.y:238.26-43: $1 of `geom_multilinestring' has no declared type
wktparse.y:238.26-46: $2 of `geom_multilinestring' has no declared type
wktparse.y:238.26-49: $3 of `geom_multilinestring' has no declared type
wktparse.y:238.26-52: $4 of `geom_multilinestring' has no declared type
gmake[1]: *** [wktparse.tab.c] Error 1
gmake[1]: Leaving directory `/usr/src/smit/postgis-1.1.3/lwgeom'
gmake: *** [liblwgeom] Error 2
 
I have compiled with:
./configure --with-pgsql=/usr/local/pgsql8.1/bin/pg_config --with-geos --with-proj
gmake
thanks in advance
Stefano
_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
Düster Horst | 3 Jul 11:24 2006
Picon

AW: Linear Referencing: Create Measure

Hallo strk

Thak you very much for your response. The required function should measure
lines or multilines. For instance I need to measure a river network. The
measures of the rivers are implicit predefined during the creation process
of the river networkdata and don't represent the real world in all cases.
The predefinition bases on the two attributes "from" and "to" measure. The
"from" value represents the lowest measure value and the "to" value highest
measure value of any linestring in case of our rivernetwork. The units of
our predefined measures is km and the datatype is float8.  
The work to do is to interpolate the measure of every vertex point of any
linestring/multilinestring with respect to "from" and "to". With this
approach it is also possible to create measures in percent of linelength.
You have to set from=0 and to=100.

A second case could be to calculate the measures based on the length of the
relevant linestring from zero to length. Therefore you don't need to
predefine from and to.

In both cases you have to differ between linestrings and multilinestrings.
In case of continuous linestrings you can interpolate over the whole line.
In case of multilinestrings you have to consider possible gaps in the
multilinestring. I'll attach the code of a former version of Christoph
Spoerri's lrs_create_measure. Unfortunately the lrs_create_measures
functions don't work correct yet.  

I think the function call could be:
line_create_measure(geometry,[float8],[float8])

line_create_measure(wkb_geometry,from,to) or
line_create_measure(wkb_geometry,0,1) would solve the first case
line_create_measure(wkb_geometry) would solve the second case.

I hope this will be a base for a further discussion.

With best regards
 
Dr. Horst Düster 
GIS-Koordinator, Stv. Amtschef

Kanton Solothurn 
Amt für Geoinformation
Abteilung SO!GIS® Koordination
Rötistrasse 4
CH-4501 Solothurn 

Tel.: ++41 (0)32 627 25 32 
Fax: ++41 (0)32 627 22 14

horst.duester <at> bd.so.ch 
www.sogis.so.ch

> -----Ursprüngliche Nachricht-----
> Von: strk <at> refractions.net [mailto:strk <at> refractions.net]
> Gesendet am: Donnerstag, 29. Juni 2006 23:57
> An: 'postgis-users <at> postgis.refractions.net'
> Betreff: Re: [postgis-users] Linear Referencing: Create Measure
> 
> Maybe we can add such a function, but semantics must be exactly
> defined. How are 'from' and 'to' defined ? How are they applied
> to different types of geometries ?
> 
> --strk;
> 
> On Thu, Jun 29, 2006 at 11:43:44AM +0100, Düster Horst wrote:
> > I'm faced with the problem to create MGeometries for using 
> with the "Linear
> > Referencing" functions of PostGIS. I like to create the 
> measures defined by
> > two table attributes meas_from and meas_to. In further 
> versions of Christoph
> > Spoerri's LRS functions there exists a function
> > lrs_create_measure(geometry,from,to). As the result the 
> M-Values were
> > interpolated based on a start and a stop value of each line. The new
> > functions don't offer such a functionality. I would be 
> greatful for any hint
> > how to create measures along a line referenced by a from 
> and a to value of
> > this line.
> _______________________________________________
> postgis-users mailing list
> postgis-users <at> postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
> 

Attachment (lwgeom_functions_lrs.c): application/octet-stream, 46 KiB
_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
Mark Cave-Ayland | 3 Jul 12:47 2006
Picon

RE: 1.1.3 compilation problem

> From: postgis-users-bounces <at> postgis.refractions.net [mailto:postgis-users-
bounces <at> postgis.refractions.net] On Behalf Of Stefano B.
> Sent: 03 July 2006 08:09
> To: PostGIS Users Discussion
> Subject: [postgis-users] 1.1.3 compilation problem
>
> Hi, when I compile postgis 1.1.3 on my freebsd 5.3 os I get the following:
 
(cut)
 
> gmake -C lwgeom
> gmake[1]: Entering directory `/usr/src/smit/postgis-1.1.3/lwgeom'
> bison -y -vd -p lwg_parse_yy wktparse.y
> wktparse.y:40.14: parse error, unexpected ":", expecting ";" or "|"
> wktparse.y:58.20-32: $3 of `geometry' has no declared type
> wktparse.y:61.6-19: $1 of `geometry' has no declared type
> wktparse.y:145.17: parse error, unexpected ":", expecting ";" or "|"
> wktparse.y:232.14-31: $1 of `geom_multilinestring' has no declared type
> wktparse.y:232.14-34: $2 of `geom_multilinestring' has no declared type
> wktparse.y:235.20-37: $1 of `geom_multilinestring' has no declared type
> wktparse.y:235.20-40: $2 of `geom_multilinestring' has no declared type
> wktparse.y:235.20-43: $3 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-43: $1 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-46: $2 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-49: $3 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-52: $4 of `geom_multilinestring' has no declared type
> gmake[1]: *** [wktparse.tab.c] Error 1
> gmake[1]: Leaving directory `/usr/src/smit/postgis-1.1.3/lwgeom'
> gmake: *** [liblwgeom] Error 2
> gmake -C lwgeom
> gmake[1]: Entering directory `/usr/src/smit/postgis-1.1.3/lwgeom'
> bison -y -vd -p lwg_parse_yy wktparse.y
> wktparse.y:40.14: parse error, unexpected ":", expecting ";" or "|"
> wktparse.y:58.20-32: $3 of `geometry' has no declared type
> wktparse.y:61.6-19: $1 of `geometry' has no declared type
> wktparse.y:145.17: parse error, unexpected ":", expecting ";" or "|"
> wktparse.y:232.14-31: $1 of `geom_multilinestring' has no declared type
> wktparse.y:232.14-34: $2 of `geom_multilinestring' has no declared type
> wktparse.y:235.20-37: $1 of `geom_multilinestring' has no declared type
> wktparse.y:235.20-40: $2 of `geom_multilinestring' has no declared type
> wktparse.y:235.20-43: $3 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-43: $1 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-46: $2 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-49: $3 of `geom_multilinestring' has no declared type
> wktparse.y:238.26-52: $4 of `geom_multilinestring' has no declared type
> gmake[1]: *** [wktparse.tab.c] Error 1
> gmake[1]: Leaving directory `/usr/src/smit/postgis-1.1.3/lwgeom'
> gmake: *** [liblwgeom] Error 2
 

Hi Stefano,

If you haven't altered any of the bison grammar files, then it could be that
you're using a broken version of Bison - I know the PostgreSQL team often
experience problems with Bison versions > 1.875, which is the version I'm
using here without any issues.

What is more interesting is that even though we include
lex.yy.c/wktparse.tab.c in the release tarballs, under Win32 it seems to
want to always rebuild these files from the .yy source files if flex/bison
are found during the configure phase, instead of noticing that the supplied
files haven't been changed and using them as they are. Does anyone else see
this behaviour?

Kind regards,

Mark.

------------------------
WebBased Ltd
17 Research Way
Plymouth
PL6 8BT

T: +44 (0)1752 797131
F: +44 (0)1752 791023

http://www.webbased.co.uk   
http://www.infomapper.com
http://www.swtc.co.uk  

This email and any attachments are confidential to the intended recipient
and may also be privileged. If you are not the intended recipient please
delete it from your system and notify the sender. You should not copy it or
use it for any purpose nor disclose or distribute its contents to any other
person.
Warren Noll | 3 Jul 16:23 2006

Raster images

I’m new to PostGIS.  We are using it to access our GIS data, but don’t know for sure the best way to handle raster images.  Any suggestions?

 

Warren Noll

21st Century Systems, Inc.

199 East 4th Street, Suite B

University of Missouri TechnologyPark, Building 2081

Fort LeonardWood, MO65473

573-329-8526 ext. 2165

573-329-8509 (Fax)

WARREN.NOLL <at> 21CSI.COM  WWW.21CSI.COM

 

 

 

********************************************************************

  This electronic mail transmission contains confidential

  information intended only for the person(s) named.

  Any use, distribution, copying or disclosure by another

  person is strictly prohibited.

********************************************************************

 

 



_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
Stephen Woodbridge | 3 Jul 17:09 2006

Re: Raster images

Hi Warren,

There has been a lot of discussion about rasters on the list and the 
dev-list so you might want to read some of that. But I will summarize in 
really short form and leave it to others that chime in if I have it 
wrong ot there are other options.

Today, I think your best bet it to keep the raster data as files but to 
use postgres/postgis to the manage you raster colection. So you might 
include metadata, transform info, size, path to the file on disk, you 
might also want to create polygon or bbox representations of each raster 
file so you can use spatial search against these and other data you have 
in postgis.

If you are working with mapserver, I would read the mapserver archive 
for posts by Ed McNierney on rasters. He runs Topozone.com and they have 
nearly a million rasters online that require ablut 20TB of disk space.

Hope that helps,
   -Steve W

Warren Noll wrote:
> I’m new to PostGIS.  We are using it to access our GIS data, but don’t 
> know for sure the best way to handle raster images.  Any suggestions?
> 
>  
> 
> Warren Noll
> 
> **/21st Century Systems, Inc./**
> 
> //199 East 4th Street////, Suite B//
> 
> //University of Missouri Technology Park, Building 2081//
> 
> //Fort//// Leonard Wood, MO 65473//
> 
> //573-329-8526 ext. 2165//
> 
> //573-329-8509 (Fax)//
> 
> WARREN.NOLL <at> 21CSI.COM <mailto:WARREN.NOLL <at> 21CSI.COM>  WWW.21CSI.COM 
> <http://www.21CSI.COM>
> 
>  
> 
>  
> 
>  
> 
> ********************************************************************
> 
>   This electronic mail transmission contains confidential
> 
>   information intended only for the person(s) named.
> 
>   Any use, distribution, copying or disclosure by another
> 
>   person is strictly prohibited.
> 
> ********************************************************************
> 
>  
> 
>  
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users <at> postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
Warren Noll | 3 Jul 17:11 2006

bring PostGIS into the raster world

What is the best way to handle raster images when using PostGIS?  Is it possible to store the location of the raster and have that returned by the query and then let the viewer retrieve the image based upon the gml or something.

 

I’m new to this stuff, so sorry if this is a strange way to handle rasters.

 

Warren Noll

21st Century Systems, Inc.

199 East 4th Street, Suite B

University of Missouri TechnologyPark, Building 2081

Fort LeonardWood, MO65473

573-329-8526 ext. 2165

573-329-8509 (Fax)

WARREN.NOLL <at> 21CSI.COM  WWW.21CSI.COM

 

 

 

********************************************************************

  This electronic mail transmission contains confidential

  information intended only for the person(s) named.

  Any use, distribution, copying or disclosure by another

  person is strictly prohibited.

********************************************************************

 

 



_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
marco vieira | 3 Jul 22:20 2006
Picon

Fwd: [grafar_rs] FW: Primeiras páginas dos jornais de todo o mundo



---------- Forwarded message ----------
From: Santiago <rebbes <at> terra.com.br>
Date: 03/07/2006 10:41
Subject: [grafar_rs] FW: Primeiras páginas dos jornais de todo o mundo
To: grafar <grafar_rs <at> yahoogrupos.com.br>


----------
From: César Dias <cesar515 <at> terra.com.br>
Date: Sun, 2 Jul 2006 21:16:48 -0300
To: <Undisclosed-Recipient:;>
Subject: Primeiras páginas dos jornais de todo o mundo



Primeiras páginas dos jornais de todo o Mundo:
As primeiras páginas dos jornais de hoje, do Brasil e do mundo.
Cada bolinha laranja nos mapas dos continentes, são jornais de cidades daquele estado, ou País, todo dia tem a 1ª página de cada jornal.

Ao posicionar sobre a bolinha desejada, ao lado, aparece a 1ª página dos jornais, e clicando sobre a bolinha, você tem a página em tamanho maior, para facilitar a visualização e o link para ver a edição no site do mesmo.

Uma viagem ao mundo inteiro dos jornais.
http://www.newseum.org/todaysfrontpages/flash/

 



__._,_.___

Yahoo! Grupos, um serviço oferecido por:
PUBLICIDADE

Links do Yahoo! Grupos
__,_._,___


--
Marco Vieira
+55 21 9499-6800
e-mail: maovieira <at> gmail.com
_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
Gregory S. Williamson | 4 Jul 00:35 2006

RE: bring PostGIS into the raster world

As Steven Woodbridge pointed out in an earlier post, storing the raster images on disk and referring to them
in postGIS is certainly a way to go.

One reason to put images into the database is if the data is somewhat volatile and you need to endure
transactional integrity; that's harder to do when some of the data is in a regular file system. A drawback
can be the overhead of processing the data in/out of postgres, depending on how much of it there is and how it
is stored. I've done systems in the past where we stored TIFF images in blobs in a database; we were able to
tune the blob size to handle the TIFFs so disk access was quite efficient. 

That said, we at GX put our imagery on disks (ok, usually an image and a backup on a second storage device); the
database has the metadata about who owns the thing and what it is, the spatial coordinates, the primary and
secondary locations and so on. We have some scripts that we use to move the actual files and maintain sync
with the database. We're moving toward putting frequently used imagery on faster devices and migrating
the lesser used data to slower cheaper storage; hard to do that with everything in one database.

HTH,

Greg Williamson
DBA
GlobeXplorer LLC

-----Original Message-----
From:	postgis-users-bounces <at> postgis.refractions.net on behalf of Warren Noll
Sent:	Mon 7/3/2006 8:11 AM
To:	postgis-users <at> postgis.refractions.net
Cc:	
Subject:	[postgis-users] bring PostGIS into the raster world

What is the best way to handle raster images when using PostGIS?  Is it
possible to store the location of the raster and have that returned by the
query and then let the viewer retrieve the image based upon the gml or
something.

I'm new to this stuff, so sorry if this is a strange way to handle rasters.

Warren Noll

21st Century Systems, Inc.

199 East 4th Street, Suite B

University of Missouri Technology Park, Building 2081

Fort Leonard Wood, MO 65473

573-329-8526 ext. 2165

573-329-8509 (Fax)

WARREN.NOLL <at> 21CSI.COM   <http://www.21CSI.COM> WWW.21CSI.COM

********************************************************************

  This electronic mail transmission contains confidential

  information intended only for the person(s) named.

  Any use, distribution, copying or disclosure by another

  person is strictly prohibited.

********************************************************************


!DSPAM:44a933c1149656491211187!

_______________________________________________
postgis-users mailing list
postgis-users <at> postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
snacktime | 4 Jul 04:25 2006
Picon

Newbie questions on what geometry to use

I need a geometry to store latitude/longitude of street addresses.  I
will be using the points to do queries against the google map api.
I'm a bit confused about what SRID to use and want to make sure I'm
choosing the right geometry.

This is what I'm using now to define the table and geometry column:

CREATE TABLE addresses_geom ( id int4, address varchar(25) );
SELECT AddGeometryColumn( 'addresses_geom', 'geom', 4326, 'POINT', 2);

Does that look correct?  It seems to work, but I have yet to create
the real queries I will need. Which brings up another question. I need
a query or set of calculations to get all the points within an X mile
radius.  I haven't been able to really find any concrete examples on
how to go about this.  I could query all the points in the database
using distance_sphere.  The database has just under a million points,
and the search could be narrowed by only searching within a state.
Any guesses on how efficient that type of query would be?

Chris

Chris

Gmane