I replaced the hardware for repo.opengeo.org last weekend, and DNS has
now been updated to point directly to that machine (64.90.184.114)
Since we're only running DAV and static files on it we can run a much
better Apache configuration. The old server has already been proxying
requests to the n
Hi - I got your email talking about the patch. But the patch was not
included ... am I missing something?
Jody
On Thu, Jun 4, 2009 at 3:46 AM, Milton Jonathan
wrote:
> Hey Simone
>
> Just to let you know: I sent the changes as a single patch for Jody to
> review along with the other changes for t
yeah, I agree with andrea's perspective, it'd be better to split the
patch into three different patches.
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 05
Milton Jonathan ha scritto:
> Hey Simone
>
> Just to let you know: I sent the changes as a single patch for Jody to
> review along with the other changes for the Symbolizers. I hope that's ok
Those patches hit areas that are handled by a number of different
people:
- Jody for the main module
- M
Hey Simone
Just to let you know: I sent the changes as a single patch for Jody to
review along with the other changes for the Symbolizers. I hope that's ok
Milton
Simone Giannecchini wrote:
> Ciao Milton,
> see below...
>
> ---
> Ing. Simone
Hey Jody
OK, so I decided to send everything as a single patch. Other comments
below..
>> 1. Question: why not put all setters in the org.geotools.styling.Symbolizer
>> interface?
>> . Example: setGeometryPropertyName()
>> . Wouldn't it be nice to have an abstract SymbolizerImpl?
>
> That wil
Adding support to UOMs and fixing several issues with styling
-
Key: GEOT-2532
URL: http://jira.codehaus.org/browse/GEOT-2532
Project: GeoTools
Issue Type: Improvement
Com
Generalization and simplification tests fail on Oracle-NG
-
Key: GEOT-2531
URL: http://jira.codehaus.org/browse/GEOT-2531
Project: GeoTools
Issue Type: Bug
Components: data jd
Maven cannot download SNAPSHOT versions of plugins
--
Key: GEOT-2530
URL: http://jira.codehaus.org/browse/GEOT-2530
Project: GeoTools
Issue Type: Bug
Components: admin
Rep
Hi Jody,
Thank you for your quick response.
In app-schema data access, you'd have a simple feature data store, which is
mapped into the complex feature data access.
When filters are run, the complex attribute form (eg. Gml:name) would then be
unmapped to the simple feature expression (ie. The
External graphics does not respect the declared size when used in graphic fills
Key: GEOT-2529
URL: http://jira.codehaus.org/browse/GEOT-2529
Project: GeoTools
Hi Rini:
> Ideally, the filter should be unmapped first to its simple feature form, eg.
>
> Query:
> feature type: CGI_TermValue
> filter: [ gml:name = significant ]
> [properties: ALL ]
>
> Unmapped to this:
>
> Query:
> feature type: CGITermValue
> filter: [ strTrim([getID()]) = signi
Support for filtering complex attribute value
-
Key: GEOT-2528
URL: http://jira.codehaus.org/browse/GEOT-2528
Project: GeoTools
Issue Type: Wish
Components: core filter
Affects Versio
Hi list,
I have a problem trying to filter complex attribute value from a complex
feature.
Ideally, the filter should be unmapped first to its simple feature form, eg.
Query:
feature type: CGI_TermValue
filter: [ gml:name = significant ]
[properties: ALL ]
Unmapped to this:
Query:
+1, and thanks for taking the time to remove unwanted cruft. If any
users turn up, you can always resurrect it.
Simone Giannecchini wrote:
> -I am the module mantainer
> -functionality is not finished and rather use-case specific
> -it does not build and I don't think I am going to spend time on
15 matches
Mail list logo
