[Geoserver-devel] Time and Elevation support for WCS and WMS

Hi list,
I am sending this email as the result of the discussion I have had
with the GeoMatys guys, Vincent Heurteaux and Cédric Briançon about
time and elevation support for WCS and WMS.

As people on the list may know they have been hacking GeoServer for a
while now and what they demoed at FOSS4G was really good stuff. Well
lately we have discussed about ways to cooperate on this work which
interests all of us and we came up with the following idea.
We would like to create a GeoServer branch (Alessio could create it)
and commit the GeoMatys work there with the goal of keeping it aligned
with GeoServer trunk.
Alessio, Daniele and Cédric would at that point share the load of
developing this branch and keeping it aligned with trunk. Some day in
the not-too-far future we could merge this work with trunk or
probably, if things go as they should, just replace trunk with this
branch.

I think that to get this started all we need would be giving Cédric
commit privileges on the branch so that he could commit his work
there. Probably in the following also Daniele could make good use of
commit privileges on the branch.

Anyway, I would like to know what people think about this
idea/strategy and hopefully what are we supposed to do to implement it
:slight_smile: (I am still not able to get my commit privileges :frowning: )

Thx a lot,
Simone.

PS
Sorry about the incomplete email I sent out before, I am playing with
my new mac but I am not much of a mac user yet :frowning:

--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it

-------------------------------------------------------

What's the time frame for starting on it? This is just an idea that others may shoot down, but it might be nice to have the work directly on trunk. Like we should branch 1.6.x when we do RC1, which should hopefully be pretty soon, at which point trunk can become open.

It will be against GeoTools trunk, which will mean a bit more instability, but more hands makes for less instability, and will mean much less pain for everyone in the long run.

Chris

Simone Giannecchini wrote:

Hi list,
I am sending this email as the result of the discussion I have had
with the GeoMatys guys, Vincent Heurteaux and Cédric Briançon about
time and elevation support for WCS and WMS.

As people on the list may know they have been hacking GeoServer for a
while now and what they demoed at FOSS4G was really good stuff. Well
lately we have discussed about ways to cooperate on this work which
interests all of us and we came up with the following idea.
We would like to create a GeoServer branch (Alessio could create it)
and commit the GeoMatys work there with the goal of keeping it aligned
with GeoServer trunk.
Alessio, Daniele and Cédric would at that point share the load of
developing this branch and keeping it aligned with trunk. Some day in
the not-too-far future we could merge this work with trunk or
probably, if things go as they should, just replace trunk with this
branch.

I think that to get this started all we need would be giving Cédric
commit privileges on the branch so that he could commit his work
there. Probably in the following also Daniele could make good use of
commit privileges on the branch.

Anyway, I would like to know what people think about this
idea/strategy and hopefully what are we supposed to do to implement it
:slight_smile: (I am still not able to get my commit privileges :frowning: )

Thx a lot,
Simone.

PS
Sorry about the incomplete email I sent out before, I am playing with
my new mac but I am not much of a mac user yet :frowning:

Indeed, way back when we decided to pull geoserver trunk off of geotools
trunk we said that we would branch 1.6.x when we got to our first RC1,
which we are pretty close to.

Also of note is some other R&D going on (H2 + WFS datastore) which is
being written solely against gt trunk. So having a GeoServer trunk to
track it would definitley be useful.

A while back I created a "1.7.x" spike to test the new feature model
changes with GeoServer cite testing. It lives here:

http://svn.codehaus.org/geoserver/spike/1.7.x/

BUt has not been updated post foss4g code sprint, so it wont compile. In
terms of effort it took me about 2 days to port gs trunk over to gt
trunk and get all cite tests passing. So the level of effort might just
be less then people think.

My 2c.

-Justin

Chris Holmes wrote:

What's the time frame for starting on it? This is just an idea that
others may shoot down, but it might be nice to have the work directly on
trunk. Like we should branch 1.6.x when we do RC1, which should
hopefully be pretty soon, at which point trunk can become open.

It will be against GeoTools trunk, which will mean a bit more
instability, but more hands makes for less instability, and will mean
much less pain for everyone in the long run.

Chris

Simone Giannecchini wrote:

Hi list,
I am sending this email as the result of the discussion I have had
with the GeoMatys guys, Vincent Heurteaux and Cédric Briançon about
time and elevation support for WCS and WMS.

As people on the list may know they have been hacking GeoServer for a
while now and what they demoed at FOSS4G was really good stuff. Well
lately we have discussed about ways to cooperate on this work which
interests all of us and we came up with the following idea.
We would like to create a GeoServer branch (Alessio could create it)
and commit the GeoMatys work there with the goal of keeping it aligned
with GeoServer trunk.
Alessio, Daniele and Cédric would at that point share the load of
developing this branch and keeping it aligned with trunk. Some day in
the not-too-far future we could merge this work with trunk or
probably, if things go as they should, just replace trunk with this
branch.

I think that to get this started all we need would be giving Cédric
commit privileges on the branch so that he could commit his work
there. Probably in the following also Daniele could make good use of
commit privileges on the branch.

Anyway, I would like to know what people think about this
idea/strategy and hopefully what are we supposed to do to implement it
:slight_smile: (I am still not able to get my commit privileges :frowning: )

Thx a lot,
Simone.

PS
Sorry about the incomplete email I sent out before, I am playing with
my new mac but I am not much of a mac user yet :frowning:

!DSPAM:4007,471f8554246292090977483!

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

!DSPAM:4007,471f8554246292090977483!

------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:4007,471f8554246292090977483!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Hi Chris,
well as usual ths time frame is "starting from yesterday". Really, we
have got the go for spending a decent amount of time on this but if we
don't start asap I am afraid this funding could be move to some other
crazy task.

As far as working on trunk, I think my answer would greatly depend on
what trunk is supposed to be used for by the other people :-). 99% of
the work we'll do we'll be on coverage and it should be quite stable
and usable. Well it has to be that way, it is a requirement. It would
not be ideal for us to keep this part stable while something else may
experience instabilites due to substantial development going on. Our
goal is to work on coverage but we still want to have shapefiles and
postgis at least functional as they are right now (I am pretty sure
the same applies to the GeoMatys guys) hence I would really like to
spend time on testing the the results of the code sprint done at
FOSS4G :-).
Keep in mind that GeoMatys has done this work against gt-2.4.x and
that we are working ourselves with gt-2.4.x.

My choice would be, we start now quickly branching geoserver trunk
working on 2.4.x and then when geoserver branch 1.7.x we give it a
try and if everything is fine we switch to it, otherwise we wait a
bit before doing so. Anyway, as I said before, it is pretty important
for us to start this work asap :-).

Ciao,
Simone.

On 10/24/07, Chris Holmes <cholmes@anonymised.com> wrote:

What's the time frame for starting on it? This is just an idea that
others may shoot down, but it might be nice to have the work directly on
trunk. Like we should branch 1.6.x when we do RC1, which should
hopefully be pretty soon, at which point trunk can become open.

It will be against GeoTools trunk, which will mean a bit more
instability, but more hands makes for less instability, and will mean
much less pain for everyone in the long run.

Chris

Simone Giannecchini wrote:
> Hi list,
> I am sending this email as the result of the discussion I have had
> with the GeoMatys guys, Vincent Heurteaux and Cédric Briançon about
> time and elevation support for WCS and WMS.
>
> As people on the list may know they have been hacking GeoServer for a
> while now and what they demoed at FOSS4G was really good stuff. Well
> lately we have discussed about ways to cooperate on this work which
> interests all of us and we came up with the following idea.
> We would like to create a GeoServer branch (Alessio could create it)
> and commit the GeoMatys work there with the goal of keeping it aligned
> with GeoServer trunk.
> Alessio, Daniele and Cédric would at that point share the load of
> developing this branch and keeping it aligned with trunk. Some day in
> the not-too-far future we could merge this work with trunk or
> probably, if things go as they should, just replace trunk with this
> branch.
>
> I think that to get this started all we need would be giving Cédric
> commit privileges on the branch so that he could commit his work
> there. Probably in the following also Daniele could make good use of
> commit privileges on the branch.
>
> Anyway, I would like to know what people think about this
> idea/strategy and hopefully what are we supposed to do to implement it
> :slight_smile: (I am still not able to get my commit privileges :frowning: )
>
>
> Thx a lot,
> Simone.
>
> PS
> Sorry about the incomplete email I sent out before, I am playing with
> my new mac but I am not much of a mac user yet :frowning:
>

--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it

-------------------------------------------------------

Hi Justin,
my answers are inline below..

On 10/24/07, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Indeed, way back when we decided to pull geoserver trunk off of geotools
trunk we said that we would branch 1.6.x when we got to our first RC1,
which we are pretty close to.

Also of note is some other R&D going on (H2 + WFS datastore) which is
being written solely against gt trunk. So having a GeoServer trunk to
track it would definitley be useful.

I understand and agree that it would be useful. When in the past we
were managing the raster branch we used to work against trunk and fix
bugs which were not related to our work but related to changes in the
feature part and this was all fine fr us.

This time I would put it this way. The impelling goal is to integrate
the work that we have been doing with the great work that GeoMatys has
been doing and probably extend it a little bit. I would not be happy
to add the uncertainty inherited from the fm switch, at least not for
the moment. First let us integrate things and play a bit with what is
already there then, when we are confident about what we have, we can
integrate that on 1.7.x even because I am pretty sure it will be
almost painless since the fm switch should not impact much the
coverage part (correct me if I am wrong).

So, my (reasonable :slight_smile: ) request is, let us branch and see how it goes
(I am sure it will go great) then let's talk about trunk later on.

A while back I created a "1.7.x" spike to test the new feature model
changes with GeoServer cite testing. It lives here:

http://svn.codehaus.org/geoserver/spike/1.7.x/

BUt has not been updated post foss4g code sprint, so it wont compile. In
terms of effort it took me about 2 days to port gs trunk over to gt
trunk and get all cite tests passing. So the level of effort might just
be less then people think.

That's exactly what I am talking about. It "might" :-). I mean, it is
not that I don't trust the work that has been done on this topic, it
is just that I cannot afford having things that were working in the
past with respect to features (shapefile, postgis, rendering, filters,
etc..) which don't work correctly anymore since we'll be using the
work we'll be doing live demos and I believe the same applies to the
geomatys guys.

So, as I said before, let us just play a couple of weeks on a branch
of 1.6.x then we may try a quick experiment on trunk after it becomes
a bit more mature.

Ciao,
Simone.

My 2c.

-Justin

Chris Holmes wrote:
> What's the time frame for starting on it? This is just an idea that
> others may shoot down, but it might be nice to have the work directly on
> trunk. Like we should branch 1.6.x when we do RC1, which should
> hopefully be pretty soon, at which point trunk can become open.
>
> It will be against GeoTools trunk, which will mean a bit more
> instability, but more hands makes for less instability, and will mean
> much less pain for everyone in the long run.
>
> Chris
>
> Simone Giannecchini wrote:
>> Hi list,
>> I am sending this email as the result of the discussion I have had
>> with the GeoMatys guys, Vincent Heurteaux and Cédric Briançon about
>> time and elevation support for WCS and WMS.
>>
>> As people on the list may know they have been hacking GeoServer for a
>> while now and what they demoed at FOSS4G was really good stuff. Well
>> lately we have discussed about ways to cooperate on this work which
>> interests all of us and we came up with the following idea.
>> We would like to create a GeoServer branch (Alessio could create it)
>> and commit the GeoMatys work there with the goal of keeping it aligned
>> with GeoServer trunk.
>> Alessio, Daniele and Cédric would at that point share the load of
>> developing this branch and keeping it aligned with trunk. Some day in
>> the not-too-far future we could merge this work with trunk or
>> probably, if things go as they should, just replace trunk with this
>> branch.
>>
>> I think that to get this started all we need would be giving Cédric
>> commit privileges on the branch so that he could commit his work
>> there. Probably in the following also Daniele could make good use of
>> commit privileges on the branch.
>>
>> Anyway, I would like to know what people think about this
>> idea/strategy and hopefully what are we supposed to do to implement it
>> :slight_smile: (I am still not able to get my commit privileges :frowning: )
>>
>>
>> Thx a lot,
>> Simone.
>>
>> PS
>> Sorry about the incomplete email I sent out before, I am playing with
>> my new mac but I am not much of a mac user yet :frowning:
>>
>
>
> !DSPAM:4007,471f8554246292090977483!
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
>
> !DSPAM:4007,471f8554246292090977483!
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
> !DSPAM:4007,471f8554246292090977483!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it

-------------------------------------------------------

Hi Simone,

Well we of course want to create a path for you guys that makes it
easiest to work. I just get a little worried when people talk about
branching because it means that trunk wont see the result for quite some
time, if at all.

I think we can agree that the number one thing is success. Success in
that you guys can do what you need, and success in that work makes it
back the trunk.

So how about a compromise. You guys work on a branch but more
periodically than in the past merge back to the trunk. Ie, lay out some
clear milestones that involve a merge back to trunk. This mitigates the
risk of branching and prevents a "huge merge step" at the end of the
project.

Do you (and others) think this will be possible?

I understand and agree that it would be useful. When in the past we
were managing the raster branch we used to work against trunk and fix
bugs which were not related to our work but related to changes in the
feature part and this was all fine fr us.

This time I would put it this way. The impelling goal is to integrate
the work that we have been doing with the great work that GeoMatys has
been doing and probably extend it a little bit. I would not be happy
to add the uncertainty inherited from the fm switch, at least not for
the moment. First let us integrate things and play a bit with what is
already there then, when we are confident about what we have, we can
integrate that on 1.7.x even because I am pretty sure it will be
almost painless since the fm switch should not impact much the
coverage part (correct me if I am wrong).

So, my (reasonable :slight_smile: ) request is, let us branch and see how it goes
(I am sure it will go great) then let's talk about trunk later on.

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Just in order to help me to understand, I wonder: would the branch depends on
GeoTools 2.4 or GeoTools trunk? For now postgrid development uses GeoTools 2.4
because GeoServer uses that branch. But I would appreciate developping postgrid
against GeoTools trunk if possible (just a wish - I'm unconfortable with hacking
Geotools stable branch for postgrid needs as I'm doing right now, even if most
hacking happen in unsupported modules). If GeoServer trunk get aligned with
GeoTools trunk, it make GeoServer trunk more appealing in that aspect.

The Feature merge is not a risk for postgrid because postgrid is only about
coverages, and coverages are not yet features (I know they should - we will need
to fix that soon or later). However I realize that it could be a risk if we want
to serve both features and coverages in short term - so I'm not pushing for
either solution (I let you guys decide what is more appropriate). Just wanted to
put my 2 cents.

  Cheers,
  Martin

Thanks for the input Martin. So it sounds like you are for developing on
trunk. Let me state that getting GeoServer trunk on geotools trunk is a
pretty easy task. So if that is the only blocker for you guys we can
definitely do this asap.

However, Simone has a good point when he says that the first step will
be just getting the integration stuff down... and that will be a bit
unstable. What I think would be the ideal situation is if you guys could
create very short lived branch or spike to test out the integration
issues. Once you have something that generally works you can merge it
onto trunk and continue to develop there. That would also give us a
chance to branch 1.6.x and get trunk in order.

I know Simone has been opposed to the overhead of working on trunk in
the past but I think it could have benefits for you guys. For one
working on same branch as Andrea and I allows us to help out so if
anything show stopping comes up for you guys we can make it a priority.

Also, we have a decent unit testing framework on trunk now, with a
continuous build server. So when issues do come up we usually catch them
right away. Also, i fear that working on a branch alone has the nasty
side affect of producing no unit tests. Now that we have a decent
framework there is no excuse for not writing test cases.

So what do you think? If people are not opposed perhaps we could come up
with some hard dates to set for the merge. This would give us a target
for getting 1.6-RC1 out the door and creating the 1.6.x branch leaving
trunk open.

-Justin

Martin Desruisseaux wrote:

Just in order to help me to understand, I wonder: would the branch depends on
GeoTools 2.4 or GeoTools trunk? For now postgrid development uses GeoTools 2.4
because GeoServer uses that branch. But I would appreciate developping postgrid
against GeoTools trunk if possible (just a wish - I'm unconfortable with hacking
Geotools stable branch for postgrid needs as I'm doing right now, even if most
hacking happen in unsupported modules). If GeoServer trunk get aligned with
GeoTools trunk, it make GeoServer trunk more appealing in that aspect.

The Feature merge is not a risk for postgrid because postgrid is only about
coverages, and coverages are not yet features (I know they should - we will need
to fix that soon or later). However I realize that it could be a risk if we want
to serve both features and coverages in short term - so I'm not pushing for
either solution (I let you guys decide what is more appropriate). Just wanted to
put my 2 cents.

  Cheers,
  Martin

!DSPAM:4007,4720c23a151461431913854!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Hi guys,
I have given some more thoughts to this issue and I have also talked
to various people involved (not all of them unfortunately did not have
enough time) so I am reporting what seems to be the best solution for
all the involved parties, please correct me if I am wrong.

Here you have the actions we should take:

1>Justin gives commit rights to Cedric Briancon (Cedric check with
him that you have subscribed to XCircles)
2>Alessio creates a branch from the geoserver trunk for the
integration (suggestions for names welcome)
3>Cedric import the code into this branch, please.
4>We have around to weeks to play/integrate our stuff/make new
developement while we stay on a separate branch
5>When Justin and/or Andrea branch 1.6.x and trunk becomes 1.7 we
port the work we have done to trunk and we keep working on both gt and
gs trunk
6>coding, coding, coding.

I hope I didnt' get anything wrong.

Ciao,
Simone.

On 10/25/07, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Thanks for the input Martin. So it sounds like you are for developing on
trunk. Let me state that getting GeoServer trunk on geotools trunk is a
pretty easy task. So if that is the only blocker for you guys we can
definitely do this asap.

However, Simone has a good point when he says that the first step will
be just getting the integration stuff down... and that will be a bit
unstable. What I think would be the ideal situation is if you guys could
create very short lived branch or spike to test out the integration
issues. Once you have something that generally works you can merge it
onto trunk and continue to develop there. That would also give us a
chance to branch 1.6.x and get trunk in order.

I know Simone has been opposed to the overhead of working on trunk in
the past but I think it could have benefits for you guys. For one
working on same branch as Andrea and I allows us to help out so if
anything show stopping comes up for you guys we can make it a priority.

Also, we have a decent unit testing framework on trunk now, with a
continuous build server. So when issues do come up we usually catch them
right away. Also, i fear that working on a branch alone has the nasty
side affect of producing no unit tests. Now that we have a decent
framework there is no excuse for not writing test cases.

So what do you think? If people are not opposed perhaps we could come up
with some hard dates to set for the merge. This would give us a target
for getting 1.6-RC1 out the door and creating the 1.6.x branch leaving
trunk open.

-Justin

Martin Desruisseaux wrote:
> Just in order to help me to understand, I wonder: would the branch depends on
> GeoTools 2.4 or GeoTools trunk? For now postgrid development uses GeoTools 2.4
> because GeoServer uses that branch. But I would appreciate developping postgrid
> against GeoTools trunk if possible (just a wish - I'm unconfortable with hacking
> Geotools stable branch for postgrid needs as I'm doing right now, even if most
> hacking happen in unsupported modules). If GeoServer trunk get aligned with
> GeoTools trunk, it make GeoServer trunk more appealing in that aspect.
>
> The Feature merge is not a risk for postgrid because postgrid is only about
> coverages, and coverages are not yet features (I know they should - we will need
> to fix that soon or later). However I realize that it could be a risk if we want
> to serve both features and coverages in short term - so I'm not pushing for
> either solution (I let you guys decide what is more appropriate). Just wanted to
> put my 2 cents.
>
> Cheers,
> Martin
>
> !DSPAM:4007,4720c23a151461431913854!
>

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

--
-------------------------------------------------------
Eng. Simone Giannecchini
President /CEO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928

http://www.geo-solutions.it

-------------------------------------------------------

2>Alessio creates a branch from the geoserver trunk for the
integration (suggestions for names welcome)

nD branch--what else :stuck_out_tongue:

Alex

A big +1 from me. What you have laid out here sounds perfect simone. As
for getting Cedric commit access to the branch all you have to do is get
him to create his codehaus account. There are some instructions here:

http://docs.codehaus.org/display/GEOSDOC/1+Getting+Commit+Status

Simone Giannecchini wrote:

Hi guys,
I have given some more thoughts to this issue and I have also talked
to various people involved (not all of them unfortunately did not have
enough time) so I am reporting what seems to be the best solution for
all the involved parties, please correct me if I am wrong.

Here you have the actions we should take:

1>Justin gives commit rights to Cedric Briancon (Cedric check with
him that you have subscribed to XCircles)
2>Alessio creates a branch from the geoserver trunk for the
integration (suggestions for names welcome)
3>Cedric import the code into this branch, please.
4>We have around to weeks to play/integrate our stuff/make new
developement while we stay on a separate branch
5>When Justin and/or Andrea branch 1.6.x and trunk becomes 1.7 we
port the work we have done to trunk and we keep working on both gt and
gs trunk
6>coding, coding, coding.

I hope I didnt' get anything wrong.

Ciao,
Simone.

On 10/25/07, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Thanks for the input Martin. So it sounds like you are for developing on
trunk. Let me state that getting GeoServer trunk on geotools trunk is a
pretty easy task. So if that is the only blocker for you guys we can
definitely do this asap.

However, Simone has a good point when he says that the first step will
be just getting the integration stuff down... and that will be a bit
unstable. What I think would be the ideal situation is if you guys could
create very short lived branch or spike to test out the integration
issues. Once you have something that generally works you can merge it
onto trunk and continue to develop there. That would also give us a
chance to branch 1.6.x and get trunk in order.

I know Simone has been opposed to the overhead of working on trunk in
the past but I think it could have benefits for you guys. For one
working on same branch as Andrea and I allows us to help out so if
anything show stopping comes up for you guys we can make it a priority.

Also, we have a decent unit testing framework on trunk now, with a
continuous build server. So when issues do come up we usually catch them
right away. Also, i fear that working on a branch alone has the nasty
side affect of producing no unit tests. Now that we have a decent
framework there is no excuse for not writing test cases.

So what do you think? If people are not opposed perhaps we could come up
with some hard dates to set for the merge. This would give us a target
for getting 1.6-RC1 out the door and creating the 1.6.x branch leaving
trunk open.

-Justin

Martin Desruisseaux wrote:

Just in order to help me to understand, I wonder: would the branch depends on
GeoTools 2.4 or GeoTools trunk? For now postgrid development uses GeoTools 2.4
because GeoServer uses that branch. But I would appreciate developping postgrid
against GeoTools trunk if possible (just a wish - I'm unconfortable with hacking
Geotools stable branch for postgrid needs as I'm doing right now, even if most
hacking happen in unsupported modules). If GeoServer trunk get aligned with
GeoTools trunk, it make GeoServer trunk more appealing in that aspect.

The Feature merge is not a risk for postgrid because postgrid is only about
coverages, and coverages are not yet features (I know they should - we will need
to fix that soon or later). However I realize that it could be a risk if we want
to serve both features and coverages in short term - so I'm not pushing for
either solution (I let you guys decide what is more appropriate). Just wanted to
put my 2 cents.

      Cheers,
      Martin

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira a écrit :

A big +1 from me. What you have laid out here sounds perfect simone. As
for getting Cedric commit access to the branch all you have to do is get
him to create his codehaus account. There are some instructions here:

http://docs.codehaus.org/display/GEOSDOC/1+Getting+Commit+Status

Hi all,
I've created an account on Codehaus (login cedricbr) and try to join the Geoserver project as a developer in the xircles website :slight_smile:
I'm waiting for the final validation of my commits rights.

Thanks :slight_smile:
Cédric B.

Simone Giannecchini wrote:
  

Hi guys,
I have given some more thoughts to this issue and I have also talked
to various people involved (not all of them unfortunately did not have
enough time) so I am reporting what seems to be the best solution for
all the involved parties, please correct me if I am wrong.

Here you have the actions we should take:

1>Justin gives commit rights to Cedric Briancon (Cedric check with
him that you have subscribed to XCircles)
2>Alessio creates a branch from the geoserver trunk for the
integration (suggestions for names welcome)
3>Cedric import the code into this branch, please.
4>We have around to weeks to play/integrate our stuff/make new
developement while we stay on a separate branch
5>When Justin and/or Andrea branch 1.6.x and trunk becomes 1.7 we
port the work we have done to trunk and we keep working on both gt and
gs trunk
6>coding, coding, coding.

I hope I didnt' get anything wrong.

Ciao,
Simone.

On 10/25/07, Justin Deoliveira <jdeolive@anonymised.com> wrote:
    

Thanks for the input Martin. So it sounds like you are for developing on
trunk. Let me state that getting GeoServer trunk on geotools trunk is a
pretty easy task. So if that is the only blocker for you guys we can
definitely do this asap.

However, Simone has a good point when he says that the first step will
be just getting the integration stuff down... and that will be a bit
unstable. What I think would be the ideal situation is if you guys could
create very short lived branch or spike to test out the integration
issues. Once you have something that generally works you can merge it
onto trunk and continue to develop there. That would also give us a
chance to branch 1.6.x and get trunk in order.

I know Simone has been opposed to the overhead of working on trunk in
the past but I think it could have benefits for you guys. For one
working on same branch as Andrea and I allows us to help out so if
anything show stopping comes up for you guys we can make it a priority.

Also, we have a decent unit testing framework on trunk now, with a
continuous build server. So when issues do come up we usually catch them
right away. Also, i fear that working on a branch alone has the nasty
side affect of producing no unit tests. Now that we have a decent
framework there is no excuse for not writing test cases.

So what do you think? If people are not opposed perhaps we could come up
with some hard dates to set for the merge. This would give us a target
for getting 1.6-RC1 out the door and creating the 1.6.x branch leaving
trunk open.

-Justin

Martin Desruisseaux wrote:
      

Just in order to help me to understand, I wonder: would the branch depends on
GeoTools 2.4 or GeoTools trunk? For now postgrid development uses GeoTools 2.4
because GeoServer uses that branch. But I would appreciate developping postgrid
against GeoTools trunk if possible (just a wish - I'm unconfortable with hacking
Geotools stable branch for postgrid needs as I'm doing right now, even if most
hacking happen in unsupported modules). If GeoServer trunk get aligned with
GeoTools trunk, it make GeoServer trunk more appealing in that aspect.

The Feature merge is not a risk for postgrid because postgrid is only about
coverages, and coverages are not yet features (I know they should - we will need
to fix that soon or later). However I realize that it could be a risk if we want
to serve both features and coverages in short term - so I'm not pushing for
either solution (I let you guys decide what is more appropriate). Just wanted to
put my 2 cents.

      Cheers,
      Martin

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Cédric Briançon ha scritto:

Justin Deoliveira a écrit :

A big +1 from me. What you have laid out here sounds perfect simone. As
for getting Cedric commit access to the branch all you have to do is get
him to create his codehaus account. There are some instructions here:

http://docs.codehaus.org/display/GEOSDOC/1+Getting+Commit+Status

Hi all,
I've created an account on Codehaus (login cedricbr) and try to join the Geoserver project as a developer in the xircles website :slight_smile:
I'm waiting for the final validation of my commits rights.

I accepted you as a GeoServer developer.
Can you check if you can do any commit? (create a test file,
commit it, and then remove it)

Cheers
Andrea

You should be good to go now Cedric.

Cédric Briançon wrote:

Justin Deoliveira a écrit :

A big +1 from me. What you have laid out here sounds perfect simone. As
for getting Cedric commit access to the branch all you have to do is get
him to create his codehaus account. There are some instructions here:

http://docs.codehaus.org/display/GEOSDOC/1+Getting+Commit+Status

Hi all,
I've created an account on Codehaus (login cedricbr) and try to join the
Geoserver project as a developer in the xircles website :slight_smile:
I'm waiting for the final validation of my commits rights.

Thanks :slight_smile:
Cédric B.

Simone Giannecchini wrote:
  

Hi guys,
I have given some more thoughts to this issue and I have also talked
to various people involved (not all of them unfortunately did not have
enough time) so I am reporting what seems to be the best solution for
all the involved parties, please correct me if I am wrong.

Here you have the actions we should take:

1>Justin gives commit rights to Cedric Briancon (Cedric check with
him that you have subscribed to XCircles)
2>Alessio creates a branch from the geoserver trunk for the
integration (suggestions for names welcome)
3>Cedric import the code into this branch, please.
4>We have around to weeks to play/integrate our stuff/make new
developement while we stay on a separate branch
5>When Justin and/or Andrea branch 1.6.x and trunk becomes 1.7 we
port the work we have done to trunk and we keep working on both gt and
gs trunk
6>coding, coding, coding.

I hope I didnt' get anything wrong.

Ciao,
Simone.

On 10/25/07, Justin Deoliveira <jdeolive@anonymised.com> wrote:
    

Thanks for the input Martin. So it sounds like you are for developing on
trunk. Let me state that getting GeoServer trunk on geotools trunk is a
pretty easy task. So if that is the only blocker for you guys we can
definitely do this asap.

However, Simone has a good point when he says that the first step will
be just getting the integration stuff down... and that will be a bit
unstable. What I think would be the ideal situation is if you guys could
create very short lived branch or spike to test out the integration
issues. Once you have something that generally works you can merge it
onto trunk and continue to develop there. That would also give us a
chance to branch 1.6.x and get trunk in order.

I know Simone has been opposed to the overhead of working on trunk in
the past but I think it could have benefits for you guys. For one
working on same branch as Andrea and I allows us to help out so if
anything show stopping comes up for you guys we can make it a priority.

Also, we have a decent unit testing framework on trunk now, with a
continuous build server. So when issues do come up we usually catch them
right away. Also, i fear that working on a branch alone has the nasty
side affect of producing no unit tests. Now that we have a decent
framework there is no excuse for not writing test cases.

So what do you think? If people are not opposed perhaps we could come up
with some hard dates to set for the merge. This would give us a target
for getting 1.6-RC1 out the door and creating the 1.6.x branch leaving
trunk open.

-Justin

Martin Desruisseaux wrote:
      

Just in order to help me to understand, I wonder: would the branch depends on
GeoTools 2.4 or GeoTools trunk? For now postgrid development uses GeoTools 2.4
because GeoServer uses that branch. But I would appreciate developping postgrid
against GeoTools trunk if possible (just a wish - I'm unconfortable with hacking
Geotools stable branch for postgrid needs as I'm doing right now, even if most
hacking happen in unsupported modules). If GeoServer trunk get aligned with
GeoTools trunk, it make GeoServer trunk more appealing in that aspect.

The Feature merge is not a risk for postgrid because postgrid is only about
coverages, and coverages are not yet features (I know they should - we will need
to fix that soon or later). However I realize that it could be a risk if we want
to serve both features and coverages in short term - so I'm not pushing for
either solution (I let you guys decide what is more appropriate). Just wanted to
put my 2 cents.

      Cheers,
      Martin

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:4007,47221aa388053668746562!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira a écrit :

You should be good to go now Cedric.

He just went away for the weekend. More news Monday I guess. Thanks for doing that!

  Martin

Hi all guys … so … I’m going to branch GeoServer, is it ok? Can I proceed?

On 10/26/07, Martin Desruisseaux < martin.desruisseaux@anonymised.com> wrote:

Justin Deoliveira a écrit :

You should be good to go now Cedric.

He just went away for the weekend. More news Monday I guess. Thanks for doing that!

Martin


This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it


Alessio Fabiani ha scritto:

Hi all guys .... so ... I'm going to branch GeoServer, is it ok? Can I proceed?

Go! :slight_smile:
Cheers
Andrea

Branch done
https://svn.codehaus.org/geoserver/branches/1.6.x-Cov-nD/

Cedric, let me know when you have committed your work so we can start coding together :slight_smile:

Cheers,
Alessio.

On 10/29/07, Andrea Aime <aaime@anonymised.com> wrote:

Alessio Fabiani ha scritto:

Hi all guys … so … I’m going to branch GeoServer, is it ok? Can I
proceed?

Go! :slight_smile:
Cheers
Andrea

Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it


Alessio Fabiani a écrit :

Branch done
https://svn.codehaus.org/geoserver/branches/1.6.x-Cov-nD/

Cedric, let me know when you have committed your work so we can start coding together :slight_smile:

I will do a first commit in a few moment.

I've three things to say about this code :
1) There are some calls to methods that are stored on another SVN (the Seagis project on Sourceforge). I've used a reflexive way in order to call these methods, because the two projects Geoserver and Seagrid are separated, and I didn't want to make these projects related up to now. The coming work on this branch will regroup this two projects in a same place, reflexions will be replaced by direct calls :slight_smile:

2) The PostGrid coverage reader is stored on the Seagis SVN. A link to this SVN will be done, in order to provide you the code for this reader.

3) Since the "TIME" and "ELEVATION" parameters are not well caught in the StreamingRenderer class of Geotools, I've added some code in this class in order to give them to the reader by the array of GeneralParameterValue. In fact the StreamingRenderer class is the one which creates this array, with the parameters given in a GetMap request. This code is needed if we want to use the nD possibilities of WMS. I can probably open a jira-task or something like that for the Geotools project ...

Since I'm quite busy today (sigh :frowning: I've something I must finish as quick as possible ...), I will do a first commit of all the changes I've done in my local version of Geoserver. Others commits about PostGrid will come in one or two days ...

Cheers,
Cédric B.

Cheers,
         Alessio.

On 10/29/07, *Andrea Aime* <aaime@anonymised.com <mailto:aaime@anonymised.com>> wrote:

    Alessio Fabiani ha scritto:
    > Hi all guys .... so ... I'm going to branch GeoServer, is it ok?
    Can I
    > proceed?

    Go! :slight_smile:
    Cheers
    Andrea

--
-------------------------------------------------------
Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

-------------------------------------------------------
------------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel