[ka-Map-dev] future of ka-Map

[Samuel Hiatt]

Hi Paul!

I thought I remembered seeing this subject line a few months ago...

I just wanted to quickly reply to let y'all know how I've been using ka-map
lately.

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.

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.

Thanks for initiating this discussion (again)!

Sam



On Wed, May 7, 2008 at 6:53 AM, Paul Spencer <pspencer at dmsolutions.ca>
wrote:

> Hi,
>
> 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:
>
> 1) server-side configuration without changing the client side
> 2) written in php
> 3) tile creation/management
>
> 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:
>
> * a php-based configuration file similar to the existing config.php for
> specifying various options and identifying maps and tile caches
> * a php-based tile engine similar to the existing tile.php for dynamically
> serving tiles from a cache and rendering them as necessary
> * 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)
> * 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.
>
> 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.
>
> Comments?
>
> __________________________________________
>
>   Paul Spencer
>   Chief Technology Officer
>   DM Solutions Group Inc
>   http://www.dmsolutions.ca/
>
> _______________________________________________
> ka-Map-dev mailing list
> ka-Map-dev at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/ka-map-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/ka-map-dev/attachments/20080507/93479a67/attachment.html