> 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/es/comandos-de-powershell/new-udmaprasterlayer.md). # New-UDMapRasterLayer New-UDMapRasterLayer añade una capa de teselas ráster, como imágenes de OpenStreetMap o Bing, a un New-UDMap en PowerShell Universal con opacidad configurable. ### Sinopsis Crea una capa ráster de mapa. ### Sintaxis ```powershell New-UDMapRasterLayer [-Id ] [-TileServer ] [-Attribution ] [-Opacity ] [-ZIndex ] [-Name ] [] New-UDMapRasterLayer [-Id ] -ApiKey [-Type ] -Bing [-Attribution ] [-Opacity ] [-ZIndex ] [-Name ] [] ``` ### Descripción Crea una capa ráster de mapa. ### Parámetros #### -Id El id de la capa ráster del mapa. De forma predeterminada, es un nuevo GUID. ``` Required? false Position? named Default value ([Guid]::NewGuid()) Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -TileServer El servidor de teselas que se va a usar. De forma predeterminada, es 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 clave de API que se va a usar para el servidor de teselas. ``` Required? true Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Type El tipo de mapa de Bing que se va a usar. De forma predeterminada, es Aerial. ``` Required? false Position? named Default value Aerial Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Bing Si se deben usar o no los mapas de Bing. ``` Required? true Position? named Default value False Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Attribution Texto de atribución que se mostrará en el mapa. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Opacity La opacidad del mapa. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ZIndex El índice z del mapa. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Name El nombre de la capa ráster. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Parámetros comunes Este cmdlet admite los parámetros comunes: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable y OutVariable. Para obtener más información, consulte [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/es/comandos-de-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.