| 00:03:51 | CIA-2: | mleslie * r4245 /branches/1.4/ ( 7 files in 2 dirs ): As a lemma to ticket 212, this fixes the inconsistent handling of ST_NumPoints with regards to curved polygons and compound curves. They now behave as they should, returning null. |
| 00:26:43 | CIA-2: | mleslie * r4246 /trunk/ ( 8 files in 3 dirs ): Making the changes from r4244 and r4245 onto trunk, addressing ticket 212. |
| 05:10:18 | sigq: | geosfeed: Ticket #273 ( defect updated ): trunk build failed with MinGW <http://trac.osgeo.org/geos/ticket/273#comment:3> |
| 06:28:40 | sigq: | geosfeed: Ticket #273 ( defect updated ): trunk build failed with MinGW <http://trac.osgeo.org/geos/ticket/273#comment:4> |
| 07:55:08 | CIA-2: | pramsey * r4247 /branches/1.4/HOWTO_RELEASE: more notes on requirements |
| 07:55:30 | CIA-2: | pramsey * r4248 /trunk/HOWTO_RELEASE: more notes on requirements |
| 08:24:27 | CIA-2: | pramsey * r4249 /trunk/doc/html/image_src/: add generator to ignore |
| 08:27:09 | CIA-2: | pramsey * r4250 /trunk/ ( HOWTO_RELEASE make_dist.sh ): Build doc images as part of distribution build. |
| 08:27:39 | CIA-2: | pramsey * r4251 /branches/1.4/ ( HOWTO_RELEASE make_dist.sh ): Build doc images as part of distribution build. |
| 08:52:38 | CIA-2: | pramsey * r4252 /trunk/TODO: Add SQL/MM item |
| 08:57:22 | Schuyler: | hobu: the C API doesn't appear to support everything I need |
| 08:57:50 | Schuyler: | hobu: is there a reason beyond ABI compatibility that I should specifically use the C API? |
| 08:59:48 | hobu: | API stability as well. The public API for GEOS is the C API. If you are willing to keep up with the changes, you can use the C++ API |
| 09:06:40 | Schuyler: | hm. understood. |
| 09:06:48 | Schuyler: | the C API isn't exactly documented, though. |
| 09:07:32 | Schuyler: | one kind of separate question: the Geometry::relate( ) operation is expected to be expensive? |
| 09:09:09 | pimpaa: | i think Schuyler, because it tests more then one predicate |
| 09:09:12 | hobu: | I think it just loops through all of the D9 tests, so yes, it's probably costly |
| 09:11:01 | pimpaa: | hey guys, i took a ticket to solve, but im having some problems with it |
| 09:11:16 | pimpaa: | can yu give me some sort of hel?p |
| 09:11:50 | hobu: | Schuyler: shapely and geodjango have good usage and examples of the GEOS C API |
| 09:16:41 | hobu: | also, if there is something missing from the C API, please provide a patch. We would really like to encourage folks to not use the C++ API |
| 09:19:07 | pramsey: | indeed, Schuyler, now is your moment |
| 09:19:13 | pramsey: | 3.2 will probably come out sooner than one might expect |
| 09:19:22 | pramsey: | so you can squeeze new CAPI stuff in under the bar |
| 09:22:37 | Schuyler: | understood. |
| 09:22:49 | Schuyler: | I'd like to contribute but I have a limited amount of funding for this project |
| 09:22:57 | Schuyler: | so we'll see what if anything I can squeeze in |
| 09:23:27 | pimpaa: | pramsey, can i post in the trac some options ive found on that ticket i accepted? i kinda want input from other experienced users |
| 09:23:56 | Schuyler: | another question: # include <geos/geom.h> |
| 09:24:03 | Schuyler: | throws a warning about deprecated headers |
| 09:24:12 | pramsey: | pimpaa: sure. you can also post to postgis-devel and put a link to your mail into the trac instead. |
| 09:24:21 | hobu: | this is to scare people into using the C API |
| 09:24:25 | Schuyler: | if I'm not supposed to use that to pull in the C++ headers for the Geometry classes, what *should* I be using? |
| 09:24:27 | pimpaa: | thanks pramsey, ill do both |
| 09:24:29 | Schuyler: | oh geez |
| 09:24:31 | Schuyler: | ok |