Re: [Qgis-user] Batch "ECW creating"
sorry, I did not carefully read .. obviously the wrong answer. But as far as I
understand you need a valid ERDAS license for compression.
Cheers.
Stefan
> st_kie...@web.de hat am 16. April 2019 um 12:46 geschrieben:
>
>
> you might want to have a look for
>
> https://gdal.org/frmt_gtiff.html
>
> search for "COMPRESS=" and decide which compression mode to use, and
> further parameter if posiible to control the compression level like for
> example "JPEG_QUALITY=", to extend the -co parameter.
>
> Cheers.
>
> Stefan
>
> > > Piotr Kania hat am 16. April 2019 um 12:32
> geschrieben:
> >
> > Hello!
> > I am sorry for asking about sth not connected with qgis...
> > I would like to use old FWTools 2.4.7 to convert geotiff's files to
> > ecw format. Right now I use that "command": for %i in ("d:\\*.tif") do
> > gdal_translate -of ECW -co LARGE_OK=YES "%i" "d:\.\%~ni.ecw
> >
> > Can I add sth to that "command" to achieve better "compression
> > ratio"? Thanks for any response.
> >
> > Greetings - Piotrek
> > ___
> > Qgis-user mailing list
> > Qgis-user@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >
> > >
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Batch "ECW creating"
you might want to have a look for
https://gdal.org/frmt_gtiff.html
search for "COMPRESS=" and decide which compression mode to use, and further
parameter if posiible to control the compression level like for example
"JPEG_QUALITY=", to extend the -co parameter.
Cheers.
Stefan
> Piotr Kania hat am 16. April 2019 um 12:32 geschrieben:
>
> Hello!
> I am sorry for asking about sth not connected with qgis...
> I would like to use old FWTools 2.4.7 to convert geotiff's files to ecw
> format. Right now I use that "command": for %i in ("d:\\*.tif") do
> gdal_translate -of ECW -co LARGE_OK=YES "%i" "d:\.\%~ni.ecw
>
> Can I add sth to that "command" to achieve better "compression ratio"?
> Thanks for any response.
>
> Greetings - Piotrek
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] uploading a png basemap
Hi, I don't know whether I get exakt what you mean. You might be looking for a world file (file extension .pgw in conjunction with .png). You can create it by yourself, if you know some things about the png, see https://en.wikipedia.org/wiki/World_file cheers Stefan > Mary Neale hat am 27. März 2019 um 13:14 geschrieben: > > > Hi > > I'm using the lastest version of QGIS and I've been trying to upload a > .png version of a basemap, which uploads but is not visible. When > uploading the coordinate reference system selector box pops up and I > choose OSGB 1936 / British National Grid. > > I've asked the map provider for a .vml version (which when combined with > the .png worked a treat in past versions of QGIS) but they haven't sent > it and haven't replied. > > Can someone advise whether I should be able to see the .png version and > that I'm doing something wrong or whether a .vml version of a basemap is > essential? > > I look forward to hearing from you. > > Best wishes > > Mary > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Numbering Fields by custom squence
Hi,
first idea could be something like this:
concat('OBST',lpad(to_string($id), 4, '0'))
if you don't need concrete values. You might also add an offset to $id.
concat('OBS',lpad(to_string($id + ), 4, '0'))
Hope that helps.
Regards.
Stefan
> Krišjānis Sietiņš hat am 19. März 2019 um 12:44
> geschrieben:
>
>
> Hello!
>
> I am writing fires time here.
>
> QGIS version 2.18.20
>
> We need to make user defined continuous ID numbering in attribute table
> for fields. ID should contain some letters that define objects type. For
> example starting from OBST0200 to OBST0315. And objects are too much to do it
> manually.
>
> I found Sort and Number plugin, but it has only number option.
>
> Can it be done in Field calculator and what expression should we use?
>
>
>
> With Best Regrads
>
> Krišjānis Sietiņš
>
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] nodata and raster calc
In fact I would always expect nodata. nodata is what it says: no data. How can one calculate or generate new values with one unknown term. Especially in the case of boolean. Lets take an example from real life. You have the information of wet or not wet area. In the case of wet you have to reduce irrigation if not wet you must increase irrigation. In either cases you make a mistake, if you do the opposite. Without knowledge of the inputdata (and respecting the scale), someone getting the result could do a big mistake. Particularly if the action is highly cost intensive. Nodata need special treatment. One must be aware of the lack of data, and a model has rather to fail than false simulate the existing data. What if you process hundreds of raster sets and get always valid results. If some don't like nodata, he has to actively process the data in one way, either simulate valid data (and of course knows that he has to communicate that fact) or collect more precise data. Anything else is scientifically bad behaviour (to use a buzzword: fake data). Cheers. Stefan > Havard Tveite hat am 11. Februar 2019 um 10:20 > geschrieben: > > > nodata + 1 = nodata > nodata * 1 = nodata > nodata AND 1 = nodata > nodata OR 1 = 1 > > nodata + 0 = nodata > nodata * 0 = nodata > nodata AND 0 = 0 > nodata OR 0 = nodata > > Håvard > > On 11. feb. 2019 09:47, st_kie...@web.de wrote: > > I absolutely agree. > > > > For the Discussion. nodata is a valuable information, and is getting lost > > when dealing as desired value. Although the OR part needs more Discussion. > > For consistency that has to be nodata as well. What about nodata OR 0? In > > my opinion nodata always needs a discrete treatment to avoid generating > > fallcious information. > > > > Cheers > > > > Stefan > > > >> Havard Tveite hat am 11. Februar 2019 um 09:38 > >> geschrieben: > >> > >> > >> nodata + 1 = nodata > >> nodata * 1 = nodata > >> nodata AND 1 = nodata > >> nodata OR 1 = 1 > >> > >> Håvard > >> > >> On 11. feb. 2019 03:11, Nyall Dawson wrote: > >>> Hey all, > >>> > >>> I'm seeking some feedback on whether our current handling of nodata > >>> pixels in the raster calculator is correct, or (my suspicion) annoying > >>> and limiting. > >>> > >>> Currently, we treat nodata pixels the same as a "NULL" value in SQL -- > >>> so ANY function or operation with nodata as an input results in a > >>> nodata output. > >>> > >>> This means: > >>> > >>> - nodata + 1 = nodata > >>> - nodata * 1 = nodata > >>> - nodata AND 1 = nodata > >>> - nodata OR 1 = nodata > >>> > >>> To me this is a mistake. I don't think we should treat nodata the same > >>> as NULL, and I think for rasters then "nodata OR 1" should return 1. > >>> > >>> The end result of the current behaviour is that ANY nodata input > >>> blocks processing of that pixel. So you can't do something like take > >>> two raster files, and create an output showing where either input has > >>> a 1 value (which I would expect raster1@1 OR raster2@1 to do). > >>> > >>> Otherwise, we need to have some concept of "coalesce" in the raster > >>> calc. So then at least you could do: > >>> > >>> coalesce(raster1@1, 0) OR coalesce(raster@1, 0) > >>> > >>> > >>> Thoughts? > >>> > >>> Nyall > >>> ___ > >>> Qgis-user mailing list > >>> Qgis-user@lists.osgeo.org > >>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > >>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > >>> > >> ___ > >> Qgis-user mailing list > >> Qgis-user@lists.osgeo.org > >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > > ___ > > Qgis-user mailing list > > Qgis-user@lists.osgeo.org > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] nodata and raster calc
I absolutely agree. For the Discussion. nodata is a valuable information, and is getting lost when dealing as desired value. Although the OR part needs more Discussion. For consistency that has to be nodata as well. What about nodata OR 0? In my opinion nodata always needs a discrete treatment to avoid generating fallcious information. Cheers Stefan > Havard Tveite hat am 11. Februar 2019 um 09:38 > geschrieben: > > > nodata + 1 = nodata > nodata * 1 = nodata > nodata AND 1 = nodata > nodata OR 1 = 1 > > Håvard > > On 11. feb. 2019 03:11, Nyall Dawson wrote: > > Hey all, > > > > I'm seeking some feedback on whether our current handling of nodata > > pixels in the raster calculator is correct, or (my suspicion) annoying > > and limiting. > > > > Currently, we treat nodata pixels the same as a "NULL" value in SQL -- > > so ANY function or operation with nodata as an input results in a > > nodata output. > > > > This means: > > > > - nodata + 1 = nodata > > - nodata * 1 = nodata > > - nodata AND 1 = nodata > > - nodata OR 1 = nodata > > > > To me this is a mistake. I don't think we should treat nodata the same > > as NULL, and I think for rasters then "nodata OR 1" should return 1. > > > > The end result of the current behaviour is that ANY nodata input > > blocks processing of that pixel. So you can't do something like take > > two raster files, and create an output showing where either input has > > a 1 value (which I would expect raster1@1 OR raster2@1 to do). > > > > Otherwise, we need to have some concept of "coalesce" in the raster > > calc. So then at least you could do: > > > > coalesce(raster1@1, 0) OR coalesce(raster@1, 0) > > > > > > Thoughts? > > > > Nyall > > ___ > > Qgis-user mailing list > > Qgis-user@lists.osgeo.org > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] prevrnt overlapping
Hi Boaz, this is kind of tricky, particularly, if the points in every single layer are not absolutly congruent. a) if points are congruent (or if the offset of the points are euqal and in same direction in each layer), you might set an offset in the symbol-settings. You can set an offset for the simple marker. But if points are not congruent or randomly dispersed, this might lead to no nice results. b) you combine all layers (you might distinguish them by an additional attribute if necessary) and use "Point displacement" in the symbols-settings. c) you transform layers to shift points to distinct locations. Hope that helps. regards. Stefan > Boaz Bar Ilan hat am 16. Januar 2019 um 08:16 > geschrieben: > > > hi > > im using 7 different layers with symbols on each and I want to prevent > overlapping of the symbols > what is the way ? > thanks > boaz > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
