Chris said:
Would be cool if we could also have more 'traditional' templates,
that one could add on the config >>side and just reference the name
instead of sending the xslt.
Then you might want to take a look at our outputFormats definition.
Our goal with the protocol was to allow users to define the way they
wanted the data to go back. The idea is that the provider, the one
setting up the server, maps his database to a well known ontology,
schema or control vocabulary and then users query these providers
giving them a mapping from this well known stuff to their own XML
format. We analyzed several mapping languages and finally created our
own one (aghh).
Our scenarios are a little bit different to the ones I see with
geoserver but maybe something could be considered. At least we can
advice you with some possibilities we found.
In our case, the templates, or outputFormat as we call it, are
something that you send to a server that you do not control. So we
have something like a double mapping, the user map his outputFormat to
the well known Format and the server maps his database to this Well
known Format.
Because of this we have a little bit more complicated than needed
mapping language that has the notion of objects and relations (is
complicate to explain this briefly).
But for geoserver it could be enough to implement a templating
language, there are hundreds out there for every different programming
language. My favorite one is KID for Python. The templates are really
flexible and they are valid xml themselves, then it has processors
that produces valid XHTML or even crappy HTML totally compatible with
1.0 browsers 
But at the end there are a lot of tools already available for XSLT and
users do not wanna have to learn a new thing in every program they
use.
What are your ideas for 1.4? I am really curious now 
Javier.
What are your ideas for 1.4? I am really curious now
Well, it's actually far past the idea stage and mostly implemented. There's a 1.4.0M0 release, and an RC should be coming shortly. It's more of an evolutionary change than a revolutionary one, a move to being more of a framework, making use of Spring.
See: http://docs.codehaus.org/display/GEOSDEV/Framework+Planning
http://docs.codehaus.org/display/GEOSDEV/Spring+proposal
and
http://docs.codehaus.org/display/GEOSDEV/Springing+GeoServer
for more information. There's also a sample of bundling your own application: http://docs.codehaus.org/display/GEOSDEV/3+Bundling+your+Plugin
Chris
Javier.
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
!DSPAM:1003,449828a0224221116498154!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Hi all,
I put myself into this discussion to make on "additional WMS GetFeatureInfo
question":
I'm making AJAX GetFeatureInfo requests to retrieve point-value on many
GeoTiff layers, grouped ad hoc into a LayerGroup in GeoServer.
Since it takes several seconds to achieve a response (let's say, 45 s for a
group of 500 layers), I would like to know whether this is the right
solution, or if I missed some other trick to make things faster.
I read from this topic about using WFS but this is not vector data, up to
now...
Thank you for any clues.
Piero
--
View this message in context: http://old.nabble.com/Additional-WMS-GetFeatureInfo-questions-tp4891494p30347998.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
On Wed, Dec 1, 2010 at 12:21 PM, Piero Campa <piero.campa@anonymised.com> wrote:
Hi all,
I put myself into this discussion to make on "additional WMS GetFeatureInfo
question":
I'm making AJAX GetFeatureInfo requests to retrieve point-value on many
GeoTiff layers, grouped ad hoc into a LayerGroup in GeoServer.
Since it takes several seconds to achieve a response (let's say, 45 s for a
group of 500 layers), I would like to know whether this is the right
solution, or if I missed some other trick to make things faster.
500 stacked layers is... insane. Would make any map completely unreadable.
Unless, you're misusing the layer group for a mosaic of images: in that
case you should configure an image mosaic instead, just one layer for
all the files you want.
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------
Thank you Andrea, you're always there, I appreciate.
So you're saying that if I make a GetFeatureInfo on the single ImageMosaic
(of 500 layers) get things much faster?
Keeping in count that the mosaic would be created dynamically via HTTP REST
calls.
Anyway, I will try this solution (maybe not in the immediate future), and
report the differences in response times.
Cheers,
Piero
Andrea Aime-5 wrote:
On Wed, Dec 1, 2010 at 12:21 PM, Piero Campa <piero.campa@anonymised.com>
wrote:
Hi all,
I put myself into this discussion to make on "additional WMS
GetFeatureInfo
question":
I'm making AJAX GetFeatureInfo requests to retrieve point-value on many
GeoTiff layers, grouped ad hoc into a LayerGroup in GeoServer.
Since it takes several seconds to achieve a response (let's say, 45 s for
a
group of 500 layers), I would like to know whether this is the right
solution, or if I missed some other trick to make things faster.
500 stacked layers is... insane. Would make any map completely unreadable.
Unless, you're misusing the layer group for a mosaic of images: in that
case you should configure an image mosaic instead, just one layer for
all the files you want.
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://old.nabble.com/Additional-WMS-GetFeatureInfo-questions-tp4891494p30348830.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
On Wed, Dec 1, 2010 at 2:20 PM, Piero Campa <piero.campa@anonymised.com> wrote:
Thank you Andrea, you're always there, I appreciate.
So you're saying that if I make a GetFeatureInfo on the single ImageMosaic
(of 500 layers) get things much faster?
It would be basically instant.
Keeping in count that the mosaic would be created dynamically via HTTP REST
calls.
Hmmm... I don't see how the way the mosaic is created would affect the
response times.
Do you need to add tiles to the mosaic dynamically?
If so not sure the REST api is sufficient.
Simone and Daniele should know more about updating mosaics over time
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------
Hi Andrea,
On 2 December 2010 14:59, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Wed, Dec 1, 2010 at 2:20 PM, Piero Campa <piero.campa@anonymised.com> wrote:
Thank you Andrea, you’re always there, I appreciate.
So you’re saying that if I make a GetFeatureInfo on the single ImageMosaic
(of 500 layers) get things much faster?
It would be basically instant.
Oh my God! This is a huge change in performances. !
(Thank you Simone for creating this plugin)
Keeping in count that the mosaic would be created dynamically via HTTP REST
calls.
Hmmm… I don’t see how the way the mosaic is created would affect the
response times.
Do you need to add tiles to the mosaic dynamically?
If so not sure the REST api is sufficient.
Simone and Daniele should know more about updating mosaics over time
Well, being the response almost immediate, I can now manage things offline, without dynamically create groups/mosaics.
However it can be useful to know whether a client could manage mosaics dynamically via REST, so any help is appreciated.
Thanks so much for the help.
Piero
Cheers
Andrea
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
I’m making some trial with ImageMosaic plugin: the GetFeatureInfo returns the value of ONE layer only, probably the one in the front.
Is it right or am I making some sort of mistake?
My purpose is to receive N feature values if N layers overlap on that pixel. !
Is there a configuration chance for ImageMosaic in this case?
Piero
On 2 December 2010 15:13, Piero Campalani <piero.campa@anonymised.com> wrote:
Hi Andrea,
On 2 December 2010 14:59, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Wed, Dec 1, 2010 at 2:20 PM, Piero Campa <piero.campa@anonymised.com> wrote:
Thank you Andrea, you’re always there, I appreciate.
So you’re saying that if I make a GetFeatureInfo on the single ImageMosaic
(of 500 layers) get things much faster?
It would be basically instant.
Oh my God! This is a huge change in performances. !
(Thank you Simone for creating this plugin)
Keeping in count that the mosaic would be created dynamically via HTTP REST
calls.
Hmmm… I don’t see how the way the mosaic is created would affect the
response times.
Do you need to add tiles to the mosaic dynamically?
If so not sure the REST api is sufficient.
Simone and Daniele should know more about updating mosaics over time
Well, being the response almost immediate, I can now manage things offline, without dynamically create groups/mosaics.
However it can be useful to know whether a client could manage mosaics dynamically via REST, so any help is appreciated.
Thanks so much for the help.
Piero
Cheers
Andrea
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
On Thu, Dec 2, 2010 at 6:48 PM, Piero Campalani <piero.campa@anonymised.com> wrote:
I'm making some trial with ImageMosaic plugin: the GetFeatureInfo returns
the value of ONE layer only, probably the one in the front.
Is it right or am I making some sort of mistake?
My purpose is to receive N feature values if N layers overlap on that pixel.
!
Is there a configuration chance for ImageMosaic in this case?
None, the mosaic turns the n images into one.
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------