Re: [mapguide-users] Looking for public Mapguide links.
Hi try this http://mapa.procad.pl http://mapa.stargard.pl http://chojnice.city-guide.pl -- Maciej Skórczewski programista GIS. PROCAD SA Autodesk Authorized Value Added Reseller www.procad.pl ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] Re: what's holding people back from upgrading to 2.0?
there's been a quite a few comments saying that the newer FDO releases are too slow from what I've noticed is it actually the AGG rendering engine or FDO? one of my projects uses about 9.6 Gb of data for a map, it does seem that AGG is a bit slower than GD but the latest mapguide is a lot more stable, not quite perfect yet but it's a hell of a lot better z On Tue, Oct 7, 2008 at 1:01 PM, Zac Spitzer [EMAIL PROTECTED] wrote: There seems to be quite a few people who are sticking with 1.2 due to various issues Can people post in this thread what issues are holding them back so we can get some visibility? -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
Having followed the posts and ... Better the Devil you know than the one you don't. r, dennis ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] Categories.txt still a problem on linux
Hi Jason, I don't know about monitoring tools, but I guess I can have a look. I have tried starting apache first, then mgserver, but that doesn't help either. I notice that mgserver.sh is supposed to set the variables, but when I check using printenv they don't show up once mgserver is started. Thanks Jo JasonBirch wrote: Hi Jo, Is there any kind of monitoring tool in Linux that shows failed file opens? MapGuide is obviously not looking in the right place for the files, but it's hard to know where it IS looking ;) It's odd that none of the files are being picked up... I believe those environmental variables are case sensitive; assuming you set them up in uppercase? Also... This is probably a server issue, but grasping at straws... I think that Apache may strip out environmental variables when it starts up. I wonder if there is a way of setting PROJ_LIB and GDAL_DATA in the apache conf file? Jason -Original Message- From: Joanne Cook Subject: [mapguide-users] Categories.txt still a problem on linux After once managing to sort out my categories.txt problem, and being able to see all of my coordinate systems in linux, it appears this was a one off and I now can't, either with my original 2.0.1 installation or 2.0.2. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users -- View this message in context: http://www.nabble.com/Categories.txt-still-a-problem-on-linux-tp19801069p19859506.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
even better is feedback to address this issue.. what have you gathered from the posts which make you hold back? This is really important information to share, discuss and address... z On Tue, Oct 7, 2008 at 8:55 PM, Jonio, Dennis (Aviation) [EMAIL PROTECTED] wrote: Having followed the posts and ... Better the Devil you know than the one you don't. r, dennis ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] Wrapper over MapGuide WMS
Hi All, I have developed a wrapper over MapGuide WMS which essentially filters the layers that are available to clients based on the projects that they have access. For eg: calling my wrapper as below: http://myserver/mywms/mywms.ashx?REQUEST=GETCAPABILITIESSERVICE=WMSVERSION=1.1.1FORMAT=text%2fxmlprojectname=Exercise will return the capabilities document with the list of published layers only for the Exercise project (folder which is set in Studio). This works fine when I invoke the url in a web browser. However, my question is: What should I do for my server to be recogonized as a WMS server by MapGuide Studio or any other client such as Gaia or ArcGIS? Many thanks, poy -- View this message in context: http://www.nabble.com/Wrapper-over-MapGuide-WMS-tp19855431p19855431.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
One big issue for me is the impossibility to use PostgreSQL+Postgis as database solution for geographic data. The new Postgis provider does not work (it seems to be only for windows, and not so stable). The old OGR Provider, that works fine in 1.2 ... does not work in 2.0.1 and in 2.0.2. Our build from source code doesn't work, windows binaries don't work, livecd doesn't work either. Clearly neither MGE2008. A long standing bug is opened (#666) http://trac.osgeo.org/mapguide/ticket/666 but it is not receiving any feedback (maybe the bug number is unfortunate...) Some mails to this mailing list and some questions on #mapguide and on #fdo on IRC are still waiting for answers. It appears that not so many Mapguide users are interested in Postgresql+Postgis, even if, IMHO, is one of the best RDMS for geographic data. We've seen that Mapguide 2.x has a lot of improvement over 1.2. But, as a matter of fact, does not support Postgresql+postgis. So we're stuck with old 1.2 until this problem is solved. Regards, Gabriele On Tue, Oct 7, 2008 at 12:00, Zac Spitzer [EMAIL PROTECTED] wrote: even better is feedback to address this issue.. what have you gathered from the posts which make you hold back? This is really important information to share, discuss and address... z On Tue, Oct 7, 2008 at 8:55 PM, Jonio, Dennis (Aviation) [EMAIL PROTECTED] wrote: Having followed the posts and ... Better the Devil you know than the one you don't. r, dennis ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
We experienced extreme CPU and/or memory consumption when we tested MGOS 2.x with some of our data. We created a ticket(#459 https://trac.osgeo.org/mapguide/ticket/459) to document our problems, and I have been testing this issue with all of the updated releases, and I continue to see the same results. We can't zoom all the way into our maps without the server locking up and consuming all of the CPU, which is stopping us from moving a production environment to MGOS 2. We've been able to modify 1.2 to suit our needs for almost everything with plugins; and if we couldn't add a specific feature, we went in another direction. So far, that has been a killer for our migration. Zac Spitzer wrote: even better is feedback to address this issue.. what have you gathered from the posts which make you hold back? This is really important information to share, discuss and address... z ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -Original Message- From: Jonathan Manafi Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? We experienced extreme CPU and/or memory consumption when we tested MGOS 2.x with some of our data. We created a ticket(#459 https://trac.osgeo.org/mapguide/ticket/459) to document our problems, and I have been testing this issue with all of the updated releases, and I continue to see the same results. We can't zoom all the way into our maps without the server locking up and consuming all of the CPU, which is stopping us from moving a production environment to MGOS 2. We've been able to modify 1.2 to suit our needs for almost everything with plugins; and if we couldn't add a specific feature, we went in another direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -Original Message- From: Jonathan Manafi Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? We experienced extreme CPU and/or memory consumption when we tested MGOS 2.x with some of our data. We created a ticket(#459 https://trac.osgeo.org/mapguide/ticket/459) to document our problems, and I have been testing this issue with all of the updated releases, and I continue to see the same results. We can't zoom all the way into our maps without the server locking up and consuming all of the CPU, which is stopping us from moving a production environment to MGOS 2. We've been able to modify 1.2 to suit our needs for almost everything with plugins; and if we couldn't add a specific feature, we went in another direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] ArcSDE FDO sucks !!!
Shreepad, As Jason said, it is not clear that this is a provider issue. One issue was identified sometime ago related to invalid coordinate system handling in MG. This issue was slowing down performance when coordinates system couldn't be mapped. This was fixed in the recent MG code stream but I'm not sure it was backported in the code stream where you are seeing this problem. I'm trying to contact the developer who look into this issue and see if we can get a hotfix or patch to try out. I'm not sure that it will actually fix the problem you are seeing but it doesn't cost much trying it out. I'll keep you posted. RF -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of shreepad Ranadive Sent: Monday, October 06, 2008 5:28 PM To: mapguide-users@lists.osgeo.org Subject: RE: [mapguide-users] ArcSDE FDO sucks !!! thanks jason i will create a trac for this on fdo site. I have tested this with couple layers with new schema created its still slow. let me create trac to have it looked at by developers thanks shreepad JasonBirch wrote: You may be asking on the wrong list if you want the FDO folks to respond. Though I'm sure that some of them hang out here from time to time, fdo-users is a better place. Might want to use a less inflammatory subject line though :) The problem may not be with the SDE provider though; I wonder if it is the same problem with initial schema load as has been seen with the RDBMS providers. Does performance decrease as the number of tables stored in the SDE increases, or is it consistently slow? The best way to get this fixed is to clearly describe the problem, preferably with test data, in a Trac ticket. Just saying that it is slow is not giving the developers enough to chew on. Jason -Original Message- From: shreepad Ranadive Subject: Re: [mapguide-users] ArcSDE FDO sucks !!! I found the same issue. the new fdos are bit slow with sde 9.1 /9.2 i think some one from FDO team should take a look at it seriously FDO team : please have some reply to this request ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users - Shreepad Ranadive Direcotor , Application Development ValueCAD 444 Natoma St Sanfrancisco,CA 94103 -- View this message in context: http://www.nabble.com/ArcSDE-FDO-sucks-%21%21%21-tp19832086p19846802.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
I'm using 1.2 on my release machine. It's primarily because of a bug in 2.0 which doesn't allow me to access a SDF resource after GetSelectionXML() or SetSelectionXML() is called. This is detailed in the trac ticket http://trac.osgeo.org/mapguide/ticket/524. Basically, if a user searches for a job, or parcel, then they won't be able to interact with it further because the resource will be busy. It basically negates the search function of my program, which makes the program itself pretty useless. -Mark Pendergraft -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zac Spitzer Sent: Monday, October 06, 2008 7:02 PM To: MapGuide Users Mail List Subject: [mapguide-users] what's holding people back from upgrading to 2.0? There seems to be quite a few people who are sticking with 1.2 due to various issues Can people post in this thread what issues are holding them back so we can get some visibility? -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] Please help! Has anybody used King.Oracle in real conditions?
Haris : did you get time to look into this. please let us know shreepad FISHeR1 wrote: Has anybody used King.Oracle in real conditions? Or it was created and tested by the developers, who ascertained outputed and calmed down? In real conditions it is impossible to use this provider! File mgserver.exe is damaged after a half an hour of intensive working. Earlier I have written about the reason – memory leak ( http://www.nabble.com/King.Oracle-0.7.3-(0.7.4)-Memory-Leak-with-MGOS-2.0-(2.0.1,-2.0.2)-tt19690045.html King.Oracle 0.7.3 (0.7.4) Memory Leak with MGOS 2.0 (2.0.1, 2.0.2) ), but nobody has answered. Has anybody any ideas? What to do? - Shreepad Ranadive Direcotor , Application Development ValueCAD 444 Natoma St Sanfrancisco,CA 94103 -- View this message in context: http://www.nabble.com/Please-help%21-Has-anybody-used-King.Oracle-in-real-conditions--tp19793029p19866195.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
Did you try to use scale ranges to control the style and visibility of the bad layer at high zoom factors? This may alleviate your problem. Traian -Original Message- From: [EMAIL PROTECTED] [mailto:mapguide-users- [EMAIL PROTECTED] On Behalf Of Jonathan Manafi Sent: Tuesday, October 07, 2008 3:57 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -Original Message- From: Jonathan Manafi Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? We experienced extreme CPU and/or memory consumption when we tested MGOS 2.x with some of our data. We created a ticket(#459 https://trac.osgeo.org/mapguide/ticket/459) to document our problems, and I have been testing this issue with all of the updated releases, and I continue to see the same results. We can't zoom all the way into our maps without the server locking up and consuming all of the CPU, which is stopping us from moving a production environment to MGOS 2. We've been able to modify 1.2 to suit our needs for almost everything with plugins; and if we couldn't add a specific feature, we went in another direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
We had some scale ranges in use that implemented some area styling, but I went ahead and added another, specifically for high zoom ranges(tried 0-1000). For our previous styling, we had a dashed line border(line04) and a feature label of the NAME property. I went ahead and just implemented a solid line border. - In the AGG renderer, hitting under 1:100 caused the server to consume steady 50% CPU. - In GD, nothing happened. The server continued to respond the same as in normal conditions. So, I tried changing the area style to a dashed line. In GD, using a dashed line caused the server to start eating up memory under 1:100, which really started occurring around 1:50. While zooming in, the memory would temporarily jump to over 200MB, and once the server was no longer using the CPU, the memory would restore itself to around 48MB. At the next zoom level, the memory would jump a little higher, perhaps 280-300MB and then restore itself. At around 1:6, the memory stayed at 520MB usage and would increase at sequential zooms. After that, the memory was never released by the server. Also, once the memory started increasing that much, the layer would no longer be displayed beyond a certain zoom scale; it seems to occur under 1:30. If I remember correctly, when I gave the layer to be tested way back when, I think Jason made a comment that this layer was made up of thousands of vertices. I understand that styling and rendering all of that data for a layer is expensive, but how come in this situation two standard styles offered by Autodesk(solid and dashed lines) differ so differently in performance? Thanks for your help. Traian Stanev wrote: Did you try to use scale ranges to control the style and visibility of the bad layer at high zoom factors? This may alleviate your problem. Traian -Original Message- From: [EMAIL PROTECTED] [mailto:mapguide-users- [EMAIL PROTECTED] On Behalf Of Jonathan Manafi Sent: Tuesday, October 07, 2008 3:57 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -Original Message- From: Jonathan Manafi Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? We experienced extreme CPU and/or memory consumption when we tested MGOS 2.x with some of our data. We created a ticket(#459 https://trac.osgeo.org/mapguide/ticket/459) to document our problems, and I have been testing this issue with all of the updated releases, and I continue to see the same results. We can't zoom all the way into our maps without the server locking up and consuming all of the CPU, which is stopping us from moving a production environment to MGOS 2. We've been able to modify 1.2 to suit our needs for almost everything with plugins; and if we couldn't add a specific feature, we went in another direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
I have modified the viewer to prevent zooming closer than 1:100, because the server performs terrible at that point. I have logged an issue here: http://trac.osgeo.org/mapguide/ticket/523 I have not tried different styles, but I was guessing that the renderer tries to map the the entire polygon to pixels, and a building at 1:3 takes MANY pixels. Regards, Kenneth Skovhede, GEOGRAF A/S Jonathan Manafi skrev: We had some scale ranges in use that implemented some area styling, but I went ahead and added another, specifically for high zoom ranges(tried 0-1000). For our previous styling, we had a dashed line border(line04) and a feature label of the NAME property. I went ahead and just implemented a solid line border. - In the AGG renderer, hitting under 1:100 caused the server to consume steady 50% CPU. - In GD, nothing happened. The server continued to respond the same as in normal conditions. So, I tried changing the area style to a dashed line. In GD, using a dashed line caused the server to start eating up memory under 1:100, which really started occurring around 1:50. While zooming in, the memory would temporarily jump to over 200MB, and once the server was no longer using the CPU, the memory would restore itself to around 48MB. At the next zoom level, the memory would jump a little higher, perhaps 280-300MB and then restore itself. At around 1:6, the memory stayed at 520MB usage and would increase at sequential zooms. After that, the memory was never released by the server. Also, once the memory started increasing that much, the layer would no longer be displayed beyond a certain zoom scale; it seems to occur under 1:30. If I remember correctly, when I gave the layer to be tested way back when, I think Jason made a comment that this layer was made up of thousands of vertices. I understand that styling and rendering all of that data for a layer is expensive, but how come in this situation two standard styles offered by Autodesk(solid and dashed lines) differ so differently in performance? Thanks for your help. Traian Stanev wrote: Did you try to use scale ranges to control the style and visibility of the bad layer at high zoom factors? This may alleviate your problem. Traian -Original Message- From: [EMAIL PROTECTED] [mailto:mapguide-users- [EMAIL PROTECTED] On Behalf Of Jonathan Manafi Sent: Tuesday, October 07, 2008 3:57 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -Original Message- From: Jonathan Manafi Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? We experienced extreme CPU and/or memory consumption when we tested MGOS 2.x with some of our data. We created a ticket(#459 https://trac.osgeo.org/mapguide/ticket/459) to document our problems, and I have been testing this issue with all of the updated releases, and I continue to see the same results. We can't zoom all the way into our maps without the server locking up and consuming all of the CPU, which is stopping us from moving a production environment to MGOS 2. We've been able to modify 1.2 to suit our needs for almost everything with plugins; and if we couldn't add a specific feature, we went in another direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
