Re: [Qgis-user] Re: Overview (inset map ) in map composer
I don't think that "they" (they being me, by the way) forgot that was a problem. I probably just did a poor job of articulating the issue and solution. I recognize that the overview map is not always what you want for an overview map in the composer. What might be a better solution would be to have an overview map option in the composer that uses those layers that you have selected to be in the overview map on the canvas. You could then change the scale of this overview map in the composer, recenter, etc. Something like a "Place overview map" tool or similar. Cheers, John On Oct 27, 2010, at 3:47 PM, Alister Hood wrote: > Hi guys, > There is a feature request for adding the map from the overview pane to > the composer: > https://trac.osgeo.org/qgis/ticket/2348 > That person is after essentially the same result as you Marco, but they > seem to have forgotten that the extent of the map view is almost always > at least slightly different from the extent of the detail map in the > print composer. So the map extent rectangle shown in the overview would > be wrong. > > It might be more flexible anyway to have a plugin add a rectangle to a > normal map canvas on the print composer, showing the extents of another > map canvas. I think this would be a popular feature - does anyone know > how feasible it would be? > > I imagine the other problem mentioned in that ticket (the difficulty > around preserving/changing the layers shown on a map canvas in the > composer) is something that should be addressed separately. > > Regards, > Alister > >> Date: Wed, 27 Oct 2010 15:42:10 + (UTC) >> From: Marco Tuckner >> Subject: [Qgis-user] Re: Overview (inset map ) in map composer >> To: qgis-user@lists.osgeo.org >> Message-ID: >> Content-Type: text/plain; charset=us-ascii >> >>> You can simply add another map to the canvas, and then set the >> extents and >> scale to only cover your area of interest. >> Yes. >> But how do I make them dynamically zoom and also display an extend >> rectangle on >> the overview map showing th extend of the detailed map? >> >> Thanks for following up. >> >> Regards, >> Marco > ___ > 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] Re: [GRASS-user] tiff imported to GRASS loses minus sign in west coordinate
On 10/28/2010 07:56 PM, A. Marcia BARBOSA wrote: Dear lists, I need to import the map available here (http://geodata.grid.unep.ch/mod_download/download_geospatial.php?selectedID=2150&newFile=download/Nightlights_2003_tif.zip) to GRASS. The map is in Tiff format and appears fine in QGIS, but when I import it to GRASS (with r.in.gdal) it becomes a very narrow N-S stripe. Here's the raster info that QGIS gives me on this map: I think I know what the problem is. Have a look at the bounds below: Corner Coordinates: Upper Left (-180.0041667, 65.0041667) (180d 0'15.00"W, 65d 0'15.00"N) Lower Left (-180.0041667, -65.0041661) (180d 0'15.00"W, 65d 0'15.00"S) Upper Right ( 180.0041652, 65.0041667) (180d 0'14.99"E, 65d 0'15.00"N) Lower Right ( 180.0041652, -65.0041661) (180d 0'14.99"E, 65d 0'15.00"S) The left (W) extent goes beyond -180 and the right (E) also goes beyond +180. So the image has "fallen off the edge" ;-) If I check with gdalinfo on the original tiff, before importing into GRASS, here's what I see: mi...@hayun-820:~/Download$ gdalinfo Nightlights_2003.tif Driver: GTiff/GeoTIFF Size is 43201, 15601 ... more lines ... Pixel Size = (0.00830042660,-0.00830042660) ... more metadata ... Corner Coordinates: Upper Left (-180.000, 65.000) (180d 0'0.00"W, 65d 0'0.00"N) Lower Left (-180.000, -65.0082820) (180d 0'0.00"W, 65d 0'29.82"S) Upper Right ( 180.0081912, 65.000) (180d 0'29.49"E, 65d 0'0.00"N) Lower Right ( 180.0081912, -65.0082820) (180d 0'29.49"E, 65d 0'29.82"S) Center ( 0.0040956, -0.0041410) ( 0d 0'14.74"E, 0d 0'14.91"S) Here again the Right side is > 180. So, in import to GRASS, it gets "wrapped" to the west, and the end result is, like above, a very narrow raster with E-W extent 0.015 degrees. One way to work this out is to clip the original raster slightly before importing. The gdal tool gdal_translate does this with the -projwin option like: gdal_translate -projwin -179.99 65 179.99 -65 Nightlights_2003.tif Nightlights_2003clip.tif Here, I've shaved off a bit on the E and W so it fits into the -180 to 180 bounds. Now if I redo r.in.gdal using the clipped raster, it appears correctly in GRASS. -- Micha Thanks for any help, Márcia ___ grass-user mailing list grass-u...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user This mail was received via Mail-SeCure System. -- Micha Silver Arava Development Co. +972-52-3665918 http://surfaces.co.il ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Nightly builds on Ubuntu
> As a related issue the grass package in ubuntugis is incompatible with > qgis-plugin-grass. I want to mention it in case it is just a packaging > issue that can be easily solved (I don't really know if it is). I mean the qgis-plugin-grass package in debian-nightly. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Nightly builds on Ubuntu
2010/10/27 Jürgen E. : > Hi Agus, > > On Wed, 27. Oct 2010 at 15:40:12 +0200, Agustin Lobo wrote: >> Is there any way to set the repositories >> deb http://qgis.org/debian-nightly lucid main >> deb-src http://qgis.org/debian-nightly lucid main > >> for nightly builds but keep the stable version also? >> (the one from ubuntugis/ubuntugis-unstable ) > > No, but you can downgrade. > As a related issue the grass package in ubuntugis is incompatible with qgis-plugin-grass. I want to mention it in case it is just a packaging issue that can be easily solved (I don't really know if it is). Goyo ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] QGIS Stuck in Full Screen Mode
Hi Darren, On Thu, 28. Oct 2010 at 12:00:32 -0700, Darren Cope wrote: > What am I missing? The registry: HKEY_CURRENT_USER\Software\QuantumGIS Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-20 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] QGIS Stuck in Full Screen Mode
Hi all, A strange question. I somehow managed to get qgis stuck in 'full screen' mode, with no title bars visible. How do I get it back to 'normal'? I'm on Windows 7, and installed via OSGeo4W. I am running the 'dev' version, but the setting seems to be applied to the 'stable' version as well. I've tried reinstalling via OSGeo4W, and also tried renaming the .qgis folder in my user folder, thinking it would reset any user settings back to default, but that also doesn't seem to help! What am I missing? -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/QGIS-Stuck-in-Full-Screen-Mode-tp5683925p5683925.html Sent from the qgis-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] tiff imported to GRASS loses minus sign in west coordinate
Dear lists, I need to import the map available here (http://geodata.grid.unep.ch/mod_download/download_geospatial.php?selectedID=2150&newFile=download/Nightlights_2003_tif.zip) to GRASS. The map is in Tiff format and appears fine in QGIS, but when I import it to GRASS (with r.in.gdal) it becomes a very narrow N-S stripe. Here's the raster info that QGIS gives me on this map: - - - Driver: GTiff/GeoTIFF Files: /media/disk/MARCIA/dadosExternos/variaveis/UNEP/nightLights/N_Light_2003.tif /media/disk/MARCIA/dadosExternos/variaveis/UNEP/nightLights/N_Light_2003.aux /media/disk/MARCIA/dadosExternos/variaveis/UNEP/nightLights/N_Light_2003.rrd Size is 43201, 15601 Coordinate System is: GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS 84",6378137,298.257223563, AUTHORITY["EPSG","7030"]], AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich",0], UNIT["degree",0.0174532925199433], AUTHORITY["EPSG","4326"]] Origin = (-180.0041989,65.00416667004) Pixel Size = (0.0083330,-0.0083330) Metadata: TIFFTAG_SOFTWARE=IMAGINE TIFF Support Copyright 1991 - 1999 by ERDAS, Inc. All Rights Reserved @(#)$RCSfile: etif.c $ $Revision: 1.10.1.9.1.9.2.11 $ $Date: 2004/09/15 18:42:01EDT $ TIFFTAG_XRESOLUTION=1 TIFFTAG_YRESOLUTION=1 TIFFTAG_RESOLUTIONUNIT=1 (unitless) AREA_OR_POINT=Area Image Structure Metadata: INTERLEAVE=BAND Corner Coordinates: Upper Left (-180.0041667, 65.0041667) (180d 0'15.00"W, 65d 0'15.00"N) Lower Left (-180.0041667, -65.0041661) (180d 0'15.00"W, 65d 0'15.00"S) Upper Right ( 180.0041652, 65.0041667) (180d 0'14.99"E, 65d 0'15.00"N) Lower Right ( 180.0041652, -65.0041661) (180d 0'14.99"E, 65d 0'15.00"S) Center ( -0.007, 0.003) ( 0d 0'0.00"W, 0d 0'0.00"N) Band 1 Block=64x64 Type=Byte, ColorInterp=Gray Min=0.000 Max=63.000 Minimum=0.000, Maximum=63.000, Mean=2.909, StdDev=3.132 Overviews: 10801x3901, 5401x1951, 2701x976, 1351x488, 676x244, 338x122, 169x61 Metadata: STATISTICS_MINIMUM=0 STATISTICS_MAXIMUM=63 [...] - - - And here's what r.info says about the same map after importing it to GRASS: - - - Raster: NLight2003 Rows: 15601 Columns: 43201 N-S resolution: 0.0083 E-W resolution: 1.92863e-07 North: 65.0042 South: -65.0042 East: 180.004 West: 179.996 Format: integer (0 byte) Minimum value: 0 Maximum value: 63 Data description: generated by r.in.gdal Comments: r.in.gdal -o input="/media/disk/MARCIA/TdadosExternos/variaveis/UNEP/nightLights/N_Light_2003.tif" output="NLight2003" - - - Most of this info looks fine, except the E-W resolution which should be 0.008333 (like the N-S one), and the west coordinate which should have a "minus" sign. I'm using QGIS 1.5 with the GRASS plugin, and tried both under Ubuntu and Windows. I tried also having someone save it as ASCII and importing with r.in.arc, but the result was always the same. Any ideas about what might be causing this? Anyone can manage to import this map to GRASS correctly? Thanks for any help, Márcia ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: AW: Re: Fwd: [Qgis-user] QGIS "Near"
Isn't a problem like this usually solved with a two-pass method. The first pass uses the spatial index to eliminate all of the features that could not possibly intersect/touch/etc. And then in the second pass, an actual (more expensive) spatial overlay operation is performed on those candidates to determine their true spatial relationships. David. On Thu, Oct 28, 2010 at 10:29 AM, Giuseppe Sucameli wrote: > Hi Stefan, > > On Thu, Oct 28, 2010 at 7:48 AM, Ziegler Stefan > wrote: >> >> thanks for looking into this. Do you think it's worth filling out a bug >> report since the nearestNeighbor method does not the keep the promise or is >> this the normal behaviour of a spatial index based method? > > I think we should fill a bug report because the nearestNeighbor doesn't work > as > expected. > I don't know if the QgsSpatialIndex can be improved to manage complex > geometries, > but AFAICS in the few inline comments within the code, in this moment it > manages only > Points, Lines and Regions (rectangles), so every polygonal geometry must be > converted to Regions. > > This issue could take a lot of time to be fixed, but we can use the ticket > to require > the documentation about the QgsSpatialIndex class. In this moment it's > missing. > > Cheers. > >> ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: AW: Re: Fwd: [Qgis-user] QGIS "Near"
Hi Stefan, On Thu, Oct 28, 2010 at 7:48 AM, Ziegler Stefan wrote: > thanks for looking into this. Do you think it's worth filling out a bug > report since the nearestNeighbor method does not the keep the promise or is > this the normal behaviour of a spatial index based method? > I think we should fill a bug report because the nearestNeighbor doesn't work as expected. I don't know if the QgsSpatialIndex can be improved to manage complex geometries, but AFAICS in the few inline comments within the code, in this moment it manages only Points, Lines and Regions (rectangles), so every polygonal geometry must be converted to Regions. This issue could take a lot of time to be fixed, but we can use the ticket to require the documentation about the QgsSpatialIndex class. In this moment it's missing. Cheers. > - Originalnachricht - > Von: "Giuseppe Sucameli" > Gesendet: Mit, 27.10.2010 17:30 > An: "Ziegler Stefan" > Cc: "Jim Hammack" ; qgis-user < > qgis-user@lists.osgeo.org> > Betreff: Re: AW: Re: Fwd: [Qgis-user] QGIS "Near" > > Hi Stefan, > your workaround works fine in my case! > > I looked at the QgsSpatialIndex code and I have bad news... It uses the > bounding box > of the geometries! > This means that your workaround can work in a lot of cases but not in all > cases, e.g. if > > > you have more than N geometries (10 considering your workaround), ones > inside > each other. > > Cheers. > > On Tue, Oct 26, 2010 at 6:47 PM, Ziegler Stefan > wrote: > > > > Hi Giuseppe > > > > I wrote a little workaround. Could you please update to 0.0.6 and check it > with your test case? Thanks. > > > > regards > > Stefan > > > > mit freundlichem Gruss > > Stefan Ziegler > > > > > > - Originalnachricht - > > Von: "Giuseppe Sucameli" > > Gesendet: Mon, 25.10.2010 14:09 > > An: "Ziegler Stefan" > > Cc: "Jim Hammack" ; qgis-user < > qgis-user@lists.osgeo.org> > > > > Betreff: Re: AW: Re: Fwd: [Qgis-user] QGIS "Near" > > > > Hi all, > > > > two days ago I wrote a similar plugin for a LD talk in Pisa. > > I was unaware of the QgsSpatialIndex class (seems there's no documentation > > about it in the online QGis API pages or maybe I missed it) so I wrote a > simple > > > > > > loop to find the closest feature. > > > > Now I tried also the Nearest plugin and they are different behavior! > > See the scheenshots [1] [2]. > > > > AFAICS, Nearest select a wrong polygon. > > I see the plugin's code and I think it could a QgsSpatialIndex bug, but it > could be > > > > > > also the normal behaviour (I didn't found its documentation on the API > pages > > so I don't know). > > > > I'm going to add my plugin (ClosestFeatureFinded) to the Faunalia repo so > you > > can try it and check the different behavior. > > > > > > > > I hope this can help to find the bug (if any). > > If you confirm it, I'll fill a bug report. > > > > Cheers. > > > > [1] http://img87.imageshack.us/img87/3232/nearest.jpg > > > > > > [2] http://img64.imageshack.us/img64/2066/closest.jpg > > > > On Fri, Oct 22, 2010 at 9:19 AM, Ziegler Stefan > wrote: > > > > > > there is some strange behaviour when using it with polygon features (at > least I think it's a bit strange): sometimes when you click into a polygon I > would expect that it selects the polygon I clicked into but it selects an > adjacent polygon. This is probably due to the nearestNeighbor method of the > spatial index. Since the two neighboring polygons share a common border the > distance would be equal but the spatial index does not check if the > coordindates of the mouse click lies within one of the two polygons. > > > > > > > > > > > > > > > regards > > > > Stefan > > > > > > > > mit freundlichem Gruss > > > > Stefan Ziegler > > > > > > > > > > > > - Originalnachricht - > > > > Von: "Jim Hammack" > > > > Gesendet: Don, 21.10.2010 19:20 > > > > An: "Ziegler Stefan" > > > > Cc: qgis-user > > > > Betreff: Re: AW: Re: Fwd: [Qgis-user] QGIS "Near" > > > > > > > > > > > >Stefan, > > > > > > > > > > > > > > > > I was looking for the same functionality as Zoran so have > > > >also been working with your "Nearest" plugin. It is exactly > > > >what I need and seems to work well. > > > > > > > > > > > > > > > >Thanks! > > > > > > > >Jim > > > > > > > > > > > > > > > >On 10/20/2010 01:54 PM, Ziegler Stefan wrote: > > > > > > > > > > > > Hi Zoran > > > > > > > > > > > > > > > > I had some time left, took all > > > >my code snippets and also the one from Carson. Please try > > > >the plugin "Nearest" that should cover your example 1: > > > > > > > > > > > > > > > > http://www.catais.org/qgis/plugins.xml > > > > > > > > > > > > > > > > regards > > > > > > > > Stefan > > > > > > > > > > > >-Ursprüngliche > > > >Nachricht- > > > > > > > >
Re: [Qgis-user] Re: Overview (inset map ) in map composer
Hi Lionel, Do you mean a zoom-rectangle in the selected map view? I usually set the map scale to some round value (I don't like map scales that are not rounded). This sets the zoom value for me. Then you can change the map extent by dragging the map content. Are you aware that you can also zoom with the mouse wheel in the map in the print composer? Given this functionality - do you still think that the zoom rectangle is necessary? Andreas On Thu, October 28, 2010 9:39 am, Lionel Roubeyrie wrote: > HI, > and a select zoom area button in the print composer would be a great > thing too, setting manually extents is not as simple as in the map > canvas. > cheers > > 2010/10/28 Alister Hood : >> Hi guys, >> There is a feature request for adding the map from the overview pane to >> the composer: >> https://trac.osgeo.org/qgis/ticket/2348 >> That person is after essentially the same result as you Marco, but they >> seem to have forgotten that the extent of the map view is almost always >> at least slightly different from the extent of the detail map in the >> print composer. So the map extent rectangle shown in the overview would >> be wrong. >> >> It might be more flexible anyway to have a plugin add a rectangle to a >> normal map canvas on the print composer, showing the extents of another >> map canvas. I think this would be a popular feature - does anyone know >> how feasible it would be? >> >> I imagine the other problem mentioned in that ticket (the difficulty >> around preserving/changing the layers shown on a map canvas in the >> composer) is something that should be addressed separately. >> >> Regards, >> Alister >> >>> Date: Wed, 27 Oct 2010 15:42:10 + (UTC) >>> From: Marco Tuckner >>> Subject: [Qgis-user] Re: Overview (inset map ) in map composer >>> To: qgis-user@lists.osgeo.org >>> Message-ID: >>> Content-Type: text/plain; charset=us-ascii >>> >>> > You can simply add another map to the canvas, and then set the >>> extents and >>> scale to only cover your area of interest. >>> Yes. >>> But how do I make them dynamically zoom and also display an extend >>> rectangle on >>> the overview map showing th extend of the detailed map? >>> >>> Thanks for following up. >>> >>> Regards, >>> Marco >> ___ >> Qgis-user mailing list >> Qgis-user@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-user >> > > > > -- > Lionel Roubeyrie > lionel.roubey...@gmail.com > http://youarealegend.blogspot.com > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-user > -- Andreas Neumann http://www.carto.net/neumann/ http://www.svgopen.org/ ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: Overview (inset map ) in map composer
HI, and a select zoom area button in the print composer would be a great thing too, setting manually extents is not as simple as in the map canvas. cheers 2010/10/28 Alister Hood : > Hi guys, > There is a feature request for adding the map from the overview pane to > the composer: > https://trac.osgeo.org/qgis/ticket/2348 > That person is after essentially the same result as you Marco, but they > seem to have forgotten that the extent of the map view is almost always > at least slightly different from the extent of the detail map in the > print composer. So the map extent rectangle shown in the overview would > be wrong. > > It might be more flexible anyway to have a plugin add a rectangle to a > normal map canvas on the print composer, showing the extents of another > map canvas. I think this would be a popular feature - does anyone know > how feasible it would be? > > I imagine the other problem mentioned in that ticket (the difficulty > around preserving/changing the layers shown on a map canvas in the > composer) is something that should be addressed separately. > > Regards, > Alister > >> Date: Wed, 27 Oct 2010 15:42:10 + (UTC) >> From: Marco Tuckner >> Subject: [Qgis-user] Re: Overview (inset map ) in map composer >> To: qgis-user@lists.osgeo.org >> Message-ID: >> Content-Type: text/plain; charset=us-ascii >> >> > You can simply add another map to the canvas, and then set the >> extents and >> scale to only cover your area of interest. >> Yes. >> But how do I make them dynamically zoom and also display an extend >> rectangle on >> the overview map showing th extend of the detailed map? >> >> Thanks for following up. >> >> Regards, >> Marco > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-user > -- Lionel Roubeyrie lionel.roubey...@gmail.com http://youarealegend.blogspot.com ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
