Hallo,
I did the "KML Placemark Templates" example
(http://docs.codehaus.org/display/GEOSDOC/KML+Placemark+Templates). In
Google earth everything works fine. Now I made a small openlayers page with
a getfeatureinfo. So I can quote data by using Geoserver`s WMS. When I try
to use the the same template as in Google Earth, I get in the openlayers
page following error: Unable to generate information
java.lang.NullPointerException
Is it possible to use generated templates in the same way as in the Google
Earth example? What must I change?
By the way, I use Geoserver 1.6.0 beta
Hallo,
I did the "KML Placemark Templates" example
(http://docs.codehaus.org/display/GEOSDOC/KML+Placemark+Templates). In
Google earth everything works fine. Now I made a small openlayers page with
a getfeatureinfo. So I can quote data by using Geoserver`s WMS. When I try
to use the the same template as in Google Earth, I get in the openlayers
page following error: Unable to generate information
java.lang.NullPointerException
Is it possible to use generated templates in the same way as in the Google
Earth example? What must I change?
By the way, I use Geoserver 1.6.0 beta
I think you just hit against http://jira.codehaus.org/browse/GEOS-1188, which I fixed yesterday. If you're interested, you can try out a nightly
from here: http://geo.openplans.org/nightly/trunk/
As for the template, you can of course change it, it's just a matter
of knowing what's the name of the template you have to use.
so if you want to change GetFeatureInfo, I guess you just
have to provide both of them in the directory of the feature
type of your choice or, if you want to change them globally,
on the featuretypes directory. Yet, I haven't double checked
these details, so maybe Justin can provide you with some more
information (I've cc'ed him).
so if you want to change GetFeatureInfo, I guess you just
have to provide both of them in the directory of the feature
type of your choice or, if you want to change them globally,
on the featuretypes directory. Yet, I haven't double checked
these details, so maybe Justin can provide you with some more
information (I've cc'ed him).
Well my understanding is that templates for description and title have not been hooked up to the GetFeatureInfo operation yet... Although I understand the confusion as they are in the same directory as the rest of the GetFeatureInfo code.
The ideal would be able to change the two templates (description/title) and have them apply directly to kml,georss, and getfeatureinfo (html format). However the problem is that in the former two the template is setup to handle a single feature at a time. Whereas the latter must be able to handle multiple features at a time, possibly of different feature types...
So we are stuck with a trade off:
1. We make the template model more complex which makes it harder for the user to create custom templates or:
2. We separate kml + georss from getfeatureinfo which also puts a burden on the template writer to possibly maintain two different templates to convey the same information...
Tough one.
-Justin
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Well my understanding is that templates for description and title have not been hooked up to the GetFeatureInfo operation yet... Although I understand the confusion as they are in the same directory as the rest of the GetFeatureInfo code.
The ideal would be able to change the two templates (description/title) and have them apply directly to kml,georss, and getfeatureinfo (html format). However the problem is that in the former two the template is setup to handle a single feature at a time. Whereas the latter must be able to handle multiple features at a time, possibly of different feature types...
So we are stuck with a trade off:
1. We make the template model more complex which makes it harder for the user to create custom templates or:
2. We separate kml + georss from getfeatureinfo which also puts a burden on the template writer to possibly maintain two different templates to convey the same information...
Well, having separate templates allows people to have different renderings for KML and GetFeatureInfo, which is good imho since they
are two different contexts (graphically speaking, they may ask for
differently looking layouts and colours).