[Qgis-user] Calculate intersecting area of two layers in a virtual field. Context of @geometry in overlay_intersects()
Hello List, Hello Bruno and Klaus - (Long time lurker, first time poster) Easy way to get the area of intersecting polygons is to do the "union" from the vector drop down menu. Make sure there is something in the attribute table that helps you know which layer is which. Then you get a layer which includes a) the polygons in both, b) the polygons in one but not the other and c) the polygons in the other but not in the first! Then just run stats to get the area you need. Abi Save Time Do It Online! We have made a few key improvements to our site to make our services easy to access. Now you can do everything from paying your council tax, to reporting a faulty street light online. Go to: www.northumberland.gov.uk and click 'pay, apply or report' to access the relevant forms. This email is intended solely for the individual or individuals to whom it is addressed, and may contain confidential and/or privileged material. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this email is prohibited. If you receive this email in error, please contact the sender and delete the email from any computer. All email communication may be subject to recording and/or monitoring in accordance with internal policy and relevant legislation. [Northumberland County Council Stay Home] ___ 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] [QGIS-Developer] Announce - migrate our mailing lists to Discourse
> I didn't see it coming honestly. Make it hard for them so only the > best ones can join us? Not quite - make asking questions take more effort than doing your own research, so lazy people are encouraged to find their own answers before asking. It's not about excluding people, it's about minimising the types of questions that could be solved by looking at the documentation or by doing a web search. > > In my own experience, if it's too easy for people to ask questions, > > then they tend to do so before doing their own research. > > Don't you think it is already the case. Moderators everywhere are > doing this job to remind people to just do their homework before > asking. Yes and this is my argument exactly. Those places make it too easy for lazy people to ask questions, and so you end up with moderators spending large amounts of time reminding people of basic things. In my opinion, instead of bringing in more moderators, it is better to reduce the amount of these low-effort questions. > Would you want to make life harder for those who still want to learn, > but just don't get the mailing list stuff? It is very easy to subscribe to a mailing list. If you can't figure that out, I think you will have no hope understanding QGIS. But it is not about making it hard or complicated, it is making it so that people are encouraged to do at least a little work on their own before asking questions. > From my experience, stupid questions are either not answered, or very > gently refocused on the good way of asking questions, which is also > something I like in our communities. That is true, but it seems this list does not get very many questions like that. If we start to get a lot of them, the community's attitude could change. > > This is why generally speaking, it's often better to add some > > hurdles in before people can ask questions, such as figuring out > > how to subscribe to an e-mail list. > > This is a radical point of view. Another option is to make them pass > through helpers that reminds them to search before asking. Something > positive, like when you create an issue in gitlab and the UI gently > propose you existing similar questions when you start typing. That is fine too, as long as people cannot ignore it and just keep typing their simple question. Look at the Microsoft support forums for example. They are next to useless, because it is so easy to post questions. There are hundreds of questions asking the same thing, and almost as many "answers" by people who have no idea what they are talking about, but are trying to be helpful by suggesting something that worked for them once when they had a completely different problem. So although their forums are easily searchable, it is incredibly rare to get a usable answer from them because the posts are of such low quality and often outright wrong. Contrast that to StackExchange. Yes, the Q&A format is limited, however by removing low-effort posts and incorrect answers, their content is consistently high quality and extremely useful. Many times I have done a web search and found my answer on a StackExchange site. Perhaps these are two extremes and the best solution is somewhere in the middle, but hopefully it at least explains the reasons behind my arguments. > > If you still think Discourse is the way to go, I would suggest > > running it in parallel with the e-mail list for a few months, and > > compare how many questions get answered there vs here. > > We can't mirror with both sides being written. If we go this way, we > would all have to follow both channels. I think it would be a mistake to switch entirely in one go. I am not saying we run both permanently, just temporarily, to give it a trial run and see how it goes. This will give the list users time to try out Discourse and see how it goes. Many of the list people will likely set up Discourse to work like a mailing list anyway, so they won't have to follow both channels - everything will come into the same inbox. If Discourse works, then as more and more questions are asked there, fewer questions will be asked on the lists, and perhaps at some point they can be turned off and nobody will even notice. I am reminded of the recent Reddit debacle, where management forced their changes onto their community of volunteers, and as a result, a large majority of them left the community entirely. It does seem like there is a similar push here, to move everyone to Discourse whether we like it or not. And that is fine, I am not paying for the servers, but if having a helpful community is of value to the project, it is probably best to take things slowly and give people a chance to adjust, rather than to dictate what is happening. > Older ones will stay in mailing lists, Users will try Discourse, > community is split in half. Remember the community being split in half, is exactly the same as half the community leaving because they do not like the change. > I remin
Re: [Qgis-user] QGIS-User Digest, Vol 218, Issue 9
I've had good luck with hiding the original folder/directory containing the files I'm moving (or just moving it wholesale) starting up the QGIS project when it shows the list of files it cannot find I select one and use Browse to find that file in its new location followed by Apply Changes This generally results in it finding all the other missing files that share the same directory... I'm assuming that Browse updates a "Path" that is then automatically used to check for other missing files. Also, it **may** depend on QGIS being set to use Options - General > Project Files > Default paths: Relative rather than Absolute. I always use Relative and have not checked the effect of Absolute. Of course, the file names have to be UNchanged, but it seems to work very well when I relocate whole directories. On 4/4/24 Tony Shepherd \(FarmMaps NZ\)" wrote: I am sure I am not the first to ponder how to deal with this. I have loads, thousands likely, of project files in a series of folders and subfolders. I need to move those files and folders to a new location to enable other staff to use the project files and their associated shp files, geo packages, rasters etc. ... -- Garth Fletcher ___ 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] Moving many project files - bulk updating paths to tables?
On Wed, 10 Apr 2024 17:38:58 +0200, Antonio Viscomi via QGIS-User wrote: > That's no matter for 'sed' command if the extension is .qgz or qgs The extension itself surely not, but the contens matters. The '.qgs' file is a plain text XML file, that sed(1) has no problem to work on. The '.qgz' file is a ZIP archive that may contain even more than a single text file. The '.qgs' file being one of them. The sed(1) command doesn't know how to deal with this kind of archive: $ unzip -l Training_Empty.qgz Archive: Training_Empty.qgz Length DateTimeName - -- - 10858 2020-05-28 19:57 Training_Empty.qgs 0 2020-05-28 19:57 Training_Empty.qgd - --- 10858 2 files HTH > > Saluti > > Antonio Roxo -- Non luctari, ludare ---+ WYSIWYG Fernando M. Roxo da Motta | Editor? Except where explicitly stated I speak on my own behalf.| VI !! PU5RXO | PX5Q6048 | I see text, Quis custodiet ipsos custodes?-+ I get text! ___ 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] [QGIS-Developer] Announce - migrate our mailing lists to Discourse
On 4/10/2024 9:00 AM, Régis Haubourg via QGIS-User wrote: I also heard yesterday another argument, given that we have StackExchange, mailing list and forums would be of no use. Except you don't discuss on StackExchange, you only ask questions. And we don't own the content (side remark) there. Stack Exchange is not a good substitute. A number of the most active users are quick to close any post with more than one question, often making it hard to coherently post about your issue. ___ 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] Moving many project files - bulk updating paths to tables?
That's no matter for 'sed' command if the extension is .qgz or qgs Saluti Antonio Il giorno ven 5 apr 2024 alle ore 16:00 David Strip < qgis-u...@stripfamily.net> ha scritto: > On 4/5/2024 2:15 AM, Antonio Viscomi via QGIS-User wrote: > > if you're using linux what you need is simply use the 'sed' command by > terminal as i.e.: > > *sudo sed -i 's/NEWPATHTOSUBSTITUTE(your path or IP or domain)/OLDPATH/g' > *.qgs* > > > The original request noted that the files were .qgz files, not .qgs, so > you need to first unzip, the rezip the files. > And this single line solution assumes all files are in a single directory, > so you need something "find" to walk the directory structure. > ___ 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] [QGIS-Developer] Announce - migrate our mailing lists to Discourse
Hey Adam, On 10/04/2024 16:19, Adam Nielsen wrote: At PSC, we discussed this topic and decide to phase the migration plan, by starting QGIS PSC and QGIS users first. Those are the first places we want users to jump in easily. What's the reason you want users to be able to jump in easily? I didn't see it coming honestly. Make it hard for them so only the best ones can join us? In my own experience, if it's too easy for people to ask questions, then they tend to do so before doing their own research. This runs the risk that they will ask a question before bothering to do even a simple web search, resulting in many low-effort questions that the askers could easily have solved themselves. Don't you think it is already the case. Moderators everywhere are doing this job to remind people to just do their homework before asking. I also heard yesterday another argument, given that we have StackExchange, mailing list and forums would be of no use. Except you don't discuss on StackExchange, you only ask questions. And we don't own the content (side remark) there. Don't you also think that AI stuff will catch all those questions asked too quickly ? The end result is that humans end up functioning like AI LLMs - they simply repeat parts of the documentation that people could not be bothered to search for themselves. Would you want to make life harder for those who still want to learn, but just don't get the mailing list stuff? Now if you like repeating similar answers to simple questions then that's fine, but most people tend to get bored with that and lose interest fairly quickly, or become rude with their replies as they are tired of repeating the same basic information over and over again, and this then tarnishes the community as "hostile" or "toxic" to new users. From my experience, stupid questions are either not answered, or very gently refocused on the good way of asking questions, which is also something I like in our communities. This is why generally speaking, it's often better to add some hurdles in before people can ask questions, such as figuring out how to subscribe to an e-mail list. It means people will do some web searches first as they are the easier option, and only ask the community for help if they really are stuck and really do need help. This cuts down on a lot of low-effort questions and demands less time from community volunteers responding. This is a radical point of view. Another option is to make them pass through helpers that reminds them to search before asking. Something positive, like when you create an issue in gitlab and the UI gently propose you existing similar questions when you start typing. If you still think Discourse is the way to go, I would suggest running it in parallel with the e-mail list for a few months, and compare how many questions get answered there vs here. We can't mirror with both sides being written. If we go this way, we would all have to follow both channels. Older ones will stay in mailing lists, Users will try Discourse, community is split in half. I remind you that the issue is that we do not have any plan at osgeo to provide a mailman 3 solution. And new users just don't use mailing lists. This is a fact. Myself in my new job being forced to use outlook f**ing client, I can't realistically follow our lists anymore. This is also a fact. We try to answer to this reality. Clearly if Discourse doesn't make it for PSC and user lists, after correct communication and after the transition period, we'll discuss it again. Cheers Régis ___ 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] [QGIS-Developer] Announce - migrate our mailing lists to Discourse
> At PSC, we discussed this topic and decide to phase the migration plan, > by starting QGIS PSC and QGIS users first. Those are the first places > we want users to jump in easily. What's the reason you want users to be able to jump in easily? In my own experience, if it's too easy for people to ask questions, then they tend to do so before doing their own research. This runs the risk that they will ask a question before bothering to do even a simple web search, resulting in many low-effort questions that the askers could easily have solved themselves. The end result is that humans end up functioning like AI LLMs - they simply repeat parts of the documentation that people could not be bothered to search for themselves. Now if you like repeating similar answers to simple questions then that's fine, but most people tend to get bored with that and lose interest fairly quickly, or become rude with their replies as they are tired of repeating the same basic information over and over again, and this then tarnishes the community as "hostile" or "toxic" to new users. This is why generally speaking, it's often better to add some hurdles in before people can ask questions, such as figuring out how to subscribe to an e-mail list. It means people will do some web searches first as they are the easier option, and only ask the community for help if they really are stuck and really do need help. This cuts down on a lot of low-effort questions and demands less time from community volunteers responding. Now if you are a paid company accepting money for support agreements then this does not matter, but if you are relying on the goodwill of volunteers to answer the incoming questions, then it is most important to cater to the needs of those volunteers. If they all become unhappy and leave, then it does not matter how easy it is to ask a question if there is nobody around to answer it. If you still think Discourse is the way to go, I would suggest running it in parallel with the e-mail list for a few months, and compare how many questions get answered there vs here. If Discourse questions are getting answered then it means it is a viable replacement for the lists and the list can be closed, but if the questions are going unanswered then it may be Discourse that should be discontinued and the e-mail lists retained. Either way you will have some real-world statistics to back up the decision one way or another. Cheers, Adam. ___ 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] [QGIS-Developer] Announce - migrate our mailing lists to Discourse
Hi all, I've read you reactions carefully. All your points are very valid concerning Discourse as a bad mailing list alternative. At PSC, we discussed this topic and decide to phase the migration plan, by starting QGIS PSC and QGIS users first. Those are the first places we want users to jump in easily. Developer's list will be discussed once we get experience on this front only. Maybe some issues will be fixed in the meantime, or maybe we will find a better solution in Discourse itself. I keep on looking around at other projects. The mailing list "fake" option makes everyone unhappy, maybe because it is not really the right way to use Discourse. I found that Fedora project decided to organize its Discourse instance using tags, and subscription to tags : https://discussion.fedoraproject.org/t/navigating-fedora-discussion-tags-categories-and-concepts/3 We are still in testing phase, please feel free to join discussions at https://discourse.osgeo.org/c/discourse-issues-and-requests/19 ! Regards Régis 05/04/2024 10:35, Sandro Santilli via QGIS-User wrote: On Thu, Apr 04, 2024 at 05:58:32PM +0200, Marco Bernasocchi via QGIS-Developer wrote: Seems fixed :) https://trac.osgeo.org/osgeo/ticket/3073#comment:19 That's actually more of a workaround than a fix. Discourse still ruins the body of email text/plain email messages. Even those sent for administrative purpose (links are turned into html anchor tags) --strk; ___ 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] Python console sys.stdout.encoding
> Effectively it is part of the answer I am looking for. But my problem is > "higher" in the python settings for QGIS. If I write 'sys.stdout.encoding = > "utf-8"' to the console, my plugin will be loaded without problem. I am > developing a plugin whit "from ultralytics import YOLO" and I am receiving > the following message : > >File > "C:\Users\pierr\AppData\Roaming\Python\Python39\site-packages\ultralytics\ut > ils\__init__.py", line 238, in set_logging > if WINDOWS and sys.stdout.encoding != "utf-8": > AttributeError: 'NoneType' object has no attribute 'encoding' > > Ultralytics YOLO needs an encoding attribute for "sys.stdout" to be > imported. I didn't find any solution to set the encoding attribute with the > startup.py file. I'm no Python expert, but can you change that code so that it does not rely on that property? e.g. if WINDOWS and hasattr(sys.stdout, 'encoding') and sys.stdout.encoding != "utf-8": If that works maybe you can submit an upstream patch to the ultralytics package? Otherwise your only option would be to add the 'encoding' property to the QGIS stdout redirection module as Andrea posted about earlier. Cheers, Adam. ___ 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] geojson
Hi Manuel,
Can you give some more info about your data and how you are trying to use it?
If you can share a link to a copy or sample of the data, even better.
>From your sample it looks like you're maybe trying to make a webmap - where
>does QGIS fit in? Are you using the qgis2web plugin?
The more info you can share about your data and workflow the more likely it is
someone will be able to help.
Regards,
Alexei
On Wed, 10 Apr 2024, at 08:27, Manuel Fernandez wrote:
> Hello Alexei.
> My problem is that I can't put the street name tag. My file is a geojson. And
> the field es name. I have trid :
>
> var totcmnosLayer = L.geoJson(null);
> $.getJSON("data/tot_cmnos.geojson", function(data){
> totcmnosLayer.addData(data);
> onEachFeature: function(feature, layer) {
> if (feature.properties && feature.properties.DENOMINACI1) {
> layer.bindPopup(feature.properties.DENOMINACI1);
> }
> }
> or layer.bindLabel, bindTooltip
> But I doesn't work. :(
> Thanks a lot
>
>
>
> El mié, 10 abr 2024 a las 9:16, Alexei Schwab via QGIS-User
> () escribió:
>> __
>> Hi Manuel,
>>
>> You can change the position of the label in the layer label settings:
>> https://docs.qgis.org/3.34/en/docs/user_manual/style_library/label_settings.html#placement-for-line-layers
>>
>> Under the Placement tab > General settings section, you can change the text
>> position from Above line to On line.
>>
>> You might want to add a buffer or backgroiund to the text to keep it legible
>> over the line.
>>
>> Regards,
>>
>> Alexei
>>
>> On Tue, 9 Apr 2024, at 15:50, Manuel Fernandez via QGIS-User wrote:
>>> I have a streets layer in geojson. Is it possible to put the name tag on
>>> the line? Not in a popup.
>>> Thanks a lot
>>> ___
>>> 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] geojson
Hi Manuel, You can change the position of the label in the layer label settings: https://docs.qgis.org/3.34/en/docs/user_manual/style_library/label_settings.html#placement-for-line-layers Under the Placement tab > General settings section, you can change the text position from Above line to On line. You might want to add a buffer or backgroiund to the text to keep it legible over the line. Regards, Alexei On Tue, 9 Apr 2024, at 15:50, Manuel Fernandez via QGIS-User wrote: > I have a streets layer in geojson. Is it possible to put the name tag on the > line? Not in a popup. > Thanks a lot > ___ > 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
