View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061127211801Lbuild.105
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chan
Justin Deoliveira wrote:
> Hi all,
>
> I have run into a situation I am not sure how to solve. What happens
> when a binary operator runs into a null value. Right now the null value
> gets converted to the string "null" and the comparison proceeds, this
> leads to strange results.
>
> So what is on
Hi all,
I have run into a situation I am not sure how to solve. What happens
when a binary operator runs into a null value. Right now the null value
gets converted to the string "null" and the comparison proceeds, this
leads to strange results.
So what is one to do. I can think of a couple of opt
dear Chris, thanks for your prompt and full response,
On Mon, Nov 27, 2006 at 06:37:16PM -0500, Chris Holmes wrote:
> I would love it if we could include our ideas on transactions and
> versioning and the like in WFS-Simple, but unfortunately I do fear that
> when you get in to transactions, auth
I have been following the wfs simple discussions and like the focus on
usability by mere mortals. However I have to agree with Chris with that
transactions by nature are non-simple. But Andrea's approach to
versioning follows the KISS philosophy so I remain optimistic that the
two will be compatibl
Jo Walsh wrote:
dear Justin, all,
On Mon, Nov 27, 2006 at 11:45:24AM -0800, Justin Deoliveira wrote:
Considering that not many people implement wfs altogether, I dont think
a ton of people will implement wfs-t. I agree that a simple protocol is
a big win, but not if it starts to reek havoc wit
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-trunk?log=log20061127183157
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to shar
Justin Deoliveira wrote:
> Actually I think that what I was thinking about is something different.
>
We cannot extend Expression - we can make a function - but we cannot
extend (and encode) an expression. Not sure I understand your code
example - did you mean to build up a set of geometries to
Actually I think that what I was thinking about is something different.
class DefaultGeometry implements Expression {
Object evaluate( Object object, Class context ) {
List accessors = FactoryFinder.propertyAccessors(
object );
for ( PropertyAccessor pa : accessors ) {
List geo
View results here ->
http://geo.openplans.org:9090/buildresults/geotools-2.3.x?log=log20061127180812Lbuild.56
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chanc
First of appologizes to Andrea for the confusion - we are talking about
capturing the idea of DefaultGeometry (not removing it).
In talking with Justin the following idea was brought up, rather then
add a PropertyAccessor method to getDefaultGeometry
we should handle it as yet another PropertyAc
dear Justin, all,
On Mon, Nov 27, 2006 at 11:45:24AM -0800, Justin Deoliveira wrote:
> Considering that not many people implement wfs altogether, I dont think
> a ton of people will implement wfs-t. I agree that a simple protocol is
> a big win, but not if it starts to reek havoc with existing clie
Hey Paul and all.
Sorry I missed the irc meeting today, but thought I'd lend a few
thoughts on the topic of versioning in pl/pgsql.
What you say makes sense, and I think it would be great if these ideas
made it in to PostGIS core as pl/pgsql. But this round is really more
prototyping what v
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Hi Andrea,
>>
>> Finally got a chance to look your proposal over, i must say this looks
>> pretty darn cool. I had an idea about how to extend the protocol.
>>
>> Instead of modifying any of the existing wfs schema files, could we
>> define all
Good old Adrian always taking notes :-P
Adrian, you and Martin are both of course correct. But we still should
see if we can do something; if it is dependent on a server's
configuration then perhaps our client code that talks to that server is
the best place to have this ... at the very least
Justin Deoliveira ha scritto:
> Hi Andrea,
>
> Finally got a chance to look your proposal over, i must say this looks
> pretty darn cool. I had an idea about how to extend the protocol.
>
> Instead of modifying any of the existing wfs schema files, could we
> define all of the needed functionalit
Hi Andrea,
Finally got a chance to look your proposal over, i must say this looks
pretty darn cool. I had an idea about how to extend the protocol.
Instead of modifying any of the existing wfs schema files, could we
define all of the needed functionality to support versioning in terms of
new oper
A certain Jody Garnett once said to me,
SRS can be anything depending on the particular server's
configuration... Has the semantics of SRS become better defined?
---adrian
On Mon, 2006-11-27 at 08:26 -0800, Jody Garnett wrote:
> I have been hanging out a bit more with real users and have notic
Jody,
Cool. Thanks for the info on how the Literal semi-typing system works
on trunk. Clearly that fixes this problem for gt-2.4.x-based solutions.
However, I'm not sure I understand how this problem might be fixed on
the 2.3.x branch. Your second comment notes that a geoAPI change would
be
Jody Garnett a écrit :
> But really we need some additional methods for the CRS facade - so users stop
> guessing:
>
> String CRS.encodeSRS( CoordinateReferneceSystem crs );
> String CRS.decodeSRS( String srs );
What is the SRS string? Is it some kind of WKT, or authority code?
Martin
I have been hanging out a bit more with real users and have noticed a
large gap that keeps occuring - between interaction without GeoTools and
the outside world.
We really need a helper method to allow users to go between SRS and
CoordinateReferneceSystem - I got this in a code example today:
>
Oracle sql encoder assumes 0 as lack of SRID, but it may not be so
--
Key: GEOT-1044
URL: http://jira.codehaus.org/browse/GEOT-1044
Project: GeoTools
Issue Type: Bug
Affects
Hi all,
at Geoserver we are working on developing a versioned WFS-T extension
which, at first, should provide single branch versioning with history,
attribution and rollback. Here I have written down the results of my
research (warning, big document):
http://docs.codehaus.org/display/GEOS/Versioni
23 matches
Mail list logo
