Ciao Guys,
well, there are various considerations to be made and various aspects to be
taken into account.
Let me try to explain (I am realizing that I am flooding the ml a little bit
too much lately, sorry about that).
Both custom streams and asciigrids are ImageIO plugins, hence their place
woul
http://geo.openplans.org:9090/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/589
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
Infinite recursivity in CRS.findMathTransform(...) when (longitude,latitude)
axis order is forced
-
Key: GEOT-1161
URL: http://jira.codehaus.org/browse/GEOT-1161
Extract the authority code from an unidentified CRS
---
Key: GEOT-1160
URL: http://jira.codehaus.org/browse/GEOT-1160
Project: GeoTools
Issue Type: Improvement
Components: core refere
It used to have GCE stuff in there as well; I do not mind if we break
out a new module - the point if it is common code it should be in the
library.
Jody
> Jody Garnett ha scritto:
>> Hi Guys - can I jump in here for a second?
>>
>> Extensions is for "pure" extensions that build ontop of the geo
Andrea Aime wrote:
> Sure, but I have no time to put on this. Versioning WFS has been delayed
> due to 1.5.x release and trunk merge, now I have to work on it full
> steam.
Andrea I am not asking for your time - I am asking for your
consideration of a solution. I was unable to tell from this emai
http://geo.openplans.org:9090/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/581
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-in
On Tuesday 13 February 2007 22:16, Andrea Aime wrote:
> Gabriel Roldán ha scritto:
> > hmmm it seems nothing in the CQL grammar talks about id filters,
> > but... the first thing that arises to my head is to extend the definition
> > of attribute to support @id?
> > guess that way we'll easily
Gabriel Roldán ha scritto:
> hmmm it seems nothing in the CQL grammar talks about id filters, but...
> the first thing that arises to my head is to extend the definition of
> attribute to support @id?
> guess that way we'll easily create
> @idfid-1
>
> The geotools filters shall support that
There is no distinction in the standards between vector and raster data.
Some data file formats may produce both vector and raster data
simultaneously. Consider the MODIS Fire Product. You can read vectors
(i.e. a Point Coverage of fire detections) or a raster (i.e. a class map of
the scene) fro
hmmm it seems nothing in the CQL grammar talks about id filters, but...
the first thing that arises to my head is to extend the definition of
attribute to support @id?
guess that way we'll easily create
@idfid-1
The geotools filters shall support that pretty well with the new
PropertyAccess
http://geo.openplans.org:9090/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/571
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-in
Jody Garnett ha scritto:
> Hi Guys - can I jump in here for a second?
>
> Extensions is for "pure" extensions that build ontop of the geotools
> library and its plug-ins. With that in mind...
>
> - imageio/customstreams - this is code that is used by several plugin
> implementations for data ac
Jody Garnett ha scritto:
> Justin Deoliveira wrote:
>> 1. By not processing the extension point, and not picking up the slow
>> xpath processing property accessor. Instantiate a fast processor and
>> just use it.
> You would need to look at the expression and confirm that xpath was not
> used. Y
Justin Deoliveira wrote:
> 1. By not processing the extension point, and not picking up the slow
> xpath processing property accessor. Instantiate a fast processor and
> just use it.
You would need to look at the expression and confirm that xpath was not
used. You are performing the check once -
Hi Matthias - this "transition to GeoAPI" game is happening in a couple
places now - let's see how it works out for style.
Matthias Basler wrote:
>>> 2. What is the roadmap to get the whole styling API use GeoAPI
>>>expressions?
>>>
>>>
>> RIght.
>> 1. collapse GeoAPI style interface
Matthias Basler wrote:
> Ok, I see you need volunteers. On the one hand I have done quite a bit of
> refactoring in my own code so got very much used to it. ;-) On the other hand
> I have hardly enough time to push the widgets further - and I fear if I start
> working on GT directly I will never
Hi Guys - can I jump in here for a second?
Extensions is for "pure" extensions that build ontop of the geotools
library and its plug-ins. With that in mind...
- imageio/customstreams - this is code that is used by several plugin
implementations for data access - let's roll this into the "data"
An observation:
A reprojection service should not be implemented in a renderer, but should
be provided by the Geometry implementation. In fact, any operation which
could significantly impact performance should be offered as an optimized
service by the implementation. There should also be a colle
Hey all,
My understanding from the meeting yesterday is that Jody has paid work to
bring one of the ISO Geometry branches into "supported" status. He's
currently leaning toward unsupported/geometry. I would like to finish what
I started last summer in the JTS-Wrapper branch. I have till the en
Jody Garnett wrote:
> GeoAPI (the specification) has PropertyName
> GeoTools has PropertyName2 with some additional/optional/extra
> information that we want.
>
> You can see this in action when looking at the Style APIs, we did this
> to put a graphic behind the text. I am not sure if the
I believe catalog has the notion of a RecordId, defined in the filter
1.1 spec. From what I can tell it is basically the equivalent of
FeatureId but in catalog land.
-Justin
Andrea Aime wrote:
> Hi Gabriel,
> a cursory look at the code and grammar seems to suggest
> the CQL filter does not supp
Hi Gabriel,
a cursory look at the code and grammar seems to suggest
the CQL filter does not support FID filters?
I guess this is because catalog does not have the
concept of a feature id?
As a generic filter parser for geotools it would be
nice if it supported fid filters as well
Cheers
Andrea
--
Simone Giannecchini ha scritto:
> Hi guys, (especially you andrea),
> I am done with merging 2.3.x/cleaning 2.4 phase 1, but I have a doubt.
> Where should I place the following projects?
>
> - imageio/customstreams(I would move it there under extension)
> - spike/imageio/asciigrid
Thanks Simone - that extra detail is what I needed.
Jody
Simone wrote:
> I think there is a little bit of confusione here.
>
> My baseline goal with the geometry --> shape converter classes is
> simply to move them out of
> the renderer module and place them back in the main module. In this
> wa
I think there is a little bit of confusione here.
My baseline goal with the geometry --> shape converter classes is simply to
move them out of
the renderer module and place them back in the main module. In this way
everybody can gain access
to the capabilities of converting JTS geometries into J
Andrea Aime wrote:
> Jody Garnett ha scritto:
>> Hi Simboss; just a follow up to our question on how to separate out
>> the Geometry -> Shape transition from the rendering code. Since we
>> will be defining no new API we do not need a proposal for this one;
>> you have my permission as module ma
Simone wrote:
> Ciao Jody,
> I am kind of puzzed here (maybe it's time to go to bed) since I do not
> understand why you are talking about controling decimation.
Perhaps we are both puzzled here in different directions - the rendering
package has some Geometry --> Shape code. When making the
tra
Hi guys, (especially you andrea),
I am done with merging 2.3.x/cleaning 2.4 phase 1, but I have a doubt.
Where should I place the following projects?
- imageio/customstreams(I would move it there under extension)
- spike/imageio/asciigrid (I would move it there under extension)
Jody Garnett ha scritto:
> Hi Simboss; just a follow up to our question on how to separate out the
> Geometry -> Shape transition from the rendering code. Since we will be
> defining no new API we do not need a proposal for this one; you have my
> permission as module maintainer to package up th
30 matches
Mail list logo
