From danlittle at yahoo.com Mon Apr 2 14:30:57 2012 From: danlittle at yahoo.com (Dan Little) Date: Mon Apr 2 14:31:55 2012 Subject: [Geomoose-users] Yahoo Layer wrong projection In-Reply-To: <1333051754758-3868924.post@n3.nabble.com> References: <1333051754758-3868924.post@n3.nabble.com> Message-ID: <1333391457.54755.YahooMailNeo@web161202.mail.bf1.yahoo.com> According to that configuration, your application is using your native projection, but Yahoo uses Web Mercator.? So you have a few options: 1. Don't use the Yahoo satellite imagery.? This will require you to find a local data source in a format you can serve (think GeoTIFF, ERW, JPEG2000 with Geo attributes attached, Mr SID, lots of options here). 2. Convert your data sources to display in Web Mercator.? If your source data is in the local projection then you can either create projected data sources or you can have mapserver do the dirty work and have it project it out as a part of the WMS configuration. >________________________________ > From: maddqc >To: geomoose-users@lists.osgeo.org >Sent: Thursday, March 29, 2012 3:09 PM >Subject: [Geomoose-users] Yahoo Layer wrong projection > >Hi list, > >I have a problem that is giving me headache. My problem is that I'm trying >to show a Yahoo satellite layer, but it seems that my projection is...kinda >wrong because my map show right at the middle of the Mediterranean Sea, when >it's supposed to show right over Quebec (Canada). > >I've set my projection to EPSG:32188 > >Here is the place where I've set this: > >In my main .HTML > >??? > > >??? >??? >??? >??? >??? >??? > > > > >In my Mapbook: >EPSG:32187 > >In Compiled.js: >'projection' : "EPSG:32188", > >In my Settings.ini: >[map] >projection=EPSG:32188 > > > > >Seriously...what's wrong with that??? > >Thanks to all of you!!! Your help is really appreciated. > > >-- >View this message in context: http://geomoose-users.964460.n3.nabble.com/Yahoo-Layer-wrong-projection-tp3868924p3868924.html >Sent from the Geomoose-users mailing list archive at Nabble.com. >_______________________________________________ >Geomoose-users mailing list >Geomoose-users@lists.osgeo.org >http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120402/1f9ea437/attachment.html From brent.lund at state.mn.us Wed Apr 4 15:54:19 2012 From: brent.lund at state.mn.us (Lund, Brent (ADM)) Date: Wed Apr 4 16:09:36 2012 Subject: [Geomoose-users] adding ArcGIS service to geomoose 2.4 Mercator Message-ID: <6AAF8F92E0B14C4DB1C4AFF7B98AD5E4090946@055-CH1MPN1-022.055d.mgd.msft.net> I'd like to add an ArcGIS rest service to a Geomoose 2.4 Mercator app (http://www.mngeo.state.mn.us/structures_ro/). I use the ArcGIS rest service in OpenLayers apps like http://www.mngeo.state.mn.us/glo/index.html. Here's how I define the layer var esriStreets = new OpenLayers.Layer.XYZ("ESRI Streets", "http://server.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer/tile/${z}/${y}/${x}", { sphericalMercator: true, attribution: "Tiles courtesy of arcgis.com", numZoomLevels: 20 }); So I guess the question is: How do I add an ArcGIS rest service to my mapbook? Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120404/d2ad4b14/attachment.html From danlittle at yahoo.com Wed Apr 4 17:12:39 2012 From: danlittle at yahoo.com (Dan Little) Date: Wed Apr 4 17:12:49 2012 Subject: [Geomoose-users] adding ArcGIS service to geomoose 2.4 Mercator In-Reply-To: <6AAF8F92E0B14C4DB1C4AFF7B98AD5E4090946@055-CH1MPN1-022.055d.mgd.msft.net> References: <6AAF8F92E0B14C4DB1C4AFF7B98AD5E4090946@055-CH1MPN1-022.055d.mgd.msft.net> Message-ID: <1333573959.90435.YahooMailNeo@web161206.mail.bf1.yahoo.com> not 100% on all the Arc stuff, however we do have a few options that can be seen in the demo examples: ?????? ??????????????? http://gis.metc.state.mn.us/ArcGIS/rest/services/BaseLayer/UTMBaseMap/MapServer/export ??????????????? ??????????????? ??????? And: ???? ??????????????? ??????????????? http://tah.openstreetmap.org/Tiles/tile/${z}/${x}/${y}.png ??????????????? ??????????????? ??????? Not sure which version of that works best for the ArcGIS Rest implementation.? IIRC, the "ags" source type is used for the cached version. >________________________________ > From: "Lund, Brent (ADM)" >To: "geomoose-users@lists.osgeo.org" >Sent: Wednesday, April 4, 2012 2:54 PM >Subject: [Geomoose-users] adding ArcGIS service to geomoose 2.4 Mercator > > > >I?d like to add an ArcGIS rest service to a Geomoose 2.4 Mercator app (http://www.mngeo.state.mn.us/structures_ro/). >? >I use the ArcGIS rest service in OpenLayers apps like http://www.mngeo.state.mn.us/glo/index.html.?? Here?s how I define the layer >? >var esriStreets = new OpenLayers.Layer.XYZ("ESRI Streets", "http://server.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer/tile/${z}/${y}/${x}", { >?? sphericalMercator: true, >?? attribution: "Tiles courtesy of arcgis.com", >?? numZoomLevels: 20 >}); >? >? >So I guess the question is: How do I add an ArcGIS rest service to my mapbook? >? >Thanks, >? >Brent >? >_______________________________________________ >Geomoose-users mailing list >Geomoose-users@lists.osgeo.org >http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120404/24dff038/attachment.html From bfischer at houstoneng.com Thu Apr 5 11:02:37 2012 From: bfischer at houstoneng.com (Brian Fischer) Date: Thu Apr 5 11:04:14 2012 Subject: [Geomoose-users] RE: adding ArcGIS service to geomoose 2.4 Mercator In-Reply-To: <6AAF8F92E0B14C4DB1C4AFF7B98AD5E4090946@055-CH1MPN1-022.055d.mgd.msft.net> References: <6AAF8F92E0B14C4DB1C4AFF7B98AD5E4090946@055-CH1MPN1-022.055d.mgd.msft.net> Message-ID: Brent, Currently GeoMoose only supports using an ArcGIS Rest service through the export task. It does not currently support using an ArcGIS mapcache (tiles) like you referenced. I know OpenLayers supports this so I want to try to get this added into GeoMoose for version 2.6 as well but not sure on the timing of it yet. I'm not sure if that is any different though than the XYZ layer type that is already supported. I just haven't have time to research that yet. Brian Fischer, CFM GIS Manager Houston Engineering, Inc. O 763.493.4522 | D 763.493.6664 | M 763.229.2734 From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Lund, Brent (ADM) Sent: Wednesday, April 04, 2012 2:54 PM To: geomoose-users@lists.osgeo.org Subject: [Geomoose-users] adding ArcGIS service to geomoose 2.4 Mercator I'd like to add an ArcGIS rest service to a Geomoose 2.4 Mercator app (http://www.mngeo.state.mn.us/structures_ro/). I use the ArcGIS rest service in OpenLayers apps like http://www.mngeo.state.mn.us/glo/index.html. Here's how I define the layer var esriStreets = new OpenLayers.Layer.XYZ("ESRI Streets", "http://server.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer/tile/${z}/${y}/${x}", { sphericalMercator: true, attribution: "Tiles courtesy of arcgis.com", numZoomLevels: 20 }); So I guess the question is: How do I add an ArcGIS rest service to my mapbook? Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120405/4ce57fcd/attachment-0001.html From danlittle at yahoo.com Fri Apr 6 15:11:33 2012 From: danlittle at yahoo.com (Dan Little) Date: Fri Apr 6 15:12:54 2012 Subject: [Geomoose-users] 2.6 RC1 Teaser Screenshot Message-ID: <1333739493.74381.YahooMailNeo@web161205.mail.bf1.yahoo.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: teaser_26rc1.png Type: image/png Size: 313626 bytes Desc: not available Url : http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120406/0697b4bf/teaser_26rc1-0001.png From mailing at tam.si Sat Apr 7 14:04:26 2012 From: mailing at tam.si (Matej Mailing) Date: Sat Apr 7 14:04:36 2012 Subject: [Geomoose-users] 2.6 RC1 Teaser Screenshot In-Reply-To: <1333739493.74381.YahooMailNeo@web161205.mail.bf1.yahoo.com> References: <1333739493.74381.YahooMailNeo@web161205.mail.bf1.yahoo.com> Message-ID: Hi, excellent! What is the approx. planned release date for 2.6? Thx. 2012/4/6 Dan Little : > Hope everyone has an enjoyable weekend.? I thought I'd share a screenshot of > the new "grey" skin running in GM 2.6. > > > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > From danlittle at yahoo.com Mon Apr 9 12:01:39 2012 From: danlittle at yahoo.com (Dan Little) Date: Mon Apr 9 12:01:48 2012 Subject: [Geomoose-users] FOSS4G-NA Message-ID: <1333987299.26906.YahooMailNeo@web161202.mail.bf1.yahoo.com> Jim and I will both be at FOSS4G-NA. There is lots of time for Birds-of-a-Feature gatherings.? You may find me there randomly hacking out code depending on session interest.? However, of those who are going, do you have a preference on when we could meet up? Else, I'll be around, please come around to harass me about 2.6, the website, how much you're going to volunteer/donate to the project. :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120409/8a2f2d34/attachment.html From MarkVolz at co.lyon.mn.us Mon Apr 9 13:59:51 2012 From: MarkVolz at co.lyon.mn.us (Mark Volz) Date: Mon Apr 9 14:17:26 2012 Subject: [Geomoose-users] per user layers Message-ID: <36CA828A36E29F45B7CF0A1766E5DFA30F7567@swmail01.r8nssis.local> Hello, Is there a way in GeoMOOSE 2.x to password protect some layers in the TOC without having to recreate several mapbooks. For example: Catalog -Public Layers -Layers only visible to county workers -Layers only visible to the Highway Department -Layers only visible to the Assessor Department -Layers only for the City Thanks Mark Volz GIS Specialist -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120409/5d1134f1/attachment.html From danlittle at yahoo.com Mon Apr 9 14:40:05 2012 From: danlittle at yahoo.com (Dan Little) Date: Mon Apr 9 14:40:34 2012 Subject: [Geomoose-users] per user layers In-Reply-To: <36CA828A36E29F45B7CF0A1766E5DFA30F7567@swmail01.r8nssis.local> References: <36CA828A36E29F45B7CF0A1766E5DFA30F7567@swmail01.r8nssis.local> Message-ID: <1333996805.45186.YahooMailNeo@web161206.mail.bf1.yahoo.com> Replace getmapbook.php.? You'll need to create a login solution, of which there are many and varied.? Essentially it goes this like: 1. Create something like "/gis/login.php" - Then if you want , have a link there for "public" or "guests" 2. login.php gets the credentials, checks them against a database or LDAP/AD, and you get a role.? PHP's session functionality makes this pretty easy.? Then login.php would forward the user to "geomoose.html" (or whatever it's called on your system) 3. getmapbook.php, probably reads a "header.xml", then for the body (map-source's and catalog) you'd write a quick for-loop that would either use a XML/DOM building utility or just some text that makes valid XML to output in the form of a mapbook, finally a "footer.xml".? The script would populate the available layers based on the auth levels of the user and I'd probably store that info in postgresql. >________________________________ > From: Mark Volz >To: "geomoose-users@lists.osgeo.org" >Sent: Monday, April 9, 2012 12:59 PM >Subject: [Geomoose-users] per user layers > > > >Hello, >? >Is there a way in GeoMOOSE 2.x to password protect some layers in the TOC without having to recreate several mapbooks.? For example: >? >Catalog >-Public Layers >-Layers only visible to county workers >-Layers only visible to the Highway Department >-Layers only visible to the Assessor Department >-Layers only for the City >? >? >Thanks >? >Mark Volz >GIS Specialist >? >? >_______________________________________________ >Geomoose-users mailing list >Geomoose-users@lists.osgeo.org >http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120409/2bce1ff3/attachment.html From klassen.js at gmail.com Mon Apr 9 14:54:42 2012 From: klassen.js at gmail.com (Jim Klassen) Date: Mon Apr 9 14:55:08 2012 Subject: [Geomoose-users] per user layers In-Reply-To: <1333996805.45186.YahooMailNeo@web161206.mail.bf1.yahoo.com> References: <36CA828A36E29F45B7CF0A1766E5DFA30F7567@swmail01.r8nssis.local> <1333996805.45186.YahooMailNeo@web161206.mail.bf1.yahoo.com> Message-ID: <331B4446-97B9-46DD-9545-2BC6E1187D36@gmail.com> Also, don't forget to password protect your datasource. No sense hiding the layer from GeoMoose if someone can just get the data straight from MapServer anyway. One option I've used involves separate map files for each data source and a lot of apache rules. Another option I've used was to write a script that implements WMS via mapscript and validates off of your auth solution. Also, don't forget the printing and query scripts need to understand the login part too. On Apr 9, 2012, at 13:40, Dan Little wrote: > Replace getmapbook.php. You'll need to create a login solution, of which there are many and varied. Essentially it goes this like: > > > 1. Create something like "/gis/login.php" - Then if you want , have a link there for "public" or "guests" > 2. login.php gets the credentials, checks them against a database or LDAP/AD, and you get a role. PHP's session functionality makes this pretty easy. Then login.php would forward the user to "geomoose.html" (or whatever it's called on your system) > 3. getmapbook.php, probably reads a "header.xml", then for the body (map-source's and catalog) you'd write a quick for-loop that would either use a XML/DOM building utility or just some text that makes valid XML to output in the form of a mapbook, finally a "footer.xml". The script would populate the available layers based on the auth levels of the user and I'd probably store that info in postgresql. > > From: Mark Volz > To: "geomoose-users@lists.osgeo.org" > Sent: Monday, April 9, 2012 12:59 PM > Subject: [Geomoose-users] per user layers > > Hello, > > Is there a way in GeoMOOSE 2.x to password protect some layers in the TOC without having to recreate several mapbooks. For example: > > Catalog > -Public Layers > -Layers only visible to county workers > -Layers only visible to the Highway Department > -Layers only visible to the Assessor Department > -Layers only for the City > > > Thanks > > Mark Volz > GIS Specialist > > > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120409/a21e30ba/attachment.html From danlittle at yahoo.com Thu Apr 12 10:18:35 2012 From: danlittle at yahoo.com (Dan Little) Date: Thu Apr 12 10:18:51 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? Message-ID: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> Hello List, We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. A demo is available here: - http://www.geomoose.org/demo/geomoose.html The current state of the documentation is here: - http://www.geomoose.org/trunk/ A relevant change log is here: - http://www.geomoose.org/trunk/releases/2.6.html Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose.? We have moved to a versioned documentation system and the old docs will be preserved here: - http://www.geomoose.org/2.4/ "geomoose.org/" really just points to the latest stable documentation. Does anyone have an objection to cleaning up the docs to *only* apply to 2.6?? My motivation is clarity.? 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. We will be dropping an RC1 pending a few tickets.? Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. Thanks for any input! -Duck -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120412/0bf0109e/attachment.html From Bob.Basques at ci.stpaul.mn.us Thu Apr 12 10:22:52 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Thu Apr 12 10:23:38 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> Message-ID: <4F869EEC020000A80003517B@heckle> Skipped content of type multipart/alternative From boesiii at yahoo.com Thu Apr 12 11:15:14 2012 From: boesiii at yahoo.com (Ed Boesenberg) Date: Thu Apr 12 11:16:01 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> Message-ID: <002101cd18bf$107c8ab0$3175a010$@com> I will be upgrading all of my GM apps to the 2.6 version, so I have no objections. I would be happy to help write some of the docs, I would need someone to point me in the right direction. Ed From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Dan Little Sent: Thursday, April 12, 2012 10:19 AM To: GeoMOOSE Users List Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? Hello List, We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. A demo is available here: - http://www.geomoose.org/demo/geomoose.html The current state of the documentation is here: - http://www.geomoose.org/trunk/ A relevant change log is here: - http://www.geomoose.org/trunk/releases/2.6.html Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose. We have moved to a versioned documentation system and the old docs will be preserved here: - http://www.geomoose.org/2.4/ "geomoose.org/" really just points to the latest stable documentation. Does anyone have an objection to cleaning up the docs to *only* apply to 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. We will be dropping an RC1 pending a few tickets. Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. Thanks for any input! -Duck -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120412/fca84ea3/attachment-0001.html From Bob.Bistrais at maine.gov Thu Apr 12 11:18:07 2012 From: Bob.Bistrais at maine.gov (Bistrais, Bob) Date: Thu Apr 12 11:18:21 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <002101cd18bf$107c8ab0$3175a010$@com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> Message-ID: <4EFF8BB964547748A07CA32961810C041D640393@SOM-TEAQASMAIL1.som.w2k.state.me.us> Likewise, I could help write docs if someone tells me what's needed. From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Ed Boesenberg Sent: Thursday, April 12, 2012 11:15 AM To: 'Dan Little'; 'GeoMOOSE Users List' Subject: RE: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? I will be upgrading all of my GM apps to the 2.6 version, so I have no objections. I would be happy to help write some of the docs, I would need someone to point me in the right direction. Ed From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Dan Little Sent: Thursday, April 12, 2012 10:19 AM To: GeoMOOSE Users List Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? Hello List, We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. A demo is available here: - http://www.geomoose.org/demo/geomoose.html The current state of the documentation is here: - http://www.geomoose.org/trunk/ A relevant change log is here: - http://www.geomoose.org/trunk/releases/2.6.html Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose. We have moved to a versioned documentation system and the old docs will be preserved here: - http://www.geomoose.org/2.4/ "geomoose.org/" really just points to the latest stable documentation. Does anyone have an objection to cleaning up the docs to *only* apply to 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. We will be dropping an RC1 pending a few tickets. Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. Thanks for any input! -Duck -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120412/8445f0b9/attachment.html From danlittle at yahoo.com Thu Apr 12 11:30:27 2012 From: danlittle at yahoo.com (Dan Little) Date: Thu Apr 12 11:31:18 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <002101cd18bf$107c8ab0$3175a010$@com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> Message-ID: <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> Eli, please point Ed to the right direction. :D >________________________________ > From: Ed Boesenberg >To: 'Dan Little' ; 'GeoMOOSE Users List' >Sent: Thursday, April 12, 2012 10:15 AM >Subject: RE: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? > > >I will be upgrading all of my GM apps to the 2.6 version, so I have no objections. >? >I would be happy to help write some of the docs, I would need someone to point me in the right direction. >? >Ed >? >? >? >? >From:geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Dan Little >Sent: Thursday, April 12, 2012 10:19 AM >To: GeoMOOSE Users List >Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? >? >Hello List, >? >We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. >? >A demo is available here: >- http://www.geomoose.org/demo/geomoose.html >? >The current state of the documentation is here: >- http://www.geomoose.org/trunk/ >? >A relevant change log is here: >- http://www.geomoose.org/trunk/releases/2.6.html >? >Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose.? We have moved to a versioned documentation system and the old docs will be preserved here: >- http://www.geomoose.org/2.4/ >? >"geomoose.org/" really just points to the latest stable documentation. >? >Does anyone have an objection to cleaning up the docs to *only* apply to 2.6?? My motivation is clarity.? 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. >? >We will be dropping an RC1 pending a few tickets.? Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. >? >Thanks for any input! >? >-Duck >? >? >? >? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120412/ec93415a/attachment-0001.html From eadam at co.lincoln.or.us Thu Apr 12 13:23:15 2012 From: eadam at co.lincoln.or.us (Eli Adam) Date: Thu Apr 12 13:23:28 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> Message-ID: Ed and Bob (Bistrais in addition to bobb), Dan, and all, Thanks for volunteering with documentation writing. The docs are generated using sphinx (http://sphinx.pocoo.org/) which just uses restructured text which is fairly simple txt files. You can look at them here, http://trac.osgeo.org/geomoose/browser/geomoose2/trunk/sphinx-docs/source Also, anywhere on the website you can click the 'Show Source' link under 'This Page'. Looking at and mimicking the existing files works fairly well for me. The general workflow for writing docs is to svn checkout/update, write the documentation locally, have sphinx installed and locally build the documentation, check that it is all correct, create a patch and attach to a ticket (http://trac.osgeo.org/geomoose/report) or svn commit, the website will reflect your changes 15 minutes or so after it is committed. If you want to use that workflow, I'm available to help offline to get subversion and sphinx set up in your environment. If you don't want to use that workflow, then you can open tickets and just put the documentation in the ticket and I will convert it to the correct format and get it on the website. > Does anyone have an objection to cleaning up the docs to *only* apply to > 2.6?? My motivation is clarity.? 2.6 simplifies installation quite a bit but > it also deprecates a few functions and I'd rather not have too much "diff > docing" going on as it can confuse new users. I thought about this last night as I added strike through to some changed items. I'm all for changing trunk and the 2.6 branch to match those realities. Previous versions of documentation can live in their own branches, I think that dedicated version specific documentation is far better than 'diff docing'. Looking forward to it, Eli From Bob.Basques at ci.stpaul.mn.us Thu Apr 12 13:38:15 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Thu Apr 12 13:38:37 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> Message-ID: <4F86CCB7020000A8000351B7@heckle> Skipped content of type multipart/alternative From eadam at co.lincoln.or.us Thu Apr 12 13:49:42 2012 From: eadam at co.lincoln.or.us (Eli Adam) Date: Thu Apr 12 13:50:36 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <4F86CCB7020000A8000351B7@heckle> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> <4F86CCB7020000A8000351B7@heckle> Message-ID: bobb, Hopefully the online validator would work well enough to avoid bad stuff. If you want to attach to a ticket I will gladly apply it. If you want, I can try to help you get sphinx running in your local environment so that you can run locally. I'm not opposed to you committing it and breaking rendering things and then me fixing it after you, so long as you were reasonably confident that your changes weren't going to break things (which perhaps an online validator would do) and/or you promptly check your commits online and revert them if they cause problems. However, such a thing should be rare (perhaps use two online validators if using one in the past didn't work). Also, other people may feel differently about commits breaking rendering things. I also can't speak for the infrastructure. If your changes were enough to impact the infrastructure, I can imagine that would be unpopular. I'm sure that we can work something out. Bests, Eli On Thu, Apr 12, 2012 at 10:38 AM, Bob Basques wrote: > All, > > Ok, last time I tried this, I did the Sphinx stuff by hand and validated > it online with a SPHINX validator and then posted. Apparently this was > bad, since I got thrown out of documentation class as a consequence. See > my remark about not being afraid of writing doc's but being told I did it > wrong. > > . . . . > > bobb > > > > > >>> Eli Adam wrote: > > Ed and Bob (Bistrais in addition to bobb), Dan, and all, > > Thanks for volunteering with documentation writing. The docs are > generated using sphinx (http://sphinx.pocoo.org/) which just uses > restructured text which is fairly simple txt files. You can look at > them here, > http://trac.osgeo.org/geomoose/browser/geomoose2/trunk/sphinx-docs/source > Also, anywhere on the website you can click the 'Show Source' link > under 'This Page'. Looking at and mimicking the existing files works > fairly well for me. > > The general workflow for writing docs is to svn checkout/update, write > the documentation locally, have sphinx installed and locally build > the documentation, check that it is all correct, create a patch and > attach to a ticket (http://trac.osgeo.org/geomoose/report) or svn > commit, the website will reflect your changes 15 minutes or so after > it is committed. > > If you want to use that workflow, I'm available to help offline to get > subversion and sphinx set up in your environment. If you don't want > to use that workflow, then you can open tickets and just put the > documentation in the ticket and I will convert it to the correct > format and get it on the website. > > > Does anyone have an objection to cleaning up the docs to *only* apply to > > 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit > but > > it also deprecates a few functions and I'd rather not have too much "diff > > docing" going on as it can confuse new users. > > I thought about this last night as I added strike through to some > changed items. I'm all for changing trunk and the 2.6 branch to match > those realities. Previous versions of documentation can live in their > own branches, I think that dedicated version specific documentation is > far better than 'diff docing'. > > Looking forward to it, Eli > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120412/e1aeaf61/attachment.html From Bob.Basques at ci.stpaul.mn.us Thu Apr 12 15:24:27 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Thu Apr 12 15:25:10 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> <4F86CCB7020000A8000351B7@heckle> Message-ID: <4F86E59B020000A8000351D0@heckle> Skipped content of type multipart/alternative From mailing at tam.si Fri Apr 13 18:24:59 2012 From: mailing at tam.si (Matej Mailing) Date: Fri Apr 13 18:25:38 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <4F86E59B020000A8000351D0@heckle> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <002101cd18bf$107c8ab0$3175a010$@com> <1334244627.34650.YahooMailNeo@web161206.mail.bf1.yahoo.com> <4F86CCB7020000A8000351B7@heckle> <4F86E59B020000A8000351D0@heckle> Message-ID: Just a little note: on http://www.geomoose.org/trunk/ at the announcement of 2.6 RC1 the year is wrong (2011 instead of 2012). 4/13/2011 - GeoMOOSE 2.6 RC1 Available Now BR, Matej 2012/4/12 Bob Basques > Eli, > > It's all good stuff. Even me learning a new thing or two (whether I > like it not) about sphinx. > > bobb > > > > >>> Eli Adam wrote: > > bobb, > > Hopefully the online validator would work well enough to avoid bad stuff. > If you want to attach to a ticket I will gladly apply it. If you want, I > can try to help you get sphinx running in your local environment so that > you can run locally. > > I'm not opposed to you committing it and breaking rendering things and > then me fixing it after you, so long as you were reasonably confident that > your changes weren't going to break things (which perhaps an online > validator would do) and/or you promptly check your commits online and > revert them if they cause problems. However, such a thing should be rare > (perhaps use two online validators if using one in the past didn't work). > Also, other people may feel differently about commits breaking rendering > things. I also can't speak for the infrastructure. If your changes were > enough to impact the infrastructure, I can imagine that would be unpopular. > > I'm sure that we can work something out. > > Bests, Eli > > On Thu, Apr 12, 2012 at 10:38 AM, Bob Basques < > Bob.Basques@ci.stpaul.mn.us> wrote: > >> All, >> >> >> Ok, last time I tried this, I did the Sphinx stuff by hand and >> validated it online with a SPHINX validator and then posted. Apparently >> this was bad, since I got thrown out of documentation class as a >> consequence. See my remark about not being afraid of writing doc's but >> being told I did it wrong. >> >> >> . . . . >> >> >> bobb >> >> >> >> >> >> >>> Eli Adam wrote: >> >> Ed and Bob (Bistrais in addition to bobb), Dan, and all, >> >> Thanks for volunteering with documentation writing. The docs are >> generated using sphinx (http://sphinx.pocoo.org/) which just uses >> restructured text which is fairly simple txt files. You can look at >> them here, >> http://trac.osgeo.org/geomoose/browser/geomoose2/trunk/sphinx-docs/source >> Also, anywhere on the website you can click the 'Show Source' link >> under 'This Page'. Looking at and mimicking the existing files works >> fairly well for me. >> >> The general workflow for writing docs is to svn checkout/update, write >> the documentation locally, have sphinx installed and locally build >> the documentation, check that it is all correct, create a patch and >> attach to a ticket (http://trac.osgeo.org/geomoose/report) or svn >> commit, the website will reflect your changes 15 minutes or so after >> it is committed. >> >> If you want to use that workflow, I'm available to help offline to get >> subversion and sphinx set up in your environment. If you don't want >> to use that workflow, then you can open tickets and just put the >> documentation in the ticket and I will convert it to the correct >> format and get it on the website. >> >> > Does anyone have an objection to cleaning up the docs to *only* apply to >> > 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit >> but >> > it also deprecates a few functions and I'd rather not have too much >> "diff >> > docing" going on as it can confuse new users. >> >> I thought about this last night as I added strike through to some >> changed items. I'm all for changing trunk and the 2.6 branch to match >> those realities. Previous versions of documentation can live in their >> own branches, I think that dedicated version specific documentation is >> far better than 'diff docing'. >> >> Looking forward to it, Eli >> >> _______________________________________________ >> Geomoose-users mailing list >> Geomoose-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/geomoose-users >> >> > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120414/27879773/attachment.html From MarkVolz at co.lyon.mn.us Mon Apr 16 10:39:36 2012 From: MarkVolz at co.lyon.mn.us (Mark Volz) Date: Mon Apr 16 10:39:53 2012 Subject: [Geomoose-users] geocode address 2.6 RC1 status Message-ID: <36CA828A36E29F45B7CF0A1766E5DFA3103875@swmail01.r8nssis.local> Hello, I noticed that Geocoding addresses does not appear to work out of the box for Geomoose 2.6 RC1. Has anyone else noticed any problems? Mark Volz GIS Specialist -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120416/92b8a983/attachment.html From bfraser at geoanalytic.com Mon Apr 16 15:08:23 2012 From: bfraser at geoanalytic.com (Brent Fraser) Date: Mon Apr 16 15:09:24 2012 Subject: [Geomoose-users] GeoMoose API: GeoMOOSE.turnLayerOn problem with multi map-source layers Message-ID: <4F8C6E27.8060003@geoanalytic.com> Dan, I'm using the GeoMoose API (v2.4 I think) in a JavaScript user extension to turn on a multi-mapsource Layer: GeoMOOSE.turnLayerOn("Image/image:Filler/all"); In geomoose.js, turnLayerOn calls changeLayerVisibility, where the layerpath is split and the DOM is queried for each portion. But those portions are Map-Sources, not Layers, and therefor are not found. So I changed the code to simply query on the original path (not the portions), and it seems to work: changeLayerVisibility : function(layerPath, visibility) { /* var paths = this.splitPaths(layerPath); for(var p = 0; p < paths.length; p++) { var e = document.getElementById('catalog-'+paths[p]); if(!e && !Catalog.setLayerVisibility(paths[p], visibility)) { OpenLayers.Console.log('Layer '+paths[p]+' does not exist'); } else if(e && e.checked != visibility) { e.checked = visibility; e.onclick(); } } */ var e = document.getElementById('catalog-'+layerPath); if(!e && !Catalog.setLayerVisibility(layerPath, visibility)) { OpenLayers.Console.log('Layer '+layerPath+' does not exist'); } else if(e && e.checked != visibility) { e.checked = visibility; e.onclick(); } }, If you think the above fix is valid, I'll file an Issue in Trac (I guess we're still filing issues on v2.4), and put the fix in SVN. Thanks! -- Best Regards, Brent Fraser -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120416/8c0ddf34/attachment.html From Johan.Forsman at LA.GOV Mon Apr 16 15:24:48 2012 From: Johan.Forsman at LA.GOV (Johan Forsman) Date: Mon Apr 16 15:26:34 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? Message-ID: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> All: I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part. On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and 2) using the "all" parameter in the layer definition in the mapbook returns an error. For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such: ./sdwp/roads/webmaps_osm_lahwys.map The forwarded URL request is: http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 The map file contains many scale-dependent line- and annotation layers and renders beautifully. In the 2.6 environment the same mapbook definition and mapfile results in this call: http://oph-isb-gis01/cgi-bin/mapserv.exe? MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 which returns: msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter. I have unsuccessfully searched for documentation on this topic. Please advise. Thanks! Johan Forsman Geologist Engineering Services LDHH-OPH-CEHS 225.342.7309 From Bob.Basques at ci.stpaul.mn.us Mon Apr 16 15:40:48 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Mon Apr 16 15:41:55 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> Message-ID: <4F8C2F70020000A80003542F@heckle> Skipped content of type multipart/alternative From Bob.Basques at ci.stpaul.mn.us Mon Apr 16 15:45:46 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Mon Apr 16 15:46:22 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> Message-ID: <4F8C309A020000A80003543B@heckle> Skipped content of type multipart/alternative From klassen.js at gmail.com Mon Apr 16 15:46:40 2012 From: klassen.js at gmail.com (Jim Klassen) Date: Mon Apr 16 15:46:55 2012 Subject: [Geomoose-users] GeoMoose API: GeoMOOSE.turnLayerOn problem with multi map-source layers In-Reply-To: <4F8C6E27.8060003@geoanalytic.com> References: <4F8C6E27.8060003@geoanalytic.com> Message-ID: <6956D94C-CE3F-4ADD-AA06-2BDE30EC2397@gmail.com> I don't think we've made the 2.4.1 release yet either. I have already applied some fixes in branches/geomoose-2.4 in anticipation for the 2.4.1 release (update for Mapserver 6.x and the famous extra comma). I think it is all sitting pending testing. My main confusion is that the 2.4.0 tarball and the 2.4.0 tag and branch in SVN somehow ended up at slightly different versions and I'm not sure which is most correct. On Apr 16, 2012, at 2:08 PM, Brent Fraser wrote: > Dan, > > I'm using the GeoMoose API (v2.4 I think) in a JavaScript user extension to turn on a multi-mapsource Layer: > > GeoMOOSE.turnLayerOn("Image/image:Filler/all"); > > In geomoose.js, turnLayerOn calls changeLayerVisibility, where the layerpath is split and the DOM is queried for each portion. But those portions are Map-Sources, not Layers, and therefor are not found. > > So I changed the code to simply query on the original path (not the portions), and it seems to work: > > > changeLayerVisibility : function(layerPath, visibility) { > /* > var paths = this.splitPaths(layerPath); > for(var p = 0; p < paths.length; p++) { > var e = document.getElementById('catalog-'+paths[p]); > if(!e && !Catalog.setLayerVisibility(paths[p], visibility)) { > OpenLayers.Console.log('Layer '+paths[p]+' does not exist'); > } else if(e && e.checked != visibility) { > e.checked = visibility; > e.onclick(); > } > } > */ > var e = document.getElementById('catalog-'+layerPath); > if(!e && !Catalog.setLayerVisibility(layerPath, visibility)) { > OpenLayers.Console.log('Layer '+layerPath+' does not exist'); > } else if(e && e.checked != visibility) { > e.checked = visibility; > e.onclick(); > } > }, > > If you think the above fix is valid, I'll file an Issue in Trac (I guess we're still filing issues on v2.4), and put the fix in SVN. > > Thanks! > -- > Best Regards, > Brent Fraser > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120416/bf900802/attachment-0001.html From klassen.js at gmail.com Mon Apr 16 16:02:06 2012 From: klassen.js at gmail.com (Jim Klassen) Date: Mon Apr 16 16:02:27 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> Message-ID: <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> It was intentional to migrate to using WMS over the MapServer specific calls in the default case as it eases interoperability with other servers and simplifies the code in many cases. I don't think it was intentional to loose the layers=all trick (which was implemented inside MapServer not GeoMoose). Do any of the suggestions in the MapServer ticket referenced by Bob work as a workaround for you? While 2.6 is near to release, one of the bigger tasks left is finishing up documentation. Thank you for testing and bring this to our attention. On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote: > All: > > I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part. > > On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in > > 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and > > 2) using the "all" parameter in the layer definition in the mapbook returns an error. > > For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such: > > > ./sdwp/roads/webmaps_osm_lahwys.map > > > > > The forwarded URL request is: > > http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 > > The map file contains many scale-dependent line- and annotation layers and renders beautifully. > > In the 2.6 environment the same mapbook definition and mapfile results in this call: > > http://oph-isb-gis01/cgi-bin/mapserv.exe? > MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 > > which returns: > > > msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter. > > > I have unsuccessfully searched for documentation on this topic. Please advise. > > Thanks! > Johan Forsman > Geologist > Engineering Services > LDHH-OPH-CEHS > 225.342.7309 > > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users From Bob.Basques at ci.stpaul.mn.us Mon Apr 16 16:07:10 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Mon Apr 16 16:07:56 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> Message-ID: <4F8C359E020000A800035449@heckle> Skipped content of type multipart/alternative From danlittle at yahoo.com Mon Apr 16 20:53:32 2012 From: danlittle at yahoo.com (Dan Little) Date: Mon Apr 16 20:53:49 2012 Subject: [Geomoose-users] GeoMoose API: GeoMOOSE.turnLayerOn problem with multi map-source layers In-Reply-To: <6956D94C-CE3F-4ADD-AA06-2BDE30EC2397@gmail.com> References: <4F8C6E27.8060003@geoanalytic.com> <6956D94C-CE3F-4ADD-AA06-2BDE30EC2397@gmail.com> Message-ID: <1334624012.80304.YahooMailNeo@web161201.mail.bf1.yahoo.com> Jim's right, we should be able to integrate this patch. >________________________________ > From: Jim Klassen >To: Brent Fraser >Cc: Dan Little ; GeoMOOSE Users List >Sent: Monday, April 16, 2012 2:46 PM >Subject: Re: [Geomoose-users] GeoMoose API: GeoMOOSE.turnLayerOn problem with multi map-source layers > > >I don't think we've made the 2.4.1 release yet either. ?I have already applied some fixes in branches/geomoose-2.4 in anticipation for the 2.4.1 release (update for Mapserver 6.x and the famous extra comma). ?I think it is all sitting pending testing. ?My main confusion is that the 2.4.0 tarball and the 2.4.0 tag and branch in SVN somehow ended up at slightly different versions and I'm not sure which is most correct. > > >On Apr 16, 2012, at 2:08 PM, Brent Fraser wrote: > >Dan, >> >>? I'm using the GeoMoose API (v2.4 I think) in a JavaScript user extension to? turn on a multi-mapsource Layer: >> >>??? ? GeoMOOSE.turnLayerOn("Image/image:Filler/all"); >> >>In geomoose.js, turnLayerOn calls changeLayerVisibility, where the layerpath is split and the DOM is queried for each portion.? But those portions are Map-Sources, not Layers, and therefor are not found. >> >>So I changed the code to simply query on the original path (not the portions), and it seems to work: >> >> >>??? changeLayerVisibility : function(layerPath, visibility) {??? ? >>/*??? >>??? ??? var paths = this.splitPaths(layerPath); >>??? ??? for(var p = 0; p < paths.length; p++) { >>??? ??? ??? var e = document.getElementById('catalog-'+paths[p]); >>??? ??? ??? if(!e && !Catalog.setLayerVisibility(paths[p], visibility)) { >>??? ??? ??? ??? OpenLayers.Console.log('Layer '+paths[p]+' does not exist'); >>??? ??? ??? } else if(e && e.checked != visibility) { >>??? ??? ??? ??? e.checked = visibility; >>??? ??? ??? ??? e.onclick(); >>??? ??? ??? } >>??? ??? } >>*/??? ??? >>??? ??? var e = document.getElementById('catalog-'+layerPath); >>??? ??? if(!e && !Catalog.setLayerVisibility(layerPath, visibility)) { >>??? ??? ??? OpenLayers.Console.log('Layer '+layerPath+' does not exist'); >>??? ??? } else if(e && e.checked != visibility) { >>??? ??? ??? e.checked = visibility; >>??? ??? ??? e.onclick(); >>??? ??? } >>??? }, >> >>If you think the above fix is valid, I'll file an Issue in Trac (I guess we're still filing issues on v2.4), and put the fix in SVN. >> >>Thanks! >> >>-- Best Regards, Brent Fraser _______________________________________________ >>Geomoose-users mailing list >>Geomoose-users@lists.osgeo.org >>http://lists.osgeo.org/mailman/listinfo/geomoose-users >> > >_______________________________________________ >Geomoose-users mailing list >Geomoose-users@lists.osgeo.org >http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120416/4b532cfb/attachment-0001.html From Johan.Forsman at LA.GOV Mon Apr 16 21:08:17 2012 From: Johan.Forsman at LA.GOV (Johan Forsman) Date: Mon Apr 16 21:08:32 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <4F8C359E020000A800035449@heckle> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> <4F8C359E020000A800035449@heckle> Message-ID: <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> Success! The fastest method I could think of to test all layers was a bulk Find of "STATUS ON" and Replace with "GROUP 'all'" which indeed allows the layers to display as intended using in the mapbook. I think this topic needs to be documented front and center in the migration guide as it represents a fundamental change in the way the application works. I am sure there are many instances of legacy GM/MapServer installations that may require significant retooling to work with the new version, especially if they are not configured to serve WMS already. Thanks for the tips and for a really great product. I am curious about Jim's "in the default case" statement. Does this mean there is a case where the MapServer layers are *not* translated to WMS calls? Incidentally, I may have discovered a few other items that may not be as intended. If they are not user error, where is appropriate to report them? Thanks again, Johan. From: Bob Basques [mailto:Bob.Basques@ci.stpaul.mn.us] Sent: Monday, April 16, 2012 3:07 PM To: Jim Klassen; Johan Forsman Cc: geomoose-users@lists.osgeo.org Subject: Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? All (of you), Just adding the desired layers to a GROUP called "all", should fix things (I think) bobb >>> Jim Klassen > wrote: It was intentional to migrate to using WMS over the MapServer specific calls in the default case as it eases interoperability with other servers and simplifies the code in many cases. I don't think it was intentional to loose the layers=all trick (which was implemented inside MapServer not GeoMoose). Do any of the suggestions in the MapServer ticket referenced by Bob work as a workaround for you? While 2.6 is near to release, one of the bigger tasks left is finishing up documentation. Thank you for testing and bring this to our attention. On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote: > All: > > I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part. > > On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in > > 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and > > 2) using the "all" parameter in the layer definition in the mapbook returns an error. > > For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such: > > > ./sdwp/roads/webmaps_osm_lahwys.map > > > > > The forwarded URL request is: > > http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 > > The map file contains many scale-dependent line- and annotation layers and renders beautifully. > > In the 2.6 environment the same mapbook definition and mapfile results in this call: > > http://oph-isb-gis01/cgi-bin/mapserv.exe? > MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 > > which returns: > > > msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter. > > > I have unsuccessfully searched for documentation on this topic. Please advise. > > Thanks! > Johan Forsman > Geologist > Engineering Services > LDHH-OPH-CEHS > 225.342.7309 > > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users _______________________________________________ Geomoose-users mailing list Geomoose-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geomoose-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120416/1d4278f6/attachment.html From klassen.js at gmail.com Mon Apr 16 21:41:59 2012 From: klassen.js at gmail.com (Jim Klassen) Date: Mon Apr 16 21:42:20 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> <4F8C359E020000A800035449@heckle> <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> Message-ID: <63E03A1F-B3B1-408C-A2A7-C5AC09447879@gmail.com> Cool! The list is always a good place to start for problems/questions/feedback. At one point I thought there was a fallback to the old MapServer mode, but I'm not seeing it in the code now. Maybe I missed it. Dan? On Apr 16, 2012, at 8:08 PM, Johan Forsman wrote: > Success! > > The fastest method I could think of to test all layers was a bulk Find of ?STATUS ON? and Replace with ?GROUP ?all?? which indeed allows the layers to display as intended using in the mapbook. > > I think this topic needs to be documented front and center in the migration guide as it represents a fundamental change in the way the application works. I am sure there are many instances of legacy GM/MapServer installations that may require significant retooling to work with the new version, especially if they are not configured to serve WMS already. > > Thanks for the tips and for a really great product. > > I am curious about Jim?s ?in the default case? statement. Does this mean there is a case where the MapServer layers are *not* translated to WMS calls? > > Incidentally, I may have discovered a few other items that may not be as intended. If they are not user error, where is appropriate to report them? > > Thanks again, > > Johan. > > From: Bob Basques [mailto:Bob.Basques@ci.stpaul.mn.us] > Sent: Monday, April 16, 2012 3:07 PM > To: Jim Klassen; Johan Forsman > Cc: geomoose-users@lists.osgeo.org > Subject: Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? > > > All (of you), > > Just adding the desired layers to a GROUP called "all", should fix things (I think) > > bobb > > > > >>> Jim Klassen wrote: > It was intentional to migrate to using WMS over the MapServer specific calls in the default case as it eases interoperability with other servers and simplifies the code in many cases. > > I don't think it was intentional to loose the layers=all trick (which was implemented inside MapServer not GeoMoose). Do any of the suggestions in the MapServer ticket referenced by Bob work as a workaround for you? > > While 2.6 is near to release, one of the bigger tasks left is finishing up documentation. Thank you for testing and bring this to our attention. > > On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote: > > > All: > > > > I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part. > > > > On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in > > > > 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and > > > > 2) using the "all" parameter in the layer definition in the mapbook returns an error. > > > > For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such: > > > > > > ./sdwp/roads/webmaps_osm_lahwys.map > > > > > > > > > > The forwarded URL request is: > > > > http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 > > > > The map file contains many scale-dependent line- and annotation layers and renders beautifully. > > > > In the 2.6 environment the same mapbook definition and mapfile results in this call: > > > > http://oph-isb-gis01/cgi-bin/mapserv.exe? > > MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 > > > > which returns: > > > > > > msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter. > > > > > > I have unsuccessfully searched for documentation on this topic. Please advise. > > > > Thanks! > > Johan Forsman > > Geologist > > Engineering Services > > LDHH-OPH-CEHS > > 225.342.7309 > > > > > > _______________________________________________ > > Geomoose-users mailing list > > Geomoose-users@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120416/735f8d50/attachment-0001.html From eadam at co.lincoln.or.us Tue Apr 17 04:16:38 2012 From: eadam at co.lincoln.or.us (Eli Adam) Date: Tue Apr 17 04:16:44 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> <4F8C359E020000A800035449@heckle> <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> Message-ID: Johan, On Mon, Apr 16, 2012 at 6:08 PM, Johan Forsman wrote: > **** > > Success!**** > > The fastest method I could think of to test all layers was a bulk Find of > ?STATUS ON? and Replace with ?GROUP ?all?? which indeed allows the layers > to display as intended using in the mapbook. **** > > I think this topic needs to be documented front and center in the > migration guide as it represents a fundamental change in the way the > application works. I am sure there are many instances of legacy > GM/MapServer installations that may require significant > I have updated documentation here, http://geomoose.org/trunk/releases/2.6.html#release and here, http://geomoose.org/trunk/docs/faq.html#why-doesn-t-layers-all-work-anymore(should show updates in a while) Please review it to confirm that it is sufficient. > retooling to work with the new version, especially if they are not > configured to serve WMS already.**** > > Thanks for the tips and for a really great product.**** > > I am curious about Jim?s ?in the default case? statement. Does this mean > there is a case where the MapServer layers are **not** translated to WMS > calls?**** > > Incidentally, I may have discovered a few other items that may not be as > intended. If they are not user error, where is appropriate to report them? > The email list is always a great place to confirm things. Once you are certain, a Trac Ticket is usually the best route, http://trac.osgeo.org/geomoose/newticket Bests, Eli **** > > Thanks again,**** > > Johan.**** > > *From:* Bob Basques [mailto:Bob.Basques@ci.stpaul.mn.us] > *Sent:* Monday, April 16, 2012 3:07 PM > *To:* Jim Klassen; Johan Forsman > *Cc:* geomoose-users@lists.osgeo.org > *Subject:* Re: [Geomoose-users] Changes to mapserver-type layer handling > in GM 2.6?**** > > ** ** > > All (of you), **** > > ** ** > > Just adding the desired layers to a GROUP called "all", should fix things > (I think) **** > > ** ** > > bobb **** > > ** ** > > > > >>> Jim Klassen wrote:**** > > It was intentional to migrate to using WMS over the MapServer specific > calls in the default case as it eases interoperability with other servers > and simplifies the code in many cases. > > I don't think it was intentional to loose the layers=all trick (which was > implemented inside MapServer not GeoMoose). Do any of the suggestions in > the MapServer ticket referenced by Bob work as a workaround for you? > > While 2.6 is near to release, one of the bigger tasks left is finishing up > documentation. Thank you for testing and bring this to our attention. > > On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote: > > > All: > > > > I am slowly migrating a GM 2.2 site with some minor customizations to > 2.6 and am wondering if what I am observing with my mapserver layers is by > design or an error on my part. > > > > On 2.6 it appears that all mapserver layers are requested as WMS which > appears to result in > > > > 1) any mapserver-type layer returns an error if the map file does not at > least contain something like 'ows_enable_request' '*', and > > > > 2) using the "all" parameter in the layer definition in the mapbook > returns an error. > > > > For example, in the 2.2 environment I have a "roads" source defined in > the mapbook very simply as such: > > > > > > ./sdwp/roads/webmaps_osm_lahwys.map > > > > > > show-legend="true" fade="false" unfade="false"/> > > > > The forwarded URL request is: > > > > > http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 > > > > The map file contains many scale-dependent line- and annotation layers > and renders beautifully. > > > > In the 2.6 environment the same mapbook definition and mapfile results > in this call: > > > > http://oph-isb-gis01/cgi-bin/mapserv.exe? > > > MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 > > > > which returns: > > > > > > msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the > LAYERS parameter. > > > > > > I have unsuccessfully searched for documentation on this topic. Please > advise. > > > > Thanks! > > Johan Forsman > > Geologist > > Engineering Services > > LDHH-OPH-CEHS > > 225.342.7309 > > > > > > _______________________________________________ > > Geomoose-users mailing list > > Geomoose-users@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users**** > > ** ** > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/fa1e022f/attachment.html From danlittle at yahoo.com Tue Apr 17 09:38:50 2012 From: danlittle at yahoo.com (Dan Little) Date: Tue Apr 17 09:39:44 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <63E03A1F-B3B1-408C-A2A7-C5AC09447879@gmail.com> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> <4F8C359E020000A800035449@heckle> <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> <63E03A1F-B3B1-408C-A2A7-C5AC09447879@gmail.com> Message-ID: <1334669930.48915.YahooMailNeo@web161201.mail.bf1.yahoo.com> There is no fall-back to MapServer mode. I really thought LAYERS=all was still working. In fact, I thought it's being used in the demo? To: Johan Forsman >Cc: Bob Basques ; "geomoose-users@lists.osgeo.org" >Sent: Monday, April 16, 2012 8:41 PM >Subject: Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? > > >Cool! > >The list is always a good place to start for problems/questions/feedback. > > >At one point I thought there was a fallback to the old MapServer mode, but I'm not seeing it in the code now. ?Maybe I missed it. ?Dan? > > >On Apr 16, 2012, at 8:08 PM, Johan Forsman wrote: > >Success! >>The fastest method I could think of to test all layers was a bulk Find of ?STATUS ON? and Replace with ?GROUP ?all?? which indeed allows the layers to display as intended using in the mapbook. >>I think this topic needs to be documented front and center in the migration guide as it represents a fundamental change in the way the application works. I am sure there are many instances of legacy GM/MapServer ?installations that may require significant retooling to work with the new version, especially if they are not configured to serve WMS already. >>Thanks for the tips and for a really great product. >>I am curious about Jim?s ?in the default case? ?statement. Does this mean there is a case where the MapServer layers are *not* translated to WMS calls? >>Incidentally, I may have discovered a few other items that may not be as intended. If they are not user error, where is appropriate to report them? >>Thanks again, >>Johan. >>From:?Bob Basques [mailto:Bob.Basques@ci.stpaul.mn.us]? >>Sent:?Monday, April 16, 2012 3:07 PM >>To:?Jim Klassen; Johan Forsman >>Cc:?geomoose-users@lists.osgeo.org >>Subject:?Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? >>? >>All (of you), >>? >>Just adding the desired layers to a GROUP called "all", should fix things (I think) >>? >>bobb >>? >> >> >>>>> Jim Klassen wrote: >>It was intentional to migrate to using WMS over the MapServer specific calls in the default case as it eases interoperability with other servers and simplifies the code in many cases. >> >>I don't think it was intentional to loose the layers=all trick (which was implemented inside MapServer not GeoMoose).? Do any of the suggestions in the MapServer ticket referenced by Bob work as a workaround for you? >> >>While 2.6 is near to release, one of the bigger tasks left is finishing up documentation.? Thank you for testing and bring this to our attention. >> >>On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote: >> >>> All: >>> >>> I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part. >>> >>> On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in >>> >>> 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and >>> >>> 2) using the "all" parameter in the layer definition in the mapbook returns an error. >>> >>> For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such: >>> >>> >>> ./sdwp/roads/webmaps_osm_lahwys.map >>> >>> >>> >>> >>> The forwarded URL request is: >>> >>>?http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 >>> >>> The map file contains many scale-dependent line- and annotation layers and renders beautifully. >>> >>> In the 2.6 environment the same mapbook definition and mapfile results in this call: >>> >>>?http://oph-isb-gis01/cgi-bin/mapserv.exe? >>> MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 >>> >>> which returns: >>> >>> >>> msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter. >>> >>> >>> I have unsuccessfully searched for documentation on this topic. Please advise. >>> >>> Thanks! >>> Johan Forsman >>> Geologist >>> Engineering Services >>> LDHH-OPH-CEHS >>> 225.342.7309 >>> >>> >>> _______________________________________________ >>> Geomoose-users mailing list >>>?Geomoose-users@lists.osgeo.org >>>?http://lists.osgeo.org/mailman/listinfo/geomoose-users >> >>_______________________________________________ >>Geomoose-users mailing list >>Geomoose-users@lists.osgeo.org >>http://lists.osgeo.org/mailman/listinfo/geomoose-users >>? > >_______________________________________________ >Geomoose-users mailing list >Geomoose-users@lists.osgeo.org >http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/b89362f7/attachment-0001.html From bfraser at geoanalytic.com Tue Apr 17 10:21:54 2012 From: bfraser at geoanalytic.com (Brent Fraser) Date: Tue Apr 17 10:23:03 2012 Subject: [Geomoose-users] Is the GeoMoose Wiki functioning? Message-ID: <4F8D7C82.8070400@geoanalytic.com> Is the GeoMoose Wiki functioning? I'm trying to access http://www.geomoose.org/wiki/index.php/Main_Page Is that the right URL? -- Best Regards, Brent Fraser From danlittle at yahoo.com Tue Apr 17 11:27:01 2012 From: danlittle at yahoo.com (Dan Little) Date: Tue Apr 17 11:27:50 2012 Subject: [Geomoose-users] Is the GeoMoose Wiki functioning? In-Reply-To: <4F8D7C82.8070400@geoanalytic.com> References: <4F8D7C82.8070400@geoanalytic.com> Message-ID: <1334676421.9481.YahooMailNeo@web161204.mail.bf1.yahoo.com> Fixed.? Mismatched postgresql driver/php versions. >________________________________ > From: Brent Fraser >To: GeoMOOSE Users List >Sent: Tuesday, April 17, 2012 9:21 AM >Subject: [Geomoose-users] Is the GeoMoose Wiki functioning? > > >Is the GeoMoose Wiki functioning?? I'm trying to access http://www.geomoose.org/wiki/index.php/Main_Page > >Is that the right URL? > >-- Best Regards, >Brent Fraser > > >_______________________________________________ >Geomoose-users mailing list >Geomoose-users@lists.osgeo.org >http://lists.osgeo.org/mailman/listinfo/geomoose-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/a7fb015c/attachment.html From Bob.Basques at ci.stpaul.mn.us Tue Apr 17 11:31:48 2012 From: Bob.Basques at ci.stpaul.mn.us (Bob Basques) Date: Tue Apr 17 11:32:35 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <1334669930.48915.YahooMailNeo@web161201.mail.bf1.yahoo.com> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> <4F8C359E020000A800035449@heckle> <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> <63E03A1F-B3B1-408C-A2A7-C5AC09447879@gmail.com> <1334669930.48915.YahooMailNeo@web161201.mail.bf1.yahoo.com> Message-ID: <4F8D4694020000A8000354DE@heckle> Skipped content of type multipart/alternative From danlittle at yahoo.com Tue Apr 17 11:42:06 2012 From: danlittle at yahoo.com (Dan Little) Date: Tue Apr 17 11:42:59 2012 Subject: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? In-Reply-To: <4F8D4694020000A8000354DE@heckle> References: <660F6AF362EE674B875E7BD4E289E2D80767FB50@MAILMBX06.MAIL.LA.GOV> <74BE956F-D6F1-4C58-AB82-71B41386FC27@gmail.com> <4F8C359E020000A800035449@heckle> <660F6AF362EE674B875E7BD4E289E2D80767FC6E@MAILMBX06.MAIL.LA.GOV> <63E03A1F-B3B1-408C-A2A7-C5AC09447879@gmail.com> <1334669930.48915.YahooMailNeo@web161201.mail.bf1.yahoo.com> <4F8D4694020000A8000354DE@heckle> Message-ID: <1334677326.40491.YahooMailNeo@web161206.mail.bf1.yahoo.com> None of that stuff is used from the *mapping* side of things.? This only effects *map rendering.*? You don't need to make any chances to any templates.? You are not forced to use SLD to configure cartography.? It simply *calls* mapserver using WMS instead of MODE=map.? This reduced quite a bit of code and creates significantly more consistency and testability with how requests are made. Plus, it forces users to configure WMS which is (theoretically) more secure and (definitely) more standardized. >________________________________ > From: Bob Basques >To: Jim Klassen ; Johan Forsman ; Dan Little >Cc: "geomoose-users@lists.osgeo.org" >Sent: Tuesday, April 17, 2012 10:31 AM >Subject: Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? > > >Hmm, ?I would vote for putting the MAPSERVER calling functionality back in, doesn't need to be default or anything, but removing functionality seems wrong for some reason. ?There are other things that mapserver can do that WMS/WFS can't yet. ?The templating options alone should be reason to keep it around. ?SLD templates are a bear to build. > >Is this something that could be applied via a extra module packaging or ??? > >bobb > > > >>>> Dan Little wrote: > >There is no fall-back to MapServer mode. > > >I really thought LAYERS=all was still working. In fact, I thought it's being used in the demo? > > >To:?Johan Forsman >>Cc:?Bob Basques ; "geomoose-users@lists.osgeo.org" >>Sent:?Monday, April 16, 2012 8:41 PM >>Subject:?Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? >> >> >> >>Cool! >> >> >>The list is always a good place to start for problems/questions/feedback. >> >> >>At one point I thought there was a fallback to the old MapServer mode, but I'm not seeing it in the code now. ?Maybe I missed it. ?Dan? >> >> >>On Apr 16, 2012, at 8:08 PM, Johan Forsman wrote: >> >> >>Success! >>>The fastest method I could think of to test all layers was a bulk Find of ?STATUS ON? and Replace with ?GROUP ?all?? which indeed allows the layers to display as intended using in the mapbook. >>>I think this topic needs to be documented front and center in the migration guide as it represents a fundamental change in the way the application works. I am sure there are many instances of legacy GM/MapServer ?installations that may require significant retooling to work with the new version, especially if they are not configured to serve WMS already. >>>Thanks for the tips and for a really great product. >>>I am curious about Jim?s ?in the default case? ?statement. Does this mean there is a case where the MapServer layers are *not* translated to WMS calls? >>>Incidentally, I may have discovered a few other items that may not be as intended. If they are not user error, where is appropriate to report them? >>>Thanks again, >>>Johan. >>>From:?Bob Basques [mailto:Bob.Basques@ci.stpaul.mn.us]? >>>Sent:?Monday, April 16, 2012 3:07 PM >>>To:?Jim Klassen; Johan Forsman >>>Cc:?geomoose-users@lists.osgeo.org >>>Subject:?Re: [Geomoose-users] Changes to mapserver-type layer handling in GM 2.6? >>>? >>>All (of you), >>>? >>>Just adding the desired layers to a GROUP called "all", should fix things (I think) >>>? >>>bobb >>>? >>> >>> >>>>>> Jim Klassen wrote: >>>It was intentional to migrate to using WMS over the MapServer specific calls in the default case as it eases interoperability with other servers and simplifies the code in many cases. >>> >>>I don't think it was intentional to loose the layers=all trick (which was implemented inside MapServer not GeoMoose).? Do any of the suggestions in the MapServer ticket referenced by Bob work as a workaround for you? >>> >>>While 2.6 is near to release, one of the bigger tasks left is finishing up documentation.? Thank you for testing and bring this to our attention. >>> >>>On Apr 16, 2012, at 2:24 PM, Johan Forsman wrote: >>> >>>> All: >>>> >>>> I am slowly migrating a GM 2.2 site with some minor customizations to 2.6 and am wondering if what I am observing with my mapserver layers is by design or an error on my part. >>>> >>>> On 2.6 it appears that all mapserver layers are requested as WMS which appears to result in >>>> >>>> 1) any mapserver-type layer returns an error if the map file does not at least contain something like 'ows_enable_request' '*', and >>>> >>>> 2) using the "all" parameter in the layer definition in the mapbook returns an error. >>>> >>>> For example, in the 2.2 environment I have a "roads" source defined in the mapbook very simply as such: >>>> >>>> >>>> ./sdwp/roads/webmaps_osm_lahwys.map >>>> >>>> >>>> >>>> >>>> The forwarded URL request is: >>>> >>>>?http://oph-isb-gis01/cgi-bin/mapserv.exe?map=/mapserver/apps/geomoose2/maps//sdwp/roads/webmaps_osm_lahwys.map&layers=all&mode=map&mapext=-10879743+3088767+-9475743+4200267&imgext=-10879743+3088767+-9475743+4200267&map_size=1404+1111&imgx=702&imgy=555.5&imgxy=1404+1111 >>>> >>>> The map file contains many scale-dependent line- and annotation layers and renders beautifully. >>>> >>>> In the 2.6 environment the same mapbook definition and mapfile results in this call: >>>> >>>>?http://oph-isb-gis01/cgi-bin/mapserv.exe? >>>> MAP=/mapserver/apps/geomoose26/maps//sdwp/roads/webmaps_osm_lahwys.map&FORMAT=image/png&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&LAYERS=all&SRS=EPSG%3A3857&BBOX=-10706687.23566,3214635.152984,-9648798.7643401,4074398.847016&WIDTH=865&HEIGHT=703 >>>> >>>> which returns: >>>> >>>> >>>> msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the LAYERS parameter. >>>> >>>> >>>> I have unsuccessfully searched for documentation on this topic. Please advise. >>>> >>>> Thanks! >>>> Johan Forsman >>>> Geologist >>>> Engineering Services >>>> LDHH-OPH-CEHS >>>> 225.342.7309 >>>> >>>> >>>> _______________________________________________ >>>> Geomoose-users mailing list >>>>?Geomoose-users@lists.osgeo.org >>>>?http://lists.osgeo.org/mailman/listinfo/geomoose-users >>> >>>_______________________________________________ >>>Geomoose-users mailing list >>>Geomoose-users@lists.osgeo.org >>>http://lists.osgeo.org/mailman/listinfo/geomoose-users >>>? >> >> >> >>_______________________________________________ >>Geomoose-users mailing list >>Geomoose-users@lists.osgeo.org >>http://lists.osgeo.org/mailman/listinfo/geomoose-users >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/ca091b14/attachment-0001.html From MarkVolz at co.lyon.mn.us Tue Apr 17 12:48:43 2012 From: MarkVolz at co.lyon.mn.us (Mark Volz) Date: Tue Apr 17 12:49:06 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> Message-ID: <36CA828A36E29F45B7CF0A1766E5DFA3104B84@swmail01.r8nssis.local> Dan, Sorry for the late reply, you had previously asked the group about documentation: Does anyone have an objection to cleaning up the docs to *only* apply to 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. Other projects, such as apache keep their documentation in separate subfolders. I don't know if it would be easy to implement, but maybe something like this would be clear, and useful for people stuck on older versions: Geomoose.org (the current version of GeoMOOSE) Geomoose.org/2.4 Geomoose.org/1.6 Geomoose.org/trunk Mark Volz GIS Specialist From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Dan Little Sent: Thursday, April 12, 2012 9:19 AM To: GeoMOOSE Users List Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? Hello List, We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. A demo is available here: - http://www.geomoose.org/demo/geomoose.html The current state of the documentation is here: - http://www.geomoose.org/trunk/ A relevant change log is here: - http://www.geomoose.org/trunk/releases/2.6.html Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose. We have moved to a versioned documentation system and the old docs will be preserved here: - http://www.geomoose.org/2.4/ "geomoose.org/" really just points to the latest stable documentation. Does anyone have an objection to cleaning up the docs to *only* apply to 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. We will be dropping an RC1 pending a few tickets. Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. Thanks for any input! -Duck -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/fa3a107a/attachment.html From danlittle at yahoo.com Tue Apr 17 13:08:18 2012 From: danlittle at yahoo.com (Dan Little) Date: Tue Apr 17 13:08:47 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <36CA828A36E29F45B7CF0A1766E5DFA3104B84@swmail01.r8nssis.local> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <36CA828A36E29F45B7CF0A1766E5DFA3104B84@swmail01.r8nssis.local> Message-ID: <1334682498.73701.YahooMailNeo@web161203.mail.bf1.yahoo.com> Mark, I think you'll find in the 2nd paragraph of my original email that we are keeping version-tagged docs. >________________________________ > From: Mark Volz >To: Dan Little ; GeoMOOSE Users List >Sent: Tuesday, April 17, 2012 11:48 AM >Subject: RE: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? > > > >Dan, >? >Sorry for the late reply, you had previously asked the group about documentation: >? >Does anyone have an objection to cleaning up the docs to *only* apply to 2.6?? My motivation is clarity.? 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. >? >Other projects, such as apache keep their documentation in separate subfolders.? I don?t know if it would be easy to implement, but maybe something like this would be clear, and useful for people stuck on older versions: >? >Geomoose.org? (the current version of GeoMOOSE) >Geomoose.org/2.4 >Geomoose.org/1.6 >Geomoose.org/trunk? >? >? >Mark Volz >GIS Specialist >? >From:geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Dan Little >Sent: Thursday, April 12, 2012 9:19 AM >To: GeoMOOSE Users List >Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? >? >Hello List, >? >We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. >? >A demo is available here: >- http://www.geomoose.org/demo/geomoose.html >? >The current state of the documentation is here: >- http://www.geomoose.org/trunk/ >? >A relevant change log is here: >- http://www.geomoose.org/trunk/releases/2.6.html >? >Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose.? We have moved to a versioned documentation system and the old docs will be preserved here: >- http://www.geomoose.org/2.4/ >? >"geomoose.org/" really just points to the latest stable documentation. >? >Does anyone have an objection to cleaning up the docs to *only* apply to 2.6?? My motivation is clarity.? 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. >? >We will be dropping an RC1 pending a few tickets.? Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. >? >Thanks for any input! >? >-Duck >? >? >? >? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/abd2e579/attachment-0001.html From Christopher.Kroot at maine.gov Tue Apr 17 14:28:46 2012 From: Christopher.Kroot at maine.gov (Kroot, Christopher) Date: Tue Apr 17 14:47:32 2012 Subject: [Geomoose-users] Is the GeoMoose Wiki functioning? In-Reply-To: <4F8D7C82.8070400@geoanalytic.com> References: <4F8D7C82.8070400@geoanalytic.com> Message-ID: Works for me Christopher Kroot Enterprise GIS Applications Manager, Maine Office of GIS State of Maine, Office of Information Technology State House Station 174 264 Civic Center Drive Augusta, Maine 04333-0174 christopher.kroot@maine.gov 207-592-0162 -----Original Message----- From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Brent Fraser Sent: Tuesday, April 17, 2012 10:22 AM To: GeoMOOSE Users List Subject: [Geomoose-users] Is the GeoMoose Wiki functioning? Is the GeoMoose Wiki functioning? I'm trying to access http://www.geomoose.org/wiki/index.php/Main_Page Is that the right URL? -- Best Regards, Brent Fraser _______________________________________________ Geomoose-users mailing list Geomoose-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geomoose-users From klassen.js at gmail.com Tue Apr 17 14:52:45 2012 From: klassen.js at gmail.com (Jim Klassen) Date: Tue Apr 17 14:53:16 2012 Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? In-Reply-To: <1334682498.73701.YahooMailNeo@web161203.mail.bf1.yahoo.com> References: <1334240315.29944.YahooMailNeo@web161204.mail.bf1.yahoo.com> <36CA828A36E29F45B7CF0A1766E5DFA3104B84@swmail01.r8nssis.local> <1334682498.73701.YahooMailNeo@web161203.mail.bf1.yahoo.com> Message-ID: <27064892-D4E5-4713-8712-3B91279B39E1@gmail.com> Also, old versions are always available in SVN. On Apr 17, 2012, at 12:08 PM, Dan Little wrote: > Mark, I think you'll find in the 2nd paragraph of my original email that we are keeping version-tagged docs. > > From: Mark Volz > To: Dan Little ; GeoMOOSE Users List > Sent: Tuesday, April 17, 2012 11:48 AM > Subject: RE: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? > > Dan, > > Sorry for the late reply, you had previously asked the group about documentation: > > Does anyone have an objection to cleaning up the docs to *only* apply to 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. > > Other projects, such as apache keep their documentation in separate subfolders. I don?t know if it would be easy to implement, but maybe something like this would be clear, and useful for people stuck on older versions: > > Geomoose.org (the current version of GeoMOOSE) > Geomoose.org/2.4 > Geomoose.org/1.6 > Geomoose.org/trunk > > > Mark Volz > GIS Specialist > > From: geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org] On Behalf Of Dan Little > Sent: Thursday, April 12, 2012 9:19 AM > To: GeoMOOSE Users List > Subject: [Geomoose-users] 2.6 - To Doc? To Purge? To Release? > > Hello List, > > We are getting *very* comfortable with the status of the code for the new GeoMoose 2.6 release. > > A demo is available here: > - http://www.geomoose.org/demo/geomoose.html > > The current state of the documentation is here: > - http://www.geomoose.org/trunk/ > > A relevant change log is here: > - http://www.geomoose.org/trunk/releases/2.6.html > > Currently, the docs contain a substantial amount of legacy instructions from older versions of GeoMoose. We have moved to a versioned documentation system and the old docs will be preserved here: > - http://www.geomoose.org/2.4/ > > "geomoose.org/" really just points to the latest stable documentation. > > Does anyone have an objection to cleaning up the docs to *only* apply to 2.6? My motivation is clarity. 2.6 simplifies installation quite a bit but it also deprecates a few functions and I'd rather not have too much "diff docing" going on as it can confuse new users. > > We will be dropping an RC1 pending a few tickets. Most of the docs will continue to apply but we are also looking for volunteers who are unafraid of writing docs and looking at some code. > > Thanks for any input! > > -Duck > > > > > > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/cc906fb0/attachment.html From Bob.Bistrais at maine.gov Tue Apr 17 17:12:33 2012 From: Bob.Bistrais at maine.gov (Bistrais, Bob) Date: Tue Apr 17 17:13:19 2012 Subject: [Geomoose-users] Table view in 2.6? Message-ID: <4EFF8BB964547748A07CA32961810C041D64109D@SOM-TEAQASMAIL1.som.w2k.state.me.us> In trying the latest GeoMoose demo, I tried the select features tool. Results show up in the window as expected. But there doesn't seem to be a table view as in previous versions? Did I miss something? That feature was very useful to us, and I hope it's implemented in 2.6. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/3f235ab9/attachment.html From anderson.dean at co.polk.or.us Tue Apr 17 17:14:43 2012 From: anderson.dean at co.polk.or.us (Anderson, Dean) Date: Tue Apr 17 17:22:38 2012 Subject: [Geomoose-users] Table view in 2.6? In-Reply-To: <4EFF8BB964547748A07CA32961810C041D64109D@SOM-TEAQASMAIL1.som.w2k.state.me.us> References: <4EFF8BB964547748A07CA32961810C041D64109D@SOM-TEAQASMAIL1.som.w2k.state.me.us> Message-ID: The "table view" is an Oregon extension. It will be replaced in the coming project by a new one based on the new software. Dean On Tue, Apr 17, 2012 at 2:12 PM, Bistrais, Bob wrote: > In trying the latest GeoMoose demo, I tried the select features tool. > Results show up in the window as expected. But there doesn?t seem to be a > table view as in previous versions? Did I miss something? That feature > was very useful to us, and I hope it?s implemented in 2.6.**** > > _______________________________________________ > Geomoose-users mailing list > Geomoose-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geomoose-users > > -- Dean R Anderson IT Director Polk County -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20120417/b1db2106/attachment-0001.html From bfraser at geoanalytic.com Tue Apr 17 17:39:00 2012 From: bfraser at geoanalytic.com (Brent Fraser) Date: Tue Apr 17 17:39:56 2012 Subject: [Geomoose-users] Setting initial conditions Message-ID: <4F8DE2F4.8030406@geoanalytic.com> Looks like I have a need to set an initial condition for my GeoMoose v2.4 site based on URL request values (these URLs are presented in a Django-generated page from a database query). There already are a couple of ways to set initial values in GeoMoose: 1. Specifying a Startup Service (http://www.geomoose.org/howto/startup.html) geomoose.html?call=set_image&fid=10&image_id=20 2. Bookmarks (hey, where's the Bookmark doc?) geomoose.html?extent=-2530013,12782588,-2028586,13213082&on=Icebergs/all But instead of the above scenarios, I want to call a JavaScript function (in my user extension) to programmatically select an item in the ZoomTo combo box, something like: geomoose.html?UX_call=set_combobox&image_id=20 Note that I keep the id in the value tag of the combo box options: