This is my pom.xml
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.geotools.demo.gui
geotools-gui
jar
1.0-SNAPSHOT
geotools-gui
ht
OK, so I'm still investigating this problem.
Because I'm new to GIS, Geotools as well as Oracle spatial bear with me.
When I refer to the type name string as a parameter in getFeatureSource I'm
using the table name. This results in 'Exception in thread "main"
java.lang.NoSuchMethodError'
org.g
Jody thanks, would be nice to work with you.
To be fair I have to say that my primary target is to do a GeoXACML
implementation (my customers need it and it is part of my master thesis)
GeoXACML requires an XACML implementation, at the moment I am looking for an
OS Project where I can contrib
Evaluating expressions on complex features
--
Key: GEOT-2370
URL: http://jira.codehaus.org/browse/GEOT-2370
Project: GeoTools
Issue Type: Improvement
Components: core main
Affects Version
Justin,
I just found a case when we have to make your LinkedHashMap fix (or
other change to respect iteration order). In unit tests, if a complex
type is programmatically constructed, the XSD schema that is
automatically generated from it uses the property iteration order. This
is effectively
No objection here Justin; I think I will also step up and take ownership of
the wms module. I have a timeout patch here to apply as well.
Jody
On Thu, Mar 5, 2009 at 10:10 AM, Justin Deoliveira wrote:
> Hi Frank,
>
> Since there were no objections I have gone ahead and applied this patch
> to bot
Jody Garnett wrote:
> I would be happy to mentor this one (having sat through the design of
> WMS I can at least relay what we learned from the experience).
>
> Andrea has already responded about GeoServer WCS implementation. There
> are a couple more things to note - I think WCS 1.1.1 may be ou
Hi Frank,
Since there were no objections I have gone ahead and applied this patch
to both 2.5.x and trunk. Thanks or the patch.
-Justin
[email protected] wrote:
> Hello,
>
> After having some problems adding a WMS 1.3.0 Layer (served from ArcGIS
> Server) if found an entry in geotoo
I would be happy to mentor this one (having sat through the design of WMS I
can at least relay what we learned from the experience).
Andrea has already responded about GeoServer WCS implementation. There are a
couple more things to note - I think WCS 1.1.1 may be out?
The OGC Climate Change Interg
One thing I liked (after posting the 2007 report) was noting how much
progress we have made on things we have earlier identified as weaknesses.
If you have anything to add please edit that page; or chat on the email list
here and I can figure out how to roll it in.
Jody
On Wed, Mar 4, 2009 at 6:2
Example of problems with the Style Bindings framework
-
Key: GEOT-2369
URL: http://jira.codehaus.org/browse/GEOT-2369
Project: GeoTools
Issue Type: Bug
Components: core styling
Hi Frank,
I've had a look at your patch and, for such minor changes, I don't
think there would be any problems. Unfortunately we can't consult the
module maintainer because there isn't one at the moment.
Please add it as a Jira issue and we'll give folks a few days to
comment, then, if there are
Filter 2.0 xml bindings
---
Key: GEOT-2368
URL: http://jira.codehaus.org/browse/GEOT-2368
Project: GeoTools
Issue Type: New Feature
Components: ext xml-xsd
Reporter: Justin Deoliveira
Ass
Add temporal filter classes.
Key: GEOT-2367
URL: http://jira.codehaus.org/browse/GEOT-2367
Project: GeoTools
Issue Type: New Feature
Components: core filter
Reporter: Justin Deoliveira
Christian Müller wrote:
> I have 2 questions about this proposal
>
> 1) Who would be the mentor
Don't know.
> 2) Does geoserver implement the full WCS specification (for testing)
GeoServer is reference implementation for WCS 1.1, but there are two
caveats:
- it does not support ND coverages
Christian Müller wrote:
> I have 2 questions about this proposal
>
> 1) Who would be the mentor
I guess it depends on the tech used for the front end. Will this be
desktop of web based, etc...
> 2) Does geoserver implement the full WCS specification (for testing)
>
Yes, GeoServer is the refere
I have 2 questions about this proposal
1) Who would be the mentor
2) Does geoserver implement the full WCS specification (for testing)
The idea is: Since I am writing my master thesis and I have to study the WCS
specification, half the work seems to be done :-)
christian
--
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1431/changes
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enter
Hi Frank,
Yeah, this is pretty clearly a bug, and the patch looks good. I am happy
to apply the patch however I am not he maintainer that module. The
current maintainer (richard gould) has been inactive for quite some time.
Has anyone take ownership of the wms module? If not any objections to m
See http://hudson.opengeo.org/hudson/job/geotools-trunk/1430/changes
--
started
Updating http://svn.osgeo.org/geotools/trunk
U
demo/introduction/src/main/java/org/geotools/demo/introduction/DemoBase.java
U
demo/introduction/src/main/java/or
List,
I use geotools version 2.5.2.
I think this is a bug in the LikeFilterImpl:
If i create a propertyIsLike(LikeFilterImpl) filter i get a empty filter tag
when the filter is encoded. Am i using the right functions?
A simple piece of code:
FilterFactory2 ff =
CommonFactoryFinder.getFilterF
Filter encoder does not properly handle PropertyIsLike
--
Key: GEOT-2366
URL: http://jira.codehaus.org/browse/GEOT-2366
Project: GeoTools
Issue Type: Bug
Components: ext xml-xsd
Martin Desruisseaux wrote:
> Andrea Aime a écrit :
>> I can commit it. I was tghinking of rolling a separate method
>> setCode(preparedStatement, int index, String code)
>> so that subclasses can override the defult behavior and use setString
>> instead. That should handle the IGN specific case.
>
I known that CRS.decode(...,) and CRS.decode(..., true) are commonly used -
they
will not change. But are anyone using the same method with a "false" argumment
value?
In GeoTools 2.6 we have:
CRS.decode(..., true) : set FORCE_LONGITUDE_FIRST_AXIS_ORDER to TRUE
CRS.decode(..., false) :
Andrea Aime a écrit :
> I can commit it. I was tghinking of rolling a separate method
> setCode(preparedStatement, int index, String code)
> so that subclasses can override the defult behavior and use setString
> instead. That should handle the IGN specific case.
We can wait before making this met
Hello,
After having some problems adding a WMS 1.3.0 Layer (served from ArcGIS Server)
if found an entry in geotools-user list
(http://n2.nabble.com/Parsing-WMS-Capabilities-td1942642.html) and an issue
created in Jira (http://jira.codehaus.org/browse/GEOT-1858)
I guess i found a solution for
26 matches
Mail list logo