Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d279388059/htdocs/blog/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/37/d279388059/htdocs/blog/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/37/d279388059/htdocs/blog/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d279388059/htdocs/blog/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/37/d279388059/htdocs/blog/wp-includes/class.wp-dependencies.php on line 15
Vacaciones | el blog

Posts tagged: vacaciones


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 55

Las mejores vacaciones de aventura… del mundo

By Rubén,
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d279388059/htdocs/blog/wp-includes/functions.php on line 55
22 Mayo 2010 11:01

agencias viajes de aventura

agencias viajes de aventura

El año pasado National Geographic Adventure publicó la lista de las mejores empresas de viajes de aventura y turismo activo del Mundo. Un proyecto ambicioso ¿verdad? Pero ya sabemos que para los chicos de NG no hay límites.

La metodología para puntuar y valorar a estas empresas y añadirlas a un ranking se describe en su web:

Usando la base de datos mundial de National Geographic Adventure, y con la ayuda de Sustainable Travel International, The Adventure Travel Trade Association, la Sociedad Internacional de Ecoturismo, y otras organizaciones de viajes y turismo, llegamos a cientos de compañías de turismo en todo el mundo.

Se les pidió que completaran una encuesta completa. Cada encuesta fue puntuada del 1 al 100 en cada una de las siguientes categorías: Educación, Sostenibilidad, Calidad de Servicio, y el Espíritu de Aventura.

Luego, los investigadores entrevistaron al azar referencias de clientes para todas las empresas basadas en las mismas categorías y genera una puntuación, también entre 1 y 100. Un equipo de editores de AVENTURA NG expertos en viajes filtraron las calificaciones a partir de 85 puntos. A partir de este grupo de candidatos, se identificaron las mejores compañías de viajes de aventura.

El resultado es un completo directorio donde podemos filtrar nuestras búsquedas en función del tipo de viaje de aventura que queramos realizar:

  • Viajes Multiaventura
  • Viajes de Trekking y Senderismo
  • Viajes de Montañismo
  • Safaris en África
  • Cruceros de aventura
  • Viajes en bici
  • Naturaleza y vida salvaje

En próximos post analizaremos algunas de estas propuestas de cara a las vacaciones de verano que está ya aquí a la vuelta de la esquina.

Y aunque Multiaventura Buendía no aparezca (de momento :P ) en el listado, es una buena opción para pasar unos días de aventura, descanso, buenas viandas entre amigos o en familia en tus vacaciones de verano o escapadas de fin de semana con los descensos en Rafting, aguas bravas, barranquismo, las rutas en piragua a la luz de la luna llena…

Feliz día!