Sorry, this is too good to let pass by:
> Here you go. It occurs when you union the US and Mexico. Thanks for your
> help!
I'm guessing there is no problem with the US and Canada?
Is GEOS supporting the Democratic candidates that want to renegotiate NAFTA?
Maybe Ross Perot was right after all
Paul,
Thanks for the info. I've switched to the GEOS C api (to
quote the doxygen doc: "If you prefer troubles you can use
the C++ interface.")
Since
gNodedGeoms = GEOSIntersection( *gGeoms, NULL );
causes a crash, how would I create an empty geometry
collection?
And for comparision, the
Well... it is a Steering Committee, not a Coding Committee, no? 8^)
But I agree - Mateusz would be a good voice to have on board.
Paul Ramsey wrote:
I agree... one thing I see lacking in my proposed PSC is people who
would feel comfortable committing right away. The Safe and Autodesk
folks a
I agree... one thing I see lacking in my proposed PSC is people who
would feel comfortable committing right away. The Safe and Autodesk
folks aren't going to get their hands dirty right out of the gate,
Martin provides architecture but no direct code mucking.
So Mateusz on the PSC.
On Thu, Apr 3,
Send me the shapefile and I'll try it out in JTS.
M
Martin Chapman wrote:
Unfortunately, I do not have JTS but I will try to step through the code and
see if I can learn more about the problem. Perhaps a careful inspection of
the input and output point sets will yield some clues because the pr
Unfortunately, I do not have JTS but I will try to step through the code and
see if I can learn more about the problem. Perhaps a careful inspection of
the input and output point sets will yield some clues because the problem is
predictable.
Best regards,
Martin
-Original Message-
From:
+1 for me. I'm still willing to participate as PSC member.
Additionally, I would also like to nominate Mateusz Loskot for the
GEOS PSC membership list. His work has left a huge imprint on GEOS,
and he's kept things rolling through the various developmental lulls
in the project after Sandr
+1 for me.
I am happy to be included in the PSC, but really have minimal spare time
to devote to yet another project! So I can really only function in an
advisory role, not a leadership role.
M
Mateusz Loskot wrote:
Paul Ramsey wrote:
Folks we are going to need a PSC to start with, somet
Paul Ramsey wrote:
Folks we are going to need a PSC to start with, something smaller
would be better, I think.
I previously proposed a small group here:
http://lists.osgeo.org/pipermail/geos-devel/2007-October/003076.html
Could I have comments, additions / subtractions?
In my opinion, the ro
Most probably a bug... any chance you could run this same test case
under JTS so we can confirm if it's a problem at the algorithm level
or the port level?
Thanks,
P
On Thu, Apr 3, 2008 at 10:47 AM, Martin Chapman <[EMAIL PROTECTED]> wrote:
> All,
>
> When I union the two features USA and Mexic
Folks we are going to need a PSC to start with, something smaller
would be better, I think.
I previously proposed a small group here:
http://lists.osgeo.org/pipermail/geos-devel/2007-October/003076.html
Could I have comments, additions / subtractions?
Paul
__
Frank,
I'm getting back onto this horse...
First, I've started moving the main page for geos to the geos trac wiki.
That leaves the subsidiary tasks of moving the download, svn snap, and
svn log to downloads.osgeo.org at some point.
Second, I've started to flesh out a PSC page. If you could do
12 matches
Mail list logo
