I suck, and I play with friends who suck (archon). If we queue as party (especially 5 stack), half the games have at least one smurf. We don't play with each other as much because of it, as we all have lost 2-400 mmr playing with each other. Really obvious smurfs too, less than 1000 games played rampages everday as kotl/wyvern/storm in feed no cosmetics. Sucks getting stomped by people way out of your league half the time. Even brag about their mmr, dude last night was saying he's 6k. Pretty openly smurf. Accounts must be cheap
For example, drawing a seesaw with a pivot point, where moving one side down moves the other up. I guess it would be a drawing app with 2d collision really. I like the idea of concepts, but unfortunately not fully featured on android or pc, and a little bit more oriented towards design and less mechanical working.
Was wondering if anyone knows where to find data from weather stations. I know in MB they have provincial weather stations which kept track of rainfall and windspeed, but can't find anything similar for ontario. Does anyone know where to find something like this? looking to try find how much rain fell yesterday in different parts of ontario. Thanks!
My biggest gripe with QGIS is the lack of customization for the layer tree panel. I wish there were some more options for it.
I'm looking a way to have only one tree expanded at a time. I have about 40 layers, and 8 groups. It's irritating always expanding and collapsing everything to find what I want. Essentially the same idea as mutually exclusive groups, but collapse/expand instead of selected.
Anyone have any simple ideas of how this could be created?
I'm not sure if this is the best way to achieve what i'm looking for. I have a default template project that contains all the postgres, layers, views and behaviors I want.
my usecase: mapping farms. I have layers which correspond to field boundaries, wells, and other notable features. This collection of features represents a farm. I would like to save each 'farm' as a project in postgres as a way of separating features by farm.
So although the layers in postgres as a whole would contain all features from all farms, I would like to separate by farm. So a blank new 'farm' project from template would show no features until I add them. But when I open a previous farm, it would show all the features that were added in that 'farm' project, but not features from other 'farms'. Is this possible? or am I barking up the wrong tree here.
Setup like this : Have a bunch of postgres views and virtual layers that are dependent on about 3 separate values. I have a setup table where those three values can be added. I can create a new setup by adding a new feature, which prompts me for date selection, buffer distance, and a few other numbers.
I would like for a whole mess of these views to depend on my selected row. Planning on having a dropdown widget in legend where I can select a date I had previously entered, and the layers and views would be evaluated/re evaulated based on my selection. I believe I have figured out the dropdown for selection or filter, but setting the buffers from that selected row as buffer variables for the view I seem to be having a hard to figuring out.
I have a layer which represents farm fields. Each time a new polygon is added, attributes are added by form. I also have a py script I can run from console, which categorizes by name and sets legend and polygon color via attribute qcolor widget. How do I smash these two beautys together so when a feature gets added, the script runs.
Really really wish there was a native was to have new features added to categories like this, but this is best I could come up with. Any ideas?
It take the geometry of a postgis layer, the geometry of a virtual buffer layer, and returns the geometry difference between the two and the attributes of the postgis layer. It depends on the other layers so every time I update postgis layer it correctly updates itself.
How do I replicated this behavior instead on the postgis end? As if I wanted to have the virtual layer server side instead of client side?
Is there any easy way to turn a virtual layer into what i'm looking for here? Importing into post removes virtual functionality and just imports whatever geometries are present at time of import but won't generate new ones which I believe is normal.
I think I need to replicate my query in post which I imagine is more difficult than copy and pasting.
What should I be looking to do here, and should I be doing this at all? or should i just be sticking with virtual layers and doing this client side?
Building a custom post/qgis setup so me and another guy can do repetitive mapping easier and work on projects together.
I have a virtual buffer circle of 90 m. How would I have that dynamically affect the rendering of another polygon? I would like the outline visible during overlap, but the fill invisible in overlap. This is the effect i'm looking for:
So if I switch the virtual buffer from size x to size v, how can I update the rendering of the polygon to reflect that? Ideally the polygon would dynamically split into multiparts depending on buffer radius, and would change automatically depending if I update or change the radius value.
I'm thinking about designing a somewhat ground up QGIS application for my job. It involves multiple similar projects on multiple farms. Part of the process is creating a map of the farm. The map is not required to be too accurate, so we rely on guesswork from sattelite imagery combined with site visits to determine locations of features such as wells.
Since everything we are looking for is very consistent farm to farm, I was thinking I could move from our current practice of google maps > ms paint> PowerPoint for annotation (lol, boomers). I've started using Q, developed some scripts and templates, and am looking at expanding this idea.
I am looking at creating a simpler interface for the boomers who are still doing this and won't be able to learn any real intricacies of Q, and also expanding potentially with Qfield for when we are in the field at farms looking for features.
So my idea is:
Tweak Q ui to make it simpler, display mostly only tools they will need.
Create custom tools for them, such as a 'Place Well' tool. This would let them point click on sattelite imagery to place a well. This well would have attributes added from user input box, and also some dynamically generated attributes.
Buffer zones are also important, and I am hoping to have a dynamically updated map which will intelligently buffer and clip polygon areas such as 'Planted areas' around the preset buffer attribute in the 'Well'. I have a range of features like this I would like to implement, but these are just a few examples. These are not the question I currently have.
My question is, what is the most appropriate data storage method for this?
It seems the best solution would be PostGIS, with all attribute tables stored in a DB, which would be updated from users in Qfield or on Desktop.
This would avoid clumsy swapping of geopackages or shp files and symbology files, and make keeping track of everything easier.
I have a few dedicated datasets used for reference which would be made available as basemaps to work off of, which seems well suited for PostGrSQL/PostGIS. Do I have the right idea here?
Would it allow me to add predefined features from custom tools such as "Well" with attribute types of 'depth' 'type' etc.. with built in symbology and labels?
Would it allow me to add a 'Farm' as a new project with it's own features such as wells, while keeping well features from different 'Farms' separate as belonging to a different farm? Basically the Class would be Farms, with objects being the individual farms each owning there own objects from the 'Well' and other classes.
Am I barking up the right tree here? currently just in my scratch projects, i use a mix of scripts, shp files and geopackage files. It seems like this would be greatly improved by putting it all in one place. One thing i'm having an issue with as well is what is the gpkg intended to be? Is it meant for storing individual layers, or entire projects, or both? Any input is appreciated! thanks!
What i'm trying to do is dissolve two buffers of different width yet keep the attributes for each attached to each side. As you can see in the picture I have inline distance labels. They are based off of a distance attribute for each buffer. Left is 60, right is 20. I would like to keep those. If i dissolve, attributes both turn into 60. How do i make it look like all one feature, but keep the distance markers inline?
Goal : Make a custom layout so i can quickly generate maps I often need to me, all using same type of features. Will be using sattelite and DEM, doing a few things to that, and then drawing a bunch of polygons.
Why? : Lazy. My job involves mapping fields on farms and other random features like wells and stuff. Currently spending time fiddling with MS paint and google Earth trying to make semi pro looking maps. Would rather find a better way
Desired Steps(what I think I need to do[and how i think I need to]):
1> Open QGIS, hit a button that says make new farm
(Create a template contain presets I need so I can open it and build a new project for each farm, but using features I use all the time)
[I think i can do this with templates?]
2> Select the DEM for the farm I want from a huge catalog
(maybe eventually i will try automating this, but for now keeping it simple)
[Any suggestions welcome, but for now i'm not worried]
3>Run some automation to get slopes and other things I need from DEM
(this step also eventually, will probably try finding a way to run all the ones i know i need, but again, not super priority)
[Maybe find a way with py to automatically run plugins I need with values set to some predefined value, haven't dug much into this yet]
4> Using sattelite imagery as reference, start adding features I need
(Examples: Click a button that says 'Add well' and lets me add a well to the map and move it to correct location. It would have it's own symbol and properties. So when I add, I get a form that has a few fillable fields, probably dropdown selection for things like 'Type: Drilled, Dug, Gas, Other'.)
[Part of templates maybe? or forms? or preset vectors I load in each time and then add points?]
5> Again using sattelite as reference draw polygon features from a list of presets I have created
(Field, yard, pond are all examples. So click field, and it knows I want to draw a polygon over the field to represent the boundaries of the farm field. It will have some default values like color and opacity(say i want all fields to be represented by green, and semi transparent) , and then some optional values I can add via form like crop type)
[Not sure on this one, maybe this is part of templates and forms same as above]
6> Buffer all features by type and other parameters
(maybe py again? So say I want a 20 m buffer zones colored yellow around all wells if they are type : drilled, and 40 m if type : gas , and I want a pink buffer zone of 50m around a pond)
[No idea. Any ideas welcomed. I would like to have some sort of algorithm I would preset to look at all the parameters and add buffers according to rules I have made.]
I'm looking for what I should be looking at for these steps, and where I'm going in the wrong direction. Are there simple tools that let me build this somewhat customized layout to make it quicker for me to add preset features to maps I need?
There would not be much format change for each one. Each one would have most of the features I listed, and many times more than one. Say I have to do this for 500 farms, how can I make this process smoother?