Hi,
I would like to create a sample data directory for WPS somewhere.
It would be a svn copy of the release one, without a few data sets
and with demo requests geared towards WPS.
Is it ok if I add it to SVN? If so, where? /configuration?
Or since WPS is still community, better add it inside the WPS
module itself? (community/wps/configuration)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Hi Andrea,
+1, but also a suggestion. Are you planning to use svn:externals to reference the parts of the release data dir you want to re-use. Or are you thinking of just a straight copy?
FYI I did this for the the various h2 data directories and it works pretty well.
-Justin
Andrea Aime wrote:
Hi,
I would like to create a sample data directory for WPS somewhere.
It would be a svn copy of the release one, without a few data sets
and with demo requests geared towards WPS.Is it ok if I add it to SVN? If so, where? /configuration?
Or since WPS is still community, better add it inside the WPS
module itself? (community/wps/configuration)Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi Andrea,
+1, but also a suggestion. Are you planning to use svn:externals to reference the parts of the release data dir you want to re-use. Or are you thinking of just a straight copy?
FYI I did this for the the various h2 data directories and it works pretty well.
I was planning on a straight copy. Copies are cheap, handling all
the externals seems more work for... nothing? For example, what if
I want to add some extra data? To allow for that I would have to
use as externals only small sub-parts of the configuration, for example,
data/nyc but not data, and featureTypes/states but not featureTypes...
What are the extra advantages of svn:external over a plain copy (if
you don't plan to exactly mirror what you're copying)?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I was planning on a straight copy. Copies are cheap, handling all
the externals seems more work for... nothing?
Are copies of binary data cheap? My understanding is that when it comes to binary data all the fancy tricks go out the window.
But yeah, I guess past that the only benefit is keeping things in sync. Like if we change some data in the release config it gets propogated without any additional work.
Anyways, I don't have a strong opinion. Do whatever you feel is right :).
For example, what if
I want to add some extra data? To allow for that I would have to
use as externals only small sub-parts of the configuration, for example,
data/nyc but not data, and featureTypes/states but not featureTypes...What are the extra advantages of svn:external over a plain copy (if
you don't plan to exactly mirror what you're copying)?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
I was planning on a straight copy. Copies are cheap, handling all
the externals seems more work for... nothing?Are copies of binary data cheap? My understanding is that when it comes to binary data all the fancy tricks go out the window.
No, because the svn copy would just create a copy to the diff list of
the binary data, so it's cheap no matter how you slice it.
The fancy tricks going out of the window are just the binary diff, which
is there, but not particularly efficient. That is what I know, at least.
But yeah, I guess past that the only benefit is keeping things in sync. Like if we change some data in the release config it gets propogated without any additional work.
Anyways, I don't have a strong opinion. Do whatever you feel is right :).
Cool, I guess I'll create the configuraiton in the wps module to avoid
getting in the way. When we start shipping wps we may be so lucky to
have pluggable demos and the data dir issue may go away, replaced by
a wps-demo-release plugin.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.