Re: [mapguide-users] MapGuide REST Extension Documentations
Hi! You can get some information on www.georest.com and from sample which comes with georest download. There will be some documentation/wiki soon, but for now I can give you some explanation on how to work with georest. simon On Sun, Mar 28, 2010 at 8:42 PM, Nimrod Cnaan nimcn...@hotmail.com wrote: Is there any Documentations on how to work with Jason's RESTful technology ? -- View this message in context: http://n2.nabble.com/MapGuide-REST-Extension-Documentations-tp4814222p4814222.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
[mapguide-users] turquoiseyellow theme SelectionPanel error
With this theme, if you select an object in the map, It doesn't appear in the selection panel. What's wrong? -- View this message in context: http://n2.nabble.com/turquoiseyellow-theme-SelectionPanel-error-tp4823135p4823135.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] Re: turquoiseyellow theme SelectionPanel error
It must be any error with the file fusionSF-compressed.js. If I remove this line (using fusion.js), the problem appear fixed. -- View this message in context: http://n2.nabble.com/turquoiseyellow-theme-SelectionPanel-error-tp4823135p4823277.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] Re: Feature Labels are fade in MGOS 2.0 in Linux
Hi zspitzer, Sorry for not responding long time due to some medical issue i am not able to access. Below are the answer step wise I am using very common font in windows that is Arial and it is present in the Centos 5 where I upload the package. Layer XML ===START== ?xml version=1.0 encoding=UTF-8? LayerDefinition xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xsi:noNamespaceSchemaLocation=LayerDefinition-1.1.0.xsd version=1.1.0 VectorLayerDefinition ResourceIdLibrary://WebGIS/Data/Data.FeatureSource/ResourceId FeatureNameOGRSchema:house_no_labels/FeatureName FeatureNameTypeFeatureClass/FeatureNameType Filter/ PropertyMapping Nametext/Name Valuetext/Value /PropertyMapping Geometrywkb_geometry/Geometry Url/ ToolTip/ VectorScaleRange LineTypeStyle LineRule LegendLabel/ Label UnitPoints/Unit SizeContextDeviceUnits/SizeContext SizeX10/SizeX SizeY10/SizeY Rotation0/Rotation Texttext/Text FontNameArial/FontName ForegroundColorffc6/ForegroundColor BackgroundColor/BackgroundColor BackgroundStyleTransparent/BackgroundStyle HorizontalAlignment'Center'/HorizontalAlignment VerticalAlignment'Baseline'/VerticalAlignment Boldfalse/Bold Italicfalse/Italic Underlinedfalse/Underlined /Label /LineRule /LineTypeStyle /VectorScaleRange /VectorLayerDefinition /LayerDefinition ===END== Screen Shots You can view maney labels which is fade some of them are highlighted with Black squire. http://n2.nabble.com/file/n4823648/house_no_label.jpg Please let me know if have any idea on this. Thanking You Sudip Barman -- View this message in context: http://n2.nabble.com/Feature-Labels-are-fade-in-MGOS-2-0-in-Linux-tp4539572p4823648.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] Re: re: google mapintegration with mapguide
I have the same issue now. Maybe is a bug in fussion. -- View this message in context: http://n2.nabble.com/re-google-mapintegration-with-mapguide-tp3049773p4823732.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] building 64bit openmapguide on rhel 5.4
Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] openmapguide 2.1 build problem
Dear fellows, Our office have a 64bit RHEL 5.4 Linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. I already tried the latest version of DWFTK from Autodesk, but didn't help. Can anyone help me, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users Balogh Ádám adatbázisgazda GDS 2000 Kft. 1074 Budapest, VII. ker. Dohány u. 20. III/15. Telefon: +36-1-344-5495 Balogh Ádám adatbázisgazda GDS 2000 Kft. 1074 Budapest, VII. ker. Dohány u. 20. III/15. Telefon: +36-1-344-5495 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ 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] Re: re: google mapintegration with mapguide
To work around the Overview map projection issue do the following: O On line 110 of OverviewMap.js, add the following 2 lines: this.mapObject.projection = this.getMap().oMapOL.getProjection() this.mapObject.oLayerOL.projection = this.getMap().oMapOL.getProjection() This will alllow the overview to support whatever projection your main map is in. The overview map is only a single layer - the MapGuide layers being the single layer. It doesn't allow a MapGuide and Google layer at the same time without some coding (someone correct me if I am off base). I fiddled with the code and got the Google layer in, but haven't got it working quite properly. Need more spare time. Cheers, Kori Maleski On Tue, Mar 30, 2010 at 3:48 AM, Jose Cerrejon g...@mapas-sll.com wrote: I have the same issue now. Maybe is a bug in fussion. -- View this message in context: http://n2.nabble.com/re-google-mapintegration-with-mapguide-tp3049773p4823732.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
[mapguide-users] Re: re: google mapintegration with mapguide
I filed a ticket in the fusion trac for this and it was closed because the latest trunk version could not reproduce it. I haven't had time to test it myself, but you might try downloading the latest version and see if that fixes your problem. -Mark P. -- View this message in context: http://n2.nabble.com/re-google-mapintegration-with-mapguide-tp3049773p4825273.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] Out of memory exception when generating tiles from large raster imagery
Hi MapGuide users, Following the release to public of our application based on Autodesk MapGuide Entreprise 2010, we are facing some annoying crashes of the service (a minimum of one crash per day and sometime every couple of hours). Of course, before the release to public, with only few users and not an extensive use, but with the exact same MapGuide service and hardware, we did not detect this problem. Thanks to the logs generated since last week, we found that the error is almost every time the same: an out of memory exception when generating tiles from large raster imagery. Example of this error: 2010-03-30T09:42:31 3380Ajax Viewer xx.xxx.xx.xxAdministrator Error: Failed to stylize layer: X Out of memory. bad allocation StackTrace: - MgMappingUtil.StylizeLayers() line 791 file d:\build\testarossa_nightly\build_37.1\ent\os\server\src\services\mapping\MappingUtil.cpp When this error occur, the service throws few unclassified exceptions during 1 or 2 minutes. Restarting the service is not an option as it refuses to stop himself. The only solution is to kill the process through a taskkill command (fortunately we developed a small application to do it automatically, based upon a Jason's idea : http://lists.osgeo.org/pipermail/mapguide-users/2006-May/001039.html). We found a lot of thing to read ([mapguide out of memory] on Google = 1650 results), and the scenarios described are close to our : - MG Error Out of memory, bad allocation, by juergenk http://n2.nabble.com/MG-Error-Out-of-memory-bad-allocation-td3298687.html This case uses TIFF files, but without tiled layers in MapGuide. - Continued MGOS 2.0.1 Crashes, by Andy Morsell http://n2.nabble.com/Continued-MGOS-2-0-1-Crashes-td1817284.html No answer to this old post (2008). - Ticket #480 (reopened defect), by zspitzer Crash with MgInvalidStreamHeaderException with GETTILEIMAGE (load test) http://trac.osgeo.org/mapguide/ticket/480 This old still open ticket demonstrates a way to reproduce a crash server with an MgInvalidStreamHeaderException. We also have sometime this exception just before the service crash. Some other time is an OSGeo.MapGuide.MgDbXmlException Error: Out of memory in NsSAX2Reader parse File. Furthermore, we also read carefully the best practices wiki on http://sandbox.mapguide.com Some specifications: - MapGuide installation Autodesk MapGuide Entreprise 2010 Update 1b .NET IIS FDO 3.4 - Server hardware Windows Server 2003 Datacenter Edition SP2 Intel Xeon E5405 2.00 GHz x 4 8.00 GB RAM We are suspicious about the out of memory exception (does MapGuide log the real exception?) as MapGuide service uses only 300 to 400 MB (but it's maybe already too high?). The CPU is never above 25%. However, just before the crash, the CPU can be higher than 80% during a couple of minutes. Here's my questions: Our rasters are ECW files, tiles generated by MapGuide are JPEG files of 600px, the FDO provider is the Autodesk Raster provider and layers are only display beneath a zoom of 1:3. - Is Autodesk Raster provider better than OpenSource GDAL provider? - Is ECW a good (or the best) format for raster imagery inside MapGuide? - Maybe TIFF is preferable? Our ECW files are around 25 MB and there are 200 files per folder (i.e. one folder = 4.5 GB = 1 DVD!). - Is there some guideline about number of files and size? On the map definiton, we have one base layer group with five base layers (1 base layer = 1 DVD). - Is it better to merge all files into a single base layer (and a single folder on the file system) or to dispatch them into a lot of base layers? Thank for reading, I would appreciate some feedback. -- View this message in context: http://n2.nabble.com/Out-of-memory-exception-when-generating-tiles-from-large-raster-imagery-tp4825554p4825554.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] Out of memory exception when generating tiles from large raster imagery
Hello Julien, For a multi user load, the Autodesk raster provider should give you better performance. The GDAL provider in MapGuide is currently limited to a single thread to improve stability. ECW is an excellent format for MapGuide. TIFF is also good but it requires a lot more disk space. For ECW, you may get a more usable memory footprint by using a smaller number of larger ECW images. I have not tried this myself so I cannot say for certain. The out of memory exception is typically caused by exceeding the virtual memory on the MapGuide Server process, and not the working set. Under Windows Task Manager, View... Select Columns... add Peak Memory Usage and Virtual Memory Size. If either of these hit 1.5GB or more for the MapGuide Server process, you are likely to run into problems. Once the beta for MapGuide 2.2 is out the door, I will be looking at stability and performance for the GDAL Raster Provider. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of julienltr Sent: March 30, 2010 10:17 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] Out of memory exception when generating tiles from large raster imagery Hi MapGuide users, Following the release to public of our application based on Autodesk MapGuide Entreprise 2010, we are facing some annoying crashes of the service (a minimum of one crash per day and sometime every couple of hours). Of course, before the release to public, with only few users and not an extensive use, but with the exact same MapGuide service and hardware, we did not detect this problem. Thanks to the logs generated since last week, we found that the error is almost every time the same: an out of memory exception when generating tiles from large raster imagery. Example of this error: 2010-03-30T09:42:31 3380Ajax Viewer xx.xxx.xx.xxAdministrator Error: Failed to stylize layer: X Out of memory. bad allocation StackTrace: - MgMappingUtil.StylizeLayers() line 791 file d:\build\testarossa_nightly\build_37.1\ent\os\server\src\services\mapping\MappingUtil.cpp When this error occur, the service throws few unclassified exceptions during 1 or 2 minutes. Restarting the service is not an option as it refuses to stop himself. The only solution is to kill the process through a taskkill command (fortunately we developed a small application to do it automatically, based upon a Jason's idea : http://lists.osgeo.org/pipermail/mapguide-users/2006-May/001039.html). We found a lot of thing to read ([mapguide out of memory] on Google = 1650 results), and the scenarios described are close to our : - MG Error Out of memory, bad allocation, by juergenk http://n2.nabble.com/MG-Error-Out-of-memory-bad-allocation-td3298687.html This case uses TIFF files, but without tiled layers in MapGuide. - Continued MGOS 2.0.1 Crashes, by Andy Morsell http://n2.nabble.com/Continued-MGOS-2-0-1-Crashes-td1817284.html No answer to this old post (2008). - Ticket #480 (reopened defect), by zspitzer Crash with MgInvalidStreamHeaderException with GETTILEIMAGE (load test) http://trac.osgeo.org/mapguide/ticket/480 This old still open ticket demonstrates a way to reproduce a crash server with an MgInvalidStreamHeaderException. We also have sometime this exception just before the service crash. Some other time is an OSGeo.MapGuide.MgDbXmlException Error: Out of memory in NsSAX2Reader parse File. Furthermore, we also read carefully the best practices wiki on http://sandbox.mapguide.com Some specifications: - MapGuide installation Autodesk MapGuide Entreprise 2010 Update 1b .NET IIS FDO 3.4 - Server hardware Windows Server 2003 Datacenter Edition SP2 Intel Xeon E5405 2.00 GHz x 4 8.00 GB RAM We are suspicious about the out of memory exception (does MapGuide log the real exception?) as MapGuide service uses only 300 to 400 MB (but it's maybe already too high?). The CPU is never above 25%. However, just before the crash, the CPU can be higher than 80% during a couple of minutes. Here's my questions: Our rasters are ECW files, tiles generated by MapGuide are JPEG files of 600px, the FDO provider is the Autodesk Raster provider and layers are only display beneath a zoom of 1:3. - Is Autodesk Raster provider better than OpenSource GDAL provider? - Is ECW a good (or the best) format for raster imagery inside MapGuide? - Maybe TIFF is preferable? Our ECW files are around 25 MB and there are 200 files per folder (i.e. one folder = 4.5 GB = 1 DVD!). - Is there some guideline about number of files and size? On the map definiton, we have one base layer group with five base layers (1 base layer = 1 DVD). - Is it better to merge all files into a single base layer (and a single folder on the file system) or to dispatch them into a lot of base layers? Thank for reading, I would appreciate some feedback. -- View this message in context:
[mapguide-users] RE: MapGuide REST Extension Documentations
Thanks for the reference, the explanation of the GeoREST's site helped me to get started. I hade also seen your http://www.sl-king.com/mgrest/ work. I have to pause my restful implementation for the meantime (Again) due to other commitments - be in touch. Date: Mon, 29 Mar 2010 22:47:50 -0800 From: ml-node+4823025-1108654891-67...@n2.nabble.com To: nimcn...@hotmail.com Subject: Re: MapGuide REST Extension Documentations Hi! You can get some information on www.georest.com and from sample which comes with georest download. There will be some documentation/wiki soon, but for now I can give you some explanation on how to work with georest. simon On Sun, Mar 28, 2010 at 8:42 PM, Nimrod Cnaan [hidden email] wrote: Is there any Documentations on how to work with Jason's RESTful technology ? -- View this message in context: http://n2.nabble.com/MapGuide-REST-Extension-Documentations-tp4814222p4814222.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/mapguide-users View message @ http://n2.nabble.com/MapGuide-REST-Extension-Documentations-tp4814222p4823025.html To unsubscribe from MapGuide REST Extension Documentations, click here. _ Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009 -- View this message in context: http://n2.nabble.com/MapGuide-REST-Extension-Documentations-tp4814222p4826254.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] building 64bit openmapguide on rhel 5.4
Adam, I will be grateful if you could share your learnings on 64 bit build. I tried with 2.0.2 (the one downloadable) and though after herculean efforts I managed to compile stuff (mix-match etc etc), the final thing did not run (it went into some weird loop - 100% cpu, mem consumption - so much so that I could barely kill the process) thanks rajeev Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Trevor Wekel Sent: 30 March 2010 11:17 To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ 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] Re: re: google mapintegration with mapguide
Sweet fix Kori. Works for MapGuide Enterprise 2010. -- View this message in context: http://n2.nabble.com/re-google-mapintegration-with-mapguide-tp3049773p4826477.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] Up to date and correct config.xml file
Hello, Hello, I'm running MGE2010 in Windows and to date have been unsuccessful in creating config.xml files for loaded imagery sets. Neither Studio or Maestro have generated the needed files so I wrote a workaround that accomplishes my needs. I was looking over the files today and noticed that all of the OSGEO namespace links are sorely out of date when tested. Every reference that I've checked that starts with http://fdo.osgeo.org/... returns a 'Page Not Found' error. This is due to the age of the source config.xml document that I used for my template. Is there a correct and up-to-date config.xml file floating out there that has had all of the name spaces and other URL entries vetted and corrected? Please provide the specific URL if it does exit. Thanks all Tom ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hello list, MapGuide 2.0 and 2.1 have never been validated as a 64 bit build. MapGuide 2.2 will be the first 64 bit capable release. For the beta (coming soon), we may not have 64 bit versions built and packaged. We are planning to address this before the final 2.2 release. From the last PSC meeting http://trac.osgeo.org/mapguide/wiki/PscMeeting02-04-2010, here is what was discussed: Expected release is 32 and 64 bit for windows (with 32bit webtier/apache/php), and 32 bit linux. Trevor will look into problems with 64bit linux support. Once I have completed the 32 bit build and packaging for Linux, I will investigate build and packaging of the 64 bit Server for Linux. If all goes well, MapGuide 2.2 will have both 32 and 64 bit Server binaries available for Windows, RedHat/CentOS 5.4, and Ubuntu 9.10. The Web Extensions binaries will likely be 32 bit. There have already been requests for 64 bit Web Extensions on the -internals list. If time permits, the PSC may re-evaluate the feasibility of a 64 bit Web Extensions. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh Sent: March 30, 2010 12:07 PM To: MapGuide Users Mail List Cc: ad...@geoform.hu Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Adam, I will be grateful if you could share your learnings on 64 bit build. I tried with 2.0.2 (the one downloadable) and though after herculean efforts I managed to compile stuff (mix-match etc etc), the final thing did not run (it went into some weird loop - 100% cpu, mem consumption - so much so that I could barely kill the process) thanks rajeev Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Trevor Wekel Sent: 30 March 2010 11:17 To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ 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
Re: [mapguide-users] Re: re: google mapintegration with mapguide
Thanks Gordon, Mark, I am stuck on a specific version of the trunk at the moment so I can't upgrade yet - so I am stuck with the workaround for a bit. Cheers, Kori Maleski On Tue, Mar 30, 2010 at 11:57 AM, GordonL gordon.luck...@arrowgeomatics.com wrote: Sweet fix Kori. Works for MapGuide Enterprise 2010. -- View this message in context: http://n2.nabble.com/re-google-mapintegration-with-mapguide-tp3049773p4826477.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
[mapguide-users] Discalaimer Patch ?
I'm not sure on the process or ramifications of modifying the ajaxmappane
are.
But I've been playing around with the disclaimer place holders (a couple of
postes here have shown how they are implemented) and thought it might be a
worthy addition ?
I've added the following functions to the ajaxmappane.templ
function SetDisclaimer(content)
{
disclaimerDiv.innerHTML = content;
}
function GetDisclaimer()
{
return disclaimerDiv.innerHTML;
}
Also added the following div after the td id=map onmouseout=return
ExitMap(event)
div id=disclaimerDiv style=position:absolute;
right:3px;bottom:3px;z-index:999;
This function could be hooked into when layers are turned on and off.
I'd like some ideas of a better way to implement this as I belive a
disclaimer about data age/integrity is important information that the user
needs to be aware of for some datastores.
Even a way of imprinting this on the image that is produced for the viewer
as an option so when printing or creating a print layout the diclaimer
remains.
--
View this message in context:
http://n2.nabble.com/Discalaimer-Patch-tp4827930p4827930.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] building 64bit openmapguide on rhel 5.4
Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb On Tue, 2010-03-30 at 15:15 +0200, ad...@geoform.hu wrote: Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ 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] building 64bit openmapguide on rhel 5.4
Thanks for sharing that - though Trevor has explicitly said that 2.2 is the one that might be 64 bit, let me share my experience on Centos 5.5 (btw you can use the 32 bit build on 64 bit machine) **Trevor - my interest in 64 bit was actually to use it against 64 bit java (and the current plan for not doing 64 bit web components, in my opinion, restricts utility to a large extent. I also did -fPIC - infact lots of the makefiles did not pass on the parameters (i.e. the makefiles being generated do not follow good practices of taking things from environment). So created a script wrapper around gcc/cc/g++/c++ (yup all the 4 compiler commands are used by the make files) The DwfCore needed to be tweaked (for the Tick32) and some compile directives needed to be checked. I got a sense looking at these files and one of the core component files (I forget which one) had assumptions builit in about size of int and there were issues fixed for 16 to 32 bit conversion, though I think we did a cursory fix the end result was that though successful compilation happened, the thing did not run. Anyway I will look at 2.2 branch and retry 64 bit compilation. thx Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of kfw...@bombasticlocution.com Sent: 30 March 2010 21:43 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb On Tue, 2010-03-30 at 15:15 +0200, ad...@geoform.hu wrote: Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core'
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hi Rajeev, You will need to create 64 bit FDO libraries before compiling MapGuide. MapGuide 2.2 should be built against FDO 3.5.0. I have started working on Linux build and packaging scripts for both FDO and MapGuide. The scripts are a work in progress but they might get you somewhere on a 64 bit machine. I haven't tried them yet. http://svn.osgeo.org/fdo/branches/3.5/install/ - buildall.sh, buildfdocore.sh, buildfdoprovider.sh http://svn.osgeo.org/mapguide/trunk/Installer/scripts/ - build.sh, revnum.pl If you make some headway with the 64bit Linux builds and would like to make changes to these scripts, please let me know. A couple of cautionary words before you begin: - MapGuide 2.2 will only build on GCC 4.1. Trying to use GCC 4.4 is problematic to say the least. - Check out http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. It could save you a few hours. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh Sent: March 30, 2010 10:56 PM To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Thanks for sharing that - though Trevor has explicitly said that 2.2 is the one that might be 64 bit, let me share my experience on Centos 5.5 (btw you can use the 32 bit build on 64 bit machine) **Trevor - my interest in 64 bit was actually to use it against 64 bit java (and the current plan for not doing 64 bit web components, in my opinion, restricts utility to a large extent. I also did -fPIC - infact lots of the makefiles did not pass on the parameters (i.e. the makefiles being generated do not follow good practices of taking things from environment). So created a script wrapper around gcc/cc/g++/c++ (yup all the 4 compiler commands are used by the make files) The DwfCore needed to be tweaked (for the Tick32) and some compile directives needed to be checked. I got a sense looking at these files and one of the core component files (I forget which one) had assumptions builit in about size of int and there were issues fixed for 16 to 32 bit conversion, though I think we did a cursory fix the end result was that though successful compilation happened, the thing did not run. Anyway I will look at 2.2 branch and retry 64 bit compilation. thx Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of kfw...@bombasticlocution.com Sent: 30 March 2010 21:43 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb On Tue, 2010-03-30 at 15:15 +0200, ad...@geoform.hu wrote: Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed
