Hi Paul!<br><br>I thought I remembered seeing this subject line a few months ago... <br><br>I just wanted to quickly reply to let y'all know how I've been using ka-map lately. <br><br>Because I already had a prototype system running on ka-map, when I completed implementing our custom WMS / WCS, I found it to be rather convenient to use the same user interface, but to use wmsLayer.js instead, adding some modifications to make it work with a TIME parameter. Because my tiles were coming from a separate WMS, I was able to bypass the php tiling system and I ended up with a pure javascript client.<br>
<br>In retrospect, I would probably use MapBuilder / OpenLayers for building my web GUI... but what I have now is working out alright. As soon as I have everything cleaned up, and when my system is running on a public server I'll be happy to share the code.<br>
<br>Thanks for initiating this discussion (again)!<br><br>Sam<br><br><br><br><div class="gmail_quote">On Wed, May 7, 2008 at 6:53 AM, Paul Spencer <<a href="mailto:pspencer@dmsolutions.ca">pspencer@dmsolutions.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
just wondering what, if anything, people are planning to do with ka-Map these days. I have a feeling that most developer efforts are, in fact, going into OpenLayers. However, ka-Map has a few features that are appealing to some folks and are not served by OpenLayers:<br>
<br>
1) server-side configuration without changing the client side<br>
2) written in php<br>
3) tile creation/management<br>
<br>
I think it may be useful to pull out portions of ka-Map's server side stuff, clean it up and add some new features, and provide more direct support for OpenLayers. I'm not entirely sure what this would look like but it may be something like:<br>
<br>
* a php-based configuration file similar to the existing config.php for specifying various options and identifying maps and tile caches<br>
* a php-based tile engine similar to the existing tile.php for dynamically serving tiles from a cache and rendering them as necessary<br>
* a php-based tool that returns javascript or json to the client with an appropriately configured layer(s) (all the settings for the layer are taken from the configuration of the cache and other settings)<br>
* a client-side way of using the javascript or json from the server-side - could be as simple as including a script tag after OpenLayers.js or an entirely new Control or add-in for OpenLayers.<br>
<br>
This would focus efforts on improving tile.php rendering, tile management tools such as precache.php, and cleaning up that code while leaving the javascript stuff to OpenLayers.<br>
<br>
Comments?<br>
<br>
__________________________________________<br>
<br>
Paul Spencer<br>
Chief Technology Officer<br>
DM Solutions Group Inc<br>
<a href="http://www.dmsolutions.ca/" target="_blank">http://www.dmsolutions.ca/</a><br>
<br>
_______________________________________________<br>
ka-Map-dev mailing list<br>
<a href="mailto:ka-Map-dev@lists.maptools.org" target="_blank">ka-Map-dev@lists.maptools.org</a><br>
<a href="http://lists.maptools.org/mailman/listinfo/ka-map-dev" target="_blank">http://lists.maptools.org/mailman/listinfo/ka-map-dev</a><br>
</blockquote></div><br>