> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/de/powershell-befehle/new-udmaprasterlayer.md). # New-UDMapRasterLayer New-UDMapRasterLayer fügt einer New-UDMap in PowerShell Universal eine Raster-Kachelebene hinzu, etwa OpenStreetMap- oder Bing-Bilder, mit konfigurierbarer Deckkraft. ### Übersicht Erstellt eine Karten-Rasterebene. ### Syntax ```powershell New-UDMapRasterLayer [-Id ] [-TileServer ] [-Attribution ] [-Opacity ] [-ZIndex ] [-Name ] [] New-UDMapRasterLayer [-Id ] -ApiKey [-Type ] -Bing [-Attribution ] [-Opacity ] [-ZIndex ] [-Name ] [] ``` ### Beschreibung Erstellt eine Karten-Rasterebene. ### Parameter #### -Id Die ID der Karten-Rasterebene. Standardmäßig ist dies eine neue GUID. ``` Required? false Position? named Default value ([Guid]::NewGuid()) Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -TileServer Der zu verwendende Kachelserver. Standardmäßig ist dies OpenStreetMap. ``` Required? false Position? named Default value https://a.tile.openstreetmap.org/{z}/{x}/{y}.png Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ApiKey Der für den Kachelserver zu verwendende API-Schlüssel. ``` Required? true Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Type Der zu verwendende Bing-Kartentyp. Standardmäßig ist dies Aerial. ``` Required? false Position? named Default value Aerial Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Bing Ob Bing Maps verwendet werden soll oder nicht. ``` Required? true Position? named Default value False Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Attribution Auf der Karte anzuzeigender Attributionstext. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Opacity Die Deckkraft der Karte. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ZIndex Der Z-Index der Karte. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Name Der Name der Rasterebene. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Allgemeine Parameter Dieses Cmdlet unterstützt die allgemeinen Parameter: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable und OutVariable. Weitere Informationen finden Sie unter [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/powershell-universal/de/powershell-befehle/new-udmaprasterlayer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.