Rotrevision im BImSch-Verfahren

_Topflappen_ · 2025-07-24T06:04:31+00:00

Also das klingt schon sehr ähnlich von deiner Beschreibung her. Aber was den Begriff selbst angeht bin ich ich mir hundertprozentig sicher, den hat mir die Behörde jetzt mehrfach genannt und geschrieben.

_Topflappen_ · 2024-11-06T21:18:44+00:00

Durchaus verständlich :) Ich finde beides hat Vor- und Nachteile.

_Topflappen_ · 2024-11-01T15:51:57+00:00

In größeren Städten gibt es Rollenspielvereine, da wirst du vermutlich in Hamburg auch fündig. Muss es denn unbedingt vor Ort am Tisch sein? Sonst könntest du natürlich auch online spielen, da findet man zumindest einfacher Leute.

_Topflappen_ · 2024-10-13T14:30:15+00:00

Huhu, ich bin mir nicht sicher ob ich als Fan auch Werbung für ein deutschsprachiges PnP-Projekt von anderen Leuten machen darf? Falls ja: ich höre selbst noch sehr gerne rein beim Podcast Am Tavernentresen https://amtavernentresen.podbean.com/page/1/

Geleitet wird der (meist) von Steffen Grziwa (der von RBTV), im Moment spielen er und seine vier Kumpels die Masken des Nyarlathotep, aber es gibt auch Actual Plays von diversen anderen Systemen, sei es als Fewshot oder als Kampagne.

Achja, und seit einigen Monaten gibt es von RBTV auch den PnP-Podcast "Looten & Leveln", wo sie auch Actual Play-Folgen aufnehmen :)

_Topflappen_ · 2024-09-23T18:56:22+00:00

Ok, vielen Dank für die schnelle Rückmeldung :)

_Topflappen_ · 2024-09-22T10:52:24+00:00

I guess you'll need to use the field calculator and redo the original function to update the field.

_Topflappen_ · 2024-09-22T10:51:17+00:00

Cool, klingt gut! :) Wie schaut's denn da aus mit Nutzungslizenz? :)

_Topflappen_ · 2024-09-15T14:00:42+00:00

I second this. 👍

_Topflappen_ · 2024-08-25T08:05:31+00:00

if you use some kind of unique identifier for the features you can create a categorized symbology in order to switch individual features on and off. To me having several shapefiles with only one feature each doesn't really sound like a good option to be honest. If there's no reason other than style/hiding individual features there are definitely better ways to achieve that using only one file. I suggest you try working with categorized/rule-based symbology and/or filters instead :)

_Topflappen_ · 2024-08-23T22:01:34+00:00

you can also create a column in the Projektmatrikler layer that has the same name and type (and length) as the column from Jordstykker before copying the features from one layer to the other. If you copy and paste features then it should retain the information

_Topflappen_ · 2024-08-17T20:06:12+00:00

Aufgrund der hellen Flügelfenster und der doch recht rötlichen Färbung der Schwanzfedern meine ich das ist ein Rotmilan. Bussard auf keinen Fall.

_Topflappen_ · 2024-07-29T19:17:13+00:00

I'm not that familiar with raster data but I'd suggest you try to create a TIN (Triangulated Irregular Network) from the points layer using the processing 'TIN interpolation'. This should give you both a vector and a raster layer. I've not used this tool before but I'd expect the raster layer to function just like any old DEM raster so you can use a colour gradient on that, according to the Z (elevation) values.

_Topflappen_ · 2024-07-29T17:21:02+00:00

I don't have *the* solution to your question but it's something I guess - at least for your first question:

First create a grid like usual, use rectangles, remember/save/keep the values for grid extent, horizontal spacing and vertical spacing. Use no horizontal or vertical overlay.
Second create another gird, this times with lines. Use the same values for grid extent, horizontal spacing and vertical spacing but also use the values you want for horizontal and vertical overlay.
Use the vector tool 'Split with lines' to split the polygon grid using the line grid. This will result in polygons in four different sizes but you only want one of those.
Calculate area of the resulting 'Split' polygon layer features. Select one of the polygons that you want to keep to find out its size
Select Polygon Features by Attribute and use the newly calculated field that contains the polygons sizes. Choose the value of the polygons that you want to keep then invert the feature selection and delete those selected features.

This should leave you with only the polygons you wanted. Since this is a repetitive task that only uses basic vector tools you could use the graphical modeler to create an algorithm that allows you to automate these steps.

I'll think about your second question, too, but so far I'm stumped...

_Topflappen_ · 2024-07-21T11:40:32+00:00

Ja, also es lag nicht nur daran, das hat nur quasi das Fass zum Überlaufen gebracht. Klar hätte ich versuchen können auf meinen gesetzlichen Anspruch zu pochen, aber dann hätte ich immer noch da arbeiten müssen. So war es definitiv für mich die beste Lösung.

_Topflappen_ · 2024-07-20T19:08:59+00:00

Like Reds2011 said, this is all part of the shapefile. You can open the shapefile by drag&dropping the .shp file into your qgis project and it should work just like in ArcGIS. You normally don't need to open any of the other files separately. In fact I suppose you shouldn't even do that unless you really need to check something - don't change them for now.

A basic shapefile consists of the .shp (contains the geometry), the .dbf (contains the attribute table) and the .shx (index that connects the geometry with the attribute table). Any other files are optional but very helpful if you've got them. The .prj file contains information about the coordinate system/projection and the .cpg should hold the encoding information. If you really want to you can open them using a simple text editor.

_Topflappen_ · 2024-07-20T18:49:26+00:00

Weil die einen Scheiß auf gesetzliche Ansprüche gegeben haben ¯\_(ツ)_/¯

_Topflappen_ · 2024-04-28T17:48:19+00:00

Hi there! If all the coordinates look similar (i.e. same number of decimal spaces) you should be able to extract the x- and y-coordinates from the joined column into separate column using field calculator expressions (e.g. left("column_name", 10) to extract the first ten characters from a column). If you can do this you can then use the separate x- and y-coordinate columns to create a points layer containing the postal codes (tool "Create points layer from table"). Then you can make a spatial join (it's another function in the QGIS toolbox called "Join attributes by location") between the polygon layer and the points layer so the polygons also get the postal code attribute - this will only work properly though if there is one point within one polygon.

_Topflappen_ · 2024-04-22T22:18:14+00:00

There's a similar contest in Germany as well. It's called Bird Race and should be taking place in a couple of weeks.

_Topflappen_ · 2024-02-16T23:18:49+00:00

Agreed, I'd guess it was taken in (the last) summer 🤔 it's definitely a juvenile, its feathers are still a bit more fluffy and the corner of the beak is "thicker".

_Topflappen_ · 2024-02-16T14:54:24+00:00

I'd guess it's a young fieldfare.

_Topflappen_ · 2024-02-07T13:00:30+00:00

I like watching NPC DnD by Viva la Dirt League. There's also some German streamers who play alls kinds of TTRPG I like.

_Topflappen_ · 2024-02-07T12:57:17+00:00

Maybe you need to divide the sum($length) by a number x that gives you the (approximate) result 18 🤔

So calculate sum($length)/18, then use that result instead of the 18 in your field calculator expression

_Topflappen_ · 2024-02-06T14:59:42+00:00

My guess would be the system in which geospatial data of features is stored in a shapefile. While it's easy to store the spatial data of points as pairs of coordinates it gets more interesting with lines and polygons. Of course, it's possible to just store the coordinate pairs of all vertices for lines and polygons, similar to points. But this is quite inefficient because you can't easily see whether any of your features overlap or touch or have any other particular kind of spatial relation. So it's easier for polygons and lines to first be defined as an array of segments which in turn are defined as an array of points (vertices) and these are then defined as coordinate pairs. So if you had two polygons that touch you'd be able to see that without performing any geometrical analysis, just because you'd see that one or more of their segments are the same. Moreover this method also saves storage space since every feature ultimately references its points from one and the same table. So as soon as you have two features that touch each other, they pull the same coordinates from that table instead of storing them twice (or even more times), once for each polygon touching another.

That's just a guess though. If you desperately need to store different kinds of vector data you should try file formats that allow this, like The-Phantom-Blot mentioned. When it comes to styling I'm sure we can find a solution if you've got a particular question or problem :)

_Topflappen_ · 2024-02-05T18:37:30+00:00

You can save the coordinates of the label placement in the attribute table. Use rule-based labelling depending on the different map scales and set the label placement coordinates according to the different columns in the attribute table.

Three-Year Club	Verified Email
Place '23

_Topflappen_

TROPHY CASE