[postgis-users] KML Export

Hi there, I made a tour on Google to look around if there exist some KML export tool. I've seen the Set_AsKML command; I've seen this dicussion; and have found that someone wrote a script for postgis; and a phyton script. But it seems that there is no easy-way-to-go export/wrapper script,

[postgis-users] FW: [pgsql-advocacy] PostGIS opportunity?

Thought PostGIS people may find this thread on pgsql-advocacy useful. http://archives.postgresql.org/pgsql-advocacy/2009-07/msg00239.php Josh et. Al -- by the way the archives look messed up on my IE 8 browser. All the thread stuff shows at the bottom. Not sure what happened. I reacall it look

Re: [postgis-users] Postgis - Line to Point distance

Peter, Whilst I think it is common practice to refer to the coordinates as Lat Lon, I would argue that in a professional system it only matters that there is clarity (I am a licensed pilot). So when using spherical coordinates people may refer to a location as North 1° East 43°, this woul

Re: [postgis-users] pg_dump of a big table

Le lundi 13 juillet 2009 à 20:51:50, Nelson Correia a écrit : > [...] > I need to do a backup from a big table that is in a machine with almost no > disk space. > > Running pg_dump from another machine needs much space on the DB host? Or it > just outputs the data as it goes? > If you do on server

[postgis-users] pg_dump of a big table

Hi all, I need to do a backup from a big table that is in a machine with almost no disk space. Running pg_dump from another machine needs much space on the DB host? Or it just outputs the data as it goes? Is there a better way to do this? Thanks, Nelson ___

Re: [postgis-users] PostGIS-PostgreSQL

Yes BUT you should never have a changeable value like street_name as the primary / foreign key. Instead you should have a street_name_lu table which has street_name_id and street_name, with street_name_id as the PK. Then all tables that FK into that will use the street_name_id which does not

Re: [postgis-users] PostGIS-PostgreSQL

Nenad Milasinovic wrote: Hello, I have some questions relating to PostGIS and PostgreSQL. I am interested how GEO-data from PostGIS are connected to data in PostgreSQL. Say that we have vector layer of all city streets in PostGIS table, with some street attributes (e.g. street name). Say also

Re: [postgis-users] PostGIS-PostgreSQL

I have a postgis dataset that is a series of fish collection trawls with the geometry fields for the endpoints and for the line between the endpoints. It seemed like the easiest way to do analysis on the endpoints separately of the line the endpoints create at the time. Two geometry colums wit

Re: [postgis-users] PostGIS-PostgreSQL

It's not the end of the world to have two geocolumns. From a practical perspective, there will be a few apps that have a harder time making sense of your tables, due to a one-spatial-column assumption. There's not a bit storage implication to storing two points instead of one. Note that, from a pe

Re: [postgis-users] PostGIS-PostgreSQL

Chris Hermansen wrote: I should have mentioned that it's not considered good practice to have more than one geometry column per table, and hence more than one geometry object per row. This makes sense if you think of rows as representational instances of real world objects. Hmmm. I'm storing t

Re: [postgis-users] PostGIS-PostgreSQL

I should have mentioned that it's not considered good practice to have more than one geometry column per table, and hence more than one geometry object per row. This makes sense if you think of rows as representational instances of real world objects. Chris Hermansenchris.herman...@timbe

Re: [postgis-users] PostGIS-PostgreSQL

All tables are the same. Spatial data is just a different type, like date or text. So you can put the street centreline geometry in the same table as the street name, assumed width, and a foreign key to the maintenance authority. There are two unusual aspects to geometry: first, there is an ind

Re: [postgis-users] PostGIS-PostgreSQL

A geometry column is only a type like integer or text for postgresql. See http://postgis.refractions.net/documentation/manual-1.3/ch04.html#id2572181 -Ursprüngliche Nachricht- Von: postgis-users-boun...@postgis.refractions.net [mailto:postgis-users-boun...@postgis.refractions.net] Im Auf

Re: [postgis-users] PostGIS-PostgreSQL

Thanks Chris, However maybe better question will be can spatial and non-spatial data be saved in one PostgreSQL table? Precisely, is it possible to have table with some spatial columns (geometry columns) and with some ordinary columns (non-spatial) and is it good practice? From your answer i can

Re: [postgis-users] PostGIS-PostgreSQL

This is a part of good database design. Street name, which can be changed, is only stored in one location. This is part of "normalization". This practice relates to any / all databases --Original Message-- From: Nenad Milasinovic Sender: postgis-users-boun...@postgis.refractions.net To:

[postgis-users] PostGIS-PostgreSQL

Hello, I have some questions relating to PostGIS and PostgreSQL. I am interested how GEO-data from PostGIS are connected to data in PostgreSQL. Say that we have vector layer of all city streets in PostGIS table, with some street attributes (e.g. street name). Say also that we have all data abou

Re: [postgis-users] WKT differs in PostGIS and Geos

On 07/11/09 18:57, Paragon Corporation wrote: > Maxime, > > ST_AsText does not produce the fidelity of the geometry. It truncates > floating points and I think where they truncate between GEOS and PostGIS is > different. GEOS and PostGIS do not share the same WKT writers. > > My question is --