[webmap-discuss] Re: Strategic Direction
Paul Spencer
pspencer at dmsolutions.ca
Thu Sep 21 21:45:09 EDT 2006
http://wiki.osgeo.org/index.php/Choosing_a_Web_Mapping_Platform
Please feel free to edit to your hearts content ... alternate views
of the universe would also be welcome, as well as any changes in
wording, grammer, content etc.
Any projects missing from the matrix need to add themselves.
All projects should come up with a blurb about the project and its
main benefits/drawbacks that would help a potential new user (or even
an existing one) select an appropriate project for a new application
Cheers
Paul
On 21-Sep-06, at 5:02 PM, Cameron Shorter wrote:
> This thread has become more about WebMap.js and so I'm moving it to
> the webmap list, (and will start a "What sucks about Mapbuilder"
> thread for the mapbuilder list.
>
> Thanks all for filling me in, as I wasn't at FOSS4G I'm playing
> catchup.
>
> Paul, I don't understand what your definition of Managed and
> Unmanaged. Could you please expand.
>
> Paul, I like your ASCII art, we should put it into a graphic
> somewhere to help users pick a suitable webmapping client. Maybe on
> an OSGeo page titled "Picking a suitable Webmapping client".
>
> FYI: There is a cool ASCII art program at http://www.jave.de/
>
> Paul Spencer wrote:
>> I'd have to agree with Schuyler. Each project has a different
>> underlying philosophy ... To help me understand it, I've divided
>> them into four groups - two categories with two sub-categories.
>> First category is how the template is done. Second is how the
>> maps are created/used.
>> Templating can be managed or unmanaged
>> Maps can be client side (direct from OGC services) or server side
>> (rendered by MapServer/MapGuide)
>> The divisions are not precise, obviously! Here is my horrible
>> attempt at ASCII art ...
>> managed | unmanaged
>> |
>> mapbender | mapbuilder
>> client | OpenLayers (2)
>> |
>> -----------
>> -----------------| WebMap.js |------------
>> -----------
>> |
>> | chameleon
>> server mapguide | ka-map (1)
>> |
>> |
>> (1) ka-Map is actually a client side app and can do client-side
>> direct from WMS but its not the primary mechanism and the default
>> install requires a server side component.
>> (2) OpenLayers can do server-side from ka-Map, but its not the
>> primary mechanism
>> Not sure where cartoweb fits in the picture, I don't know much
>> about it. And I probably missed some ... not sure which.
>> In my view of the world, then, the AJAX BOF was discussing
>> something that could easily fit into the center of this
>> diagram ... this is the proposed WebMap.js.
>> So we end up with each project owning and promoting a particular
>> space in my view of the AJAX web mapping world. I think there
>> are benefits and drawbacks to each space and its excellent to be
>> able to chose a different solution for any given client based on
>> what they really need.
>> Cheers
>> Paul
>> On 21-Sep-06, at 5:39 AM, Schuyler Erle wrote:
>>> * On 18-Sep-2006 at 4:30PM EDT, Cameron Shorter said:
>>>
>>>>
>>>> There are a number of AJAX Web Mapping clients and not all of
>>>> them will
>>>> thrive. In particular, OpenLayers is addressing the simple
>>>> mapping use
>>>> cases and is cutting into Mapbuilder's potential user base. We
>>>> should
>>>> set our development path toward merging with OpenLayers.
>>>
>>>
>>> Well, I hope we're not cutting into each other's user bases, so much
>>> as serving somewhat different use cases in the same general sphere.
>>>
>>> At the FOSS4G conference in Lausanne last week, we had a web mapping
>>> client BoF session, in which it was agreed that the OpenLayers team
>>> should try to split off a basic core for fetching map images/
>>> tiles and
>>> displaying them in an HTML div.
>>>
>>> Our hope is that our fellow AJAX mapping projects will be able to
>>> incorporate this map display library in their code, providing us all
>>> with a common stable base on which to build better web mapping apps.
>>> Provisionally, we've been calling this code "Webmap.js" (or
>>> something
>>> similar).
>>>
>>> In the meantime, we would appreciate any kind of direction that
>>> Mapbuilder and the other AJAX mapping projects have to offer about
>>> what the shape of this shared map display core should look like. Our
>>> plan is to have a rough cut of the library available in the next
>>> couple weeks.
>>>
>>> I think this is a very exciting opportunity for all of us to
>>> collaborate, and I hope that we can make it work for everyone!
>>>
>>> SDE
>>>
>>> --------------------------------------------------------------------
>>> -- ---
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance
>>> to share your
>>> opinions on IT & business topics through brief surveys -- and
>>> earn cash
>>> http://www.techsay.com/default.php?
>>> page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> mapbuilder-devel mailing list
>>> mapbuilder-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
>> +-----------------------------------------------------------------+
>> |Paul Spencer pspencer at dmsolutions.ca |
>> +-----------------------------------------------------------------+
>> |Chief Technology Officer |
>> |DM Solutions Group Inc http://www.dmsolutions.ca/|
>> +-----------------------------------------------------------------+
>
>
> --
> Cameron Shorter
> http://cameron.shorter.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webmap-discuss-unsubscribe at mail.osgeo.org
> For additional commands, e-mail: webmap-discuss-help at mail.osgeo.org
>
+-----------------------------------------------------------------+
|Paul Spencer pspencer at dmsolutions.ca |
+-----------------------------------------------------------------+
|Chief Technology Officer |
|DM Solutions Group Inc http://www.dmsolutions.ca/|
+-----------------------------------------------------------------+
More information about the Webmap-discuss
mailing list