| 02:36:13 | hauxon: | Hi, does anyone know if I can use the PostGIS 1.3.6 for PostgreSQL 8.3 wit 8.4 RC1?? |
| 02:37:23 | hauxon: | I installed PG 8.4 RC1 on my dev machine and PostGIS was not a part of the "Stackbuilder" installation options |
| 02:37:38 | hauxon: | Will 1.3.6 for 8.3 work |
| 06:46:59 | aerostop: | hey ive never been in here before. It just occured to me that it might exists. |
| 06:47:17 | pimpaa: | it does :P |
| 06:49:42 | aerostop: | I have a map with a lot of points. around 30,000. I want to index them in a way that will help a tile serving program to pull them out quickly |
| 06:51:49 | aerostop: | I don't know alot about SPATIAL indexes but is there a way I can do that with POSTGIS that will speed it up? Or is it best to create a regular index by some hex value representation of each bounding box? |
| 06:53:18 | aerostop: | by tile serving I mean it just returns groups of points, for each tile requested. |
| 07:34:29 | : | * mlechner found a nice bottleneck of performance using the st_within( ) - is this improvable or just a special case? anyone interested? |
| 07:39:46 | mlechner: | we are using within( geometry, geometry ) to test if some ( ~1200 ) points are within a polygon. the polygon is defined as buffer( linegeometry, dist ). the problem is, that the line is always the same and therefore the result of buffer( linegeometry, dist ) is always the same. while iterating through the points the within( ) calculates the buffer( linegeometry ) each time again. the function takes 40s. instead of 0.04s if i calculate the bu |
| 07:39:46 | mlechner: | ffergeometry first and use it as "fixed geometry" at within( ) - is this improvable ( within( ) recognizing such a behaviour?, ... ) |
| 07:44:53 | strk: | use a subselect ? |
| 07:48:03 | mlechner: | u mean something like: select within( pointgeometry, select buffer( linegeometry,dist ) ); ? |
| 07:52:15 | strk: | ask pramsey, I'm a bit busy atm |
| 07:52:27 | strk: | ( hello paul : ) |
| 07:54:48 | mlechner: | hi paul. time for a small question? strk is busy. |
| 07:58:01 | mlechner: | i'll test it first. |
| 08:35:31 | CIA-4: | pramsey * r2606 /branches/3.1/Makefile.am: Include nmake.opt in 'dist' target ( #274 ) |
| 08:36:04 | CIA-4: | pramsey * r2607 /trunk/Makefile.am: Include nmake.opt in 'dist' target ( #274 ) |
| 08:39:07 | sigq: | geosfeed: Ticket #274 ( task closed ): how to compile this new package <http://trac.osgeo.org/geos/ticket/274#comment:1> |
| 08:44:11 | sigq: | geosfeed: Ticket #273 ( defect updated ): trunk build failed with MinGW <http://trac.osgeo.org/geos/ticket/273#comment:2> |
| 11:58:56 | Andre: | hi all |
| 12:00:13 | Andre: | I have point data in an excel sheet ( deg, min, sec ) and want to load this into postgis and create a geometry so that the points could be plotted on a map |
| 12:00:27 | pimpaa: | ok |
| 12:00:51 | pimpaa: | you can, but i am unsure of the format postgis uses to represent degrees minutes and seconds |
| 12:01:11 | pimpaa: | a suggestion is that you transform those to decilmal degrees and then insert em. im pretty sure that will work fine |
| 12:02:02 | Andre: | how do I convert them to decimal?, and once converted, how do I then import that into postgis and create geometry? |
| 12:02:15 | pramsey: | deg + min/60 + sec/2600 |
| 12:02:24 | pramsey: | deg + min/60 + sec//3600 |
| 12:03:01 | pramsey: | upload the table into the database as a non-spatial table |
| 12:03:11 | pramsey: | alter table spsheet add column geom geometry; |
| 12:03:36 | Andre: | ok, thanks, let me try |
| 12:03:57 | pramsey: | update spsheet set geom = st_makepoint( lon_deg + lon_min/60 + lon_sec/3600, lat_deg + lat_min/60 + lat_sec/3600 ); |
| 12:08:50 | pimpaa: | pramsey: postgis does not support the use of degrees and minutes and seconds, right? if it does, whst is the format used? |
| 12:09:37 | pramsey: | no, it doesn't, pimpaa, it is decimal degrees, as you said. |
| 12:11:34 | Andre: | Hi Paul, and how's Canada? |
| 12:11:50 | Andre: | I have met you in Victoria on Foss4G |
| 12:12:39 | Andre: | is there a tool that can automate this process? that is converting deg, min, sec, then load that into postgis and then create geom? |
| 12:13:11 | pimpaa: | an simples excel or spreadsheet software can do that for you quite easily |
| 12:13:20 | Andre: | any pointers on loading postgis on Vista, because Vista is a nightmare! |
| 12:13:55 | pimpaa: | hey Andre, sincerely? ditch vista |
| 12:14:02 | Andre: | I can convert easily with spreadsheet |
| 12:14:10 | pimpaa: | i bought a laptop that came with vista and i regret it forever |
| 12:14:10 | Andre: | I wish I could!!! |
| 12:14:14 | pimpaa: | i installed xp |
| 12:15:01 | Andre: | same here!!!, got a new laptop lastweek and must say, running every little thing as administrator kills me, simple things, like loading postgis is becoming an issue |
| 12:15:04 | pimpaa: | pramsey, thanks for the info |
| 12:15:16 | pimpaa: | its super annoying |
| 12:15:18 | pimpaa: | its impossible to use |
| 12:15:31 | pimpaa: | imagine when you try to develop anything on a machine like that |
| 12:15:44 | pimpaa: | "are you sure you wnat software x to execute Y program?" |
| 12:15:55 | pimpaa: | "are you really sure" |
| 12:15:59 | pimpaa: | "seriously: ? |
| 12:16:02 | pramsey: | Andre; perl |
| 12:16:35 | Andre: | hey, pramsey, I am no GEEK, I am a suite!!! |
| 12:17:12 | Andre: | still rember the Geek, suite talk on FOSS4G ( Victoria ) |
| 12:17:25 | pramsey: | I really don't have anything for you, offhand. As I said, if you load the sheet and *then* create the geometries you can use PgSQL for the conversion. |
| 12:17:25 | Andre: | we still joke about this with friends |
| 12:17:41 | pimpaa: | i wish i had the money to go to foos4g |
| 12:17:41 | pramsey: | that *was* a good talk. |
| 12:17:57 | Andre: | np, just a thought there might be some software out already |
| 12:18:14 | Andre: | boy it is a must and treat!! |
| 12:18:26 | Andre: | I have learned a lot the 2 time I went! |
| 12:18:44 | Andre: | will have to miss this year, but hopefully next year! |
| 12:18:56 | pimpaa: | yea but im in brazil, international travelling is not cheap :P |
| 12:19:18 | pimpaa: | the dolar value and euro has decreased, but still |
| 12:19:36 | pimpaa: | 1R$ ~= $1,80 |
| 12:19:50 | pimpaa: | 1R$ ~= 2,90E |
| 12:24:56 | pramsey: | Brazil -> Sydney... it's all antipodal : ) |
| 12:32:11 | pimpaa: | ehehe |
| 12:32:19 | pimpaa: | it is |
| 12:32:33 | pimpaa: | you should make one foos4g here |
| 12:32:40 | pimpaa: | foss4g* |
| 12:33:44 | pramsey: | 2008 almost was |
| 12:33:49 | pramsey: | Brazil hasn't bid since. |
| 12:35:18 | pimpaa: | yeap ive heard about that |
| 12:35:34 | pimpaa: | well we have a chapter here, but i dont have much contact with it |
| 13:00:24 | Andre: | simple question, when loading dec data from csv file, what field type should I use, in order to create a geom |
| 13:05:00 | pimpaa: | load both of your columns in columns with type double precision |
| 13:05:07 | pimpaa: | lat and long |
| 13:05:48 | pimpaa: | then insert it to a column with type geometry |
| 13:30:35 | Andre: | great, manage to load data into database, table with fields lat, long and name |
| 13:30:43 | Andre: | now I need to create geometry |
| 13:31:16 | Andre: | should that be done from pgadmin ( sql plane )? |
| 17:22:15 | sigq: | geosfeed: 2.PNG attached to ticket #274 <http://trac.osgeo.org/geos/attachment/ticket/274/2.PNG> |
| 17:36:22 | sigq: | geosfeed: Ticket #274 ( task reopened ): how to compile this new package <http://trac.osgeo.org/geos/ticket/274#comment:3> |
| 17:40:22 | sigq: | geosfeed: Ticket #274 ( task closed ): how to compile this new package <http://trac.osgeo.org/geos/ticket/274#comment:4> |
| 17:48:25 | sigq: | geosfeed: 3.PNG attached to ticket #274 <http://trac.osgeo.org/geos/attachment/ticket/274/3.PNG> |
| 17:50:26 | sigq: | geosfeed: Ticket #274 ( task updated ): how to compile this new package <http://trac.osgeo.org/geos/ticket/274#comment:6> |
| 18:58:48 | sigq: | geosfeed: Ticket #274 ( task updated ): how to compile this new package <http://trac.osgeo.org/geos/ticket/274#comment:7> |
| 23:30:57 | CIA-2: | mleslie * r4231 /trunk/ ( liblwgeom/lwgunparse.c regress/sql-mm-curvepoly_expected ): First swing at ticket 212. |
| 23:42:06 | CIA-2: | mleslie * r4232 /trunk/liblwgeom/lwsegmentize.c: Enabling the compound curve parsing for segmentisation; reported in ticket 213 |
