Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the webp-converter-for-media domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the polylang domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (o `amp_is_request()`, anteriormente `is_amp_endpoint()`) se llamó demasiado pronto y por tanto no funcionará correctamente. WordPress is currently doing the `plugins_loaded` hook. Llamar a esta función antes de la acción `wp` significa que no se tendrá acceso a `WP_Query` y el objeto de la consulta para determinar si es una respuesta AMP, por tanto, no se tendrán en cuenta ni el filtro `amp_skip_post()` ni el conmutador de que está activado AMP. Parece que el plugin con el slug `google-analytics-for-wordpress` es el responsable; por favor, contacta con el autor. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (o `amp_is_request()`, anteriormente `is_amp_endpoint()`) se llamó demasiado pronto y por tanto no funcionará correctamente. WordPress is currently doing the `plugins_loaded` hook. Llamar a esta función antes de la acción `wp` significa que no se tendrá acceso a `WP_Query` y el objeto de la consulta para determinar si es una respuesta AMP, por tanto, no se tendrán en cuenta ni el filtro `amp_skip_post()` ni el conmutador de que está activado AMP. Parece que el plugin con el slug `google-analytics-for-wordpress` es el responsable; por favor, contacta con el autor. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the bridge domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Por favor, visita Depuración en WordPress para más información. (Este mensaje fue añadido en la versión 6.7.0). in /opt/bitnami/apps/wordpress/htdocs/wp-includes/functions.php on line 6170
Nostrum Bay | Carlos Ott

Nostrum Bay



Un volumen compacto distintivo simple junto a la bahía del puerto de Montevideo, un edificio de gran altura de viviendas asequibles, acomoda las 194 unidades residenciales, 103 puestos de estacionamiento y áreas comerciales. Columnas altas de 4 pisos en forma de V rodean el podio comercial con techo verde. Una marquesina rectangular superior y dos volúmenes oscuros inclinados coronan la torre residencial con aletas grises de fachada que refuerzan la elegancia y la verticalidad.

UBICACIÓN: Montevideo, Uruguay
ÁREA: 19.089 m2
FECHA: 2016
ESTADO: Finalizado 2021
ARQUITECTO CONCEPTUAL: Carlos Ott en asociación con Carlos Ponce de León
ARQUITECTO DE REGISTRO: Carlos Ott en asociación con Carlos Ponce de León

Otros Proyectos