if you are interested in Google Maps + MapServer, take a look at <http://ecoservices.eidesis.org>
On 2/8/07, Bradley Mclain <[EMAIL PROTECTED]> wrote:
Well I decided to give Openlayers a go and so far ive tried setting up the Mapfiel for WMS support and I've attached what I've done so far I've got no idea whether or not this is right but can you take a look and see. Also how do I setup open layer I simply pasted the lib directory files into my apache lib directory and then the .js file from build into the apache build directory is this correct? If so, how do I go about calling the map file into openlayers? Brad >From: Gregor Mosheh <[EMAIL PROTECTED]> >Reply-To: Gregor Mosheh <[EMAIL PROTECTED]> >To: [email protected] >Subject: Re: [UMN_MAPSERVER-USERS] Implementing Mapserver and AJAX (Need >info and advice) >Date: Thu, 8 Feb 2007 17:35:58 -0700 > > > AJAX style functionality (like Google Maps, with smooth panning and zoom > > etc). > > I was looking for advice on what it the best way of going about this, >the > > two products I have come across are ka-map and msCross. > >I've been disappointed with ka-Map, but have been very excited and pleased >with OpenLayers (www.openlayers.org) It involves setting up your mapfile >to act as a WMS server, then using OpenLayers to read from that WMS. Once >you get it working, check out TileCache for an extra bit of complexity and >performance. > > > > The final step in the process that I want to achieve is to either: > > 1) Import Google Maps layers into mapserver to use as a base then >overlay > > my custom maps > > or > > 2) Use Google Maps to import mapserver as a custom overlay. > >#2 is definitely easy to achieve. Set up your mapfile for WMS, then do a >Google for "using wms in google maps" and you'll see how to overlay youor >WMS into it. > >#1, I've heard (grain of salt, anyone?) that that's a violation of >Google's terms of use and that they keep sabotaging efforts to do that. >Perhaps somebody's heard otherwise or something has changed. > > >At any rate, going with OpenLayers instead of Google Maps would get around >some concerns you may have about your content, e.g. Google's terms of use, >the map not being 100% freely public, the content of the map, or plain old >caprice on Google's part.
-- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ --------------------------------------------------------------------- collaborate, communicate, compete =====================================================================
