Re: [Qgis-user] Re: Annoying CRS-Problem with EPSG 31468 / 2167: Conclusions?
Am 30.03.2012 19:44, schrieb Etienne Tourigny: On Fri, Mar 30, 2012 at 6:23 AM,bernhard.stro...@jena.de wrote: Etienne, I see this stuff from a user's point of view. I am currently not working with different projections but my projects are EPSG:31468 and my data, too. So this is my perspective. I am neither a geodesist nor did I dig into how different software handles srs or prj files. All that I know is that QGIS (1.7.4) imports EPSG:31468 shape files as EPSG:2167 because it does neither evaluate the DATUM[D_Deutsches_Hauptdreiecksnetz nor the SPHEROID[Bessel_1841 infos given. Trunk creates a user-defined SRS and does not apply EPSG:31468 either. I would prefer QGIS to recognize the shape file as being EPSG:31468. Strictly speaking it is not exactly EPSG:31468 (that would require the AUTHORITY node, which .prj files do not have), but the PROJ.4 string should match that of EPSG:31468, at least. yup That is the problem with .prj files, it`s not easy to relate them to EPSG. then I would like to come back to my former suggestion: analyze the prj file and find any matching EPSG-code one EPSG - OK but tell user several - let user choose (and probably remember choice) none - ask user Am 30.03.2012 03:23, schrieb Etienne Tourigny: [snip] You can also play with the command line and see what comes up. GDAL_FIX_ESRI_WKT=GEOGCS gdalsrsinfo file.prj PROJ.4 : '+proj=tmerc +lat_0=0 +lon_0=12 +k=1 +x_0=450 +y_0=0 +ellps=bessel +towgs84=598.1,73.7,418.2,0.202,0.045,-2.455,6.7 +units=m +no_defs ' GDAL_FIX_ESRI_WKT=TOWGS84 gdalsrsinfo file.prj PROJ.4 : '+proj=tmerc +lat_0=0 +lon_0=12 +k=1 +x_0=450 +y_0=0 +ellps=bessel +towgs84=598.1,73.7,418.2,0.202,0.045,-2.455,6.7 +units=m +no_defs ' GDAL_FIX_ESRI_WKT=NO gdalsrsinfo file.prj PROJ.4 : '+proj=tmerc +lat_0=0 +lon_0=12 +k=1 +x_0=450 +y_0=0 +datum=potsdam +units=m +no_defs ' This would be my preferred parameters as datum=potsdam can be different towgs84 parameters in different locations How would this be decided? By the user or some magic way? The user can change it with the plugin Coordinate Systems Updater. You see: if the datum gets translated into a towgs84 parameter and the projection is matched based on this then if a different user-defined towgs84 paramter exists the right projection is not found. according to http://mapref.org/GeodeticReferenceSystemsDE.html#Zweig733 the towgs84=598.1,73.7,418.2,0.202,0.045,-2.455,6.7 is applicable for the whole country of Germany but local towgs84 parameters may differ Then it makes sense to have those +towgs84 parameters as the default, if you leave them out then you get an incorrect datum shift. agreed This sort of contradicts your statement that it should be recognized as EPSG:31468 because that code is NOT potsdam datum (in GDAL/OGR anyway) AFAIK the DHDN is the realisation of the Potsdam Datum see e.g. here: http://georepository.com/datum_6314/Deutsches-Hauptdreiecksnetz.html so in the prj file it is called DATUM[Deutsches_Hauptdreiecksnetz whereas Proj4 says +datum=potsdam ; both mean the same OK Using proj-4.7.1 and gdal-1.9 the +datum=potsdam gives different towgs84 parameters than EPSG:4314. This has been fixed in proj-4.8. Could this contribute to the problem? I would not think so, as it is just another towgs84 parameter set which gives a different position when making a 7-parameter transformation $ gdalsrsinfo '+proj=tmerc +lat_0=0 +lon_0=12 +k=1 +x_0=450 +y_0=0 +datum=potsdam +units=m +no_defs ' PROJ.4 : '+proj=tmerc +lat_0=0 +lon_0=12 +k=1 +x_0=450 +y_0=0 +ellps=bessel +towgs84=606,23,413,0,0,0,0 +units=m +no_defs ' $ gdalsrsinfo EPSG:4314 PROJ.4 : '+proj=longlat +ellps=bessel +towgs84=598.1,73.7,418.2,0.202,0.045,-2.455,6.7 +no_defs ' However the problem persists that QGIS does not recognize the projection as EPSG:31468 no matter if I set it to GEOGCS, TOWGS84 or NO! Neiter does it detect the correct projction from the prj file QGIS itself created. The GEOGCS option to GDAL_FIX_ESRI_WKT fixes the GEOGCS authority node, but not the root node which is a PROJCS (see example below)! Trying to match all possible projections can be more challenging than matching the possible geogcs definitions. It is possible, but I didn't get there yet. Just to make sure I understand - is the expected behaviour in QGis (from you POV) to see the file as EPSG:31468 with the TOWGS84 parameters seen above? Or the more generic 'potsdam' datum? Maybe it would be better to see the towgs84 parameters (as defined by QGIS default or the user via the plugin) but 1) it must be imported as EPSG:31468 (and not as user-defined) 2) if saving to shapefile only the DATUM[Deutsches_Hauptdreiecksnetz must be written (as QGIS does) and IMHO not the TOWGS84[598.1,73.7,418.2,0.202,0.045,-2.455,6.7] I agree. What is written to .prj file by QGis when you choose EPSG:31468 ? 1.7.4:
[Qgis-user] Re: [Qgis-developer] SEXTANTE for QGIS has been released
Thanks Radim That means that some distributions of QGIS might have a QT version lower that 4.7? The one I am using works fine, so i gues is 4.7. Is there any way of checking it on the fly, so I can execute that line only if the version is recent enough? Thanks in advance El día 1 de abril de 2012 22:14, Radim Blazek radim.bla...@gmail.com escribió: JFYI, AttributeError: 'QLineEdit' object has no attribute 'setPlaceholderText' setPlaceholderText was introduced in Qt 4.7. QT_MIN_VERSION in QGIS is 4.4.0. Radim On Thu, Mar 29, 2012 at 11:11 PM, Victor Olaya vola...@gmail.com wrote: Hi all I am glad to announce that a first (tagged as 'experimental') version SEXTANTE for QGIS has been released. It includes, among other things: -Full support for SAGA algorithms -ftool(vector processes) and mmqgis algorithms (these are not only added to be used directly, but also as real examples of how to create new algorithms or migrate existing ones into the SEXTANTE platform) -Support for user-defined R scripts -Support for user defined Python scripts -Graphical modeler -Batch processing interface -History You can download it using the QGIS plugin installer Please, read the manual before using the plugin. You can access it selecting the SEXTANTE help option in the SEXTANTE menu. This version is still missing some functionalities, but should be fully usable. Users should be particularly aware of the following issues: -External applications (SAGA and R) have been tested mostly on Windows, but not so much in Linux, so problems might appear on that platform. No testing has been done at all under Mac OS. -GRASS algorithms have been deactivated, in order to have a working version as soon as possible. We hope to have GRASS incorporated into the set of available algorithms pretty soon -Although most algorithms support multiple formats for their ouput layers, these are currently limited to tiff for raster layers, shapefiles for vector layers and dbf files for tables. This can be changed easily and will be done in a next version -Calling external applications might not work if using layers such as those coming from remote services or DB connections. Please, use just file-based data by now (we are working on improving that as well, but it might take time... ;-) ) -Using tables (and also opening those generated by geoalgorithms) is still a bit in development, since there is no built-in default method of opening independent tables. By now, attribute tables of vector layers can be used, but only if these are in shapefile format (since we can refer to the associated dbf file). We expect to change this soon, probably creating some plugin to improve that handling of independent tables (or if anyone can point us to an existing one that can be coupled with SEXTANTE, that good be even better...) Once again, read the manual before trying it, as it will greatly help you to understand SEXTANTE and what you can do with it. For developers: I know a lot of documentation is needed...hope to have that solved soon (or at least start to solve it). A SEXTANTE for QGIS developers manual is also on its way... there is already a mechanism to create QGIS plugins that register new algorithms in SEXTANTE (thanks to Alexander Bruy for the suggestion!), but still has to be documented. I am currently working on an well documented example case, to be released soon as well Of course, all bug reports and comments are welcome, since this is still a beta version. Thanks in advance for your interest. ___ Qgis-developer mailing list qgis-develo...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] SEXTANTE for QGIS has been released
Please remember also that it is possible to use rasters in GRASS without importing them, but just registering them (r.external), with insignificant loss of performances. Thus, we can more or less forget about grass rasters in their native format, for most of the uses. All the best. -- , Interesting. Thanks for the information! ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: [Qgis-developer] SEXTANTE for QGIS has been released
On Mon, Apr 2, 2012 at 9:59 AM, Victor Olaya vola...@gmail.com wrote:
Thanks Radim
That means that some distributions of QGIS might have a QT version
lower that 4.7? The one I am using works fine, so i gues is 4.7. Is
there any way of checking it on the fly, so I can execute that line
only if the version is recent enough?
Hi Victor
in Python you can use 'hasattr' builtin function:
edit = QLineEdit()
if hasattr(edit, 'setPlaceholderText'): edit.setPlaceholderText('foo')
Cheers
Martin
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: [Qgis-developer] SEXTANTE for QGIS has been released
On Mon, Apr 2, 2012 at 1:34 PM, Alexander Bruy alexander.b...@gmail.com wrote: minQtVersion = '4.6.0' def initGui(self): if qVersion() minQtVersion: QMessageBox.warning( self.iface.mainWindow(), Error, Your message) self.loadingCanceled = True return None Hi Alex there may be a problem with above code. Imagine that PyQt4 is built with e.g. Qt 4.2 - that means that it will provide only methods available in Qt 4.2 and below. If the user updates Qt version to 4.8, the new methods and classes will not be available in PyQt4, however qVersion() will return '4.8.0'. There is also PYQT_VERSION_STR variable in PyQt4.QtCore that returns the version of Qt used to build PyQt. Martin ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] SEXTANTE for QGIS has been released
Hi Victor, A great idea, the original one :-). I am sure you are right the way data is organized in GRASS is scary for new users. It took me some time before I got used to GRASS and its way of data organization. And although I like it very much now, it is a steep learning curve. So this would really open the GRASS set of functions for a much wider audience. I am also happy you are planning the other way around for the near future. Unfortunately I cannot offer much help in terms of programming, but when the time is there, I am happy to do some testing if needed. Best regards, Paulo On 04/02/2012 12:10 PM, Victor Olaya wrote: Paulo, The idea (at least, my original idea) was to let users with no GRASS knowledge to use GRASS algorithms from a more common GIS interface. So they do not have to worry about mapsets and things like that, and they execute the algorithm just like they would do with any other one. The mapset and location is created automatically each time the algorithm is run, and all data imported into it. Then the results are exported and loaded in the GIS. This might have some limitations, of course, but in the Java version of SEXTANTE it has proved very useful to make those algorithms available to most users, specially those that were a bit afraid of the complexity of GRASS or were not used to its interface or its command-line syntax. Using GRASS layers is a different thing, but as I said, I hope to have that already in a near future, and also to be able to use those GRASS layers in other algorithms, so SEXTNATE will become the intermediate layer for all analysis and data sources, and doing it as transparently as possible Regards El día 2 de abril de 2012 11:54, Paulo van Breugel p.vanbreu...@gmail.com escribió: On 04/02/2012 09:47 AM, Paolo Cavallini wrote: On 30/03/2012 23:19, Victor Olaya wrote: Well, the idea is just the opposite: to use any raster or vector layer in GRASS, directly from QGIS. Any in this context means any normal Please remember also that it is possible to use rasters in GRASS without importing them, but just registering them (r.external), with insignificant loss of performances. Thus, we can more or less forget about grass rasters in their native format, for most of the uses. All the best. Just to be clear, I assume you mean here that there is no need to convert (import) other raster layers to GRASS layers in order to use GRASS functions? I am asking because this option doesn't help the user who has his/her data in a GRASS database. For me the strict and transparent handling of region settings and projection has always been one of the strong points of GRASS, and I am curious how the workflow will be when working with external rasters. Like with internal rasters, an external raster layer does need to be in the same projection as the current location. Furthermore, raster functions use the region settings (extend, resolution) of the current mapset as far as I understand. When importing, it is possible to create a new location on the fly based on the raster you are importing. This makes it easier to deal with the above (I think), e.g., by creating a temporary location. I am not sure linking an external raster offers the same option (I had a quick look, but can't find the option, but maybe I just overlooked it). But then, the normal import function allows to create a location based on a raster without actually importing the raster. So the two could be combined. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Homebrew formula for QGIS
Hi list! Is there a homebrew formula for latest qgis? I'm having problems with running metatools plugin on OS X Lion. It seems like it depends on some qt modules, that aren't present in kyngchaos build. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Homebrew formula for QGIS
I don't know about homebrew, but the QGIS build instructions are quite clear. What Qt module does metatools need? I've included extra Qt stuff that made sense to me, but I can add others. On Apr 2, 2012, at 7:39 AM, Gis Mage wrote: Hi list! Is there a homebrew formula for latest qgis? I'm having problems with running metatools plugin on OS X Lion. It seems like it depends on some qt modules, that aren't present in kyngchaos build. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user - William Kyngesburye kyngchaos*at*kyngchaos*dot*com http://www.kyngchaos.com/ Time is an illusion - lunchtime doubly so. - Ford Prefect ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Homebrew formula for QGIS
Hi William, Metatools plugin used QtCore, QtGui, QtXml and QtXmlPatterns modules. 2012/4/2 William Kyngesburye wokl...@kyngchaos.com: I don't know about homebrew, but the QGIS build instructions are quite clear. What Qt module does metatools need? I've included extra Qt stuff that made sense to me, but I can add others. -- Alexander Bruy ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Homebrew formula for QGIS
Those are all included. What error are you getting? On Apr 2, 2012, at 9:00 AM, Alexander Bruy wrote: Hi William, Metatools plugin used QtCore, QtGui, QtXml and QtXmlPatterns modules. 2012/4/2 William Kyngesburye wokl...@kyngchaos.com: I don't know about homebrew, but the QGIS build instructions are quite clear. What Qt module does metatools need? I've included extra Qt stuff that made sense to me, but I can add others. -- Alexander Bruy ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user - William Kyngesburye kyngchaos*at*kyngchaos*dot*com http://www.kyngchaos.com/ The beast is actively interested only in now, and, as it is always now and always shall be, there is an eternity of time for the accomplishment of objects. - the wisdom of Tarzan ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Closure of forum
All, Throwing my two cents in here. I think I've posted to the QGIS list maybe once or twice over the years. I much prefer the Email lists over anything else. I can read at my liesure and I can read everything I'm interested in. Forums are a bear to search for stuff. Although, they do have a search function. I think a forum is better suited to a Dev list if it's a large population, simply to segment the different topics. But a smaller group is likely going to use a single list to communicate. bobb Mats Elfströmmats.elfst...@gmail.com wrote: Hi! According to qgis.org, there are ten (10) current mailing lists for Qgis. If there is a need to fragment the communication that much, maybe a traditional forum with subgroups would be a better idea than my proposal for a Google group. I feel mailing lists are outdated. There are a lot of forum services to choose from. Regards, Mats.E Den 1 april 2012 10:11 skrev MORREALE Jean Roc jr.morre...@enoreth.net: The point of the forum closure is to avoid fragmentation of the greatest and the rarest resource we have to share with the users : brains. So unless you can keep a google group in sync with the official list , using a new place will not improve the situation in this regard. Le 01/04/2012 08:50, Mats Elfström a écrit : Hi! Simply find Google Groups and look there for QGISGRASS. Then apply for membership. At the moment, only members can view topics. Personally, I'm in favor of open groups, but this is at the managers discretion. Making the group free to read, but with restricted posting is a good alternative. Google Groups works very well for the MapInfo forum, MapInfo-L, and the FME forum FME Talk. I am a member of both. Every participant can choose how to take part in the forum, from receiving every post as e-mail, abridged daily summaries, or only reading it on the web. Regards, Mats.E Den 31 mars 2012 20:50 skrev Mark Hall mhall89...@att.net mailto:mhall89...@att.net: How does one join the QGISGRASS group? *From:* Mats Elfström mats.elfst...@gmail.com mailto:mats.elfst...@gmail.com *To:* Nick Hopton nhop...@gmail.com mailto:nhop...@gmail.com *Cc:* qgis-user@lists.osgeo.org mailto:qgis-user@lists.osgeo.org *Sent:* Sat, March 31, 2012 10:30:52 AM *Subject:* Re: [Qgis-user] Closure of forum Hi! Start a Google Qgis group, or join the existing QGISGRASS group. That way all is taken care of, and no one needs to host or administer the thing. It could be fully open, or for registered users only. Regards, Mats.E Den 31 mars 2012 19:10 skrev Nick Hopton nhop...@gmail.com mailto:nhop...@gmail.com: I read QGIS-User on Nabble, where the posts on the closure of the forum appear somehow to have got mixed up with the Sextante thread, so forgive me for starting a new thread. The closure is a done deal I suppose but I think it will be harmful to QGIS. Forum users are now being pointed to Stack Exchange but many of them will, I believe, take one look at Stack Exchange and run a mile. The Stack Exchange GIS FAQ makes it quite clear that SE is intended for ...cartographers, database administrators, geographers, programmers, and anyone interested in or using GIS professionally. I don't fit into any one of these categories, nor I think would many of the people who used to post on the forum. They tended to be newcomers to QGIS, or people who make maps and use GIS as just a part of their job, or as part of a recreational activity, or any combination of the three. Some of them will be young and engaged in things like school projects. It would be nice to think that these people will shift to SE, but I can't see this happening. But we'll soon be able to tell, if things work as hoped a lot of newby-type questions should soon start appearing on SE. It will be interesting to see the responses. ___ Qgis-user mailing list Qgi s-u...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user -- __ Mats Elfström, Väpplingvägen 21, SE-227 38 LUND, Sweden tel: +46 46 145959 / mob: +46 70 595 39 35 alt e-mail: mats.elfst...@telia.com ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Re: sextante plugin on mac
Yes, the file Statistics is generated, same with other methods like nna. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/sextante-plugin-on-mac-tp4671656p4679082.html Sent from the Quantum GIS - User mailing list archive at Nabble.com. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] problems with GRASS plugin with QGIS on Fedora 16?
Hello, I don't know if the re are more people with the same problem. When I work with QGIS on Fedora 16 64 bits, I only can work when I start the program without plugins. When I start qgis with plugins I cannot work. I suspect that the problem is with the GRASS plugin, bat I'm not sure. (There is no problem with Debian Testing with QGIS + GRASS.) Thanks :) ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] problems with GRASS plugin with QGIS on Fedora 16?
Why not to test one plug-in at a time? Karlis, using Fedora 14 x 64 x...@tarbz2.net wrote: .. When I work with QGIS on Fedora 16 64 bits, I only can work when I start the program without plugins. When I start qgis with plugins I cannot work. I suspect that the problem is with the GRASS plugin, bat I'm not sure. .. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] problems with GRASS plugin with QGIS on Fedora 16?
Ok, 1.- I tested without plugins: $ qgis --noplugins and it works perfectly. 2.- Then, I have removed the qgis-grass plugin rpm: # yum remove qgis-grass and the package qgis-grass.x86_64 0:1.7.4-1.fc16 was removed. Then I tested with the rest of plugins: xavi@chryse64:~$ qgis Warning: QNetworkDiskCache::expire() The cache directory is not set Python support ENABLED :-) Loaded : RasterCalc (package: rastercalc) Loaded : fTools (package: fTools) Loaded : GdalTools (package: GdalTools) Loaded : SEXTANTE (package: sextante) Loaded : Plugin Installer (package: plugin_installer) Loaded : OpenStreetMap plugin (package: osm) Loaded : MapServer Export (package: mapserver_export) and it works perfectly. 3.- Then I have reinstalled the grass plugin qgis-grass.x86_64 0:1.7.4-1.fc16 : root@chryse64 xavi# yum install qgis-grass ang then QGIS crashed when I tried to start: xavi@chryse64:~$ qgis Warning: QNetworkDiskCache::expire() The cache directory is not set Python support ENABLED :-) terminate called after throwing an instance of 'QgsGrass::Exception' what(): Incompatible library version for module. You need to rebuild GRASS or untangle multiple installations. I tested with Fedora 16 x 64. The version of GRASS I have, is: xavi@chryse64:~$ yum info grass Connectors carregats: fastestmirror, langpacks, presto, refresh-packagekit, : tidy-cache Loading mirror speeds from cached hostfile * fedora: mirror.uv.es * rpmfusion-free: mirror.de.leaseweb.net * rpmfusion-free-updates: mirror.de.leaseweb.net * rpmfusion-nonfree: mirror.de.leaseweb.net * rpmfusion-nonfree-updates: mirror.de.leaseweb.net * updates: mirror.uv.es Paquets instal·lats Name: grass Arch: x86_64 Version : 6.4.2 Release : 2.fc16 Size: 45 M Repo: installed From repo : updates Summary : GRASS - Geographic Resources Analysis Support System URL : http://grass.fbk.eu License : GPLv2+ Descripció : GRASS (Geographic Resources Analysis Support System) is a : Geographic Information System (GIS) used for geospatial data : management and analysis, image processing, graphics/maps : production, spatial modeling, and visualization. GRASS is : currently used in academic and commercial settings around the : world, as well as by many governmental agencies and : environmental consulting companies. Why not to test one plug-in at a time? Karlis, using Fedora 14 x 64 x...@tarbz2.net wrote: .. When I work with QGIS on Fedora 16 64 bits, I only can work when I start the program without plugins. When I start qgis with plugins I cannot work. I suspect that the problem is with the GRASS plugin, bat I'm not sure. .. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] (no subject)
I think that I could resolve the problem, if I do an upgrade of the package QGIS. Sorry, I'm new in the Fedora world :) https://bugzilla.redhat.com/show_bug.cgi?id=806442 ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] problems with GRASS plugin with QGIS on Fedora 16 [SOLVED]
I think that I could resolve the problem, if I do an upgrade of the package QGIS. Sorry, I'm new in the Fedora world :) https://bugzilla.redhat.com/show_bug.cgi?id=806442 And when I have reinstalled the new builds of QGIS: http://koji.fedoraproject.org/koji/buildinfo?buildID=309750 the problem was solved :-) ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] sextante plugin on mac
On Apr 1, 2012, at 2:19 AM, Victor Olaya wrote: but others complaint about python (e.g. sextante help, or line intersections). Line intersection is fixed. The problem with help is that it calls the default application for opening the pdf manual. I prepared it to work on linux and windows...but not on mac, so basically it should be trying to open it like it does in linux, which I gess it is not working :( Hi Victor, What is your linux command? On OSX, a simple bash command of `open foo.pdf` will open the default pdf viewer. I'm not sure if that helps or not. Regards, John___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] sextante plugin on mac
Perfect, that it what I said I was looking for, colllaboration from the community. It is not necessary to actually code, but to help me (or others) do things easily, in this case considering that I do not know anything about OSX Regards El día 2 de abril de 2012 17:58, John C. Tull jct...@gmail.com escribió: On Apr 1, 2012, at 2:19 AM, Victor Olaya wrote: but others complaint about python (e.g. sextante help, or line intersections). Line intersection is fixed. The problem with help is that it calls the default application for opening the pdf manual. I prepared it to work on linux and windows...but not on mac, so basically it should be trying to open it like it does in linux, which I gess it is not working :( Hi Victor, What is your linux command? On OSX, a simple bash command of `open foo.pdf` will open the default pdf viewer. I'm not sure if that helps or not. Regards, John ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Re: sextante plugin on mac
I can help in Python but the problem is that there is no version of SAGA GIS for Mac OS X. I tried to install it following http://sourceforge.net/apps/trac/saga-gis/wiki/Compiling%20SAGA%20on%20Mac%20OS%20X http://sourceforge.net/apps/trac/saga-gis/wiki/Compiling%20SAGA%20on%20Mac%20OS%20X but without success. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/sextante-plugin-on-mac-tp4671656p4679434.html Sent from the Quantum GIS - User mailing list archive at Nabble.com. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Re: sextante plugin on mac
yes, but it is necessary to compile these modules -- View this message in context: http://osgeo-org.1560.n6.nabble.com/sextante-plugin-on-mac-tp4671656p4679860.html Sent from the Quantum GIS - User mailing list archive at Nabble.com. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
