Re: [postgis-users] Export as X3D

Thank you Olivier for your quick reply ! Can I use postgres 8.3 and the patch or unfortunately it's deprecated ? X3d and collada format is still in the roadmap or not ? Sylvain Le jeudi 03 février 2011 à 08:28 +0100, Olivier Courtin a écrit : On Feb 3, 2011, at 7:36 AM, Sylvain wrote: Hi

Re: [postgis-users] Export as X3D

Oh ! Collada format is available in Postgressql / Postgis ? If yes could you tell me which version to use for testing ? Thank you. Le jeudi 03 février 2011 à 09:22 +0100, Olivier Courtin a écrit : On Feb 3, 2011, at 9:17 AM, Sylvain wrote: Can I use postgres 8.3 and the patch or

Re: [postgis-users] Postgresql, postgis and PHP

LJ, The first chapter is a free download. We took Paolo Coriti's advice (hmm I think others suggested it to),and made the first chapter very quick paced. So it covers, geometry, geography types, how to load and how to do common spatial joins with it. You might want to check that out. It's

[postgis-users] Postgres Tuning - Actual Results

I have a long, computationally intensive query I am running on Ubuntu Linux 64bit, 8G ram PostgreSQL 9, PostGIS trunk. I have a question about memory usage and setttings.. postgresql.conf memory related settings: work_mem = 512M shared_buffers =

Re: [postgis-users] Postgres Tuning - Actual Results

Brian, * Brian Hamlin (mapl...@light42.com) wrote: I am guessing that work_mem is the wildcard that is causing the large allocations.. Comments / Suggestions on this ? Yes, work_mem is used to determine, for each sort/hash/etc, if it should be done in-memory or done on disk. If you have a

[postgis-users] Unprojected lat/long to 3081?

I have a database containing a Postgres native point data type *event* that has the latitude and longitude for certain events. An example value of * event* is *(32.7748777996749,-96.7680574022233)*. Note: this is *not* a PostGIS data type. It's a native Postgres type. I tried to convert this into

Re: [postgis-users] Unprojected lat/long to 3081?

EPSG 3081 is a metre projection, so you need to transform your points from lat long into the appropriate projection. Try something like this: *UPDATE event_table* *SET the_geom = ST_Transform(ST_SetSRID(ST_Point(event_location[1], event_location[0]), 4326), 3081) * This assumes your input

Re: [postgis-users] Unprojected lat/long to 3081?

Thank you. That was it! I did some more online reading and finally realized I'm dealing with a conversion from a spherical projection to Cartesian. Aren On Thu, Feb 3, 2011 at 7:24 PM, Francis Markham fmark...@gmail.com wrote: EPSG 3081 is a metre projection, so you need to transform your

Re: [postgis-users] ERROR: ptarray_area_spheroid: cannot handle ptarraythat crosses equator

Marcello, So you get an error about ptarray_area_spheroid. You know off hand which version of PostGIS 2.0.0 you are running. We are running a 2011-01-29 build and your queries return answers for us. Whether the answer is right is a different question. polygon |gsareageo

[postgis-users] Core dumps

We do have code dumps enabled on our developement servers and, from time to time, some PostgreSQL/PostGIS process dumps core. Could some useful feedback be provided to the developers from these dumps? Is the back trace enough, like the following: Program terminated with signal 11, Segmentation