Thanks a million chris
I had in mind a more suitable place for other questions of this type, i.e.
general gis questions rather than special postgis questions
Anyway, your kind help was so useful for me
Best Regards.
From: Chris Hermansen
To: PostGIS Users Di
You have no join condition between your two tables, so the resultant
table is going to be the cartesian product of the two tables
(nrows(table1) * nrows(table2)). If the tables are big enough, that
alone can take a very long time.
P.
On Thu, Jun 23, 2011 at 5:36 PM, Conor Henley wrote:
> Hi all,
Hi all,
I'm encountering an incredibly slow run time when I attempt to create a
new table (CREATE TABLE AS) with fields populated by calculations which
reference two other tables. Does referencing multiple tables in a
calculation like this usually result in a slower run time?
Here is a por
Good news. Yeah, the folks who wrote those NN articles recently published
the only PostGIS book - "PostGIS in Action", which you'll want if you are
just getting into it and plan to use it a lot.
Mark
On Thu, Jun 23, 2011 at 8:14 PM, Sheara Cohen wrote:
> I figured it all out. Thanks for your he
I figured it all out. Thanks for your help. And Mark, your links were
awesome!
Sheara Cohen
Planner
C A L T H O R P E A S S O C I A T E S
2095 ROSE STREET, SUITE 201, BERKELEY, CALIFORNIA, 94709 USA
___
postgis-users mailing list
postgis-users@p
Figure out where your libproj.so file is installed (probably /usr/local/lib)
and add that directory to /etc/ld.so.conf and run ldconfig. Best guess.
P.
On Thu, Jun 23, 2011 at 12:25 PM, Chris Seker wrote:
> Hi all. I am running PostgreSQL 9.1 and PostGIS2.0 under CENTOS. After
> install, the
Hi Frans,
On 24 June 2011 02:56, Frans Knibbe wrote:
> About the order of coordinates: I see that PostGIS uses EPSG as the
> authority that defines coordinate reference systems. If you look up the
> definition of EPSG:4326 (for example at http://www.epsg-registry.org/, use
> 'retrieve by code'),
Hello Chris,
Actually, I was wrong in stating that one degree of latitude equals
1852 meters. That should have been a minute (on sixtieth of a
degree).
I agree that it is not good to start rounding coordinates or other
intermediate values when performing
Hi all. I am running PostgreSQL 9.1 and PostGIS2.0 under CENTOS. After
install, the server worked fine and we spent about 2 weeks building databases,
etc. Then after some routine hardware maintenance and re-boot, we get the
following error.
Top of Form
SQL select * from "oxbuildings2" limit
Hey all and Mark -
Mark, thanks again for your suggestions. I am having trouble making it
work, and I'm wondering if you or anyone else has any suggested fixes to
any of the following scripts. These were my various failed attempts:
Take One:
[WARNING ] CREATE TABLE
public.census_bg_near_i
Frans,
You think of your input coordinates as accurate to the nearest meter. Well
perhaps :-) But anyway, the output of the transformation is as accurate as
possible a representation of your input coordinates in the new coordinate
system. That is, the transformation contains multiplication, div
Hi Mike,
Thanks for your response.
About the order of coordinates: I see that PostGIS uses EPSG as the
authority that defines coordinate reference systems. If you look up the
definition of EPSG:4326 (for example at http://www.epsg-registry.org/,
use 'retrieve by code'), you can see that it ex
Hello Mike,
there are 2 standards PostGIS and most other software use the
http://en.wikipedia.org/wiki/Right_hand_rule.
In surveying only the "left hand rule" is the truth.
Gr
Ralf
Am Donnerstag 23 Juni 2011, 16:05:18 schrieb Mike Toews:
> On 24 June 2011 01:19, Frans Knibbe wrote:
> > POINT(
On 24 June 2011 01:19, Frans Knibbe wrote:
> POINT(6.86264236062518 53.3160795502069)
> There are two things wrong with this result:
> 1) The coordinates are in the wrong order (EPSG:4326 uses latitude,
> longitude).
They are in the correct order. Standards say "X, Y" which are "long,
lat". This
Hello all,
I am having some problems with the output of ST_Transform. To illustrate
the problem, I have a point in the EPSG:28992 SRS:
POINT(253328 593188)
I want to transform it to WGS84 (EPSG:4326). This is the output of
ST_Transform:
POINT(6.86264236062518 53.3160795502069)
There are t
15 matches
Mail list logo