Blueprint B Version 3.0 Pdf

0 views
Skip to first unread message

Sueann

unread,
Aug 4, 2024, 4:01:45 PM8/4/24
to grunarcider
Thisreference is part of the blueprint extension for the Azure CLI (version 2.50.0 or higher). The extension will automatically install the first time you run an az blueprint version command. Learn more about extensions.

Total number of items to return in the command's output. If the total number of items available is more than the value specified, a token is provided in the command's output. To resume pagination, provide the token value in --next-token argument of a subsequent command.


Some assets are not backwards compatible. Perhaps also depends on the blueprint code. But for testing you could recreate the folder structure inside the older project, copy/past the newer version blueprint into it, and see if it is displayed inside the project. However, theoretically it could even yield a serial mismatch error.


The Blueprint identifies priority areas based on a suite of natural and cultural resource indicators representing terrestrial, freshwater, and marine ecosystems. A connectivity analysis identifies corridors that link coastal and inland areas and span climate gradients. Because the Blueprint is a living plan, it will evolve over time, driven by improvements to the underlying science, our growing understanding of on-the-ground conditions, and input from new partners. So far, more than 2,000 people from over 600 different organizations have actively participated in developing the Southeast Blueprint.


Southeast Blueprint 2023 was released in October 2023 at the annual meeting of the Southeastern Association of Fish and Wildlife Agencies. For the first time, this Blueprint used a consistent approach across the entire geography and did not have to stitch together any subregional inputs. The 2023 Blueprint expanded consistent methods and indicators to Puerto Rico, the U.S. Virgin Islands, and nearshore U.S. Caribbean waters, as well as to the full extent of U.S. waters in the Atlantic Ocean and Gulf of Mexico. This update significantly improved the older expert-driven, watershed-scale priorities for Puerto Rico, and the previous priorities for parts of the Atlantic and Gulf marine areas. It added new coverage of the U.S. Virgin Islands, U.S. Caribbean nearshore waters, and the rest of the Gulf and Atlantic marine environment. It also included minor refinements to the inland continental Southeast priorities and updated hubs and corridors for the full Blueprint area.


You can explore and download the data on the Blueprint page of the SECAS Atlas, a free online mapping platform. Here, you can also read more about the methods and underlying datasets used to create Version 2023. For a full list of everything that changed in Version 2023, check out the Southeast Blueprint changelog.


Do you have a question about the Blueprint? Would you like help using the Blueprint to support a proposal or inform a decision? Staff across the Southeast are here to support you! You can also explore the Online Guide to using the Southeast Blueprint, which will walk you through how to use it on your own.


These are just a few of the more than 250 Blueprint uses completed so far, with over 60 still in progress! For more in-depth examples of how the Blueprint is being used, check out the SECAS in Action story map. You can also see a detailed list of the organizations using the Blueprint.


In the fall of 2013, SECAS leadership set a goal of developing a first-generation Southeast Blueprint for landscape-scale conservation by the fall of 2016. Many different conservation planning efforts were already underway, but most eco-regional plans only covered parts of states, while state-specific plans stopped at the state line. The results of all this parallel planning did not yet add up to an integrated regional strategy.


Three years later, Version 1.0 of the Southeast Blueprint was released in December 2016. Development of this first Blueprint relied heavily on Landscape Conservation Cooperative (LCC) partnerships across the Southeast and Caribbean. This plan provided the first ever integration of spatial plans developed through the South Atlantic, Appalachian, Gulf Coastal Plains and Ozarks, Gulf Coast Prairie, North Atlantic, Peninsular Florida and Caribbean LCCs. It also included priorities from the Mississippi River Basin/Gulf Hypoxia Initiative spearheaded by seven LCCs (Appalachian, Eastern Tallgrass Prairie and Big Rivers, Great Plains, Gulf Coast Prairie, Gulf Coastal Plains and Ozarks, Plains and Prairie Potholes, and Upper Midwest and Great Lakes).


Version 2.0 of the Southeast Blueprint was released in November 2017. This plan incorporated the improved subregional Blueprints from several LCCs and established priority connections with western states through the Crucial Habitat Assessment Tool. Significant improvements over Version 1.0 included improved consistency across LCC boundaries, improved consistency in climate change response, and improved integration beyond the Southeast.


Version 3.0 of the Southeast Blueprint was first introduced at the October 2018 SEAFWA annual conference, and officially released in February 2019. Its development occurred during a time of transition for the LCC Network where the structure and function of some LCCs was changing. Despite these changes, the capacity and commitment to continue to support Blueprint users and improve the Southeast Blueprint remains strong, evidenced by the many examples of Blueprint implementation, as well as progress on Blueprint improvements. Blueprint 3.0 added full coverage of Texas, integrated threat layers covering the full Southeast, and a hubs and corridors layer covering part of the region.


Version 4.0 of the Southeast Blueprint was released in October 2019 at the SEAFWA annual conference. Improvements over the previous version included: corrected overprioritization in Texas, Oklahoma, and the mountains of West Virginia and Virginia; improved priorities in the Lower Mississippi Valley, Louisiana marshes, and the Southern Appalachians; updated inputs from Florida and the Middle South subregion; expanded marine coverage to include state and federal waters around Florida; and expanded hubs and corridors that now cover all of Florida.


Southeast Blueprint 2021 was released in November 2021 following the virtual SEAFWA annual conference. Significant improvements over the previous versions included: updated and improved indicators, better incorporation of equity, deep-sea coral, fire, and important grasslands, and multiple connectivity improvements in the South Atlantic subregion, as well as correcting a scoring issue in the Middle Southeast subregion.


Southeast Blueprint 2022 was released in October 2022 at the SEAFWA annual conference. Rather than continuing to stitch together so many different subregional plans, the 2022 Blueprint took massive strides toward regional consistency by using the same methods and indicators across 15 states of the Southeast. To provide more complete coverage of the SECAS geography, it also incorporated two additional input plans: the latest update to the Florida Marine Blueprint for marine areas in Florida and the Caribbean Landscape Conservation Design for inland areas in Puerto Rico.


Southeast Blueprint 2023 was released in October 2023 at the SEAFWA annual conference. For the first time, this Blueprint used a consistent approach across the entire geography and did not have to stitch together any subregional inputs. The 2023 Blueprint expanded consistent methods and indicators to Puerto Rico, the U.S. Virgin Islands, and nearshore U.S. Caribbean waters, as well as to the full extent of U.S. waters in the Atlantic Ocean and Gulf of Mexico. This update significantly improved the older expert-driven, watershed-scale priorities for Puerto Rico, and the previous priorities for parts of the Atlantic and Gulf marine areas. It added new coverage of the U.S. Virgin Islands, U.S. Caribbean nearshore waters, and the rest of the Gulf and Atlantic marine environment. It also included minor refinements to the inland continental Southeast priorities and updated hubs and corridors for the full Blueprint area.


CARB's Office of Community Air Protection requested public comment on this draft version of Blueprint 2.0., which will replace the 2018 Program Blueprint. Part One is a strategic plan for CARB and Air Districts to grow the Program over the next five years. It includes goals, objectives, actions and guiding principles informed by lessons learned from the first five years of the program. Part Two of Draft BP 2.0 offers practical guidance for air districts, communities, affected industry, and other partners to actively engage in improving air quality at the local level.


One more thing could you click the Download Local Logs button from the Support tab in Local and share that zip here? This will generate an archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering. Thank you!


I tried replicated the issue this morning using Local 8.3.2. I spun up a preferred site, created a Blueprint, and then tried to create a new site based on that Blueprint but it worked just fine for me. We can take a look at your logs though and see if anything stands out!


Something to clarify here is this just happening when you try to make a blueprint of a specific site? Or for example if you try to make a blueprint of a different site or a new site does the same thing happen?


Apologies there I messed up those steps a little bit! What I intended was for you to create a site from that blueprint, export the site, reimport, and then use that to create a blueprint on the new Local version.


Solved for me: I had the same error as shown in the screenshots whenever trying to clone (did not use a blueprint) and my Users/username/ Library/Application Support/Local/run/RANDOM_STRING/conf folder was empty each time. I downgraded all the way to 8.2.0 and nothing worked. Then I toggled the PHP version of my site I was cloning from from PHP 8.0 to 8.2 and cloning worked again! Re-upgraded to Local 9.0 and it still worked!

3a8082e126
Reply all
Reply to author
Forward
0 new messages