> 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/fr/commandes-powershell/new-udmaprasterlayer.md). # New-UDMapRasterLayer New-UDMapRasterLayer ajoute une couche de tuiles matricielles, comme les images OpenStreetMap ou Bing, à un New-UDMap dans PowerShell Universal, avec une opacité configurable. ### Résumé Crée une couche matricielle de carte. ### Syntaxe ```powershell New-UDMapRasterLayer [-Id ] [-TileServer ] [-Attribution ] [-Opacity ] [-ZIndex ] [-Name ] [] New-UDMapRasterLayer [-Id ] -ApiKey [-Type ] -Bing [-Attribution ] [-Opacity ] [-ZIndex ] [-Name ] [] ``` ### Description Crée une couche matricielle de carte. ### Paramètres #### -Id L'id de la couche matricielle de carte. La valeur par défaut est un nouveau GUID. ``` Required? false Position? named Default value ([Guid]::NewGuid()) Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -TileServer Le serveur de tuiles à utiliser. La valeur par défaut est 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 La clé d'API à utiliser pour le serveur de tuiles. ``` Required? true Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Type Le type de carte Bing à utiliser. La valeur par défaut est Aerial. ``` Required? false Position? named Default value Aerial Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Bing Utiliser ou non les cartes Bing. ``` Required? true Position? named Default value False Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Attribution Le texte d'attribution à afficher sur la carte. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Opacity L'opacité de la carte. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ZIndex L'index z de la carte. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Name Le nom de la couche matricielle. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Paramètres communs Cette applet de commande prend en charge les paramètres communs : Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable et OutVariable. Pour plus d'informations, consultez [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/fr/commandes-powershell/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.