Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-terms-conditions 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-captcha 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themify 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themify 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the logo-carousel-pro 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-tm-extra-product-options 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo 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 /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themify 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 /var/www/html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":6509,"date":"2021-10-14T16:31:20","date_gmt":"2021-10-14T16:31:20","guid":{"rendered":"https:\/\/oceanbuilders.com\/?p=6509"},"modified":"2023-01-11T20:44:51","modified_gmt":"2023-01-11T20:44:51","slug":"scouting-trip-to-boquete-panama-to-find-locations-for-the-greenpod","status":"publish","type":"post","link":"https:\/\/oceanbuilders.com\/blog\/scouting-trip-to-boquete-panama-to-find-locations-for-the-greenpod\/","title":{"rendered":"Scouting Trip To Boquete, Panama To Find Locations For The GreenPod"},"content":{"rendered":"\n
\n
\n
\n
\n \n
\n
\n

Here we have some footage of land near the Lucero Golf Course<\/a> near Boquete, Panama. On a flight from Toronto to Panama in late 2019, our CEO, Grant had a conversation with the man sitting next to him on the flight. During their conversation, the man mentioned that he was interested in building 3D printed homes for the residential area of his golf course.<\/p>

The man ended up being the owner of the Lucero Golf Course and he and Grant continued their conversation. Grant mentioned that Ocean Builders has the largest 3D printer in Latin America and that it was going to be used to build 3D printed homes. The discussion went further and it led to the Ocean Builders team to take a trip to the Lucero Golf Course.<\/p>

The scouting trip to the golf course resulted in the idea of creating a small community of about 10-15 of our GreenPods<\/a> at the golf course. This is a potential location where we could build our first GreenPods.<\/p>

The GreenPod is similar to the SeaPod, but as the name implies, it is built on land instead of in the ocean. As with the theme of everything that we do, the GreenPod is designed to be as eco-friendly as possible. With the elevated home standing above the ground, the footprint is incredibly small compared to a traditional home. This is much less disruptive to the nature since there is no clear cutting and it allows for the home to co-exist with the nature.<\/p>

While maintaining the same functions of the SeaPod, this is an alternative for those who don\u2019t want to live at sea. The GreenPod offers all of the conveniences and luxuries that are found in the SeaPod as well as the technologies that make our homes so special and unique. With its elevated design putting you above the earth and closer to the treetops, the GreenPod is like a treehouse from the future that is eco-friendly and smart.<\/p>

As you can see in the video of the Lucero Golf Course, this is an excellent location to put our project into action. With the beautiful hills and undisturbed forests, the sights and surroundings for the GreenPod will be second to none, coupled with the amenities offered by the golf course and surrounding areas, this is the perfect place to get our feet wet.<\/p>

We feel that the GreenPod will be the future of land-based sustainable and eco-friendly living. Be sure to follow along to watch the progress as this project continues to march forward!<\/p> <\/div>\n<\/div>\n\n

\n
\n
\n