|
From: Peter S. <co...@pe...> - 2007-07-11 10:50:05
|
Hi Roberto, Your question whether we should use region or placemark, makes me think we should generalize this even more. Cause we really want to be able to use everything. The objects might be fixed, but also moving - so the kml must be customizable. So my question is: - Would it be possible to create a report template that produces xml (which in this case will be kml)? - The kml url mention earlier, will then instead of being kml specific, be mapped to a report - so that you can get a report (with any template) on the fly just using a url. How would this be? regards, Peter On Tuesday 10 July 2007 16:58:18 you wrote: > Hi Peter, > > Yes, I started looking into the google-map integration. > > The approach to this task would be to create e a servlet with *.kml > mapping. The request with > http://lmappletserver.lightminds.com/lmas-addons-example/ > kml/mysearch.kml<http://lmappletserver.lightminds.com/lmas-addons-example/k >ml/mysearch.kml>, that mysearch will be the saved search name, this I think > is the best because the Saved search name is unique, and can be used as > identifier. When the servlet is called and executes the saved search a > transformer class will create the mysearch.kml content string from the > result of the search. Then this string will be sent to the client as output > stream. At this moment I look at two approaches, and I would like for you > to tell which one to use, first one is to use the Placemark tag to create a > yellow pin(in Google Earth), and lead the user to that spot. This is done > by kml like this: > > <?xml version="1.0" encoding="UTF-8"?> > <kml xmlns="http://earth.google.com/kml/2.1"> > <Placemark> > <name>Macky Auditorium</name> > <description>University of Colorado.</description> > <LookAt> > <longitude>-105.2727379358738</longitude> > <latitude>40.01000594412381</latitude> > <altitude>0</altitude> > <range>127.2393107680517</range> > <tilt>65.74454495876547</tilt> > <heading>-27.70337734057933</heading> > </LookAt> > </Placemark> > </kml> > > Or we can use the Region tag, and show regions of the airport, and be > visible only when the user reaches certain zooming resolution. This is done > by kml like this: > > <?xml version="1.0" encoding="UTF-8"?> > <kml xmlns="http://earth.google.com/kml/2.1"> > <Document> > <name>romania Document</name> > <Region> > <LatLonAltBox> > <north>50.625</north> > <south>45</south> > <east>28.125</east> > <west>22.5</west> > </LatLonAltBox> > <Lod> > <minLodPixels>128</minLodPixels> > <maxLodPixels>1024</maxLodPixels> > </Lod> > </Region> > </Document> > </kml> > > Here because of the fact that in the current database we have only > latitude, longitude and altitude we have to make coordinate transformation, > therefore I think that this approach is not appropriate for our > application. > > Regards, > Roberto > > On 7/9/07, Peter Salomonsen <co...@pe...> wrote: > > Hi, > > > > This and the checkbox scrollbar looks good as far as I can see.. > > > > Have you looked into the google-map (kml) integration? > > > > regards, > > > > Peter > > > > On Sunday 08 July 2007 17:59:30 you wrote: > > > Hi Peter, > > > > > > The change to display the metadatacolumn name is no key exists in > > > property file is commited. Additionally I did anothetr small change to > > > display the localized strings in the search combo box. > > > > > > Regards, > > > Roberto > > > > > > Peter Salomonsen wrote: > > > > Hi Roberto, > > > > > > > > The new MetaDataColumnNames.properties file works just perfect. Could > > > > we > > > > > > also extend it so that if a key doesn't exist, the metadatacolumn > > > > name > > > > is > > > > > > showed directly? > > > > > > > > regards, > > > > > > > > Peter |