Am So, 5.03.2017, 04:03 schrieb Nyall Dawson:
>
> A change I just pushed to master also prevents this full table load if
> you use the "show selected features" mode. So that helps a bit.
Thanks, so this will appear in v3.0?
I'm using OSGeo4W, let me try the nightly builds.
Thanks
I think its because overwheigt. The file itself is few gigas. The big
problem is to create a legend to one or two layers . It brings forward all
the layers detailed and its impossible to handle.
Thanks
Boaz
בתאריך 5 במרץ 2017 05:12, "Nyall Dawson" כתב:
> On 4
[I just noticed the typos in my Subject line. I hope that has not
violated any list etiquette.]
Brent,
The OSM project sounds interesting, and as you say, there is more
interest in high density areas. If I did not have the number of
projects on the go that I have, I might take a look at
No problems Stephen,
Unfortunately many government agencies can't keep up with edits of new
tracks/trails but that is the beauty of Open Street Map. Your contribution, by
adding tracks, means that all the folks making derivative products get the
benefits. You also get the benefit of their
On 4 March 2017 at 15:16, Boaz Bar Ilan wrote:
> hallo
>
> you are right
>
> well, I am trying to export qgis produce into ppt . I want to save the image
> with a legend. I'm trying to activate composer manager in order to produce
> map and legend and to export it as image
Stephan,
I'd recommend having another, closer look at the OSM project. It was
created by by people just like you wanting a better base map. People
all over world contribute either by digitizing features using Bing
imagery on the OSM website, or by uploading their own GPS tracks.
Various
On 4 March 2017 at 18:41, Alessandro Pasotti wrote:
> On Sat, Mar 4, 2017 at 9:25 AM, Nathan Woodrow wrote:
>>
>> Hmm are you sure we don't do this already?
>>
>> I suspect we do. Each provider can handle the sorting, giving to it by
>> QgsFeatureRequest,
On 4 March 2017 at 18:03, Tobias Wendorff
wrote:
> Am Sa, 4.03.2017, 08:34 schrieb Alessandro Pasotti:
>>
>> Yes, that would be a strategy, but you might run into problem with
>> sorting and filtering if the data provider does not support for it.
>
> All
Phil,
Someone suggested the same OSM approach in an off list email. Here was
my response:
I have just taken a look at OSM, and the maps there, for my area of
interest, are taken from the ancient (pre 1992) British
Columbia/Canada maps that are very incomplete and riddled with
errors. It is
Depending on the size of the area involved and how 'custom' your maps are
likely to be you may be better off looking at solutions from OSM. There are
many sites that create files suitable for Garmin GPS
http://garmin.openstreetmap.nl/
If the areas are small you could also create KMZ (Google
I am running QGIS 2.18.3 and am at a very early learning stage. I wish
to create simple maps, with 2 or 3 shape files for my Garmin GPSMaps
76CSx. This map would consist of Trails and Streams shp files and maybe
Contours. It would also be accepted by Mapsource and Base Camp.
There were
Ahaha ero fuso, almeno 4 o 5 :-D
Grazie comunque! Credo di aver capito! Domani applico e credo di aver
risolto!
Andrea G.
Il giorno 4 marzo 2017 22:51, AV [via OSGeo.org] <
ml-node+s1560n5310689...@n6.nabble.com> ha scritto:
> * andrea gagna wrote costituito da tanti triangoli che hanno sempre e
/
andrea gagna wrote
> costituito da tanti triangoli che hanno sempre e solo tre vertici
/
Perche', quanti vertici dovrebbe avere un triangolo, altrimenti ?!?
:D
--
View this message in context:
On 03/04/2017 09:42 PM, Even Rouault wrote:
On samedi 4 mars 2017 18:55:03 CET Micha Silver wrote:
> Hello:
> (I'm double posting as this problem is somewhere between GDAL and QGIS.)
>
> I have converted an ECW compressed aerial photo to geotiff with JPEG
> compression on a Windows
On 3/4/17, andrea gagna wrote:
> Ciao, ti ringrazio.
ciao (quando diventa accanimento terapeutico dimmelo),
> Il problema e' proprio sviluppare la routine in python per applicarlo
> massivamente.
> La formula per calcolarne 1 e' chiaramente quella.
beh, la lettura dello
Ciao, ti ringrazio.
Il problema e' proprio sviluppare la routine in python per applicarlo
massivamente.
La formula per calcolarne 1 e' chiaramente quella.
Andrea.
Il sabato 4 marzo 2017, giulianc [via OSGeo.org] <
ml-node+s1560n5310680...@n6.nabble.com> ha scritto:
> On 3/4/17, andrea gagna
On 3/4/17, andrea gagna wrote:
> Ciao a tutti;
ciao,
> ...
> Non trovo una funzione o routine per calcolare massivamente tutti gli angoli
> di ogni triangolo.
> Chiaramente conosco quale dei 3 angoli di ogni triangolo mi serve calcolare
> ed e' sempre lo stesso in
On samedi 4 mars 2017 18:55:03 CET Micha Silver wrote:
> Hello:
> (I'm double posting as this problem is somewhere between GDAL and QGIS.)
>
> I have converted an ECW compressed aerial photo to geotiff with JPEG
> compression on a Windows computer with gdal_translate. The resulting tif
> image
Am Sa, 4.03.2017, 18:29 schrieb Richard Duivenvoorde:
> I still think it is a misconfigured WMS server.
>
> Which server are you using?
The one I've posted in the bug report. I'm using QGIS as a client.
> Which data are you using?
Check the BBOX I've posted in the bug report.
[snip]
> The
On 04-03-17 08:32, Tobias Wendorff wrote:
> Am Sa, 4.03.2017, 08:29 schrieb Richard Duivenvoorde:
>>
>> Ah, see bugreport...
>>
>> I think it is a misconfigured wms:
>>
>> [snipped out the very long URL]
>>
>> gives an image but only at that zoomlevel...
>>
>> zooming out you do not see anything
>
Hello:
(I'm double posting as this problem is somewhere between GDAL and
QGIS.)
I have converted an ECW compressed aerial photo to geotiff with JPEG
compression on a Windows computer with gdal_translate. The resulting
tif image displays fine with QGIS on the
Am Sa, 4.03.2017, 12:19 schrieb johnrobot:
>
> - Most tools seem to lack description in the help tab. Are there any
> guidelines on what must be included in this tab? Is it up the the
> supplier of the tool or can others help to create and improve the
> documentation as well?
I agree. That's
Hi
I have been testing building models in processing and I have found a few
areas where we could improve the help and documentation:
- In the list of tools, most of the tools only show their name, while some
(GRASS) also show a description of the tool in the list. I would prefer if
only the names
On 04/03/2017 10:58, Tobias Wendorff wrote:
> Am Sa, 4.03.2017, 10:38 schrieb Nathan Woodrow:
>>> If you go to settings -> options -> data sources you can change
>> "attribute table behaviour" to "show features visible on map"
>>
>> That means it will only request what you see in the map.
> Yeah,
Am Sa, 4.03.2017, 10:38 schrieb Nathan Woodrow:
>
>> If you go to settings -> options -> data sources you can change
> "attribute table behaviour" to "show features visible on map"
>
> That means it will only request what you see in the map.
Yeah, that's totally fine right now. Thanks for help :)
Hey Tobias,
What Nyall posted is the only work around here.
> If you go to settings -> options -> data sources you can change
"attribute table behaviour" to "show features visible on map"
That means it will only request what you see in the map.
- Nathan
On Sat, Mar 4, 2017 at 6:56 PM, Tobias
Am Sa, 4.03.2017, 09:43 schrieb Raymond Nijssen:
> You seem to know about databases. For me, when my data passes around 1
> million records, I turn to work directly in the database
> (using pgadmin) and only use qgis for visualising the results.
That's okay for database-guys like us. But viewing
Hi Tobias,
You seem to know about databases. For me, when my data passes around 1
million records, I turn to work directly in the database (using pgadmin)
and only use qgis for visualising the results.
Regards,
Raymond
On 04-03-17 09:28, Tobias Wendorff wrote:
Am Sa, 4.03.2017, 09:25
On Sat, Mar 4, 2017 at 9:25 AM, Nathan Woodrow wrote:
> Hmm are you sure we don't do this already?
>
> I suspect we do. Each provider can handle the sorting, giving to it by
> QgsFeatureRequest, and hand the results back to the caller. I thought the
> attribute table was
Hi there.
I'm new to this mailing list, so let me give some knowledge from my
work in QGIS (I don't want to take only, hehe). Maybe it helps someone
or leads to a nice discussion, how to make it even better.
Often, it's more useful to store geodata in small SQLite. Sure, it
doesn't have all the
Am Sa, 4.03.2017, 09:25 schrieb Nathan Woodrow:
> Hmm are you sure we don't do this already?
Because the counter of attribute table increased to some hundret
thousand entries and my QGIS v2.18.3 got grayed out in the back,
leading to a crash some seconds after :(
With an unsaved project of
Hmm are you sure we don't do this already?
I suspect we do. Each provider can handle the sorting, giving to it by
QgsFeatureRequest, and hand the results back to the caller. I thought the
attribute table was already implemented this way.
Regards,
Nathan
On Sat, Mar 4, 2017 at 6:03 PM, Tobias
Am Sa, 4.03.2017, 08:34 schrieb Alessandro Pasotti:
>
> Yes, that would be a strategy, but you might run into problem with
> sorting and filtering if the data provider does not support for it.
All database-like formats, even Shapefile's DBF, support sorting
on database level. I've never
33 matches
Mail list logo