| English short name| | French short name | Alpha-2 code | Alpha-3 code | Numeric |
|---|---|---|---|---|
| Åland Islands | Åland(les Îles) | AX | ALA | 248 |
| Zimbabwe | Zimbabwe (le) | ZW | ZWE | 716 |
| Zambia | Zambie (la) | ZM | ZMB | 894 |
| Yemen | Yémen (le) | YE | YEM | 887 |
| Western Sahara* |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "_comment": "Your community's configuration. The central OTE tools (editor, publish, exports) read this file from your fork. Keys starting with '_' are comments — safe to delete.", | |
| "_comment_feed": "Metadata for your published feed (feed.json, ICS, RSS). Replace every value below with your own — they're placeholders telling you what to type, not real defaults to leave in place.", | |
| "_comment_license": "License of your event DATA (not of the events themselves). Recommended: CC0-1.0 (public domain, most permissive — anyone can republish, default) or CC-BY-4.0 (requires attribution). Any SPDX identifier or URL works.", | |
| "_comment_textLanguage": "The language your feed's free text (title, description, and your events' name/description) is written in, as a BCP-47 tag ('es', 'ca', 'en'…). Declared once here so events don't have to repeat it. Optional — only needed if you use `translations`.", | |
| "_comment_organizers": "Who organizes your events, by default. Every event in events/*.json inherits this list unle |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** | |
| * Devuelve el color de fondo (hex) de una celda. | |
| * Uso: =GETCOLOR("Hoja1!B2") | |
| */ | |
| function GETCOLOR(a1Address) { | |
| if (typeof a1Address !== 'string') return ''; | |
| const ss = SpreadsheetApp.getActiveSpreadsheet(); | |
| let sheetName = ''; | |
| let cellAddress = a1Address; |
| Título del artículo | A quién va dirigido | Qué ganarás al leerlo |
|---|---|---|
| Caso de uso para cada tipo de servicio de datos | Product managers, product owners y solution architects. | Desarrollar un modelo mental claro de para qué es más adecuado cada servicio (antes de entrar en los detalles). |
| Diferencias en la creación y mantenimiento | Data engineers, desarrolladores, solution architects y technical product managers. | Comprender las ventajas y limitaciones de cada servicio, y algunos detalles de implementación de bajo nivel, para poder elegir el adecuado y planificar la mantenibilidad a largo plazo. |
| **[Diferencias en herramientas de gestión](https://www.esri.com/arcgis-blog/products/developers/developers/arcgis-hosted-dat |
A Pen by Raul Jimenez Ortega on CodePen.
A Pen by Raul Jimenez Ortega on CodePen.
A Pen by Raul Jimenez Ortega on CodePen.
A Pen by Raul Jimenez Ortega on CodePen.
NewerOlder