Andrea,
Code snippets below show first thoughts for a Lines class API. They
imply a LineControl class that holds parameters and the following
Lines methods:
SimpleFeatureSource createLines( ReferencedEnvelope bounds,
LineControl ...controls );
SimpleFeatureSource createLines( ReferencedEnvel
Hi Jody,
That sounds fine (putting it off). I don't think there's a lot to do.
Michael
On 4 May 2011 17:16, Jody Garnett wrote:
> Hey Micheal; I may put off that proposal until you guys are settled? Unless
> you want me to bring it into gt-data and you can work on it there?
>
> --
> Jody Garnet
On Wed, May 4, 2011 at 9:06 AM, Michael Bedward
wrote:
> Hi Andrea,
>
>> - having an attribute telling the x or y of the line (longitude,
>> latitude, x/y in meters)
>
> Do any of the uses you have in mind call for non-numeric attributes ?
> I have a use case where a String attribute would be good
Hey Micheal; I may put off that proposal until you guys are settled? Unless you
want me to bring it into gt-data and you can work on it there?
--
Jody Garnett
On Wednesday, 4 May 2011 at 5:06 PM, Michael Bedward wrote:
> Hi Andrea,
>
> > - having an attribute telling the x or y of the line (l
Hi Andrea,
> - having an attribute telling the x or y of the line (longitude,
> latitude, x/y in meters)
Do any of the uses you have in mind call for non-numeric attributes ?
I have a use case where a String attribute would be good.
> - having some sort of hierarchy, major and minor lines (to ha
On Wed, May 4, 2011 at 3:05 AM, Michael Bedward
wrote:
> Hello Jody, Andrea,
>
> I'd also find it handy to be able to create lines as well as the
> current polygons. I can easily add that option to the current
> unsupported module.
That would be really nice. For display purposes a list of nice to
Hello Jody, Andrea,
I'd also find it handy to be able to create lines as well as the
current polygons. I can easily add that option to the current
unsupported module.
Michael
On 3 May 2011 23:47, Andrea Aime wrote:
> On Tue, May 3, 2011 at 3:08 PM, Jody Garnett wrote:
>> So the proposal is to
On Tue, May 3, 2011 at 3:08 PM, Jody Garnett wrote:
> So the proposal is to fold it into the data module; I am fine with that.
> Andrea you mentioned wrapping this up as a DataStore; did you want to do
> that - or can we merge these classes as indicated by the proposal?
I think the utility classe
So the proposal is to fold it into the data module; I am fine with that. Andrea
you mentioned wrapping this up as a DataStore; did you want to do that - or can
we merge these classes as indicated by the proposal?
If discussion is done I would like to start the voting process.
--
Jody Garnett
O
Hello Jody,
I wonder if I could flick pass this proposal and patch to you please,
to do with it what you will at a time of your choosing.
cheers
Michael
On 19 April 2011 06:28, Andrea Aime wrote:
> On Mon, Apr 18, 2011 at 10:40 AM, Michael Bedward
> wrote:
>> Dear all,
>>
>> Please see the fo
On Mon, Apr 18, 2011 at 10:40 AM, Michael Bedward
wrote:
> Dear all,
>
> Please see the following proposal to move the vector grid classes from
> the unsupported grid module into gt-data (org.geotools.data.grid
> package)
> http://docs.codehaus.org/display/GEOTOOLS/Vector+grids
Sounds good to me.
codehaus seems to be down for me; will check the proposal when it is back.
Jody
On Mon, Apr 18, 2011 at 6:40 PM, Michael Bedward
wrote:
> Dear all,
>
> Please see the following proposal to move the vector grid classes from
> the unsupported grid module into gt-data (org.geotools.data.grid
> pack
Dear all,
Please see the following proposal to move the vector grid classes from
the unsupported grid module into gt-data (org.geotools.data.grid
package)
http://docs.codehaus.org/display/GEOTOOLS/Vector+grids
Michael
--
13 matches
Mail list logo
