WEBVTT Kind: captions Language: en 00:00:00.719 --> 00:00:04.870 align:start position:0% and<00:00:01.439> this<00:00:01.680> recording<00:00:02.560> will<00:00:03.040> be<00:00:03.679> posted<00:00:04.400> to<00:00:04.720> the 00:00:04.870 --> 00:00:04.880 align:start position:0% and this recording will be posted to the 00:00:04.880 --> 00:00:08.710 align:start position:0% and this recording will be posted to the county's<00:00:05.520> contracting<00:00:06.240> opportunities<00:00:07.200> page 00:00:08.710 --> 00:00:08.720 align:start position:0% county's contracting opportunities page 00:00:08.720 --> 00:00:09.910 align:start position:0% county's contracting opportunities page um 00:00:09.910 --> 00:00:09.920 align:start position:0% um 00:00:09.920 --> 00:00:11.509 align:start position:0% um as<00:00:10.080> well<00:00:10.400> as<00:00:10.639> we<00:00:10.800> will<00:00:10.960> create<00:00:11.200> a<00:00:11.280> written 00:00:11.509 --> 00:00:11.519 align:start position:0% as well as we will create a written 00:00:11.519 --> 00:00:13.030 align:start position:0% as well as we will create a written document<00:00:11.920> for<00:00:12.080> those<00:00:12.320> questions<00:00:12.639> that<00:00:12.719> we<00:00:12.880> can 00:00:13.030 --> 00:00:13.040 align:start position:0% document for those questions that we can 00:00:13.040 --> 00:00:14.629 align:start position:0% document for those questions that we can answer<00:00:13.280> today<00:00:13.759> as<00:00:13.920> well<00:00:14.080> as<00:00:14.160> those<00:00:14.400> that<00:00:14.480> we're 00:00:14.629 --> 00:00:14.639 align:start position:0% answer today as well as those that we're 00:00:14.639 --> 00:00:16.150 align:start position:0% answer today as well as those that we're not<00:00:14.799> able<00:00:14.960> to<00:00:15.040> answer<00:00:15.360> in<00:00:15.440> a<00:00:15.440> moment<00:00:15.839> during 00:00:16.150 --> 00:00:16.160 align:start position:0% not able to answer in a moment during 00:00:16.160 --> 00:00:19.910 align:start position:0% not able to answer in a moment during the<00:00:16.400> session 00:00:19.910 --> 00:00:19.920 align:start position:0% 00:00:19.920 --> 00:00:21.590 align:start position:0% it's<00:00:20.160> making<00:00:20.400> sure<00:00:20.640> the<00:00:20.720> recording's<00:00:21.199> going 00:00:21.590 --> 00:00:21.600 align:start position:0% it's making sure the recording's going 00:00:21.600 --> 00:00:23.750 align:start position:0% it's making sure the recording's going great<00:00:22.320> okay 00:00:23.750 --> 00:00:23.760 align:start position:0% great okay 00:00:23.760 --> 00:00:25.429 align:start position:0% great okay and<00:00:23.920> we'll<00:00:24.080> have<00:00:24.240> those<00:00:24.720> documents<00:00:25.199> up<00:00:25.279> for 00:00:25.429 --> 00:00:25.439 align:start position:0% and we'll have those documents up for 00:00:25.439 --> 00:00:27.269 align:start position:0% and we'll have those documents up for you<00:00:25.599> in<00:00:25.680> the<00:00:25.760> next<00:00:26.080> several<00:00:26.400> days<00:00:26.800> so<00:00:27.039> speaking 00:00:27.269 --> 00:00:27.279 align:start position:0% you in the next several days so speaking 00:00:27.279 --> 00:00:28.790 align:start position:0% you in the next several days so speaking of<00:00:27.439> questions<00:00:27.920> please<00:00:28.160> type<00:00:28.320> them<00:00:28.480> into<00:00:28.720> the 00:00:28.790 --> 00:00:28.800 align:start position:0% of questions please type them into the 00:00:28.800 --> 00:00:31.429 align:start position:0% of questions please type them into the chat<00:00:29.119> as<00:00:29.279> they<00:00:29.519> come<00:00:29.840> up<00:00:30.400> and<00:00:30.800> before<00:00:31.039> we<00:00:31.199> go 00:00:31.429 --> 00:00:31.439 align:start position:0% chat as they come up and before we go 00:00:31.439 --> 00:00:33.510 align:start position:0% chat as they come up and before we go further<00:00:32.000> i<00:00:32.079> do<00:00:32.239> want<00:00:32.399> to<00:00:32.559> acknowledge<00:00:33.280> this 00:00:33.510 --> 00:00:33.520 align:start position:0% further i do want to acknowledge this 00:00:33.520 --> 00:00:37.270 align:start position:0% further i do want to acknowledge this project<00:00:34.160> is<00:00:34.640> funded<00:00:35.280> by<00:00:35.760> a<00:00:35.920> prop<00:00:36.320> 68<00:00:36.880> coastal 00:00:37.270 --> 00:00:37.280 align:start position:0% project is funded by a prop 68 coastal 00:00:37.280 --> 00:00:38.950 align:start position:0% project is funded by a prop 68 coastal resilience<00:00:37.920> grant<00:00:38.320> from<00:00:38.559> the<00:00:38.640> ocean 00:00:38.950 --> 00:00:38.960 align:start position:0% resilience grant from the ocean 00:00:38.960 --> 00:00:40.549 align:start position:0% resilience grant from the ocean protection<00:00:39.440> council 00:00:40.549 --> 00:00:40.559 align:start position:0% protection council 00:00:40.559 --> 00:00:42.069 align:start position:0% protection council so<00:00:40.960> we<00:00:41.120> are<00:00:41.280> grateful<00:00:41.600> to<00:00:41.760> the<00:00:41.840> state<00:00:42.000> of 00:00:42.069 --> 00:00:42.079 align:start position:0% so we are grateful to the state of 00:00:42.079 --> 00:00:43.750 align:start position:0% so we are grateful to the state of california<00:00:42.559> for<00:00:42.719> their<00:00:42.879> support<00:00:43.280> of<00:00:43.440> this 00:00:43.750 --> 00:00:43.760 align:start position:0% california for their support of this 00:00:43.760 --> 00:00:45.750 align:start position:0% california for their support of this exciting<00:00:44.160> project 00:00:45.750 --> 00:00:45.760 align:start position:0% exciting project 00:00:45.760 --> 00:00:47.670 align:start position:0% exciting project so<00:00:45.920> i'm<00:00:46.079> going<00:00:46.239> to<00:00:46.320> step<00:00:46.719> through 00:00:47.670 --> 00:00:47.680 align:start position:0% so i'm going to step through 00:00:47.680 --> 00:00:49.430 align:start position:0% so i'm going to step through the<00:00:47.840> content<00:00:48.239> in<00:00:48.320> the<00:00:48.399> rfp<00:00:48.879> really<00:00:49.120> the<00:00:49.280> key 00:00:49.430 --> 00:00:49.440 align:start position:0% the content in the rfp really the key 00:00:49.440 --> 00:00:51.750 align:start position:0% the content in the rfp really the key considerations<00:00:50.879> and<00:00:50.960> then<00:00:51.120> open<00:00:51.360> it<00:00:51.520> up<00:00:51.600> for 00:00:51.750 --> 00:00:51.760 align:start position:0% considerations and then open it up for 00:00:51.760 --> 00:00:53.350 align:start position:0% considerations and then open it up for your<00:00:51.920> questions<00:00:52.399> so<00:00:52.640> some<00:00:52.800> of<00:00:52.879> the<00:00:52.960> broad 00:00:53.350 --> 00:00:53.360 align:start position:0% your questions so some of the broad 00:00:53.360 --> 00:00:55.430 align:start position:0% your questions so some of the broad context<00:00:54.079> of<00:00:54.239> where<00:00:54.399> this<00:00:54.640> project<00:00:54.960> is<00:00:55.120> coming 00:00:55.430 --> 00:00:55.440 align:start position:0% context of where this project is coming 00:00:55.440 --> 00:00:56.470 align:start position:0% context of where this project is coming from 00:00:56.470 --> 00:00:56.480 align:start position:0% from 00:00:56.480 --> 00:00:58.869 align:start position:0% from marin<00:00:56.800> county<00:00:57.360> has<00:00:57.680> made<00:00:58.160> significant 00:00:58.869 --> 00:00:58.879 align:start position:0% marin county has made significant 00:00:58.879 --> 00:01:01.110 align:start position:0% marin county has made significant progress<00:00:59.440> to<00:00:59.680> date<00:01:00.160> on<00:01:00.399> responding<00:01:00.879> to<00:01:00.960> sea 00:01:01.110 --> 00:01:01.120 align:start position:0% progress to date on responding to sea 00:01:01.120 --> 00:01:02.229 align:start position:0% progress to date on responding to sea level<00:01:01.440> rise 00:01:02.229 --> 00:01:02.239 align:start position:0% level rise 00:01:02.239 --> 00:01:05.189 align:start position:0% level rise in<00:01:02.640> 2016<00:01:03.840> the<00:01:04.000> county<00:01:04.400> completed<00:01:05.040> a 00:01:05.189 --> 00:01:05.199 align:start position:0% in 2016 the county completed a 00:01:05.199 --> 00:01:07.670 align:start position:0% in 2016 the county completed a vulnerability<00:01:06.159> assessment<00:01:06.960> for<00:01:07.119> the<00:01:07.280> ocean 00:01:07.670 --> 00:01:07.680 align:start position:0% vulnerability assessment for the ocean 00:01:07.680 --> 00:01:10.469 align:start position:0% vulnerability assessment for the ocean coast<00:01:08.560> it<00:01:08.720> goes<00:01:08.960> into<00:01:09.200> great<00:01:09.600> detail<00:01:10.240> on 00:01:10.469 --> 00:01:10.479 align:start position:0% coast it goes into great detail on 00:01:10.479 --> 00:01:14.230 align:start position:0% coast it goes into great detail on exposures<00:01:11.439> assets<00:01:12.000> at<00:01:12.159> risk<00:01:12.960> under<00:01:13.360> select 00:01:14.230 --> 00:01:14.240 align:start position:0% exposures assets at risk under select 00:01:14.240 --> 00:01:17.190 align:start position:0% exposures assets at risk under select near<00:01:14.960> medium<00:01:15.759> and<00:01:16.000> long-term<00:01:16.640> sea<00:01:16.799> level<00:01:17.040> rise 00:01:17.190 --> 00:01:17.200 align:start position:0% near medium and long-term sea level rise 00:01:17.200 --> 00:01:18.550 align:start position:0% near medium and long-term sea level rise scenarios 00:01:18.550 --> 00:01:18.560 align:start position:0% scenarios 00:01:18.560 --> 00:01:20.390 align:start position:0% scenarios and<00:01:18.640> then<00:01:18.880> in<00:01:18.960> 2018 00:01:20.390 --> 00:01:20.400 align:start position:0% and then in 2018 00:01:20.400 --> 00:01:23.350 align:start position:0% and then in 2018 the<00:01:20.560> county<00:01:21.040> completed<00:01:21.600> an<00:01:21.920> ocean<00:01:22.400> coast<00:01:23.119> sea 00:01:23.350 --> 00:01:23.360 align:start position:0% the county completed an ocean coast sea 00:01:23.360 --> 00:01:25.749 align:start position:0% the county completed an ocean coast sea level<00:01:23.600> rise<00:01:24.000> adaptation<00:01:24.799> report<00:01:25.520> that 00:01:25.749 --> 00:01:25.759 align:start position:0% level rise adaptation report that 00:01:25.759 --> 00:01:28.710 align:start position:0% level rise adaptation report that presented<00:01:26.240> numerous<00:01:26.880> adaptation<00:01:27.520> concepts 00:01:28.710 --> 00:01:28.720 align:start position:0% presented numerous adaptation concepts 00:01:28.720 --> 00:01:30.550 align:start position:0% presented numerous adaptation concepts and<00:01:29.119> sort<00:01:29.280> of<00:01:29.439> a<00:01:29.520> menu<00:01:29.920> of<00:01:30.079> possible 00:01:30.550 --> 00:01:30.560 align:start position:0% and sort of a menu of possible 00:01:30.560 --> 00:01:33.190 align:start position:0% and sort of a menu of possible strategies<00:01:31.439> for<00:01:31.600> marin's<00:01:32.320> seven<00:01:32.799> coastal 00:01:33.190 --> 00:01:33.200 align:start position:0% strategies for marin's seven coastal 00:01:33.200 --> 00:01:34.550 align:start position:0% strategies for marin's seven coastal communities 00:01:34.550 --> 00:01:34.560 align:start position:0% communities 00:01:34.560 --> 00:01:35.749 align:start position:0% communities so<00:01:34.720> today 00:01:35.749 --> 00:01:35.759 align:start position:0% so today 00:01:35.759 --> 00:01:37.590 align:start position:0% so today our<00:01:36.000> overall<00:01:36.400> objective<00:01:36.960> is<00:01:37.040> to<00:01:37.200> move<00:01:37.439> our 00:01:37.590 --> 00:01:37.600 align:start position:0% our overall objective is to move our 00:01:37.600 --> 00:01:39.910 align:start position:0% our overall objective is to move our work<00:01:38.079> substantially<00:01:38.720> forward<00:01:39.200> that<00:01:39.439> next 00:01:39.910 --> 00:01:39.920 align:start position:0% work substantially forward that next 00:01:39.920 --> 00:01:43.030 align:start position:0% work substantially forward that next stage<00:01:40.479> of<00:01:40.640> analysis<00:01:41.360> and<00:01:41.520> further<00:01:41.920> detail<00:01:42.880> so 00:01:43.030 --> 00:01:43.040 align:start position:0% stage of analysis and further detail so 00:01:43.040 --> 00:01:46.310 align:start position:0% stage of analysis and further detail so we're<00:01:43.280> focusing<00:01:43.840> in<00:01:44.399> at<00:01:44.560> a<00:01:44.640> community<00:01:45.360> scale 00:01:46.310 --> 00:01:46.320 align:start position:0% we're focusing in at a community scale 00:01:46.320 --> 00:01:48.950 align:start position:0% we're focusing in at a community scale for<00:01:46.479> adaptation<00:01:47.200> planning<00:01:47.680> in<00:01:47.920> stinson<00:01:48.479> beach 00:01:48.950 --> 00:01:48.960 align:start position:0% for adaptation planning in stinson beach 00:01:48.960 --> 00:01:51.190 align:start position:0% for adaptation planning in stinson beach which<00:01:49.200> is<00:01:49.280> the<00:01:49.439> area<00:01:49.680> of<00:01:49.759> west<00:01:50.079> marin<00:01:50.799> most 00:01:51.190 --> 00:01:51.200 align:start position:0% which is the area of west marin most 00:01:51.200 --> 00:01:55.030 align:start position:0% which is the area of west marin most immediately<00:01:51.920> at<00:01:52.159> risk<00:01:52.560> from<00:01:52.880> sea<00:01:53.040> level<00:01:53.360> rise 00:01:55.030 --> 00:01:55.040 align:start position:0% immediately at risk from sea level rise 00:01:55.040 --> 00:01:56.870 align:start position:0% immediately at risk from sea level rise and<00:01:55.119> the<00:01:55.280> intended<00:01:55.840> outcome 00:01:56.870 --> 00:01:56.880 align:start position:0% and the intended outcome 00:01:56.880 --> 00:01:59.109 align:start position:0% and the intended outcome of<00:01:57.040> this<00:01:57.280> vinson<00:01:57.680> beach<00:01:58.079> adaptation<00:01:58.880> and 00:01:59.109 --> 00:01:59.119 align:start position:0% of this vinson beach adaptation and 00:01:59.119 --> 00:02:01.030 align:start position:0% of this vinson beach adaptation and resilience<00:01:59.680> collaboration<00:02:00.640> i'm<00:02:00.799> going<00:02:00.880> to 00:02:01.030 --> 00:02:01.040 align:start position:0% resilience collaboration i'm going to 00:02:01.040 --> 00:02:03.590 align:start position:0% resilience collaboration i'm going to start<00:02:01.200> calling<00:02:01.520> the<00:02:01.680> stinson<00:02:02.320> arc 00:02:03.590 --> 00:02:03.600 align:start position:0% start calling the stinson arc 00:02:03.600 --> 00:02:06.830 align:start position:0% start calling the stinson arc the<00:02:03.920> the<00:02:04.320> overall<00:02:04.719> outcome<00:02:05.280> is<00:02:05.520> a<00:02:05.680> long-term 00:02:06.830 --> 00:02:06.840 align:start position:0% the the overall outcome is a long-term 00:02:06.840 --> 00:02:09.669 align:start position:0% the the overall outcome is a long-term implementable<00:02:07.920> adaptation<00:02:08.879> strategy 00:02:09.669 --> 00:02:09.679 align:start position:0% implementable adaptation strategy 00:02:09.679 --> 00:02:12.550 align:start position:0% implementable adaptation strategy roadmap<00:02:10.720> that<00:02:10.879> can<00:02:11.039> conserve<00:02:11.599> as<00:02:11.760> a<00:02:12.000> cohesive 00:02:12.550 --> 00:02:12.560 align:start position:0% roadmap that can conserve as a cohesive 00:02:12.560 --> 00:02:15.270 align:start position:0% roadmap that can conserve as a cohesive adaptation<00:02:13.200> framework<00:02:14.160> addressing<00:02:14.879> critical 00:02:15.270 --> 00:02:15.280 align:start position:0% adaptation framework addressing critical 00:02:15.280 --> 00:02:17.990 align:start position:0% adaptation framework addressing critical infrastructure<00:02:16.239> natural<00:02:16.640> resources<00:02:17.840> and 00:02:17.990 --> 00:02:18.000 align:start position:0% infrastructure natural resources and 00:02:18.000 --> 00:02:20.229 align:start position:0% infrastructure natural resources and community<00:02:18.560> assets<00:02:19.120> and<00:02:19.360> risks<00:02:20.000> in<00:02:20.080> the 00:02:20.229 --> 00:02:20.239 align:start position:0% community assets and risks in the 00:02:20.239 --> 00:02:22.949 align:start position:0% community assets and risks in the stinson<00:02:20.640> beach<00:02:20.959> area<00:02:21.920> we<00:02:22.080> really<00:02:22.319> want<00:02:22.480> to 00:02:22.949 --> 00:02:22.959 align:start position:0% stinson beach area we really want to 00:02:22.959 --> 00:02:25.030 align:start position:0% stinson beach area we really want to robustly<00:02:23.520> delineate<00:02:24.319> some<00:02:24.560> feasible 00:02:25.030 --> 00:02:25.040 align:start position:0% robustly delineate some feasible 00:02:25.040 --> 00:02:27.589 align:start position:0% robustly delineate some feasible adaptation<00:02:25.680> options<00:02:26.239> that<00:02:26.400> take<00:02:26.640> us<00:02:26.879> to 00:02:27.589 --> 00:02:27.599 align:start position:0% adaptation options that take us to 00:02:27.599 --> 00:02:29.830 align:start position:0% adaptation options that take us to mid-century<00:02:28.720> three<00:02:28.959> and<00:02:29.040> a<00:02:29.120> half<00:02:29.360> feet<00:02:29.520> of<00:02:29.599> sea 00:02:29.830 --> 00:02:29.840 align:start position:0% mid-century three and a half feet of sea 00:02:29.840 --> 00:02:31.350 align:start position:0% mid-century three and a half feet of sea level<00:02:30.160> rise<00:02:30.480> consistent<00:02:30.879> with<00:02:31.040> state 00:02:31.350 --> 00:02:31.360 align:start position:0% level rise consistent with state 00:02:31.360 --> 00:02:32.309 align:start position:0% level rise consistent with state guidance 00:02:32.309 --> 00:02:32.319 align:start position:0% guidance 00:02:32.319 --> 00:02:34.550 align:start position:0% guidance and<00:02:32.400> then<00:02:32.720> sufficiently<00:02:33.599> detail<00:02:34.080> from<00:02:34.239> there 00:02:34.550 --> 00:02:34.560 align:start position:0% and then sufficiently detail from there 00:02:34.560 --> 00:02:36.550 align:start position:0% and then sufficiently detail from there to<00:02:34.720> the<00:02:34.879> end<00:02:35.040> of<00:02:35.200> century<00:02:35.920> so<00:02:36.080> that<00:02:36.239> we<00:02:36.319> can 00:02:36.550 --> 00:02:36.560 align:start position:0% to the end of century so that we can 00:02:36.560 --> 00:02:37.990 align:start position:0% to the end of century so that we can support<00:02:36.879> the<00:02:37.040> development<00:02:37.680> of<00:02:37.760> some 00:02:37.990 --> 00:02:38.000 align:start position:0% support the development of some 00:02:38.000 --> 00:02:40.390 align:start position:0% support the development of some adaptation<00:02:38.959> pathways 00:02:40.390 --> 00:02:40.400 align:start position:0% adaptation pathways 00:02:40.400 --> 00:02:43.830 align:start position:0% adaptation pathways this<00:02:40.720> project<00:02:41.280> balances<00:02:42.160> numerous<00:02:42.720> goals 00:02:43.830 --> 00:02:43.840 align:start position:0% this project balances numerous goals 00:02:43.840 --> 00:02:45.670 align:start position:0% this project balances numerous goals and<00:02:44.000> i<00:02:44.080> just<00:02:44.239> want<00:02:44.400> to<00:02:44.560> know<00:02:44.879> key<00:02:45.120> among<00:02:45.440> those 00:02:45.670 --> 00:02:45.680 align:start position:0% and i just want to know key among those 00:02:45.680 --> 00:02:48.070 align:start position:0% and i just want to know key among those goals<00:02:46.080> we<00:02:46.239> are<00:02:46.640> actively<00:02:47.440> soliciting 00:02:48.070 --> 00:02:48.080 align:start position:0% goals we are actively soliciting 00:02:48.080 --> 00:02:50.869 align:start position:0% goals we are actively soliciting community<00:02:48.800> input<00:02:49.599> and<00:02:49.840> reflecting<00:02:50.400> diverse 00:02:50.869 --> 00:02:50.879 align:start position:0% community input and reflecting diverse 00:02:50.879 --> 00:02:53.509 align:start position:0% community input and reflecting diverse stakeholder<00:02:51.519> concerns<00:02:52.000> and<00:02:52.160> interests 00:02:53.509 --> 00:02:53.519 align:start position:0% stakeholder concerns and interests 00:02:53.519 --> 00:02:55.589 align:start position:0% stakeholder concerns and interests it's<00:02:53.760> a<00:02:53.840> goal<00:02:54.000> to<00:02:54.239> ensure<00:02:54.560> resilience<00:02:55.280> of<00:02:55.440> the 00:02:55.589 --> 00:02:55.599 align:start position:0% it's a goal to ensure resilience of the 00:02:55.599 --> 00:02:58.630 align:start position:0% it's a goal to ensure resilience of the beach<00:02:55.920> itself<00:02:56.640> and<00:02:56.959> equitable<00:02:57.599> public<00:02:58.000> access 00:02:58.630 --> 00:02:58.640 align:start position:0% beach itself and equitable public access 00:02:58.640 --> 00:03:00.869 align:start position:0% beach itself and equitable public access to<00:02:58.800> stinson's<00:02:59.280> coastal<00:02:59.680> resources<00:03:00.560> into<00:03:00.800> the 00:03:00.869 --> 00:03:00.879 align:start position:0% to stinson's coastal resources into the 00:03:00.879 --> 00:03:01.830 align:start position:0% to stinson's coastal resources into the future 00:03:01.830 --> 00:03:01.840 align:start position:0% future 00:03:01.840 --> 00:03:03.830 align:start position:0% future it<00:03:02.000> is<00:03:02.080> a<00:03:02.159> goal<00:03:02.400> to<00:03:02.560> position<00:03:02.959> stakeholders<00:03:03.599> to 00:03:03.830 --> 00:03:03.840 align:start position:0% it is a goal to position stakeholders to 00:03:03.840 --> 00:03:06.550 align:start position:0% it is a goal to position stakeholders to continue<00:03:04.640> engaging<00:03:05.599> with<00:03:05.840> adaptation 00:03:06.550 --> 00:03:06.560 align:start position:0% continue engaging with adaptation 00:03:06.560 --> 00:03:08.790 align:start position:0% continue engaging with adaptation efforts<00:03:06.879> in<00:03:07.040> stinson<00:03:07.440> beach<00:03:08.239> after<00:03:08.560> this 00:03:08.790 --> 00:03:08.800 align:start position:0% efforts in stinson beach after this 00:03:08.800 --> 00:03:10.949 align:start position:0% efforts in stinson beach after this planning<00:03:09.200> process<00:03:09.760> is<00:03:09.920> complete 00:03:10.949 --> 00:03:10.959 align:start position:0% planning process is complete 00:03:10.959 --> 00:03:12.470 align:start position:0% planning process is complete and<00:03:11.120> it's<00:03:11.280> a<00:03:11.360> goal<00:03:11.519> to<00:03:11.760> document<00:03:12.239> some 00:03:12.470 --> 00:03:12.480 align:start position:0% and it's a goal to document some 00:03:12.480 --> 00:03:14.470 align:start position:0% and it's a goal to document some actionable<00:03:13.040> lessons<00:03:13.440> learned<00:03:13.840> on<00:03:14.080> future 00:03:14.470 --> 00:03:14.480 align:start position:0% actionable lessons learned on future 00:03:14.480 --> 00:03:16.070 align:start position:0% actionable lessons learned on future adaptation<00:03:15.120> planning<00:03:15.599> but<00:03:15.840> we're<00:03:15.920> going<00:03:16.080> to 00:03:16.070 --> 00:03:16.080 align:start position:0% adaptation planning but we're going to 00:03:16.080 --> 00:03:19.190 align:start position:0% adaptation planning but we're going to be<00:03:16.239> doing<00:03:16.480> this<00:03:16.800> in<00:03:16.959> west<00:03:17.280> murray<00:03:17.599> and<00:03:17.760> beyond 00:03:19.190 --> 00:03:19.200 align:start position:0% be doing this in west murray and beyond 00:03:19.200 --> 00:03:22.070 align:start position:0% be doing this in west murray and beyond so<00:03:19.599> under<00:03:19.840> this<00:03:20.000> request<00:03:20.400> for<00:03:20.560> proposals 00:03:22.070 --> 00:03:22.080 align:start position:0% so under this request for proposals 00:03:22.080 --> 00:03:25.270 align:start position:0% so under this request for proposals cda<00:03:22.640> is<00:03:22.800> seeking<00:03:23.120> to<00:03:23.519> analyze<00:03:24.319> more<00:03:24.560> specific 00:03:25.270 --> 00:03:25.280 align:start position:0% cda is seeking to analyze more specific 00:03:25.280 --> 00:03:27.750 align:start position:0% cda is seeking to analyze more specific adaptation<00:03:26.000> strategies<00:03:26.799> and<00:03:26.959> place<00:03:27.280> them<00:03:27.599> in 00:03:27.750 --> 00:03:27.760 align:start position:0% adaptation strategies and place them in 00:03:27.760 --> 00:03:30.470 align:start position:0% adaptation strategies and place them in pathways<00:03:28.799> the<00:03:29.040> detail<00:03:29.440> the<00:03:29.599> near<00:03:29.920> and<00:03:30.000> medium 00:03:30.470 --> 00:03:30.480 align:start position:0% pathways the detail the near and medium 00:03:30.480 --> 00:03:32.789 align:start position:0% pathways the detail the near and medium term<00:03:30.799> adaptation<00:03:31.519> solutions<00:03:32.560> while 00:03:32.789 --> 00:03:32.799 align:start position:0% term adaptation solutions while 00:03:32.799 --> 00:03:35.350 align:start position:0% term adaptation solutions while identifying<00:03:33.840> sequencing<00:03:34.720> and<00:03:34.799> decision 00:03:35.350 --> 00:03:35.360 align:start position:0% identifying sequencing and decision 00:03:35.360 --> 00:03:38.390 align:start position:0% identifying sequencing and decision points<00:03:35.920> for<00:03:36.080> the<00:03:36.239> foreseeable<00:03:37.120> future 00:03:38.390 --> 00:03:38.400 align:start position:0% points for the foreseeable future 00:03:38.400 --> 00:03:40.470 align:start position:0% points for the foreseeable future potential<00:03:38.959> strategies<00:03:39.599> may<00:03:39.840> include 00:03:40.470 --> 00:03:40.480 align:start position:0% potential strategies may include 00:03:40.480 --> 00:03:42.149 align:start position:0% potential strategies may include nature-based<00:03:41.120> options 00:03:42.149 --> 00:03:42.159 align:start position:0% nature-based options 00:03:42.159 --> 00:03:45.030 align:start position:0% nature-based options structural<00:03:42.799> adaptations<00:03:44.239> and<00:03:44.480> long-term 00:03:45.030 --> 00:03:45.040 align:start position:0% structural adaptations and long-term 00:03:45.040 --> 00:03:47.589 align:start position:0% structural adaptations and long-term realignment<00:03:46.159> of<00:03:46.640> infrastructure<00:03:47.440> and 00:03:47.589 --> 00:03:47.599 align:start position:0% realignment of infrastructure and 00:03:47.599 --> 00:03:49.670 align:start position:0% realignment of infrastructure and structures<00:03:48.640> they<00:03:48.879> also<00:03:49.120> really<00:03:49.360> need<00:03:49.519> to 00:03:49.670 --> 00:03:49.680 align:start position:0% structures they also really need to 00:03:49.680 --> 00:03:52.309 align:start position:0% structures they also really need to develop<00:03:50.080> and<00:03:50.159> apply<00:03:50.720> evaluation<00:03:51.360> criteria 00:03:52.309 --> 00:03:52.319 align:start position:0% develop and apply evaluation criteria 00:03:52.319 --> 00:03:54.149 align:start position:0% develop and apply evaluation criteria that<00:03:52.560> assess<00:03:52.879> feasibility 00:03:54.149 --> 00:03:54.159 align:start position:0% that assess feasibility 00:03:54.159 --> 00:03:57.429 align:start position:0% that assess feasibility technical<00:03:54.720> efficacy<00:03:55.760> environmental<00:03:56.560> impact 00:03:57.429 --> 00:03:57.439 align:start position:0% technical efficacy environmental impact 00:03:57.439 --> 00:04:00.149 align:start position:0% technical efficacy environmental impact social<00:03:57.840> equity<00:03:58.720> and<00:03:58.959> economic<00:03:59.519> factors<00:03:59.920> both 00:04:00.149 --> 00:04:00.159 align:start position:0% social equity and economic factors both 00:04:00.159 --> 00:04:02.470 align:start position:0% social equity and economic factors both for<00:04:00.319> the<00:04:00.400> individual<00:04:00.959> adaptation<00:04:01.599> strategies 00:04:02.470 --> 00:04:02.480 align:start position:0% for the individual adaptation strategies 00:04:02.480 --> 00:04:05.670 align:start position:0% for the individual adaptation strategies and<00:04:02.799> those<00:04:03.040> adaptation<00:04:04.080> pathways 00:04:05.670 --> 00:04:05.680 align:start position:0% and those adaptation pathways 00:04:05.680 --> 00:04:08.309 align:start position:0% and those adaptation pathways i<00:04:05.840> promise<00:04:06.159> that<00:04:06.239> was<00:04:06.400> my<00:04:06.640> longest<00:04:07.200> slide 00:04:08.309 --> 00:04:08.319 align:start position:0% i promise that was my longest slide 00:04:08.319 --> 00:04:10.869 align:start position:0% i promise that was my longest slide so<00:04:08.480> the<00:04:08.640> adaptation<00:04:09.200> planning<00:04:09.599> process 00:04:10.869 --> 00:04:10.879 align:start position:0% so the adaptation planning process 00:04:10.879 --> 00:04:13.110 align:start position:0% so the adaptation planning process you<00:04:11.040> know<00:04:11.120> it<00:04:11.280> must<00:04:11.680> focus<00:04:12.159> around<00:04:12.560> community 00:04:13.110 --> 00:04:13.120 align:start position:0% you know it must focus around community 00:04:13.120 --> 00:04:15.670 align:start position:0% you know it must focus around community concerns<00:04:13.840> as<00:04:13.920> well<00:04:14.159> as<00:04:14.319> community<00:04:14.879> values<00:04:15.519> and 00:04:15.670 --> 00:04:15.680 align:start position:0% concerns as well as community values and 00:04:15.680 --> 00:04:17.430 align:start position:0% concerns as well as community values and visions<00:04:16.160> for<00:04:16.320> what<00:04:16.479> a<00:04:16.560> resilient<00:04:17.040> future 00:04:17.430 --> 00:04:17.440 align:start position:0% visions for what a resilient future 00:04:17.440 --> 00:04:18.390 align:start position:0% visions for what a resilient future looks<00:04:17.680> like 00:04:18.390 --> 00:04:18.400 align:start position:0% looks like 00:04:18.400 --> 00:04:21.030 align:start position:0% looks like but<00:04:18.560> when<00:04:18.720> we<00:04:18.880> talk<00:04:19.120> about<00:04:19.600> the<00:04:19.840> community 00:04:21.030 --> 00:04:21.040 align:start position:0% but when we talk about the community 00:04:21.040 --> 00:04:23.030 align:start position:0% but when we talk about the community it's<00:04:21.280> really<00:04:21.600> broad<00:04:21.919> this<00:04:22.160> includes<00:04:22.560> stinson 00:04:23.030 --> 00:04:23.040 align:start position:0% it's really broad this includes stinson 00:04:23.040 --> 00:04:24.950 align:start position:0% it's really broad this includes stinson residents<00:04:23.600> and<00:04:23.680> landowners 00:04:24.950 --> 00:04:24.960 align:start position:0% residents and landowners 00:04:24.960 --> 00:04:26.629 align:start position:0% residents and landowners local<00:04:25.280> businesses 00:04:26.629 --> 00:04:26.639 align:start position:0% local businesses 00:04:26.639 --> 00:04:28.950 align:start position:0% local businesses historically<00:04:27.360> excluded<00:04:28.240> and<00:04:28.400> underserved 00:04:28.950 --> 00:04:28.960 align:start position:0% historically excluded and underserved 00:04:28.960 --> 00:04:30.550 align:start position:0% historically excluded and underserved community<00:04:29.360> members 00:04:30.550 --> 00:04:30.560 align:start position:0% community members 00:04:30.560 --> 00:04:32.469 align:start position:0% community members others<00:04:30.880> in<00:04:30.960> marin<00:04:31.360> and<00:04:31.440> beyond<00:04:31.759> she<00:04:31.919> recreated 00:04:32.469 --> 00:04:32.479 align:start position:0% others in marin and beyond she recreated 00:04:32.479 --> 00:04:35.510 align:start position:0% others in marin and beyond she recreated stinson<00:04:33.280> non-governmental<00:04:34.080> organizations 00:04:35.510 --> 00:04:35.520 align:start position:0% stinson non-governmental organizations 00:04:35.520 --> 00:04:37.749 align:start position:0% stinson non-governmental organizations and<00:04:35.680> other<00:04:35.919> interested<00:04:36.400> parties 00:04:37.749 --> 00:04:37.759 align:start position:0% and other interested parties 00:04:37.759 --> 00:04:39.430 align:start position:0% and other interested parties and<00:04:37.919> i<00:04:38.000> put<00:04:38.240> this<00:04:38.400> slide<00:04:38.800> up 00:04:39.430 --> 00:04:39.440 align:start position:0% and i put this slide up 00:04:39.440 --> 00:04:41.510 align:start position:0% and i put this slide up to<00:04:39.680> show<00:04:39.840> that<00:04:40.240> sustained<00:04:40.960> engagement<00:04:41.440> of 00:04:41.510 --> 00:04:41.520 align:start position:0% to show that sustained engagement of 00:04:41.520 --> 00:04:44.310 align:start position:0% to show that sustained engagement of that<00:04:41.759> diverse<00:04:42.400> community<00:04:43.040> of<00:04:43.199> stakeholders 00:04:44.310 --> 00:04:44.320 align:start position:0% that diverse community of stakeholders 00:04:44.320 --> 00:04:47.110 align:start position:0% that diverse community of stakeholders is<00:04:44.479> going<00:04:44.639> to<00:04:44.720> require<00:04:45.199> much<00:04:45.680> more<00:04:46.400> than<00:04:46.720> just 00:04:47.110 --> 00:04:47.120 align:start position:0% is going to require much more than just 00:04:47.120 --> 00:04:49.030 align:start position:0% is going to require much more than just the<00:04:47.280> six<00:04:47.520> public<00:04:47.840> meetings<00:04:48.400> called<00:04:48.720> out<00:04:48.800> in 00:04:49.030 --> 00:04:49.040 align:start position:0% the six public meetings called out in 00:04:49.040 --> 00:04:51.110 align:start position:0% the six public meetings called out in task<00:04:49.360> two<00:04:49.600> of<00:04:49.680> the<00:04:49.759> rfp<00:04:50.639> so<00:04:50.800> while<00:04:50.960> the 00:04:51.110 --> 00:04:51.120 align:start position:0% task two of the rfp so while the 00:04:51.120 --> 00:04:52.550 align:start position:0% task two of the rfp so while the consultants<00:04:51.759> and<00:04:51.840> what<00:04:51.919> we're<00:04:52.080> talking<00:04:52.400> about 00:04:52.550 --> 00:04:52.560 align:start position:0% consultants and what we're talking about 00:04:52.560 --> 00:04:54.710 align:start position:0% consultants and what we're talking about today<00:04:52.880> with<00:04:53.040> this<00:04:53.280> rfp<00:04:54.080> they're<00:04:54.240> gonna<00:04:54.400> play<00:04:54.639> a 00:04:54.710 --> 00:04:54.720 align:start position:0% today with this rfp they're gonna play a 00:04:54.720 --> 00:04:56.870 align:start position:0% today with this rfp they're gonna play a critical<00:04:55.120> role<00:04:55.759> in<00:04:55.919> delivering<00:04:56.560> public 00:04:56.870 --> 00:04:56.880 align:start position:0% critical role in delivering public 00:04:56.880 --> 00:04:58.790 align:start position:0% critical role in delivering public meetings<00:04:57.759> i'm<00:04:57.919> showing<00:04:58.240> here<00:04:58.400> in<00:04:58.479> one<00:04:58.639> of<00:04:58.720> the 00:04:58.790 --> 00:04:58.800 align:start position:0% meetings i'm showing here in one of the 00:04:58.800 --> 00:05:01.029 align:start position:0% meetings i'm showing here in one of the boxes<00:04:59.280> i<00:04:59.520> want<00:04:59.680> folks<00:04:59.919> to<00:05:00.080> be<00:05:00.160> aware<00:05:00.880> that 00:05:01.029 --> 00:05:01.039 align:start position:0% boxes i want folks to be aware that 00:05:01.039 --> 00:05:03.189 align:start position:0% boxes i want folks to be aware that there<00:05:01.199> are<00:05:01.360> other<00:05:01.600> components<00:05:02.400> that<00:05:02.639> actively 00:05:03.189 --> 00:05:03.199 align:start position:0% there are other components that actively 00:05:03.199 --> 00:05:05.510 align:start position:0% there are other components that actively invite<00:05:03.600> substantive<00:05:04.240> community<00:05:04.800> input<00:05:05.280> into 00:05:05.510 --> 00:05:05.520 align:start position:0% invite substantive community input into 00:05:05.520 --> 00:05:08.070 align:start position:0% invite substantive community input into the<00:05:05.600> adaptation<00:05:06.320> planning<00:05:06.800> process 00:05:08.070 --> 00:05:08.080 align:start position:0% the adaptation planning process 00:05:08.080 --> 00:05:10.310 align:start position:0% the adaptation planning process so<00:05:08.320> it's<00:05:08.479> cda's<00:05:08.880> goal<00:05:09.120> to<00:05:09.280> empower<00:05:09.759> community 00:05:10.310 --> 00:05:10.320 align:start position:0% so it's cda's goal to empower community 00:05:10.320 --> 00:05:12.629 align:start position:0% so it's cda's goal to empower community to<00:05:10.560> understand<00:05:11.120> the<00:05:11.280> possibilities<00:05:12.479> and 00:05:12.629 --> 00:05:12.639 align:start position:0% to understand the possibilities and 00:05:12.639 --> 00:05:14.390 align:start position:0% to understand the possibilities and limitations<00:05:13.360> of<00:05:13.440> different<00:05:13.759> adaptation 00:05:14.390 --> 00:05:14.400 align:start position:0% limitations of different adaptation 00:05:14.400 --> 00:05:16.550 align:start position:0% limitations of different adaptation strategies<00:05:15.120> and<00:05:15.199> to<00:05:15.440> document<00:05:16.080> potential 00:05:16.550 --> 00:05:16.560 align:start position:0% strategies and to document potential 00:05:16.560 --> 00:05:18.310 align:start position:0% strategies and to document potential pros<00:05:17.120> and<00:05:17.280> cons 00:05:18.310 --> 00:05:18.320 align:start position:0% pros and cons 00:05:18.320 --> 00:05:19.990 align:start position:0% pros and cons and<00:05:18.479> different<00:05:18.800> stakeholder<00:05:19.440> interests<00:05:19.919> and 00:05:19.990 --> 00:05:20.000 align:start position:0% and different stakeholder interests and 00:05:20.000 --> 00:05:23.749 align:start position:0% and different stakeholder interests and concerns<00:05:20.880> across<00:05:21.600> adaptation<00:05:22.240> options 00:05:23.749 --> 00:05:23.759 align:start position:0% concerns across adaptation options 00:05:23.759 --> 00:05:26.629 align:start position:0% concerns across adaptation options so<00:05:24.000> to<00:05:24.160> the<00:05:24.320> study<00:05:24.800> area<00:05:25.280> of<00:05:25.360> this<00:05:25.680> process 00:05:26.629 --> 00:05:26.639 align:start position:0% so to the study area of this process 00:05:26.639 --> 00:05:29.590 align:start position:0% so to the study area of this process there<00:05:26.880> are<00:05:27.120> no<00:05:27.800> prescribed<00:05:29.120> spatial 00:05:29.590 --> 00:05:29.600 align:start position:0% there are no prescribed spatial 00:05:29.600 --> 00:05:31.590 align:start position:0% there are no prescribed spatial boundaries<00:05:30.160> to<00:05:30.320> the<00:05:30.479> stinson<00:05:30.880> beach<00:05:31.199> arc 00:05:31.590 --> 00:05:31.600 align:start position:0% boundaries to the stinson beach arc 00:05:31.600 --> 00:05:33.189 align:start position:0% boundaries to the stinson beach arc planning<00:05:32.080> process 00:05:33.189 --> 00:05:33.199 align:start position:0% planning process 00:05:33.199 --> 00:05:35.990 align:start position:0% planning process this<00:05:33.520> map<00:05:34.160> is<00:05:34.400> to<00:05:34.560> provide<00:05:34.880> some<00:05:35.120> context<00:05:35.840> the 00:05:35.990 --> 00:05:36.000 align:start position:0% this map is to provide some context the 00:05:36.000 --> 00:05:37.749 align:start position:0% this map is to provide some context the purple<00:05:36.479> outline 00:05:37.749 --> 00:05:37.759 align:start position:0% purple outline 00:05:37.759 --> 00:05:39.990 align:start position:0% purple outline shows<00:05:38.000> the<00:05:38.240> studies<00:05:38.880> you<00:05:38.960> know<00:05:39.120> real<00:05:39.440> focus 00:05:39.990 --> 00:05:40.000 align:start position:0% shows the studies you know real focus 00:05:40.000 --> 00:05:42.070 align:start position:0% shows the studies you know real focus around<00:05:40.320> the<00:05:40.400> community<00:05:41.039> of<00:05:41.120> stinson<00:05:41.600> beach 00:05:42.070 --> 00:05:42.080 align:start position:0% around the community of stinson beach 00:05:42.080 --> 00:05:44.310 align:start position:0% around the community of stinson beach the<00:05:42.240> developed<00:05:42.800> areas<00:05:43.280> the<00:05:43.440> sand<00:05:43.919> spit 00:05:44.310 --> 00:05:44.320 align:start position:0% the developed areas the sand spit 00:05:44.320 --> 00:05:45.590 align:start position:0% the developed areas the sand spit development 00:05:45.590 --> 00:05:45.600 align:start position:0% development 00:05:45.600 --> 00:05:46.390 align:start position:0% development that 00:05:46.390 --> 00:05:46.400 align:start position:0% that 00:05:46.400 --> 00:05:49.270 align:start position:0% that blue<00:05:46.960> outline<00:05:47.759> delineates<00:05:48.400> a<00:05:48.639> broader 00:05:49.270 --> 00:05:49.280 align:start position:0% blue outline delineates a broader 00:05:49.280 --> 00:05:50.710 align:start position:0% blue outline delineates a broader planning<00:05:49.759> area 00:05:50.710 --> 00:05:50.720 align:start position:0% planning area 00:05:50.720 --> 00:05:52.310 align:start position:0% planning area because<00:05:51.039> we're<00:05:51.440> considering<00:05:52.000> the<00:05:52.080> whole 00:05:52.310 --> 00:05:52.320 align:start position:0% because we're considering the whole 00:05:52.320 --> 00:05:54.950 align:start position:0% because we're considering the whole ecological<00:05:53.120> context<00:05:53.680> of<00:05:53.759> the<00:05:53.840> linus<00:05:54.160> lagoon 00:05:54.950 --> 00:05:54.960 align:start position:0% ecological context of the linus lagoon 00:05:54.960 --> 00:05:56.790 align:start position:0% ecological context of the linus lagoon the<00:05:55.120> upslope<00:05:55.600> watersheds<00:05:56.319> that<00:05:56.400> affect<00:05:56.720> the 00:05:56.790 --> 00:05:56.800 align:start position:0% the upslope watersheds that affect the 00:05:56.800 --> 00:05:58.710 align:start position:0% the upslope watersheds that affect the planning<00:05:57.280> area<00:05:57.600> and<00:05:57.680> those<00:05:58.160> boundaries 00:05:58.710 --> 00:05:58.720 align:start position:0% planning area and those boundaries 00:05:58.720 --> 00:06:00.550 align:start position:0% planning area and those boundaries include<00:05:59.120> all<00:05:59.360> the<00:05:59.440> way<00:05:59.680> up<00:05:59.759> to<00:05:59.919> the<00:06:00.000> bolinas 00:06:00.550 --> 00:06:00.560 align:start position:0% include all the way up to the bolinas 00:06:00.560 --> 00:06:03.029 align:start position:0% include all the way up to the bolinas ridge<00:06:01.280> we've<00:06:01.520> also<00:06:01.840> included<00:06:02.400> highway<00:06:02.800> one 00:06:03.029 --> 00:06:03.039 align:start position:0% ridge we've also included highway one 00:06:03.039 --> 00:06:04.390 align:start position:0% ridge we've also included highway one the<00:06:03.199> shoreline<00:06:03.680> highway<00:06:04.000> which<00:06:04.240> is<00:06:04.319> a 00:06:04.390 --> 00:06:04.400 align:start position:0% the shoreline highway which is a 00:06:04.400 --> 00:06:06.870 align:start position:0% the shoreline highway which is a critical<00:06:04.800> route<00:06:05.199> in<00:06:05.360> and<00:06:05.520> out<00:06:05.680> of<00:06:05.759> stinson 00:06:06.870 --> 00:06:06.880 align:start position:0% critical route in and out of stinson 00:06:06.880 --> 00:06:08.629 align:start position:0% critical route in and out of stinson there's<00:06:07.120> a<00:06:07.199> really<00:06:07.440> broad<00:06:07.840> planning<00:06:08.240> area<00:06:08.560> to 00:06:08.629 --> 00:06:08.639 align:start position:0% there's a really broad planning area to 00:06:08.639 --> 00:06:10.550 align:start position:0% there's a really broad planning area to consider<00:06:09.120> here<00:06:09.360> and<00:06:09.440> may<00:06:09.680> require 00:06:10.550 --> 00:06:10.560 align:start position:0% consider here and may require 00:06:10.560 --> 00:06:13.029 align:start position:0% consider here and may require integration<00:06:11.280> at<00:06:11.360> different<00:06:11.759> levels<00:06:12.400> during 00:06:13.029 --> 00:06:13.039 align:start position:0% integration at different levels during 00:06:13.039 --> 00:06:14.870 align:start position:0% integration at different levels during the<00:06:13.280> adaptation<00:06:13.840> planning<00:06:14.240> and<00:06:14.400> engineering 00:06:14.870 --> 00:06:14.880 align:start position:0% the adaptation planning and engineering 00:06:14.880 --> 00:06:16.870 align:start position:0% the adaptation planning and engineering process 00:06:16.870 --> 00:06:16.880 align:start position:0% process 00:06:16.880 --> 00:06:19.029 align:start position:0% process also<00:06:17.199> to<00:06:17.360> note<00:06:17.759> planning<00:06:18.240> activities<00:06:18.960> in 00:06:19.029 --> 00:06:19.039 align:start position:0% also to note planning activities in 00:06:19.039 --> 00:06:21.749 align:start position:0% also to note planning activities in stinson<00:06:19.520> beach<00:06:19.759> are<00:06:20.000> really<00:06:20.560> layered<00:06:21.360> so<00:06:21.520> this 00:06:21.749 --> 00:06:21.759 align:start position:0% stinson beach are really layered so this 00:06:21.759 --> 00:06:23.670 align:start position:0% stinson beach are really layered so this large<00:06:22.080> blue<00:06:22.319> circle<00:06:22.960> shows<00:06:23.199> the<00:06:23.280> different 00:06:23.670 --> 00:06:23.680 align:start position:0% large blue circle shows the different 00:06:23.680 --> 00:06:25.350 align:start position:0% large blue circle shows the different county<00:06:24.080> planning<00:06:24.560> efforts<00:06:25.039> that<00:06:25.199> are 00:06:25.350 --> 00:06:25.360 align:start position:0% county planning efforts that are 00:06:25.360 --> 00:06:26.469 align:start position:0% county planning efforts that are underway 00:06:26.469 --> 00:06:26.479 align:start position:0% underway 00:06:26.479 --> 00:06:28.790 align:start position:0% underway and<00:06:26.639> how<00:06:26.800> the<00:06:26.960> stinson<00:06:27.360> beach<00:06:27.680> arc<00:06:28.240> relates 00:06:28.790 --> 00:06:28.800 align:start position:0% and how the stinson beach arc relates 00:06:28.800 --> 00:06:30.550 align:start position:0% and how the stinson beach arc relates closely<00:06:29.199> to<00:06:29.360> these<00:06:29.600> and<00:06:29.759> quite<00:06:30.000> closely<00:06:30.319> to 00:06:30.550 --> 00:06:30.560 align:start position:0% closely to these and quite closely to 00:06:30.560 --> 00:06:33.270 align:start position:0% closely to these and quite closely to issues<00:06:30.880> under<00:06:31.120> the<00:06:31.199> local<00:06:31.600> coastal<00:06:32.080> plan 00:06:33.270 --> 00:06:33.280 align:start position:0% issues under the local coastal plan 00:06:33.280 --> 00:06:34.550 align:start position:0% issues under the local coastal plan all<00:06:33.360> these<00:06:33.600> different<00:06:33.840> county<00:06:34.160> planning 00:06:34.550 --> 00:06:34.560 align:start position:0% all these different county planning 00:06:34.560 --> 00:06:37.029 align:start position:0% all these different county planning efforts<00:06:34.960> that<00:06:35.039> are<00:06:35.199> mentioned<00:06:35.680> in<00:06:35.759> the<00:06:35.919> rfp 00:06:37.029 --> 00:06:37.039 align:start position:0% efforts that are mentioned in the rfp 00:06:37.039 --> 00:06:39.909 align:start position:0% efforts that are mentioned in the rfp are<00:06:37.280> going<00:06:37.520> to<00:06:37.759> inform<00:06:38.400> and<00:06:38.639> be<00:06:38.960> part<00:06:39.280> of<00:06:39.759> what 00:06:39.909 --> 00:06:39.919 align:start position:0% are going to inform and be part of what 00:06:39.919 --> 00:06:41.749 align:start position:0% are going to inform and be part of what gets<00:06:40.240> integrated<00:06:40.800> and<00:06:40.960> carried<00:06:41.440> through<00:06:41.680> the 00:06:41.749 --> 00:06:41.759 align:start position:0% gets integrated and carried through the 00:06:41.759 --> 00:06:44.390 align:start position:0% gets integrated and carried through the stinson<00:06:42.160> beach<00:06:42.479> arc<00:06:42.800> process 00:06:44.390 --> 00:06:44.400 align:start position:0% stinson beach arc process 00:06:44.400 --> 00:06:45.749 align:start position:0% stinson beach arc process on<00:06:44.479> top<00:06:44.720> of<00:06:44.800> that 00:06:45.749 --> 00:06:45.759 align:start position:0% on top of that 00:06:45.759 --> 00:06:47.510 align:start position:0% on top of that we've<00:06:45.919> got<00:06:46.160> county<00:06:46.479> planning<00:06:46.960> and<00:06:47.039> policy 00:06:47.510 --> 00:06:47.520 align:start position:0% we've got county planning and policy 00:06:47.520 --> 00:06:50.469 align:start position:0% we've got county planning and policy efforts<00:06:48.000> there's<00:06:48.400> also<00:06:49.120> numerous<00:06:49.759> adaptation 00:06:50.469 --> 00:06:50.479 align:start position:0% efforts there's also numerous adaptation 00:06:50.479 --> 00:06:52.390 align:start position:0% efforts there's also numerous adaptation planning<00:06:50.880> projects<00:06:51.360> and<00:06:51.520> strategies<00:06:52.160> that 00:06:52.390 --> 00:06:52.400 align:start position:0% planning projects and strategies that 00:06:52.400 --> 00:06:54.870 align:start position:0% planning projects and strategies that are<00:06:52.479> in<00:06:52.639> various<00:06:53.039> stages<00:06:53.520> of<00:06:53.599> development<00:06:54.560> for 00:06:54.870 --> 00:06:54.880 align:start position:0% are in various stages of development for 00:06:54.880 --> 00:06:56.629 align:start position:0% are in various stages of development for assets<00:06:55.280> within<00:06:55.599> stinson 00:06:56.629 --> 00:06:56.639 align:start position:0% assets within stinson 00:06:56.639 --> 00:06:58.629 align:start position:0% assets within stinson and<00:06:57.120> key<00:06:57.440> ones<00:06:57.759> i've<00:06:57.919> shown<00:06:58.160> here<00:06:58.319> in<00:06:58.400> these 00:06:58.629 --> 00:06:58.639 align:start position:0% and key ones i've shown here in these 00:06:58.639 --> 00:07:00.950 align:start position:0% and key ones i've shown here in these green<00:06:59.039> ovals<00:06:59.599> they're<00:06:59.919> led<00:07:00.160> by<00:07:00.319> numerous 00:07:00.950 --> 00:07:00.960 align:start position:0% green ovals they're led by numerous 00:07:00.960 --> 00:07:02.550 align:start position:0% green ovals they're led by numerous federal<00:07:01.599> state 00:07:02.550 --> 00:07:02.560 align:start position:0% federal state 00:07:02.560 --> 00:07:05.110 align:start position:0% federal state local<00:07:02.880> landowners<00:07:03.599> and<00:07:03.759> asset<00:07:04.160> managers<00:07:04.960> in 00:07:05.110 --> 00:07:05.120 align:start position:0% local landowners and asset managers in 00:07:05.120 --> 00:07:07.830 align:start position:0% local landowners and asset managers in the<00:07:05.199> stinson<00:07:05.680> beach<00:07:05.919> ballinas<00:07:06.400> lagoon<00:07:06.880> area 00:07:07.830 --> 00:07:07.840 align:start position:0% the stinson beach ballinas lagoon area 00:07:07.840 --> 00:07:10.790 align:start position:0% the stinson beach ballinas lagoon area so<00:07:08.080> cda<00:07:08.720> our<00:07:08.960> agency<00:07:09.440> has<00:07:09.680> done<00:07:10.080> significant 00:07:10.790 --> 00:07:10.800 align:start position:0% so cda our agency has done significant 00:07:10.800 --> 00:07:12.710 align:start position:0% so cda our agency has done significant work<00:07:11.199> developing<00:07:11.680> relationships<00:07:12.400> with<00:07:12.560> these 00:07:12.710 --> 00:07:12.720 align:start position:0% work developing relationships with these 00:07:12.720 --> 00:07:15.670 align:start position:0% work developing relationships with these asset<00:07:13.039> managers<00:07:14.000> and<00:07:14.160> compiling<00:07:15.039> data<00:07:15.520> and 00:07:15.670 --> 00:07:15.680 align:start position:0% asset managers and compiling data and 00:07:15.680 --> 00:07:18.550 align:start position:0% asset managers and compiling data and resources<00:07:16.400> on<00:07:16.479> their<00:07:16.720> efforts<00:07:17.199> to<00:07:17.440> date<00:07:18.240> and 00:07:18.550 --> 00:07:18.560 align:start position:0% resources on their efforts to date and 00:07:18.560 --> 00:07:20.230 align:start position:0% resources on their efforts to date and as<00:07:18.720> a<00:07:18.800> project<00:07:19.120> manager<00:07:19.599> i'll<00:07:19.759> be<00:07:19.840> working 00:07:20.230 --> 00:07:20.240 align:start position:0% as a project manager i'll be working 00:07:20.240 --> 00:07:22.390 align:start position:0% as a project manager i'll be working very<00:07:20.560> closely<00:07:20.960> with<00:07:21.120> the<00:07:21.280> selected<00:07:21.759> firm<00:07:22.160> to 00:07:22.390 --> 00:07:22.400 align:start position:0% very closely with the selected firm to 00:07:22.400 --> 00:07:25.430 align:start position:0% very closely with the selected firm to integrate<00:07:23.280> this<00:07:23.520> complicated<00:07:24.240> context<00:07:25.120> into 00:07:25.430 --> 00:07:25.440 align:start position:0% integrate this complicated context into 00:07:25.440 --> 00:07:27.830 align:start position:0% integrate this complicated context into the<00:07:25.520> bullying<00:07:26.000> the<00:07:26.240> stinson<00:07:26.639> beach<00:07:26.960> arc<00:07:27.199> press 00:07:27.830 --> 00:07:27.840 align:start position:0% the bullying the stinson beach arc press 00:07:27.840 --> 00:07:30.309 align:start position:0% the bullying the stinson beach arc press project<00:07:28.639> and<00:07:28.800> that's<00:07:29.039> what's<00:07:29.280> noted<00:07:29.759> in<00:07:29.840> task 00:07:30.309 --> 00:07:30.319 align:start position:0% project and that's what's noted in task 00:07:30.319 --> 00:07:34.070 align:start position:0% project and that's what's noted in task 1.2<00:07:31.280> of<00:07:31.360> the<00:07:31.520> rf 00:07:34.070 --> 00:07:34.080 align:start position:0% 00:07:34.080 --> 00:07:36.550 align:start position:0% this<00:07:34.319> is<00:07:34.400> a<00:07:34.560> graphic<00:07:35.039> about<00:07:35.360> our<00:07:35.599> project<00:07:36.240> team 00:07:36.550 --> 00:07:36.560 align:start position:0% this is a graphic about our project team 00:07:36.560 --> 00:07:37.670 align:start position:0% this is a graphic about our project team structure 00:07:37.670 --> 00:07:37.680 align:start position:0% structure 00:07:37.680 --> 00:07:39.990 align:start position:0% structure i<00:07:37.919> recognize<00:07:38.479> it's<00:07:38.800> pretty<00:07:39.199> different<00:07:39.759> than 00:07:39.990 --> 00:07:40.000 align:start position:0% i recognize it's pretty different than 00:07:40.000 --> 00:07:41.510 align:start position:0% i recognize it's pretty different than the<00:07:40.080> usual<00:07:40.560> approach<00:07:40.880> where<00:07:41.039> we'd<00:07:41.199> have<00:07:41.440> a 00:07:41.510 --> 00:07:41.520 align:start position:0% the usual approach where we'd have a 00:07:41.520 --> 00:07:44.390 align:start position:0% the usual approach where we'd have a consultant<00:07:42.319> leading<00:07:42.639> a<00:07:42.800> team<00:07:43.120> of<00:07:43.360> subs 00:07:44.390 --> 00:07:44.400 align:start position:0% consultant leading a team of subs 00:07:44.400 --> 00:07:46.550 align:start position:0% consultant leading a team of subs this<00:07:44.639> did<00:07:44.800> evolve<00:07:45.280> because<00:07:45.840> as<00:07:46.080> i<00:07:46.160> showed<00:07:46.479> in 00:07:46.550 --> 00:07:46.560 align:start position:0% this did evolve because as i showed in 00:07:46.560 --> 00:07:49.110 align:start position:0% this did evolve because as i showed in our<00:07:46.720> community<00:07:47.199> engagement<00:07:47.680> graphic<00:07:48.639> we<00:07:48.800> have 00:07:49.110 --> 00:07:49.120 align:start position:0% our community engagement graphic we have 00:07:49.120 --> 00:07:51.670 align:start position:0% our community engagement graphic we have many<00:07:49.759> sort<00:07:50.000> of<00:07:50.160> active<00:07:50.639> fronts<00:07:51.120> needed<00:07:51.520> to 00:07:51.670 --> 00:07:51.680 align:start position:0% many sort of active fronts needed to 00:07:51.680 --> 00:07:54.070 align:start position:0% many sort of active fronts needed to carry<00:07:52.000> this<00:07:52.240> process<00:07:52.800> and<00:07:53.039> some<00:07:53.280> pieces<00:07:53.840> such 00:07:54.070 --> 00:07:54.080 align:start position:0% carry this process and some pieces such 00:07:54.080 --> 00:07:54.790 align:start position:0% carry this process and some pieces such as 00:07:54.790 --> 00:07:54.800 align:start position:0% as 00:07:54.800 --> 00:07:57.510 align:start position:0% as some<00:07:55.360> visitation<00:07:56.160> studies<00:07:56.720> and<00:07:56.960> process 00:07:57.510 --> 00:07:57.520 align:start position:0% some visitation studies and process 00:07:57.520 --> 00:07:58.550 align:start position:0% some visitation studies and process design 00:07:58.550 --> 00:07:58.560 align:start position:0% design 00:07:58.560 --> 00:08:00.469 align:start position:0% design needed<00:07:58.800> to<00:07:58.960> happen<00:07:59.360> on<00:07:59.520> the<00:07:59.680> earlier<00:08:00.160> end 00:08:00.469 --> 00:08:00.479 align:start position:0% needed to happen on the earlier end 00:08:00.479 --> 00:08:01.909 align:start position:0% needed to happen on the earlier end before<00:08:00.720> we<00:08:00.879> got<00:08:01.120> this 00:08:01.909 --> 00:08:01.919 align:start position:0% before we got this 00:08:01.919 --> 00:08:03.430 align:start position:0% before we got this core<00:08:02.400> adaptation<00:08:02.960> planning<00:08:03.360> and 00:08:03.430 --> 00:08:03.440 align:start position:0% core adaptation planning and 00:08:03.440 --> 00:08:05.270 align:start position:0% core adaptation planning and environmental<00:08:04.080> engineering<00:08:04.720> component 00:08:05.270 --> 00:08:05.280 align:start position:0% environmental engineering component 00:08:05.280 --> 00:08:06.390 align:start position:0% environmental engineering component underway 00:08:06.390 --> 00:08:06.400 align:start position:0% underway 00:08:06.400 --> 00:08:08.070 align:start position:0% underway so<00:08:06.800> as<00:08:07.039> the<00:08:07.120> project<00:08:07.440> manager<00:08:07.759> for<00:08:07.919> the 00:08:08.070 --> 00:08:08.080 align:start position:0% so as the project manager for the 00:08:08.080 --> 00:08:10.070 align:start position:0% so as the project manager for the students<00:08:08.319> and<00:08:08.479> arc<00:08:08.720> i<00:08:08.800> will<00:08:09.039> schedule<00:08:09.680> host 00:08:10.070 --> 00:08:10.080 align:start position:0% students and arc i will schedule host 00:08:10.080 --> 00:08:11.909 align:start position:0% students and arc i will schedule host and<00:08:10.160> facilitate<00:08:10.879> monthly<00:08:11.280> project<00:08:11.680> team 00:08:11.909 --> 00:08:11.919 align:start position:0% and facilitate monthly project team 00:08:11.919 --> 00:08:13.990 align:start position:0% and facilitate monthly project team meetings<00:08:12.319> with<00:08:12.479> all<00:08:12.720> consultants 00:08:13.990 --> 00:08:14.000 align:start position:0% meetings with all consultants 00:08:14.000 --> 00:08:15.830 align:start position:0% meetings with all consultants um<00:08:14.319> to<00:08:14.479> ensure<00:08:14.800> we're<00:08:14.960> integrating<00:08:15.520> the<00:08:15.599> work 00:08:15.830 --> 00:08:15.840 align:start position:0% um to ensure we're integrating the work 00:08:15.840 --> 00:08:17.670 align:start position:0% um to ensure we're integrating the work effectively<00:08:16.720> and<00:08:16.800> to<00:08:16.960> be<00:08:17.039> really<00:08:17.280> clear<00:08:17.520> we 00:08:17.670 --> 00:08:17.680 align:start position:0% effectively and to be really clear we 00:08:17.680 --> 00:08:20.550 align:start position:0% effectively and to be really clear we will<00:08:17.919> kick<00:08:18.240> off<00:08:18.720> once<00:08:19.199> this<00:08:19.840> firm<00:08:20.080> is<00:08:20.240> hired 00:08:20.550 --> 00:08:20.560 align:start position:0% will kick off once this firm is hired 00:08:20.560 --> 00:08:21.830 align:start position:0% will kick off once this firm is hired we'll<00:08:20.720> kick<00:08:20.960> off<00:08:21.120> with<00:08:21.199> a<00:08:21.280> full<00:08:21.440> project 00:08:21.830 --> 00:08:21.840 align:start position:0% we'll kick off with a full project 00:08:21.840 --> 00:08:22.950 align:start position:0% we'll kick off with a full project meeting 00:08:22.950 --> 00:08:22.960 align:start position:0% meeting 00:08:22.960 --> 00:08:24.950 align:start position:0% meeting team<00:08:23.280> to<00:08:23.440> arrive<00:08:23.759> at<00:08:23.840> a<00:08:23.919> shared<00:08:24.240> work<00:08:24.479> plan<00:08:24.800> and 00:08:24.950 --> 00:08:24.960 align:start position:0% team to arrive at a shared work plan and 00:08:24.960 --> 00:08:27.350 align:start position:0% team to arrive at a shared work plan and schedule<00:08:25.680> communication<00:08:26.400> protocols<00:08:27.039> file 00:08:27.350 --> 00:08:27.360 align:start position:0% schedule communication protocols file 00:08:27.360 --> 00:08:28.710 align:start position:0% schedule communication protocols file sharing 00:08:28.710 --> 00:08:28.720 align:start position:0% sharing 00:08:28.720 --> 00:08:30.230 align:start position:0% sharing all<00:08:28.800> the<00:08:28.960> necessary<00:08:29.440> pieces<00:08:29.840> to<00:08:29.919> have<00:08:30.080> in 00:08:30.230 --> 00:08:30.240 align:start position:0% all the necessary pieces to have in 00:08:30.240 --> 00:08:31.510 align:start position:0% all the necessary pieces to have in place 00:08:31.510 --> 00:08:31.520 align:start position:0% place 00:08:31.520 --> 00:08:34.230 align:start position:0% place and<00:08:31.599> i<00:08:31.759> will<00:08:32.000> note<00:08:32.719> of<00:08:33.039> interest<00:08:33.760> to 00:08:34.230 --> 00:08:34.240 align:start position:0% and i will note of interest to 00:08:34.240 --> 00:08:36.469 align:start position:0% and i will note of interest to applicants<00:08:34.959> the<00:08:35.279> timelines<00:08:35.839> and<00:08:36.000> specific 00:08:36.469 --> 00:08:36.479 align:start position:0% applicants the timelines and specific 00:08:36.479 --> 00:08:39.029 align:start position:0% applicants the timelines and specific deliverables<00:08:37.279> for<00:08:37.440> the<00:08:37.599> economic<00:08:38.159> analysis 00:08:39.029 --> 00:08:39.039 align:start position:0% deliverables for the economic analysis 00:08:39.039 --> 00:08:41.829 align:start position:0% deliverables for the economic analysis and<00:08:39.279> ecological<00:08:40.000> analysis<00:08:40.640> support<00:08:41.599> that's 00:08:41.829 --> 00:08:41.839 align:start position:0% and ecological analysis support that's 00:08:41.839 --> 00:08:43.829 align:start position:0% and ecological analysis support that's going<00:08:41.919> to<00:08:42.000> be<00:08:42.159> refined<00:08:42.640> in<00:08:42.800> consultation<00:08:43.599> with 00:08:43.829 --> 00:08:43.839 align:start position:0% going to be refined in consultation with 00:08:43.839 --> 00:08:45.910 align:start position:0% going to be refined in consultation with the<00:08:44.000> selected<00:08:44.560> consultant<00:08:45.120> firm<00:08:45.440> under<00:08:45.680> this 00:08:45.910 --> 00:08:45.920 align:start position:0% the selected consultant firm under this 00:08:45.920 --> 00:08:47.910 align:start position:0% the selected consultant firm under this current<00:08:46.320> rfp<00:08:46.880> so<00:08:47.040> that<00:08:47.120> we<00:08:47.279> can<00:08:47.440> ensure<00:08:47.760> that 00:08:47.910 --> 00:08:47.920 align:start position:0% current rfp so that we can ensure that 00:08:47.920 --> 00:08:49.910 align:start position:0% current rfp so that we can ensure that those<00:08:48.240> timelines<00:08:48.880> data<00:08:49.200> assumptions 00:08:49.910 --> 00:08:49.920 align:start position:0% those timelines data assumptions 00:08:49.920 --> 00:08:51.990 align:start position:0% those timelines data assumptions communication<00:08:50.480> requirements<00:08:51.519> contract 00:08:51.990 --> 00:08:52.000 align:start position:0% communication requirements contract 00:08:52.000 --> 00:08:53.990 align:start position:0% communication requirements contract provisions<00:08:52.480> are<00:08:52.640> all<00:08:52.800> working<00:08:53.440> across<00:08:53.839> all 00:08:53.990 --> 00:08:54.000 align:start position:0% provisions are all working across all 00:08:54.000 --> 00:08:56.949 align:start position:0% provisions are all working across all parties 00:08:56.949 --> 00:08:56.959 align:start position:0% 00:08:56.959 --> 00:08:59.350 align:start position:0% as<00:08:57.200> far<00:08:57.360> as<00:08:57.600> budget<00:08:58.160> we<00:08:58.399> do<00:08:58.560> have<00:08:58.800> a<00:08:59.040> total 00:08:59.350 --> 00:08:59.360 align:start position:0% as far as budget we do have a total 00:08:59.360 --> 00:09:02.630 align:start position:0% as far as budget we do have a total budget<00:08:59.839> of<00:09:00.080> up<00:09:00.240> to<00:09:00.480> 180<00:09:01.519> thousand<00:09:01.920> dollars 00:09:02.630 --> 00:09:02.640 align:start position:0% budget of up to 180 thousand dollars 00:09:02.640 --> 00:09:04.790 align:start position:0% budget of up to 180 thousand dollars available<00:09:03.200> under<00:09:03.360> this<00:09:03.600> contract 00:09:04.790 --> 00:09:04.800 align:start position:0% available under this contract 00:09:04.800 --> 00:09:06.949 align:start position:0% available under this contract this<00:09:05.120> table<00:09:05.440> indicates<00:09:06.080> how<00:09:06.240> we<00:09:06.480> anticipate 00:09:06.949 --> 00:09:06.959 align:start position:0% this table indicates how we anticipate 00:09:06.959 --> 00:09:08.949 align:start position:0% this table indicates how we anticipate the<00:09:07.040> budget<00:09:07.360> breaking<00:09:07.760> down<00:09:08.240> relative<00:09:08.720> to<00:09:08.800> the 00:09:08.949 --> 00:09:08.959 align:start position:0% the budget breaking down relative to the 00:09:08.959 --> 00:09:12.310 align:start position:0% the budget breaking down relative to the areas<00:09:09.360> of<00:09:09.519> effort<00:09:10.080> in<00:09:10.160> the<00:09:10.320> rfp<00:09:10.959> scope<00:09:11.279> of<00:09:11.360> work 00:09:12.310 --> 00:09:12.320 align:start position:0% areas of effort in the rfp scope of work 00:09:12.320 --> 00:09:13.910 align:start position:0% areas of effort in the rfp scope of work and<00:09:12.560> of<00:09:12.640> course<00:09:12.959> the<00:09:13.120> boundaries<00:09:13.600> between 00:09:13.910 --> 00:09:13.920 align:start position:0% and of course the boundaries between 00:09:13.920 --> 00:09:15.910 align:start position:0% and of course the boundaries between tasks<00:09:14.560> and<00:09:14.640> how<00:09:14.800> the<00:09:14.959> budget<00:09:15.279> shakes<00:09:15.600> out 00:09:15.910 --> 00:09:15.920 align:start position:0% tasks and how the budget shakes out 00:09:15.920 --> 00:09:17.509 align:start position:0% tasks and how the budget shakes out really<00:09:16.160> depends<00:09:16.480> on<00:09:16.640> your<00:09:16.800> approach<00:09:17.120> to<00:09:17.279> this 00:09:17.509 --> 00:09:17.519 align:start position:0% really depends on your approach to this 00:09:17.519 --> 00:09:19.590 align:start position:0% really depends on your approach to this scope<00:09:18.160> so<00:09:18.399> in<00:09:18.480> your<00:09:18.640> proposal<00:09:19.200> you<00:09:19.440> are 00:09:19.590 --> 00:09:19.600 align:start position:0% scope so in your proposal you are 00:09:19.600 --> 00:09:21.829 align:start position:0% scope so in your proposal you are welcome<00:09:20.080> to<00:09:20.240> suggest<00:09:20.959> whatever<00:09:21.360> budget 00:09:21.829 --> 00:09:21.839 align:start position:0% welcome to suggest whatever budget 00:09:21.839 --> 00:09:24.710 align:start position:0% welcome to suggest whatever budget breakdown<00:09:22.800> best<00:09:23.040> supports<00:09:23.600> your<00:09:23.920> anticipated 00:09:24.710 --> 00:09:24.720 align:start position:0% breakdown best supports your anticipated 00:09:24.720 --> 00:09:26.550 align:start position:0% breakdown best supports your anticipated project<00:09:25.120> approach 00:09:26.550 --> 00:09:26.560 align:start position:0% project approach 00:09:26.560 --> 00:09:29.110 align:start position:0% project approach i'll<00:09:26.800> just<00:09:26.959> reiterate<00:09:27.519> a<00:09:27.600> note<00:09:27.839> from<00:09:28.000> the<00:09:28.080> rfe 00:09:29.110 --> 00:09:29.120 align:start position:0% i'll just reiterate a note from the rfe 00:09:29.120 --> 00:09:31.269 align:start position:0% i'll just reiterate a note from the rfe since<00:09:29.360> this<00:09:29.680> project<00:09:30.160> is<00:09:30.399> funded<00:09:30.800> by<00:09:31.120> a 00:09:31.269 --> 00:09:31.279 align:start position:0% since this project is funded by a 00:09:31.279 --> 00:09:34.150 align:start position:0% since this project is funded by a proposition<00:09:31.920> 68<00:09:32.560> grant<00:09:33.360> from<00:09:33.600> california 00:09:34.150 --> 00:09:34.160 align:start position:0% proposition 68 grant from california 00:09:34.160 --> 00:09:35.829 align:start position:0% proposition 68 grant from california ocean<00:09:34.399> protection<00:09:34.880> council<00:09:35.360> the<00:09:35.519> state 00:09:35.829 --> 00:09:35.839 align:start position:0% ocean protection council the state 00:09:35.839 --> 00:09:37.910 align:start position:0% ocean protection council the state bonded<00:09:36.320> funding<00:09:36.720> rules<00:09:36.959> will<00:09:37.200> apply<00:09:37.680> that 00:09:37.910 --> 00:09:37.920 align:start position:0% bonded funding rules will apply that 00:09:37.920 --> 00:09:39.670 align:start position:0% bonded funding rules will apply that includes<00:09:38.480> insurance<00:09:38.880> requirements<00:09:39.519> and 00:09:39.670 --> 00:09:39.680 align:start position:0% includes insurance requirements and 00:09:39.680 --> 00:09:41.269 align:start position:0% includes insurance requirements and overhead<00:09:40.080> limits<00:09:40.480> so<00:09:40.560> just<00:09:40.720> something<00:09:41.040> to<00:09:41.120> be 00:09:41.269 --> 00:09:41.279 align:start position:0% overhead limits so just something to be 00:09:41.279 --> 00:09:44.310 align:start position:0% overhead limits so just something to be aware<00:09:41.600> of<00:09:42.000> as<00:09:42.160> you<00:09:42.240> structure<00:09:42.640> your<00:09:42.720> budget 00:09:44.310 --> 00:09:44.320 align:start position:0% aware of as you structure your budget 00:09:44.320 --> 00:09:47.350 align:start position:0% aware of as you structure your budget a<00:09:44.640> look<00:09:45.040> at<00:09:45.360> the<00:09:45.600> rfp<00:09:46.160> schedule 00:09:47.350 --> 00:09:47.360 align:start position:0% a look at the rfp schedule 00:09:47.360 --> 00:09:49.269 align:start position:0% a look at the rfp schedule next<00:09:47.600> up<00:09:47.760> is<00:09:47.920> proposal<00:09:48.399> submission<00:09:48.880> deadline 00:09:49.269 --> 00:09:49.279 align:start position:0% next up is proposal submission deadline 00:09:49.279 --> 00:09:51.590 align:start position:0% next up is proposal submission deadline of<00:09:49.440> wednesday<00:09:50.000> december<00:09:50.480> 8th<00:09:50.720> at<00:09:50.880> 4<00:09:51.200> pm 00:09:51.590 --> 00:09:51.600 align:start position:0% of wednesday december 8th at 4 pm 00:09:51.600 --> 00:09:53.910 align:start position:0% of wednesday december 8th at 4 pm pacific<00:09:52.080> standard<00:09:52.959> and<00:09:53.279> depending<00:09:53.680> on<00:09:53.839> the 00:09:53.910 --> 00:09:53.920 align:start position:0% pacific standard and depending on the 00:09:53.920 --> 00:09:56.310 align:start position:0% pacific standard and depending on the number<00:09:54.160> of<00:09:54.320> proposals<00:09:54.880> received<00:09:55.680> consultant 00:09:56.310 --> 00:09:56.320 align:start position:0% number of proposals received consultant 00:09:56.320 --> 00:09:58.150 align:start position:0% number of proposals received consultant interviews<00:09:56.800> will<00:09:57.040> either<00:09:57.360> be<00:09:57.680> ahead<00:09:58.000> of<00:09:58.080> the 00:09:58.150 --> 00:09:58.160 align:start position:0% interviews will either be ahead of the 00:09:58.160 --> 00:10:00.550 align:start position:0% interviews will either be ahead of the winter<00:09:58.480> holiday<00:09:58.880> or<00:09:59.120> early<00:09:59.360> in<00:09:59.440> the<00:09:59.519> new<00:09:59.680> year 00:10:00.550 --> 00:10:00.560 align:start position:0% winter holiday or early in the new year 00:10:00.560 --> 00:10:02.790 align:start position:0% winter holiday or early in the new year so<00:10:00.720> the<00:10:00.880> selected<00:10:01.360> firm<00:10:01.760> will<00:10:01.920> work<00:10:02.160> with<00:10:02.320> cda 00:10:02.790 --> 00:10:02.800 align:start position:0% so the selected firm will work with cda 00:10:02.800 --> 00:10:05.110 align:start position:0% so the selected firm will work with cda to<00:10:03.040> refine<00:10:03.600> a<00:10:03.680> more<00:10:04.000> detailed<00:10:04.399> scope<00:10:04.720> of<00:10:04.880> work 00:10:05.110 --> 00:10:05.120 align:start position:0% to refine a more detailed scope of work 00:10:05.120 --> 00:10:06.949 align:start position:0% to refine a more detailed scope of work and<00:10:05.279> agree<00:10:05.600> on<00:10:05.680> specific<00:10:06.160> deliverables<00:10:06.720> but 00:10:06.949 --> 00:10:06.959 align:start position:0% and agree on specific deliverables but 00:10:06.959 --> 00:10:09.110 align:start position:0% and agree on specific deliverables but the<00:10:07.040> final<00:10:07.360> contract<00:10:08.320> going<00:10:08.560> to<00:10:08.720> the<00:10:08.800> board<00:10:09.040> of 00:10:09.110 --> 00:10:09.120 align:start position:0% the final contract going to the board of 00:10:09.120 --> 00:10:14.150 align:start position:0% the final contract going to the board of supervisors<00:10:10.399> by<00:10:10.640> february<00:10:11.279> 2022 00:10:14.150 --> 00:10:14.160 align:start position:0% supervisors by february 2022 00:10:14.160 --> 00:10:16.310 align:start position:0% supervisors by february 2022 all<00:10:14.320> right<00:10:14.640> two<00:10:14.800> ways<00:10:15.040> to<00:10:15.200> submit<00:10:15.920> this<00:10:16.240> is 00:10:16.310 --> 00:10:16.320 align:start position:0% all right two ways to submit this is 00:10:16.320 --> 00:10:17.910 align:start position:0% all right two ways to submit this is getting<00:10:16.560> to<00:10:16.720> the<00:10:16.800> details<00:10:17.360> that<00:10:17.519> i<00:10:17.600> think<00:10:17.760> are 00:10:17.910 --> 00:10:17.920 align:start position:0% getting to the details that i think are 00:10:17.920 --> 00:10:19.670 align:start position:0% getting to the details that i think are laid<00:10:18.240> out<00:10:18.320> pretty<00:10:18.480> clearly<00:10:18.880> in<00:10:19.040> the<00:10:19.120> document 00:10:19.670 --> 00:10:19.680 align:start position:0% laid out pretty clearly in the document 00:10:19.680 --> 00:10:22.790 align:start position:0% laid out pretty clearly in the document you<00:10:19.839> can<00:10:20.000> submit<00:10:20.399> by<00:10:20.640> email<00:10:21.120> or<00:10:21.360> by<00:10:21.600> hard<00:10:21.920> copy 00:10:22.790 --> 00:10:22.800 align:start position:0% you can submit by email or by hard copy 00:10:22.800 --> 00:10:25.590 align:start position:0% you can submit by email or by hard copy i'll<00:10:23.040> just<00:10:23.200> note<00:10:23.440> there's<00:10:23.680> the<00:10:23.920> 25<00:10:24.560> page<00:10:25.200> limit 00:10:25.590 --> 00:10:25.600 align:start position:0% i'll just note there's the 25 page limit 00:10:25.600 --> 00:10:27.910 align:start position:0% i'll just note there's the 25 page limit that<00:10:25.680> we<00:10:25.839> ask<00:10:26.160> on<00:10:26.320> narrative<00:10:26.800> content<00:10:27.760> and 00:10:27.910 --> 00:10:27.920 align:start position:0% that we ask on narrative content and 00:10:27.920 --> 00:10:29.350 align:start position:0% that we ask on narrative content and then<00:10:28.079> we<00:10:28.240> have<00:10:28.399> attachments<00:10:29.120> so<00:10:29.279> the 00:10:29.350 --> 00:10:29.360 align:start position:0% then we have attachments so the 00:10:29.360 --> 00:10:31.990 align:start position:0% then we have attachments so the additional<00:10:29.839> forms<00:10:30.240> required<00:10:31.120> by<00:10:31.279> the<00:10:31.440> county 00:10:31.990 --> 00:10:32.000 align:start position:0% additional forms required by the county 00:10:32.000 --> 00:10:33.750 align:start position:0% additional forms required by the county that<00:10:32.160> are<00:10:32.320> in<00:10:32.399> the<00:10:32.560> rfp 00:10:33.750 --> 00:10:33.760 align:start position:0% that are in the rfp 00:10:33.760 --> 00:10:35.269 align:start position:0% that are in the rfp and<00:10:33.839> then<00:10:34.000> there's<00:10:34.240> optional<00:10:34.720> attachments 00:10:35.269 --> 00:10:35.279 align:start position:0% and then there's optional attachments 00:10:35.279 --> 00:10:36.870 align:start position:0% and then there's optional attachments you<00:10:35.360> know<00:10:35.519> staff<00:10:35.839> resumes<00:10:36.320> supporting 00:10:36.870 --> 00:10:36.880 align:start position:0% you know staff resumes supporting 00:10:36.880 --> 00:10:38.069 align:start position:0% you know staff resumes supporting graphics 00:10:38.069 --> 00:10:38.079 align:start position:0% graphics 00:10:38.079 --> 00:10:40.949 align:start position:0% graphics that<00:10:38.320> all<00:10:38.560> falls<00:10:38.959> outside<00:10:39.519> of<00:10:39.680> the<00:10:39.920> 25<00:10:40.560> page 00:10:40.949 --> 00:10:40.959 align:start position:0% that all falls outside of the 25 page 00:10:40.959 --> 00:10:42.550 align:start position:0% that all falls outside of the 25 page limit<00:10:41.440> so 00:10:42.550 --> 00:10:42.560 align:start position:0% limit so 00:10:42.560 --> 00:10:44.230 align:start position:0% limit so hopefully<00:10:42.880> gives<00:10:43.120> you<00:10:43.279> space<00:10:43.519> to<00:10:43.680> describe 00:10:44.230 --> 00:10:44.240 align:start position:0% hopefully gives you space to describe 00:10:44.240 --> 00:10:45.829 align:start position:0% hopefully gives you space to describe what<00:10:44.399> your<00:10:44.640> really<00:10:44.880> cool<00:10:45.040> approaches<00:10:45.519> to<00:10:45.600> this 00:10:45.829 --> 00:10:45.839 align:start position:0% what your really cool approaches to this 00:10:45.839 --> 00:10:46.949 align:start position:0% what your really cool approaches to this work 00:10:46.949 --> 00:10:46.959 align:start position:0% work 00:10:46.959 --> 00:10:49.269 align:start position:0% work and<00:10:47.200> with<00:10:47.680> that<00:10:48.399> i<00:10:48.560> really<00:10:48.880> thank<00:10:49.040> you<00:10:49.200> for 00:10:49.269 --> 00:10:49.279 align:start position:0% and with that i really thank you for 00:10:49.279 --> 00:10:51.670 align:start position:0% and with that i really thank you for your<00:10:49.440> attention<00:10:50.399> apologize<00:10:51.040> again<00:10:51.360> that<00:10:51.440> this 00:10:51.670 --> 00:10:51.680 align:start position:0% your attention apologize again that this 00:10:51.680 --> 00:10:53.670 align:start position:0% your attention apologize again that this is<00:10:51.760> going<00:10:51.839> to<00:10:52.000> be<00:10:52.160> a<00:10:52.240> little<00:10:52.800> a<00:10:52.880> little<00:10:53.200> stilted 00:10:53.670 --> 00:10:53.680 align:start position:0% is going to be a little a little stilted 00:10:53.680 --> 00:10:56.230 align:start position:0% is going to be a little a little stilted with<00:10:53.920> how<00:10:54.320> we<00:10:54.640> navigate<00:10:55.200> the<00:10:55.440> questions<00:10:56.000> given 00:10:56.230 --> 00:10:56.240 align:start position:0% with how we navigate the questions given 00:10:56.240 --> 00:10:59.190 align:start position:0% with how we navigate the questions given my<00:10:56.480> audio<00:10:56.880> challenges 00:10:59.190 --> 00:10:59.200 align:start position:0% my audio challenges 00:10:59.200 --> 00:11:01.430 align:start position:0% my audio challenges um<00:10:59.920> i<00:11:00.079> think<00:11:00.320> a<00:11:00.399> way<00:11:00.560> i'm<00:11:00.640> going<00:11:00.720> to<00:11:00.800> propose<00:11:01.279> we 00:11:01.430 --> 00:11:01.440 align:start position:0% um i think a way i'm going to propose we 00:11:01.440 --> 00:11:03.670 align:start position:0% um i think a way i'm going to propose we do<00:11:01.600> this<00:11:01.920> i<00:11:02.079> see<00:11:02.320> folks<00:11:02.640> have<00:11:02.800> been<00:11:03.120> answering 00:11:03.670 --> 00:11:03.680 align:start position:0% do this i see folks have been answering 00:11:03.680 --> 00:11:05.430 align:start position:0% do this i see folks have been answering questions 00:11:05.430 --> 00:11:05.440 align:start position:0% questions 00:11:05.440 --> 00:11:06.790 align:start position:0% questions already<00:11:05.839> we<00:11:05.920> have<00:11:06.000> some<00:11:06.160> questions<00:11:06.560> coming 00:11:06.790 --> 00:11:06.800 align:start position:0% already we have some questions coming 00:11:06.800 --> 00:11:08.310 align:start position:0% already we have some questions coming into<00:11:06.959> the<00:11:07.120> chat 00:11:08.310 --> 00:11:08.320 align:start position:0% into the chat 00:11:08.320 --> 00:11:10.550 align:start position:0% into the chat um 00:11:10.550 --> 00:11:10.560 align:start position:0% um 00:11:10.560 --> 00:11:12.310 align:start position:0% um i<00:11:10.720> think<00:11:10.880> what<00:11:11.040> we're<00:11:11.279> going<00:11:11.440> to<00:11:11.600> do<00:11:11.839> just<00:11:12.000> so<00:11:12.240> i 00:11:12.310 --> 00:11:12.320 align:start position:0% i think what we're going to do just so i 00:11:12.320 --> 00:11:14.790 align:start position:0% i think what we're going to do just so i can<00:11:12.480> tell<00:11:12.720> when<00:11:12.959> jack<00:11:13.360> is<00:11:13.519> talking 00:11:14.790 --> 00:11:14.800 align:start position:0% can tell when jack is talking 00:11:14.800 --> 00:11:17.590 align:start position:0% can tell when jack is talking jack<00:11:15.519> yeah<00:11:15.839> let's<00:11:16.079> use<00:11:16.320> the<00:11:16.480> ray's<00:11:16.800> hand<00:11:17.200> so<00:11:17.440> i 00:11:17.590 --> 00:11:17.600 align:start position:0% jack yeah let's use the ray's hand so i 00:11:17.600 --> 00:11:19.750 align:start position:0% jack yeah let's use the ray's hand so i will<00:11:18.000> first<00:11:18.320> give<00:11:18.560> something<00:11:18.880> a<00:11:18.959> pass<00:11:19.519> i'll 00:11:19.750 --> 00:11:19.760 align:start position:0% will first give something a pass i'll 00:11:19.760 --> 00:11:21.509 align:start position:0% will first give something a pass i'll send<00:11:20.000> it<00:11:20.160> to<00:11:20.399> jack 00:11:21.509 --> 00:11:21.519 align:start position:0% send it to jack 00:11:21.519 --> 00:11:24.069 align:start position:0% send it to jack and<00:11:21.760> jack<00:11:22.320> maybe<00:11:22.720> when<00:11:22.959> you're 00:11:24.069 --> 00:11:24.079 align:start position:0% and jack maybe when you're 00:11:24.079 --> 00:11:25.670 align:start position:0% and jack maybe when you're done<00:11:24.480> speaking 00:11:25.670 --> 00:11:25.680 align:start position:0% done speaking 00:11:25.680 --> 00:11:27.590 align:start position:0% done speaking put<00:11:25.920> up<00:11:26.079> the<00:11:26.240> hand<00:11:26.640> so<00:11:26.800> that<00:11:26.959> i<00:11:27.120> know<00:11:27.360> you've 00:11:27.590 --> 00:11:27.600 align:start position:0% put up the hand so that i know you've 00:11:27.600 --> 00:11:29.190 align:start position:0% put up the hand so that i know you've finished<00:11:28.000> talk 00:11:29.190 --> 00:11:29.200 align:start position:0% finished talk 00:11:29.200 --> 00:11:31.350 align:start position:0% finished talk a<00:11:29.279> little<00:11:29.600> less 00:11:31.350 --> 00:11:31.360 align:start position:0% a little less 00:11:31.360 --> 00:11:33.350 align:start position:0% a little less all<00:11:31.519> right<00:11:31.920> so<00:11:32.399> great 00:11:33.350 --> 00:11:33.360 align:start position:0% all right so great 00:11:33.360 --> 00:11:34.790 align:start position:0% all right so great so<00:11:33.600> i'm<00:11:33.760> going<00:11:33.839> to<00:11:34.000> start<00:11:34.240> here<00:11:34.399> with<00:11:34.560> what's 00:11:34.790 --> 00:11:34.800 align:start position:0% so i'm going to start here with what's 00:11:34.800 --> 00:11:36.069 align:start position:0% so i'm going to start here with what's in<00:11:34.880> the<00:11:35.040> chat<00:11:35.279> and<00:11:35.360> then<00:11:35.519> those<00:11:35.680> of<00:11:35.760> you<00:11:35.920> who 00:11:36.069 --> 00:11:36.079 align:start position:0% in the chat and then those of you who 00:11:36.079 --> 00:11:38.069 align:start position:0% in the chat and then those of you who submitted<00:11:36.480> questions<00:11:37.279> ahead<00:11:37.519> of<00:11:37.600> time<00:11:37.839> by 00:11:38.069 --> 00:11:38.079 align:start position:0% submitted questions ahead of time by 00:11:38.079 --> 00:11:41.269 align:start position:0% submitted questions ahead of time by email<00:11:38.320> we<00:11:38.480> will<00:11:38.720> get<00:11:38.880> to<00:11:38.959> those<00:11:39.680> um 00:11:41.269 --> 00:11:41.279 align:start position:0% email we will get to those um 00:11:41.279 --> 00:11:42.870 align:start position:0% email we will get to those um all<00:11:41.440> right 00:11:42.870 --> 00:11:42.880 align:start position:0% all right 00:11:42.880 --> 00:11:44.389 align:start position:0% all right uh<00:11:43.040> will<00:11:43.200> the<00:11:43.360> presentation<00:11:43.839> be<00:11:44.000> available 00:11:44.389 --> 00:11:44.399 align:start position:0% uh will the presentation be available 00:11:44.399 --> 00:11:46.150 align:start position:0% uh will the presentation be available after<00:11:44.640> the<00:11:44.720> meeting<00:11:45.120> yes<00:11:45.440> it<00:11:45.519> will<00:11:45.680> be<00:11:45.760> posted 00:11:46.150 --> 00:11:46.160 align:start position:0% after the meeting yes it will be posted 00:11:46.160 --> 00:11:47.750 align:start position:0% after the meeting yes it will be posted on<00:11:46.240> the<00:11:46.480> marin<00:11:46.800> county<00:11:47.200> contracting 00:11:47.750 --> 00:11:47.760 align:start position:0% on the marin county contracting 00:11:47.760 --> 00:11:49.990 align:start position:0% on the marin county contracting opportunities<00:11:48.480> webpage<00:11:49.040> where<00:11:49.200> the<00:11:49.360> rfp<00:11:49.839> is 00:11:49.990 --> 00:11:50.000 align:start position:0% opportunities webpage where the rfp is 00:11:50.000 --> 00:11:51.430 align:start position:0% opportunities webpage where the rfp is currently<00:11:50.399> posted 00:11:51.430 --> 00:11:51.440 align:start position:0% currently posted 00:11:51.440 --> 00:11:54.190 align:start position:0% currently posted if<00:11:51.600> you<00:11:51.839> access<00:11:52.160> the<00:11:52.320> rfp<00:11:52.880> from<00:11:53.120> the 00:11:54.190 --> 00:11:54.200 align:start position:0% if you access the rfp from the 00:11:54.200 --> 00:11:56.790 align:start position:0% if you access the rfp from the marinslr.org<00:11:55.279> link<00:11:55.839> it's<00:11:56.079> all<00:11:56.240> connected 00:11:56.790 --> 00:11:56.800 align:start position:0% marinslr.org link it's all connected 00:11:56.800 --> 00:11:58.550 align:start position:0% marinslr.org link it's all connected online<00:11:57.279> so<00:11:57.440> you'll<00:11:57.600> still<00:11:57.839> be<00:11:58.000> able<00:11:58.160> to<00:11:58.240> get<00:11:58.480> to 00:11:58.550 --> 00:11:58.560 align:start position:0% online so you'll still be able to get to 00:11:58.560 --> 00:12:00.629 align:start position:0% online so you'll still be able to get to this<00:11:58.800> and<00:11:58.880> i'll<00:11:59.040> also<00:11:59.360> post<00:11:59.600> a<00:11:59.760> written<00:12:00.079> q<00:12:00.399> a 00:12:00.629 --> 00:12:00.639 align:start position:0% this and i'll also post a written q a 00:12:00.639 --> 00:12:02.470 align:start position:0% this and i'll also post a written q a document 00:12:02.470 --> 00:12:02.480 align:start position:0% document 00:12:02.480 --> 00:12:03.590 align:start position:0% document all<00:12:02.639> right<00:12:02.800> can<00:12:03.040> you<00:12:03.120> describe<00:12:03.519> the 00:12:03.590 --> 00:12:03.600 align:start position:0% all right can you describe the 00:12:03.600 --> 00:12:05.829 align:start position:0% all right can you describe the difference<00:12:04.000> between<00:12:04.399> facilitation<00:12:05.440> public 00:12:05.829 --> 00:12:05.839 align:start position:0% difference between facilitation public 00:12:05.839 --> 00:12:07.910 align:start position:0% difference between facilitation public outreach<00:12:06.240> and<00:12:06.399> public<00:12:06.720> engagement<00:12:07.360> great 00:12:07.910 --> 00:12:07.920 align:start position:0% outreach and public engagement great 00:12:07.920 --> 00:12:11.350 align:start position:0% outreach and public engagement great question 00:12:11.350 --> 00:12:11.360 align:start position:0% 00:12:11.360 --> 00:12:14.310 align:start position:0% facilitation<00:12:12.399> we<00:12:12.560> have<00:12:12.800> hired<00:12:13.040> a<00:12:13.120> facilitator 00:12:14.310 --> 00:12:14.320 align:start position:0% facilitation we have hired a facilitator 00:12:14.320 --> 00:12:16.310 align:start position:0% facilitation we have hired a facilitator rainwater<00:12:14.800> and<00:12:14.880> associates<00:12:15.440> llc<00:12:16.079> so<00:12:16.160> we're 00:12:16.310 --> 00:12:16.320 align:start position:0% rainwater and associates llc so we're 00:12:16.320 --> 00:12:18.150 align:start position:0% rainwater and associates llc so we're working<00:12:16.560> with<00:12:16.720> marine<00:12:17.040> rainwater 00:12:18.150 --> 00:12:18.160 align:start position:0% working with marine rainwater 00:12:18.160 --> 00:12:20.069 align:start position:0% working with marine rainwater we<00:12:18.399> are<00:12:18.560> looking<00:12:18.800> at<00:12:18.959> facilitation<00:12:19.680> as<00:12:19.839> two 00:12:20.069 --> 00:12:20.079 align:start position:0% we are looking at facilitation as two 00:12:20.079 --> 00:12:22.710 align:start position:0% we are looking at facilitation as two pieces<00:12:20.880> one<00:12:21.200> is<00:12:21.360> some<00:12:21.680> upfront<00:12:22.160> process 00:12:22.710 --> 00:12:22.720 align:start position:0% pieces one is some upfront process 00:12:22.720 --> 00:12:24.470 align:start position:0% pieces one is some upfront process design<00:12:23.200> how<00:12:23.360> do<00:12:23.440> we<00:12:23.600> structure<00:12:24.079> ourselves 00:12:24.470 --> 00:12:24.480 align:start position:0% design how do we structure ourselves 00:12:24.480 --> 00:12:26.790 align:start position:0% design how do we structure ourselves ahead<00:12:24.720> of<00:12:24.880> time<00:12:25.519> to<00:12:25.680> create<00:12:26.000> a<00:12:26.160> process<00:12:26.639> that 00:12:26.790 --> 00:12:26.800 align:start position:0% ahead of time to create a process that 00:12:26.800 --> 00:12:29.269 align:start position:0% ahead of time to create a process that can<00:12:26.959> bring<00:12:27.279> in<00:12:27.519> feedback<00:12:28.240> that<00:12:28.399> can<00:12:28.639> minimize 00:12:29.269 --> 00:12:29.279 align:start position:0% can bring in feedback that can minimize 00:12:29.279 --> 00:12:32.150 align:start position:0% can bring in feedback that can minimize conflict<00:12:29.920> maximize<00:12:30.639> input<00:12:31.519> so<00:12:31.680> that's<00:12:31.920> one 00:12:32.150 --> 00:12:32.160 align:start position:0% conflict maximize input so that's one 00:12:32.160 --> 00:12:34.069 align:start position:0% conflict maximize input so that's one aspect<00:12:32.560> of<00:12:32.639> facilitation<00:12:33.440> that's<00:12:33.680> happening 00:12:34.069 --> 00:12:34.079 align:start position:0% aspect of facilitation that's happening 00:12:34.079 --> 00:12:35.829 align:start position:0% aspect of facilitation that's happening now<00:12:34.320> behind<00:12:34.639> the<00:12:34.800> scenes 00:12:35.829 --> 00:12:35.839 align:start position:0% now behind the scenes 00:12:35.839 --> 00:12:38.389 align:start position:0% now behind the scenes active<00:12:36.240> facilitation<00:12:37.120> we<00:12:37.360> do<00:12:37.600> have<00:12:37.920> rainwater 00:12:38.389 --> 00:12:38.399 align:start position:0% active facilitation we do have rainwater 00:12:38.399 --> 00:12:39.829 align:start position:0% active facilitation we do have rainwater and<00:12:38.480> associates<00:12:39.120> contracted<00:12:39.680> for 00:12:39.829 --> 00:12:39.839 align:start position:0% and associates contracted for 00:12:39.839 --> 00:12:41.670 align:start position:0% and associates contracted for facilitation<00:12:40.560> support 00:12:41.670 --> 00:12:41.680 align:start position:0% facilitation support 00:12:41.680 --> 00:12:43.430 align:start position:0% facilitation support we<00:12:41.920> anticipate<00:12:42.560> that 00:12:43.430 --> 00:12:43.440 align:start position:0% we anticipate that 00:12:43.440 --> 00:12:44.710 align:start position:0% we anticipate that being 00:12:44.710 --> 00:12:44.720 align:start position:0% being 00:12:44.720 --> 00:12:47.190 align:start position:0% being strategic<00:12:45.360> support<00:12:46.079> for<00:12:46.720> focused 00:12:47.190 --> 00:12:47.200 align:start position:0% strategic support for focused 00:12:47.200 --> 00:12:49.750 align:start position:0% strategic support for focused conversations<00:12:48.320> so 00:12:49.750 --> 00:12:49.760 align:start position:0% conversations so 00:12:49.760 --> 00:12:51.509 align:start position:0% conversations so when<00:12:50.000> i<00:12:50.240> showed<00:12:50.720> the 00:12:51.509 --> 00:12:51.519 align:start position:0% when i showed the 00:12:51.519 --> 00:12:53.750 align:start position:0% when i showed the let<00:12:51.680> me<00:12:52.000> go<00:12:52.160> back<00:12:52.320> through<00:12:52.560> my<00:12:52.720> slides<00:12:53.440> when<00:12:53.600> i 00:12:53.750 --> 00:12:53.760 align:start position:0% let me go back through my slides when i 00:12:53.760 --> 00:12:55.190 align:start position:0% let me go back through my slides when i showed<00:12:54.079> our<00:12:54.240> spectrum<00:12:54.720> of<00:12:54.800> different 00:12:55.190 --> 00:12:55.200 align:start position:0% showed our spectrum of different 00:12:55.200 --> 00:12:58.949 align:start position:0% showed our spectrum of different community<00:12:55.760> engagement<00:12:56.399> strategies 00:12:58.949 --> 00:12:58.959 align:start position:0% community engagement strategies 00:12:58.959 --> 00:13:00.629 align:start position:0% community engagement strategies public<00:12:59.360> meetings 00:13:00.629 --> 00:13:00.639 align:start position:0% public meetings 00:13:00.639 --> 00:13:02.150 align:start position:0% public meetings some<00:13:00.880> active<00:13:01.120> working<00:13:01.440> groups<00:13:01.760> coastal 00:13:02.150 --> 00:13:02.160 align:start position:0% some active working groups coastal 00:13:02.160 --> 00:13:04.310 align:start position:0% some active working groups coastal communities<00:13:02.639> working<00:13:03.040> group<00:13:03.360> is<00:13:03.519> a 00:13:04.310 --> 00:13:04.320 align:start position:0% communities working group is a 00:13:04.320 --> 00:13:06.629 align:start position:0% communities working group is a west<00:13:04.639> marin<00:13:05.040> interest<00:13:05.440> based<00:13:05.839> group<00:13:06.399> west 00:13:06.629 --> 00:13:06.639 align:start position:0% west marin interest based group west 00:13:06.639 --> 00:13:08.629 align:start position:0% west marin interest based group west marine<00:13:06.959> advisory<00:13:07.440> group<00:13:07.680> is<00:13:07.760> a<00:13:07.920> regulatory 00:13:08.629 --> 00:13:08.639 align:start position:0% marine advisory group is a regulatory 00:13:08.639 --> 00:13:11.590 align:start position:0% marine advisory group is a regulatory agency<00:13:09.040> group<00:13:09.279> we<00:13:09.440> have<00:13:09.760> for<00:13:10.000> input 00:13:11.590 --> 00:13:11.600 align:start position:0% agency group we have for input 00:13:11.600 --> 00:13:13.670 align:start position:0% agency group we have for input all<00:13:11.839> of<00:13:11.920> these<00:13:12.160> spaces<00:13:12.639> have<00:13:12.959> opportunities 00:13:13.670 --> 00:13:13.680 align:start position:0% all of these spaces have opportunities 00:13:13.680 --> 00:13:16.310 align:start position:0% all of these spaces have opportunities for<00:13:13.839> facilitation<00:13:14.639> support<00:13:15.519> um<00:13:16.079> i<00:13:16.160> think 00:13:16.310 --> 00:13:16.320 align:start position:0% for facilitation support um i think 00:13:16.320 --> 00:13:18.069 align:start position:0% for facilitation support um i think where<00:13:16.480> we're<00:13:16.560> gonna<00:13:16.800> really<00:13:17.040> use<00:13:17.360> it<00:13:17.600> is<00:13:17.839> for 00:13:18.069 --> 00:13:18.079 align:start position:0% where we're gonna really use it is for 00:13:18.079 --> 00:13:21.030 align:start position:0% where we're gonna really use it is for structuring<00:13:18.639> some<00:13:18.800> more<00:13:19.120> focused<00:13:19.839> smaller 00:13:21.030 --> 00:13:21.040 align:start position:0% structuring some more focused smaller 00:13:21.040 --> 00:13:23.190 align:start position:0% structuring some more focused smaller interest<00:13:21.440> group<00:13:21.680> based<00:13:22.079> conversations<00:13:22.880> as<00:13:23.040> we 00:13:23.190 --> 00:13:23.200 align:start position:0% interest group based conversations as we 00:13:23.200 --> 00:13:25.190 align:start position:0% interest group based conversations as we get<00:13:23.440> into<00:13:23.680> the<00:13:23.760> more<00:13:24.079> complicated<00:13:24.720> steps<00:13:25.040> of 00:13:25.190 --> 00:13:25.200 align:start position:0% get into the more complicated steps of 00:13:25.200 --> 00:13:26.949 align:start position:0% get into the more complicated steps of adaptation<00:13:25.839> planning 00:13:26.949 --> 00:13:26.959 align:start position:0% adaptation planning 00:13:26.959 --> 00:13:30.150 align:start position:0% adaptation planning we<00:13:27.120> do<00:13:27.279> not<00:13:27.519> envision<00:13:27.920> the<00:13:28.000> facilitator<00:13:28.800> as 00:13:30.150 --> 00:13:30.160 align:start position:0% we do not envision the facilitator as 00:13:30.160 --> 00:13:31.750 align:start position:0% we do not envision the facilitator as setting<00:13:30.480> up<00:13:30.639> the<00:13:30.800> room 00:13:31.750 --> 00:13:31.760 align:start position:0% setting up the room 00:13:31.760 --> 00:13:33.670 align:start position:0% setting up the room being<00:13:32.160> the<00:13:32.320> dj 00:13:33.670 --> 00:13:33.680 align:start position:0% being the dj 00:13:33.680 --> 00:13:35.670 align:start position:0% being the dj being<00:13:33.920> the<00:13:34.079> person<00:13:34.480> running<00:13:35.200> the<00:13:35.360> public 00:13:35.670 --> 00:13:35.680 align:start position:0% being the person running the public 00:13:35.680 --> 00:13:37.269 align:start position:0% being the person running the public meeting<00:13:36.079> welcoming<00:13:36.560> people<00:13:37.040> those 00:13:37.269 --> 00:13:37.279 align:start position:0% meeting welcoming people those 00:13:37.279 --> 00:13:39.269 align:start position:0% meeting welcoming people those responsibilities<00:13:38.160> are<00:13:38.240> going<00:13:38.320> to<00:13:38.480> fall<00:13:38.880> on 00:13:39.269 --> 00:13:39.279 align:start position:0% responsibilities are going to fall on 00:13:39.279 --> 00:13:41.670 align:start position:0% responsibilities are going to fall on county<00:13:39.680> staff<00:13:40.240> and<00:13:40.399> working<00:13:40.800> with<00:13:41.040> the<00:13:41.279> hired 00:13:41.670 --> 00:13:41.680 align:start position:0% county staff and working with the hired 00:13:41.680 --> 00:13:42.949 align:start position:0% county staff and working with the hired consultant 00:13:42.949 --> 00:13:42.959 align:start position:0% consultant 00:13:42.959 --> 00:13:44.629 align:start position:0% consultant so<00:13:43.120> that<00:13:43.279> gets<00:13:43.519> us<00:13:43.680> to<00:13:43.920> what<00:13:44.079> i<00:13:44.160> would<00:13:44.320> call<00:13:44.480> the 00:13:44.629 --> 00:13:44.639 align:start position:0% so that gets us to what i would call the 00:13:44.639 --> 00:13:47.110 align:start position:0% so that gets us to what i would call the public<00:13:45.040> engagement<00:13:45.680> which<00:13:45.920> are<00:13:46.399> what<00:13:46.639> are<00:13:46.720> the 00:13:47.110 --> 00:13:47.120 align:start position:0% public engagement which are what are the 00:13:47.120 --> 00:13:50.710 align:start position:0% public engagement which are what are the events<00:13:47.760> we<00:13:47.920> can<00:13:48.160> offer<00:13:48.959> that<00:13:49.199> invite<00:13:49.839> people 00:13:50.710 --> 00:13:50.720 align:start position:0% events we can offer that invite people 00:13:50.720 --> 00:13:53.030 align:start position:0% events we can offer that invite people to<00:13:51.040> show<00:13:51.360> up<00:13:51.600> to<00:13:51.760> bring<00:13:51.920> their<00:13:52.160> ideas<00:13:52.720> to<00:13:52.880> weigh 00:13:53.030 --> 00:13:53.040 align:start position:0% to show up to bring their ideas to weigh 00:13:53.040 --> 00:13:55.269 align:start position:0% to show up to bring their ideas to weigh in<00:13:53.279> on<00:13:53.440> the<00:13:53.600> process 00:13:55.269 --> 00:13:55.279 align:start position:0% in on the process 00:13:55.279 --> 00:13:56.629 align:start position:0% in on the process but<00:13:55.519> some<00:13:55.680> of<00:13:55.760> the<00:13:55.920> structured<00:13:56.320> thinking 00:13:56.629 --> 00:13:56.639 align:start position:0% but some of the structured thinking 00:13:56.639 --> 00:13:58.629 align:start position:0% but some of the structured thinking ahead<00:13:56.959> of<00:13:57.040> time<00:13:57.279> on<00:13:57.440> how<00:13:57.600> we<00:13:57.760> manage<00:13:58.079> that<00:13:58.320> flow 00:13:58.629 --> 00:13:58.639 align:start position:0% ahead of time on how we manage that flow 00:13:58.639 --> 00:14:00.230 align:start position:0% ahead of time on how we manage that flow of<00:13:58.800> information 00:14:00.230 --> 00:14:00.240 align:start position:0% of information 00:14:00.240 --> 00:14:02.790 align:start position:0% of information what<00:14:00.720> types<00:14:01.440> of 00:14:02.790 --> 00:14:02.800 align:start position:0% what types of 00:14:02.800 --> 00:14:04.470 align:start position:0% what types of engagement<00:14:03.360> we<00:14:03.519> are<00:14:03.680> inviting<00:14:04.079> that's<00:14:04.320> where 00:14:04.470 --> 00:14:04.480 align:start position:0% engagement we are inviting that's where 00:14:04.480 --> 00:14:07.030 align:start position:0% engagement we are inviting that's where we're<00:14:04.639> getting<00:14:04.800> some<00:14:05.040> facilitation 00:14:07.030 --> 00:14:07.040 align:start position:0% we're getting some facilitation 00:14:07.040 --> 00:14:10.069 align:start position:0% we're getting some facilitation public<00:14:07.440> outreach 00:14:10.069 --> 00:14:10.079 align:start position:0% 00:14:10.079 --> 00:14:11.750 align:start position:0% i<00:14:10.240> appreciate<00:14:10.560> the<00:14:10.720> question<00:14:11.040> my<00:14:11.199> language<00:14:11.600> is 00:14:11.750 --> 00:14:11.760 align:start position:0% i appreciate the question my language is 00:14:11.760 --> 00:14:13.670 align:start position:0% i appreciate the question my language is vague<00:14:12.079> here<00:14:12.480> i<00:14:12.639> think<00:14:12.800> there's<00:14:13.040> also<00:14:13.279> public 00:14:13.670 --> 00:14:13.680 align:start position:0% vague here i think there's also public 00:14:13.680 --> 00:14:15.670 align:start position:0% vague here i think there's also public outreach<00:14:14.000> just<00:14:14.480> getting<00:14:14.880> information<00:14:15.519> out 00:14:15.670 --> 00:14:15.680 align:start position:0% outreach just getting information out 00:14:15.680 --> 00:14:18.710 align:start position:0% outreach just getting information out there<00:14:16.079> um<00:14:16.639> we<00:14:16.800> are<00:14:17.040> contracting<00:14:18.000> with<00:14:18.320> golden 00:14:18.710 --> 00:14:18.720 align:start position:0% there um we are contracting with golden 00:14:18.720 --> 00:14:21.269 align:start position:0% there um we are contracting with golden gate<00:14:19.199> national<00:14:19.600> park<00:14:19.920> conservancy 00:14:21.269 --> 00:14:21.279 align:start position:0% gate national park conservancy 00:14:21.279 --> 00:14:22.550 align:start position:0% gate national park conservancy to 00:14:22.550 --> 00:14:22.560 align:start position:0% to 00:14:22.560 --> 00:14:24.629 align:start position:0% to help<00:14:22.800> us<00:14:22.959> think<00:14:23.120> about<00:14:23.360> some<00:14:23.519> creative<00:14:24.320> events 00:14:24.629 --> 00:14:24.639 align:start position:0% help us think about some creative events 00:14:24.639 --> 00:14:26.310 align:start position:0% help us think about some creative events we<00:14:24.800> could<00:14:24.880> host<00:14:25.199> in<00:14:25.279> the<00:14:25.360> community<00:14:26.000> to<00:14:26.160> get 00:14:26.310 --> 00:14:26.320 align:start position:0% we could host in the community to get 00:14:26.320 --> 00:14:29.110 align:start position:0% we could host in the community to get people<00:14:26.639> interested<00:14:27.440> share<00:14:27.839> information 00:14:29.110 --> 00:14:29.120 align:start position:0% people interested share information 00:14:29.120 --> 00:14:30.310 align:start position:0% people interested share information so<00:14:29.199> i<00:14:29.279> think<00:14:29.519> some<00:14:29.680> of<00:14:29.760> that<00:14:29.920> is<00:14:30.000> public 00:14:30.310 --> 00:14:30.320 align:start position:0% so i think some of that is public 00:14:30.320 --> 00:14:32.870 align:start position:0% so i think some of that is public outreach<00:14:31.199> media<00:14:31.680> strategies<00:14:32.639> if<00:14:32.720> we're 00:14:32.870 --> 00:14:32.880 align:start position:0% outreach media strategies if we're 00:14:32.880 --> 00:14:35.430 align:start position:0% outreach media strategies if we're putting<00:14:33.600> ads<00:14:34.000> out<00:14:34.320> flyering<00:14:34.880> that's<00:14:35.120> some 00:14:35.430 --> 00:14:35.440 align:start position:0% putting ads out flyering that's some 00:14:35.440 --> 00:14:37.509 align:start position:0% putting ads out flyering that's some public<00:14:35.760> outreach<00:14:36.320> work 00:14:37.509 --> 00:14:37.519 align:start position:0% public outreach work 00:14:37.519 --> 00:14:38.790 align:start position:0% public outreach work jack<00:14:37.839> anything<00:14:38.079> you<00:14:38.240> want<00:14:38.320> to<00:14:38.480> add<00:14:38.639> there 00:14:38.790 --> 00:14:38.800 align:start position:0% jack anything you want to add there 00:14:38.800 --> 00:14:42.829 align:start position:0% jack anything you want to add there before<00:14:39.040> i<00:14:39.120> go<00:14:39.279> to<00:14:39.360> the<00:14:39.440> next<00:14:39.680> question 00:14:42.829 --> 00:14:42.839 align:start position:0% 00:14:42.839 --> 00:14:45.750 align:start position:0% um<00:14:43.839> i<00:14:44.000> would<00:14:44.240> say<00:14:44.480> that<00:14:44.800> uh<00:14:45.040> you<00:14:45.199> know<00:14:45.360> some<00:14:45.600> of 00:14:45.750 --> 00:14:45.760 align:start position:0% um i would say that uh you know some of 00:14:45.760 --> 00:14:47.910 align:start position:0% um i would say that uh you know some of this<00:14:46.399> the<00:14:46.560> details<00:14:47.040> of<00:14:47.120> how<00:14:47.279> this<00:14:47.519> will<00:14:47.760> be 00:14:47.910 --> 00:14:47.920 align:start position:0% this the details of how this will be 00:14:47.920 --> 00:14:50.470 align:start position:0% this the details of how this will be worked<00:14:48.240> out<00:14:48.720> is<00:14:49.199> part<00:14:49.440> of<00:14:49.519> the<00:14:49.680> process<00:14:50.240> that 00:14:50.470 --> 00:14:50.480 align:start position:0% worked out is part of the process that 00:14:50.480 --> 00:14:52.790 align:start position:0% worked out is part of the process that we'll<00:14:51.199> be<00:14:51.360> going<00:14:51.680> through<00:14:52.160> at<00:14:52.320> the<00:14:52.399> beginning 00:14:52.790 --> 00:14:52.800 align:start position:0% we'll be going through at the beginning 00:14:52.800 --> 00:14:54.470 align:start position:0% we'll be going through at the beginning when<00:14:53.040> we<00:14:53.199> bring<00:14:53.440> all<00:14:53.600> the<00:14:53.760> consultants 00:14:54.470 --> 00:14:54.480 align:start position:0% when we bring all the consultants 00:14:54.480 --> 00:14:55.590 align:start position:0% when we bring all the consultants together 00:14:55.590 --> 00:14:55.600 align:start position:0% together 00:14:55.600 --> 00:14:58.069 align:start position:0% together so<00:14:56.079> um<00:14:56.800> we'll<00:14:57.040> shake<00:14:57.279> it<00:14:57.440> out<00:14:57.519> there<00:14:57.760> but<00:14:57.920> i 00:14:58.069 --> 00:14:58.079 align:start position:0% so um we'll shake it out there but i 00:14:58.079 --> 00:14:59.509 align:start position:0% so um we'll shake it out there but i think<00:14:58.240> that 00:14:59.509 --> 00:14:59.519 align:start position:0% think that 00:14:59.519 --> 00:15:00.790 align:start position:0% think that um 00:15:00.790 --> 00:15:00.800 align:start position:0% um 00:15:00.800 --> 00:15:01.750 align:start position:0% um the 00:15:01.750 --> 00:15:01.760 align:start position:0% the 00:15:01.760 --> 00:15:04.310 align:start position:0% the different<00:15:02.160> aspects<00:15:03.040> uh 00:15:04.310 --> 00:15:04.320 align:start position:0% different aspects uh 00:15:04.320 --> 00:15:07.430 align:start position:0% different aspects uh julia's<00:15:05.040> really<00:15:05.360> address<00:15:05.760> them<00:15:06.399> well<00:15:06.720> there 00:15:07.430 --> 00:15:07.440 align:start position:0% julia's really address them well there 00:15:07.440 --> 00:15:09.430 align:start position:0% julia's really address them well there and<00:15:07.680> we'll<00:15:07.920> follow<00:15:08.320> up<00:15:08.639> with 00:15:09.430 --> 00:15:09.440 align:start position:0% and we'll follow up with 00:15:09.440 --> 00:15:10.829 align:start position:0% and we'll follow up with written 00:15:10.829 --> 00:15:10.839 align:start position:0% written 00:15:10.839 --> 00:15:13.430 align:start position:0% written information<00:15:12.000> okay<00:15:12.240> thank<00:15:12.480> you 00:15:13.430 --> 00:15:13.440 align:start position:0% information okay thank you 00:15:13.440 --> 00:15:15.350 align:start position:0% information okay thank you um 00:15:15.350 --> 00:15:15.360 align:start position:0% um 00:15:15.360 --> 00:15:17.430 align:start position:0% um and<00:15:15.519> we<00:15:15.680> share<00:15:15.920> the<00:15:16.079> scopes<00:15:16.560> for<00:15:16.800> point<00:15:17.040> blue 00:15:17.430 --> 00:15:17.440 align:start position:0% and we share the scopes for point blue 00:15:17.440 --> 00:15:19.750 align:start position:0% and we share the scopes for point blue dr<00:15:17.839> king<00:15:18.240> and<00:15:18.480> marie<00:15:18.800> rainwater<00:15:19.519> great 00:15:19.750 --> 00:15:19.760 align:start position:0% dr king and marie rainwater great 00:15:19.760 --> 00:15:21.750 align:start position:0% dr king and marie rainwater great question<00:15:20.399> we<00:15:20.560> do<00:15:20.720> not<00:15:20.880> yet<00:15:21.120> have<00:15:21.360> scopes 00:15:21.750 --> 00:15:21.760 align:start position:0% question we do not yet have scopes 00:15:21.760 --> 00:15:23.430 align:start position:0% question we do not yet have scopes formalized<00:15:22.560> for 00:15:23.430 --> 00:15:23.440 align:start position:0% formalized for 00:15:23.440 --> 00:15:25.750 align:start position:0% formalized for dr<00:15:23.760> king<00:15:24.000> for<00:15:24.160> the<00:15:24.240> economic<00:15:24.720> analysis<00:15:25.600> we 00:15:25.750 --> 00:15:25.760 align:start position:0% dr king for the economic analysis we 00:15:25.760 --> 00:15:27.590 align:start position:0% dr king for the economic analysis we have<00:15:25.839> a<00:15:25.920> draft<00:15:26.320> scope<00:15:26.639> but<00:15:26.800> we<00:15:26.880> want<00:15:27.040> to<00:15:27.199> refine 00:15:27.590 --> 00:15:27.600 align:start position:0% have a draft scope but we want to refine 00:15:27.600 --> 00:15:29.749 align:start position:0% have a draft scope but we want to refine that<00:15:27.920> once<00:15:28.240> we<00:15:28.480> hire<00:15:28.880> a<00:15:29.040> firm<00:15:29.360> under<00:15:29.519> this 00:15:29.749 --> 00:15:29.759 align:start position:0% that once we hire a firm under this 00:15:29.759 --> 00:15:32.470 align:start position:0% that once we hire a firm under this current<00:15:30.079> rfp<00:15:30.639> so<00:15:30.800> we<00:15:30.880> can<00:15:31.120> ensure<00:15:31.680> so<00:15:31.839> you<00:15:31.920> will 00:15:32.470 --> 00:15:32.480 align:start position:0% current rfp so we can ensure so you will 00:15:32.480 --> 00:15:34.870 align:start position:0% current rfp so we can ensure so you will if<00:15:32.720> hired<00:15:33.120> you<00:15:33.199> would<00:15:33.360> actively<00:15:33.839> be<00:15:34.079> part<00:15:34.720> of 00:15:34.870 --> 00:15:34.880 align:start position:0% if hired you would actively be part of 00:15:34.880 --> 00:15:37.430 align:start position:0% if hired you would actively be part of confirming<00:15:35.360> that<00:15:35.519> scope<00:15:35.839> of<00:15:36.000> work<00:15:36.720> likewise 00:15:37.430 --> 00:15:37.440 align:start position:0% confirming that scope of work likewise 00:15:37.440 --> 00:15:38.870 align:start position:0% confirming that scope of work likewise for<00:15:37.680> point<00:15:37.920> blue 00:15:38.870 --> 00:15:38.880 align:start position:0% for point blue 00:15:38.880 --> 00:15:41.910 align:start position:0% for point blue the<00:15:39.199> ecological<00:15:40.079> analysis<00:15:40.800> has<00:15:41.120> not<00:15:41.360> yet<00:15:41.600> been 00:15:41.910 --> 00:15:41.920 align:start position:0% the ecological analysis has not yet been 00:15:41.920 --> 00:15:44.230 align:start position:0% the ecological analysis has not yet been scoped<00:15:42.320> or<00:15:42.480> contracted<00:15:43.120> so<00:15:43.360> again 00:15:44.230 --> 00:15:44.240 align:start position:0% scoped or contracted so again 00:15:44.240 --> 00:15:46.150 align:start position:0% scoped or contracted so again there's<00:15:44.560> the<00:15:44.720> opportunity<00:15:45.360> there<00:15:45.680> to<00:15:45.920> weigh 00:15:46.150 --> 00:15:46.160 align:start position:0% there's the opportunity there to weigh 00:15:46.160 --> 00:15:48.389 align:start position:0% there's the opportunity there to weigh in<00:15:46.399> and<00:15:46.480> help<00:15:46.720> shape<00:15:47.040> that<00:15:47.680> we<00:15:47.839> do<00:15:48.079> have<00:15:48.240> an 00:15:48.389 --> 00:15:48.399 align:start position:0% in and help shape that we do have an 00:15:48.399 --> 00:15:50.389 align:start position:0% in and help shape that we do have an existing<00:15:48.800> scope<00:15:49.120> for<00:15:49.279> point<00:15:49.519> blue<00:15:49.759> to<00:15:49.920> conduct 00:15:50.389 --> 00:15:50.399 align:start position:0% existing scope for point blue to conduct 00:15:50.399 --> 00:15:52.870 align:start position:0% existing scope for point blue to conduct a<00:15:50.639> cell<00:15:50.880> phone<00:15:51.199> locational<00:15:51.839> data<00:15:52.240> analysis 00:15:52.870 --> 00:15:52.880 align:start position:0% a cell phone locational data analysis 00:15:52.880 --> 00:15:55.350 align:start position:0% a cell phone locational data analysis which<00:15:53.120> is<00:15:53.199> helping<00:15:53.519> us<00:15:53.680> get<00:15:53.920> an<00:15:54.079> early<00:15:54.560> look 00:15:55.350 --> 00:15:55.360 align:start position:0% which is helping us get an early look 00:15:55.360 --> 00:15:57.910 align:start position:0% which is helping us get an early look at<00:15:55.680> who<00:15:56.079> our<00:15:56.240> beach<00:15:56.480> user<00:15:56.800> communities<00:15:57.360> are<00:15:57.680> at 00:15:57.910 --> 00:15:57.920 align:start position:0% at who our beach user communities are at 00:15:57.920 --> 00:16:00.629 align:start position:0% at who our beach user communities are at stinson<00:15:58.880> and<00:15:59.040> that<00:15:59.279> scope<00:15:59.920> yes<00:16:00.320> we<00:16:00.480> can 00:16:00.629 --> 00:16:00.639 align:start position:0% stinson and that scope yes we can 00:16:00.639 --> 00:16:02.150 align:start position:0% stinson and that scope yes we can provide<00:16:00.959> that 00:16:02.150 --> 00:16:02.160 align:start position:0% provide that 00:16:02.160 --> 00:16:05.590 align:start position:0% provide that um<00:16:02.639> rainwater<00:16:03.360> we<00:16:03.600> do<00:16:03.920> have<00:16:04.320> a 00:16:05.590 --> 00:16:05.600 align:start position:0% um rainwater we do have a 00:16:05.600 --> 00:16:07.189 align:start position:0% um rainwater we do have a task 00:16:07.189 --> 00:16:07.199 align:start position:0% task 00:16:07.199 --> 00:16:09.749 align:start position:0% task um 00:16:09.749 --> 00:16:09.759 align:start position:0% um 00:16:09.759 --> 00:16:11.590 align:start position:0% um i<00:16:09.920> could<00:16:10.079> provide<00:16:10.480> it<00:16:10.639> it's<00:16:10.880> it's 00:16:11.590 --> 00:16:11.600 align:start position:0% i could provide it it's it's 00:16:11.600 --> 00:16:13.189 align:start position:0% i could provide it it's it's it's<00:16:11.759> very<00:16:12.000> big<00:16:12.320> it's<00:16:12.560> what<00:16:12.720> i<00:16:12.800> said<00:16:12.959> you<00:16:13.040> know 00:16:13.189 --> 00:16:13.199 align:start position:0% it's very big it's what i said you know 00:16:13.199 --> 00:16:14.790 align:start position:0% it's very big it's what i said you know it's<00:16:13.279> just<00:16:13.440> buckets<00:16:13.839> of<00:16:14.000> available<00:16:14.480> time<00:16:14.720> to 00:16:14.790 --> 00:16:14.800 align:start position:0% it's just buckets of available time to 00:16:14.800 --> 00:16:16.389 align:start position:0% it's just buckets of available time to help<00:16:15.040> with<00:16:15.199> process<00:16:15.680> design<00:16:16.079> and<00:16:16.160> to<00:16:16.240> help 00:16:16.389 --> 00:16:16.399 align:start position:0% help with process design and to help 00:16:16.399 --> 00:16:17.910 align:start position:0% help with process design and to help with<00:16:16.560> facilitation<00:16:17.279> so<00:16:17.440> i<00:16:17.519> don't<00:16:17.759> think 00:16:17.910 --> 00:16:17.920 align:start position:0% with facilitation so i don't think 00:16:17.920 --> 00:16:19.990 align:start position:0% with facilitation so i don't think there's<00:16:18.720> a<00:16:18.880> large<00:16:19.120> amount<00:16:19.440> to<00:16:19.600> learn<00:16:19.839> from 00:16:19.990 --> 00:16:20.000 align:start position:0% there's a large amount to learn from 00:16:20.000 --> 00:16:21.030 align:start position:0% there's a large amount to learn from that<00:16:20.160> one 00:16:21.030 --> 00:16:21.040 align:start position:0% that one 00:16:21.040 --> 00:16:22.230 align:start position:0% that one i<00:16:21.199> can 00:16:22.230 --> 00:16:22.240 align:start position:0% i can 00:16:22.240 --> 00:16:24.870 align:start position:0% i can follow<00:16:22.639> up<00:16:22.880> on<00:16:23.040> that<00:16:23.360> okay 00:16:24.870 --> 00:16:24.880 align:start position:0% follow up on that okay 00:16:24.880 --> 00:16:28.550 align:start position:0% follow up on that okay thanks<00:16:25.199> more<00:16:25.440> questions<00:16:25.839> coming<00:16:26.160> in<00:16:26.240> this 00:16:28.550 --> 00:16:28.560 align:start position:0% 00:16:28.560 --> 00:16:30.150 align:start position:0% is<00:16:28.800> providing<00:16:29.199> an<00:16:29.360> approach<00:16:29.759> to<00:16:29.920> these 00:16:30.150 --> 00:16:30.160 align:start position:0% is providing an approach to these 00:16:30.160 --> 00:16:31.990 align:start position:0% is providing an approach to these different<00:16:30.480> facilitation<00:16:31.360> and<00:16:31.440> engagement 00:16:31.990 --> 00:16:32.000 align:start position:0% different facilitation and engagement 00:16:32.000 --> 00:16:33.269 align:start position:0% different facilitation and engagement ideas 00:16:33.269 --> 00:16:33.279 align:start position:0% ideas 00:16:33.279 --> 00:16:35.189 align:start position:0% ideas in<00:16:33.440> the<00:16:33.600> response<00:16:33.920> to<00:16:34.079> rfp<00:16:34.480> helpful<00:16:34.959> or<00:16:35.120> is 00:16:35.189 --> 00:16:35.199 align:start position:0% in the response to rfp helpful or is 00:16:35.199 --> 00:16:36.550 align:start position:0% in the response to rfp helpful or is that<00:16:35.360> something<00:16:35.680> that<00:16:35.839> is<00:16:35.920> meant<00:16:36.079> to<00:16:36.160> be<00:16:36.320> part 00:16:36.550 --> 00:16:36.560 align:start position:0% that something that is meant to be part 00:16:36.560 --> 00:16:38.710 align:start position:0% that something that is meant to be part of<00:16:36.880> or<00:16:37.120> oh<00:16:37.360> go<00:16:37.519> ahead<00:16:37.759> jack 00:16:38.710 --> 00:16:38.720 align:start position:0% of or oh go ahead jack 00:16:38.720 --> 00:16:40.710 align:start position:0% of or oh go ahead jack oh<00:16:38.959> no<00:16:39.519> i'm<00:16:39.759> just<00:16:39.920> saying<00:16:40.240> it<00:16:40.399> would<00:16:40.560> be 00:16:40.710 --> 00:16:40.720 align:start position:0% oh no i'm just saying it would be 00:16:40.720 --> 00:16:41.910 align:start position:0% oh no i'm just saying it would be helpful 00:16:41.910 --> 00:16:41.920 align:start position:0% helpful 00:16:41.920 --> 00:16:44.790 align:start position:0% helpful um<00:16:42.399> i<00:16:42.560> will<00:16:42.800> respond 00:16:44.790 --> 00:16:44.800 align:start position:0% um i will respond 00:16:44.800 --> 00:16:45.749 align:start position:0% um i will respond okay 00:16:45.749 --> 00:16:45.759 align:start position:0% okay 00:16:45.759 --> 00:16:49.509 align:start position:0% okay um 00:16:49.509 --> 00:16:49.519 align:start position:0% 00:16:49.519 --> 00:16:50.949 align:start position:0% providing<00:16:50.000> an<00:16:50.079> approach<00:16:50.320> to<00:16:50.399> facilitation 00:16:50.949 --> 00:16:50.959 align:start position:0% providing an approach to facilitation 00:16:50.959 --> 00:16:52.949 align:start position:0% providing an approach to facilitation and<00:16:51.120> engagement<00:16:51.519> ideas<00:16:51.920> if<00:16:52.000> you<00:16:52.160> have<00:16:52.399> ideas 00:16:52.949 --> 00:16:52.959 align:start position:0% and engagement ideas if you have ideas 00:16:52.959 --> 00:16:54.710 align:start position:0% and engagement ideas if you have ideas for<00:16:53.120> how<00:16:53.360> we<00:16:53.519> could<00:16:53.759> improve<00:16:54.399> our 00:16:54.710 --> 00:16:54.720 align:start position:0% for how we could improve our 00:16:54.720 --> 00:16:56.550 align:start position:0% for how we could improve our coordination<00:16:55.440> across 00:16:56.550 --> 00:16:56.560 align:start position:0% coordination across 00:16:56.560 --> 00:16:58.870 align:start position:0% coordination across these<00:16:56.800> different<00:16:57.279> engagement<00:16:57.920> like<00:16:58.079> we<00:16:58.240> have 00:16:58.870 --> 00:16:58.880 align:start position:0% these different engagement like we have 00:16:58.880 --> 00:17:01.189 align:start position:0% these different engagement like we have scope<00:16:59.279> facilitation<00:17:00.160> professional<00:17:01.040> but 00:17:01.189 --> 00:17:01.199 align:start position:0% scope facilitation professional but 00:17:01.199 --> 00:17:02.870 align:start position:0% scope facilitation professional but we're<00:17:01.360> over<00:17:01.519> here<00:17:01.759> running<00:17:02.000> public<00:17:02.320> meetings 00:17:02.870 --> 00:17:02.880 align:start position:0% we're over here running public meetings 00:17:02.880 --> 00:17:04.150 align:start position:0% we're over here running public meetings if<00:17:03.040> you<00:17:03.120> have<00:17:03.279> ideas<00:17:03.680> that<00:17:03.759> you're<00:17:03.839> like<00:17:04.000> hey 00:17:04.150 --> 00:17:04.160 align:start position:0% if you have ideas that you're like hey 00:17:04.160 --> 00:17:06.069 align:start position:0% if you have ideas that you're like hey this<00:17:04.400> would<00:17:04.480> be<00:17:04.559> a<00:17:04.640> really<00:17:04.880> strategic<00:17:05.360> way<00:17:05.839> to 00:17:06.069 --> 00:17:06.079 align:start position:0% this would be a really strategic way to 00:17:06.079 --> 00:17:08.069 align:start position:0% this would be a really strategic way to leverage<00:17:06.720> those<00:17:07.039> resources<00:17:07.520> and<00:17:07.600> do<00:17:07.760> a<00:17:07.839> better 00:17:08.069 --> 00:17:08.079 align:start position:0% leverage those resources and do a better 00:17:08.079 --> 00:17:09.909 align:start position:0% leverage those resources and do a better job<00:17:08.480> we<00:17:08.640> would<00:17:08.799> love<00:17:08.959> to<00:17:09.039> hear<00:17:09.280> it<00:17:09.439> please<00:17:09.679> do 00:17:09.909 --> 00:17:09.919 align:start position:0% job we would love to hear it please do 00:17:09.919 --> 00:17:12.390 align:start position:0% job we would love to hear it please do put<00:17:10.079> it<00:17:10.240> in<00:17:10.319> your<00:17:10.880> in<00:17:11.039> your<00:17:11.360> proposal 00:17:12.390 --> 00:17:12.400 align:start position:0% put it in your in your proposal 00:17:12.400 --> 00:17:15.590 align:start position:0% put it in your in your proposal um<00:17:13.120> that<00:17:13.439> said<00:17:14.240> with<00:17:14.400> the<00:17:14.559> early<00:17:14.959> team<00:17:15.199> kickoff 00:17:15.590 --> 00:17:15.600 align:start position:0% um that said with the early team kickoff 00:17:15.600 --> 00:17:17.350 align:start position:0% um that said with the early team kickoff that<00:17:15.760> will<00:17:16.000> be<00:17:16.160> a<00:17:16.240> detailed<00:17:16.720> discussion<00:17:17.199> so 00:17:17.350 --> 00:17:17.360 align:start position:0% that will be a detailed discussion so 00:17:17.360 --> 00:17:19.669 align:start position:0% that will be a detailed discussion so everyone<00:17:17.839> knows<00:17:18.319> what<00:17:18.480> we<00:17:18.640> arrive<00:17:19.039> at<00:17:19.280> as<00:17:19.520> a 00:17:19.669 --> 00:17:19.679 align:start position:0% everyone knows what we arrive at as a 00:17:19.679 --> 00:17:21.429 align:start position:0% everyone knows what we arrive at as a project<00:17:20.160> of<00:17:20.319> verb 00:17:21.429 --> 00:17:21.439 align:start position:0% project of verb 00:17:21.439 --> 00:17:23.189 align:start position:0% project of verb i<00:17:21.520> hope<00:17:21.760> that<00:17:21.919> answers<00:17:22.319> that<00:17:22.559> question<00:17:22.959> if<00:17:23.120> i 00:17:23.189 --> 00:17:23.199 align:start position:0% i hope that answers that question if i 00:17:23.199 --> 00:17:24.069 align:start position:0% i hope that answers that question if i didn't 00:17:24.069 --> 00:17:24.079 align:start position:0% didn't 00:17:24.079 --> 00:17:25.429 align:start position:0% didn't please<00:17:24.400> put<00:17:24.559> it<00:17:24.720> again<00:17:24.880> with<00:17:25.039> a<00:17:25.120> little<00:17:25.280> more 00:17:25.429 --> 00:17:25.439 align:start position:0% please put it again with a little more 00:17:25.439 --> 00:17:28.549 align:start position:0% please put it again with a little more clarification<00:17:26.480> in<00:17:26.720> the<00:17:26.880> chat<00:17:27.600> all<00:17:27.760> right<00:17:28.319> well 00:17:28.549 --> 00:17:28.559 align:start position:0% clarification in the chat all right well 00:17:28.559 --> 00:17:30.390 align:start position:0% clarification in the chat all right well the<00:17:28.640> cell<00:17:28.880> phone<00:17:29.039> data<00:17:29.360> be<00:17:29.520> purely<00:17:29.919> hot<00:17:30.080> spot 00:17:30.390 --> 00:17:30.400 align:start position:0% the cell phone data be purely hot spot 00:17:30.400 --> 00:17:32.230 align:start position:0% the cell phone data be purely hot spot density<00:17:30.799> information<00:17:31.600> showing<00:17:31.919> the<00:17:32.000> most 00:17:32.230 --> 00:17:32.240 align:start position:0% density information showing the most 00:17:32.240 --> 00:17:34.230 align:start position:0% density information showing the most highly<00:17:32.559> visited<00:17:32.960> locations 00:17:34.230 --> 00:17:34.240 align:start position:0% highly visited locations 00:17:34.240 --> 00:17:35.909 align:start position:0% highly visited locations or<00:17:34.480> would<00:17:34.640> it<00:17:34.880> include<00:17:35.200> information<00:17:35.760> that 00:17:35.909 --> 00:17:35.919 align:start position:0% or would it include information that 00:17:35.919 --> 00:17:38.230 align:start position:0% or would it include information that could<00:17:36.080> be<00:17:36.240> used<00:17:36.720> for<00:17:36.960> economic<00:17:37.440> valuation<00:17:38.080> or 00:17:38.230 --> 00:17:38.240 align:start position:0% could be used for economic valuation or 00:17:38.240 --> 00:17:40.950 align:start position:0% could be used for economic valuation or travel<00:17:38.640> pattern<00:17:39.039> analysis<00:17:40.080> such<00:17:40.320> as<00:17:40.480> origin 00:17:40.950 --> 00:17:40.960 align:start position:0% travel pattern analysis such as origin 00:17:40.960 --> 00:17:42.789 align:start position:0% travel pattern analysis such as origin and<00:17:41.039> destination<00:17:41.679> data<00:17:42.000> demographics 00:17:42.789 --> 00:17:42.799 align:start position:0% and destination data demographics 00:17:42.799 --> 00:17:44.630 align:start position:0% and destination data demographics awesome<00:17:43.200> question<00:17:43.919> yeah<00:17:44.240> i<00:17:44.320> don't<00:17:44.480> want<00:17:44.559> to 00:17:44.630 --> 00:17:44.640 align:start position:0% awesome question yeah i don't want to 00:17:44.640 --> 00:17:45.990 align:start position:0% awesome question yeah i don't want to take<00:17:44.799> too<00:17:44.960> much<00:17:45.120> of<00:17:45.280> our<00:17:45.440> time<00:17:45.600> today 00:17:45.990 --> 00:17:46.000 align:start position:0% take too much of our time today 00:17:46.000 --> 00:17:48.150 align:start position:0% take too much of our time today detailing<00:17:46.480> the<00:17:46.640> cell<00:17:46.880> phone<00:17:47.360> data<00:17:47.679> analysis 00:17:48.150 --> 00:17:48.160 align:start position:0% detailing the cell phone data analysis 00:17:48.160 --> 00:17:50.230 align:start position:0% detailing the cell phone data analysis but<00:17:48.640> it's<00:17:48.799> important<00:17:49.200> to<00:17:49.280> know<00:17:49.520> right 00:17:50.230 --> 00:17:50.240 align:start position:0% but it's important to know right 00:17:50.240 --> 00:17:53.590 align:start position:0% but it's important to know right the<00:17:50.400> study<00:17:50.720> does<00:17:50.960> both<00:17:51.600> so<00:17:51.840> it<00:17:52.000> does<00:17:52.400> do<00:17:52.799> a 00:17:53.590 --> 00:17:53.600 align:start position:0% the study does both so it does do a 00:17:53.600 --> 00:17:56.549 align:start position:0% the study does both so it does do a hot<00:17:53.840> spot<00:17:54.240> user<00:17:54.799> density<00:17:55.440> analysis<00:17:56.320> of 00:17:56.549 --> 00:17:56.559 align:start position:0% hot spot user density analysis of 00:17:56.559 --> 00:17:59.110 align:start position:0% hot spot user density analysis of spatial<00:17:57.039> patterns<00:17:57.520> of<00:17:57.679> usage<00:17:58.160> at<00:17:58.320> the<00:17:58.480> beach 00:17:59.110 --> 00:17:59.120 align:start position:0% spatial patterns of usage at the beach 00:17:59.120 --> 00:18:01.110 align:start position:0% spatial patterns of usage at the beach spatial<00:17:59.600> with<00:17:59.840> time<00:18:00.240> components<00:18:00.880> at<00:18:00.960> the 00:18:01.110 --> 00:18:01.120 align:start position:0% spatial with time components at the 00:18:01.120 --> 00:18:02.150 align:start position:0% spatial with time components at the beach 00:18:02.150 --> 00:18:02.160 align:start position:0% beach 00:18:02.160 --> 00:18:04.150 align:start position:0% beach we're<00:18:02.320> able<00:18:02.559> to<00:18:02.799> access<00:18:03.200> data<00:18:03.520> that<00:18:03.679> goes<00:18:03.919> back 00:18:04.150 --> 00:18:04.160 align:start position:0% we're able to access data that goes back 00:18:04.160 --> 00:18:05.669 align:start position:0% we're able to access data that goes back over<00:18:04.400> three<00:18:04.640> years<00:18:04.960> so<00:18:05.120> it's<00:18:05.280> a<00:18:05.280> pretty<00:18:05.520> big 00:18:05.669 --> 00:18:05.679 align:start position:0% over three years so it's a pretty big 00:18:05.679 --> 00:18:08.310 align:start position:0% over three years so it's a pretty big data<00:18:06.000> set<00:18:06.720> um<00:18:07.120> but<00:18:07.280> a<00:18:07.360> particular<00:18:07.840> interest<00:18:08.160> to 00:18:08.310 --> 00:18:08.320 align:start position:0% data set um but a particular interest to 00:18:08.320 --> 00:18:10.789 align:start position:0% data set um but a particular interest to the<00:18:08.400> county<00:18:09.200> the<00:18:09.440> data<00:18:09.840> allows<00:18:10.240> us<00:18:10.400> to<00:18:10.480> do<00:18:10.640> a 00:18:10.789 --> 00:18:10.799 align:start position:0% the county the data allows us to do a 00:18:10.799 --> 00:18:13.350 align:start position:0% the county the data allows us to do a point<00:18:11.120> of<00:18:11.280> origin<00:18:11.840> study<00:18:12.559> so<00:18:12.720> we're<00:18:12.960> able<00:18:13.200> to 00:18:13.350 --> 00:18:13.360 align:start position:0% point of origin study so we're able to 00:18:13.360 --> 00:18:16.390 align:start position:0% point of origin study so we're able to see<00:18:13.679> where<00:18:14.080> beach<00:18:14.400> users<00:18:14.799> are<00:18:15.039> coming<00:18:15.520> from 00:18:16.390 --> 00:18:16.400 align:start position:0% see where beach users are coming from 00:18:16.400 --> 00:18:18.230 align:start position:0% see where beach users are coming from and<00:18:16.559> that<00:18:16.720> lets<00:18:16.960> us<00:18:17.120> actually<00:18:17.520> get<00:18:18.080> the 00:18:18.230 --> 00:18:18.240 align:start position:0% and that lets us actually get the 00:18:18.240 --> 00:18:20.310 align:start position:0% and that lets us actually get the granularity<00:18:18.960> of<00:18:19.120> understanding<00:18:19.840> down<00:18:20.000> to<00:18:20.160> the 00:18:20.310 --> 00:18:20.320 align:start position:0% granularity of understanding down to the 00:18:20.320 --> 00:18:22.549 align:start position:0% granularity of understanding down to the census<00:18:20.720> block<00:18:21.600> level 00:18:22.549 --> 00:18:22.559 align:start position:0% census block level 00:18:22.559 --> 00:18:23.350 align:start position:0% census block level so 00:18:23.350 --> 00:18:23.360 align:start position:0% so 00:18:23.360 --> 00:18:26.150 align:start position:0% so pretty<00:18:23.679> good<00:18:24.400> um<00:18:24.799> and<00:18:24.960> we<00:18:25.679> really<00:18:25.919> need<00:18:26.080> to 00:18:26.150 --> 00:18:26.160 align:start position:0% pretty good um and we really need to 00:18:26.160 --> 00:18:27.909 align:start position:0% pretty good um and we really need to know<00:18:26.400> that<00:18:26.640> as<00:18:26.720> soon<00:18:26.960> as<00:18:27.120> we<00:18:27.280> can<00:18:27.520> so<00:18:27.679> we<00:18:27.840> can 00:18:27.909 --> 00:18:27.919 align:start position:0% know that as soon as we can so we can 00:18:27.919 --> 00:18:30.150 align:start position:0% know that as soon as we can so we can start<00:18:28.320> shaping<00:18:28.880> our<00:18:29.120> community<00:18:29.600> engagement 00:18:30.150 --> 00:18:30.160 align:start position:0% start shaping our community engagement 00:18:30.160 --> 00:18:32.150 align:start position:0% start shaping our community engagement approaches<00:18:30.640> and<00:18:30.799> really<00:18:31.520> get<00:18:31.760> out<00:18:31.919> there 00:18:32.150 --> 00:18:32.160 align:start position:0% approaches and really get out there 00:18:32.160 --> 00:18:33.909 align:start position:0% approaches and really get out there communicating<00:18:32.880> and<00:18:32.960> trying<00:18:33.120> to<00:18:33.280> engage<00:18:33.679> each 00:18:33.909 --> 00:18:33.919 align:start position:0% communicating and trying to engage each 00:18:33.919 --> 00:18:35.909 align:start position:0% communicating and trying to engage each users<00:18:34.400> who<00:18:34.559> are<00:18:34.720> not<00:18:35.200> you<00:18:35.360> know<00:18:35.440> as<00:18:35.600> easily 00:18:35.909 --> 00:18:35.919 align:start position:0% users who are not you know as easily 00:18:35.919 --> 00:18:38.070 align:start position:0% users who are not you know as easily identifiable<00:18:36.720> as<00:18:36.880> a<00:18:37.039> resident<00:18:37.520> or<00:18:37.600> a<00:18:37.679> business 00:18:38.070 --> 00:18:38.080 align:start position:0% identifiable as a resident or a business 00:18:38.080 --> 00:18:39.590 align:start position:0% identifiable as a resident or a business owner<00:18:38.320> at<00:18:38.480> stinson 00:18:39.590 --> 00:18:39.600 align:start position:0% owner at stinson 00:18:39.600 --> 00:18:40.870 align:start position:0% owner at stinson so<00:18:39.760> that 00:18:40.870 --> 00:18:40.880 align:start position:0% so that 00:18:40.880 --> 00:18:43.190 align:start position:0% so that first<00:18:41.280> piece<00:18:41.760> the<00:18:41.919> point<00:18:42.160> of<00:18:42.320> origin<00:18:42.720> data 00:18:43.190 --> 00:18:43.200 align:start position:0% first piece the point of origin data 00:18:43.200 --> 00:18:45.909 align:start position:0% first piece the point of origin data that<00:18:43.360> analysis<00:18:44.080> has<00:18:44.320> begun<00:18:45.120> and<00:18:45.360> we<00:18:45.520> expect 00:18:45.909 --> 00:18:45.919 align:start position:0% that analysis has begun and we expect 00:18:45.919 --> 00:18:49.590 align:start position:0% that analysis has begun and we expect some<00:18:46.160> preliminary<00:18:46.799> results<00:18:47.520> early<00:18:48.000> in<00:18:48.160> 2022 00:18:49.590 --> 00:18:49.600 align:start position:0% some preliminary results early in 2022 00:18:49.600 --> 00:18:51.830 align:start position:0% some preliminary results early in 2022 and<00:18:49.679> we're<00:18:49.840> gonna<00:18:50.080> wrap<00:18:50.320> it<00:18:50.559> out<00:18:50.799> by<00:18:51.440> about 00:18:51.830 --> 00:18:51.840 align:start position:0% and we're gonna wrap it out by about 00:18:51.840 --> 00:18:54.870 align:start position:0% and we're gonna wrap it out by about april<00:18:52.640> of<00:18:52.799> 2022<00:18:54.080> and<00:18:54.160> then<00:18:54.320> we'll<00:18:54.480> get<00:18:54.720> into 00:18:54.870 --> 00:18:54.880 align:start position:0% april of 2022 and then we'll get into 00:18:54.880 --> 00:18:57.510 align:start position:0% april of 2022 and then we'll get into the<00:18:55.039> hot<00:18:55.360> spot<00:18:56.320> user 00:18:57.510 --> 00:18:57.520 align:start position:0% the hot spot user 00:18:57.520 --> 00:19:00.470 align:start position:0% the hot spot user beach<00:18:58.000> visit<00:18:58.640> patterns<00:18:59.679> further<00:19:00.160> through 00:19:00.470 --> 00:19:00.480 align:start position:0% beach visit patterns further through 00:19:00.480 --> 00:19:02.390 align:start position:0% beach visit patterns further through 2022<00:19:01.200> with<00:19:01.360> the<00:19:01.440> whole<00:19:01.600> thing<00:19:01.840> wrapped<00:19:02.160> up<00:19:02.240> by 00:19:02.390 --> 00:19:02.400 align:start position:0% 2022 with the whole thing wrapped up by 00:19:02.400 --> 00:19:03.990 align:start position:0% 2022 with the whole thing wrapped up by default<00:19:03.200> so<00:19:03.360> that<00:19:03.520> should<00:19:03.679> be<00:19:03.760> able<00:19:03.919> to 00:19:03.990 --> 00:19:04.000 align:start position:0% default so that should be able to 00:19:04.000 --> 00:19:06.390 align:start position:0% default so that should be able to provide<00:19:04.559> some<00:19:04.799> good<00:19:05.039> content<00:19:05.679> over<00:19:06.000> to<00:19:06.160> the 00:19:06.390 --> 00:19:06.400 align:start position:0% provide some good content over to the 00:19:06.400 --> 00:19:08.630 align:start position:0% provide some good content over to the adaptation<00:19:07.039> planning<00:19:07.679> team<00:19:08.240> instead<00:19:08.559> of 00:19:08.630 --> 00:19:08.640 align:start position:0% adaptation planning team instead of 00:19:08.640 --> 00:19:11.510 align:start position:0% adaptation planning team instead of thinking<00:19:08.960> about<00:19:09.440> strategies<00:19:10.240> and<00:19:10.400> location 00:19:11.510 --> 00:19:11.520 align:start position:0% thinking about strategies and location 00:19:11.520 --> 00:19:16.950 align:start position:0% thinking about strategies and location beach<00:19:11.840> assets 00:19:16.950 --> 00:19:16.960 align:start position:0% 00:19:16.960 --> 00:19:19.510 align:start position:0% all<00:19:17.200> right<00:19:17.600> great<00:19:18.160> i<00:19:18.400> am<00:19:18.559> gonna<00:19:18.799> now<00:19:19.120> shift 00:19:19.510 --> 00:19:19.520 align:start position:0% all right great i am gonna now shift 00:19:19.520 --> 00:19:21.430 align:start position:0% all right great i am gonna now shift myself<00:19:20.000> over<00:19:20.320> to<00:19:20.640> feel<00:19:20.799> free<00:19:20.960> to<00:19:21.039> keep<00:19:21.200> using 00:19:21.430 --> 00:19:21.440 align:start position:0% myself over to feel free to keep using 00:19:21.440 --> 00:19:22.870 align:start position:0% myself over to feel free to keep using the<00:19:21.520> chat<00:19:21.760> please<00:19:22.000> but<00:19:22.160> i'm<00:19:22.240> gonna<00:19:22.480> shift 00:19:22.870 --> 00:19:22.880 align:start position:0% the chat please but i'm gonna shift 00:19:22.880 --> 00:19:26.470 align:start position:0% the chat please but i'm gonna shift myself<00:19:24.240> to<00:19:24.799> the 00:19:26.470 --> 00:19:26.480 align:start position:0% myself to the 00:19:26.480 --> 00:19:27.510 align:start position:0% myself to the um 00:19:27.510 --> 00:19:27.520 align:start position:0% um 00:19:27.520 --> 00:19:29.990 align:start position:0% um questions<00:19:28.080> that<00:19:28.240> were<00:19:28.400> received<00:19:28.960> by<00:19:29.360> email<00:19:29.840> i 00:19:29.990 --> 00:19:30.000 align:start position:0% questions that were received by email i 00:19:30.000 --> 00:19:32.870 align:start position:0% questions that were received by email i just<00:19:30.320> ended<00:19:30.640> my<00:19:30.880> screen<00:19:31.280> share 00:19:32.870 --> 00:19:32.880 align:start position:0% just ended my screen share 00:19:32.880 --> 00:19:36.390 align:start position:0% just ended my screen share so<00:19:33.039> we<00:19:33.200> did<00:19:33.360> have<00:19:33.520> a<00:19:33.679> question 00:19:36.390 --> 00:19:36.400 align:start position:0% 00:19:36.400 --> 00:19:38.950 align:start position:0% about<00:19:36.880> our<00:19:37.440> vast<00:19:37.840> array<00:19:38.160> of<00:19:38.240> consultants<00:19:38.880> and 00:19:38.950 --> 00:19:38.960 align:start position:0% about our vast array of consultants and 00:19:38.960 --> 00:19:40.870 align:start position:0% about our vast array of consultants and how<00:19:39.120> we<00:19:39.280> integrate<00:19:39.760> everything<00:19:40.160> together<00:19:40.799> i 00:19:40.870 --> 00:19:40.880 align:start position:0% how we integrate everything together i 00:19:40.880 --> 00:19:43.669 align:start position:0% how we integrate everything together i hope<00:19:41.120> i<00:19:41.200> clarified<00:19:41.760> that<00:19:42.000> to<00:19:42.400> to<00:19:42.799> reiterate<00:19:43.520> we 00:19:43.669 --> 00:19:43.679 align:start position:0% hope i clarified that to to reiterate we 00:19:43.679 --> 00:19:45.990 align:start position:0% hope i clarified that to to reiterate we will<00:19:43.919> start<00:19:44.160> with<00:19:44.240> a<00:19:44.320> kickoff<00:19:44.799> meeting<00:19:45.440> across 00:19:45.990 --> 00:19:46.000 align:start position:0% will start with a kickoff meeting across 00:19:46.000 --> 00:19:47.830 align:start position:0% will start with a kickoff meeting across all<00:19:46.240> of<00:19:46.320> the<00:19:46.480> county's<00:19:46.880> consultants<00:19:47.440> for<00:19:47.600> this 00:19:47.830 --> 00:19:47.840 align:start position:0% all of the county's consultants for this 00:19:47.840 --> 00:19:50.950 align:start position:0% all of the county's consultants for this project<00:19:48.400> to<00:19:48.559> clarify<00:19:49.120> roles<00:19:49.679> timelines 00:19:50.950 --> 00:19:50.960 align:start position:0% project to clarify roles timelines 00:19:50.960 --> 00:19:53.510 align:start position:0% project to clarify roles timelines where<00:19:51.200> scopes<00:19:51.679> overlap 00:19:53.510 --> 00:19:53.520 align:start position:0% where scopes overlap 00:19:53.520 --> 00:19:55.350 align:start position:0% where scopes overlap communications<00:19:54.240> are<00:19:54.400> so<00:19:54.640> critical<00:19:55.039> this<00:19:55.280> that 00:19:55.350 --> 00:19:55.360 align:start position:0% communications are so critical this that 00:19:55.360 --> 00:19:57.110 align:start position:0% communications are so critical this that we<00:19:55.520> have<00:19:55.679> a<00:19:55.760> unified<00:19:56.320> message<00:19:56.720> that<00:19:56.880> we<00:19:57.039> are 00:19:57.110 --> 00:19:57.120 align:start position:0% we have a unified message that we are 00:19:57.120 --> 00:19:58.710 align:start position:0% we have a unified message that we are bringing<00:19:57.440> to<00:19:57.600> the<00:19:57.679> public<00:19:58.080> across<00:19:58.480> all<00:19:58.559> these 00:19:58.710 --> 00:19:58.720 align:start position:0% bringing to the public across all these 00:19:58.720 --> 00:20:00.549 align:start position:0% bringing to the public across all these fronts<00:19:59.039> and<00:19:59.200> shared<00:19:59.600> language<00:20:00.080> so<00:20:00.240> that's 00:20:00.549 --> 00:20:00.559 align:start position:0% fronts and shared language so that's 00:20:00.559 --> 00:20:01.430 align:start position:0% fronts and shared language so that's really 00:20:01.430 --> 00:20:01.440 align:start position:0% really 00:20:01.440 --> 00:20:03.029 align:start position:0% really going<00:20:01.600> to<00:20:01.679> be<00:20:01.840> an<00:20:02.000> upfront<00:20:02.320> piece<00:20:02.559> of<00:20:02.720> getting 00:20:03.029 --> 00:20:03.039 align:start position:0% going to be an upfront piece of getting 00:20:03.039 --> 00:20:06.390 align:start position:0% going to be an upfront piece of getting all<00:20:03.200> of<00:20:03.280> our<00:20:03.440> consult<00:20:04.159> the<00:20:04.320> same<00:20:04.840> page<00:20:06.080> we<00:20:06.240> had 00:20:06.390 --> 00:20:06.400 align:start position:0% all of our consult the same page we had 00:20:06.400 --> 00:20:08.470 align:start position:0% all of our consult the same page we had a<00:20:06.480> question<00:20:07.120> how<00:20:07.280> does<00:20:07.440> the<00:20:07.600> county<00:20:08.000> see 00:20:08.470 --> 00:20:08.480 align:start position:0% a question how does the county see 00:20:08.480 --> 00:20:10.710 align:start position:0% a question how does the county see tangible<00:20:09.440> progress 00:20:10.710 --> 00:20:10.720 align:start position:0% tangible progress 00:20:10.720 --> 00:20:12.870 align:start position:0% tangible progress being<00:20:11.280> made<00:20:11.600> toward<00:20:12.000> a<00:20:12.159> complex<00:20:12.720> and 00:20:12.870 --> 00:20:12.880 align:start position:0% being made toward a complex and 00:20:12.880 --> 00:20:14.549 align:start position:0% being made toward a complex and challenging<00:20:13.440> goal<00:20:13.760> oh<00:20:13.919> yeah<00:20:14.080> i'll<00:20:14.240> put<00:20:14.400> the 00:20:14.549 --> 00:20:14.559 align:start position:0% challenging goal oh yeah i'll put the 00:20:14.559 --> 00:20:16.710 align:start position:0% challenging goal oh yeah i'll put the questions<00:20:14.960> in<00:20:15.039> the<00:20:15.200> chat 00:20:16.710 --> 00:20:16.720 align:start position:0% questions in the chat 00:20:16.720 --> 00:20:18.630 align:start position:0% questions in the chat let<00:20:16.880> me<00:20:16.960> do<00:20:17.120> that<00:20:17.280> right<00:20:17.520> now 00:20:18.630 --> 00:20:18.640 align:start position:0% let me do that right now 00:20:18.640 --> 00:20:20.630 align:start position:0% let me do that right now so<00:20:19.039> thanks<00:20:19.280> for<00:20:19.360> that<00:20:19.600> suggestion<00:20:20.159> whoever 00:20:20.630 --> 00:20:20.640 align:start position:0% so thanks for that suggestion whoever 00:20:20.640 --> 00:20:24.310 align:start position:0% so thanks for that suggestion whoever said<00:20:20.880> that 00:20:24.310 --> 00:20:24.320 align:start position:0% 00:20:24.320 --> 00:20:26.230 align:start position:0% there's<00:20:24.720> the<00:20:24.880> one<00:20:25.120> question<00:20:25.520> i<00:20:25.600> just<00:20:25.760> spoke<00:20:26.080> to 00:20:26.230 --> 00:20:26.240 align:start position:0% there's the one question i just spoke to 00:20:26.240 --> 00:20:28.870 align:start position:0% there's the one question i just spoke to about<00:20:26.720> how<00:20:26.880> do<00:20:26.960> we<00:20:27.120> coordinate<00:20:28.000> this<00:20:28.559> vast 00:20:28.870 --> 00:20:28.880 align:start position:0% about how do we coordinate this vast 00:20:28.880 --> 00:20:30.789 align:start position:0% about how do we coordinate this vast array<00:20:29.200> of<00:20:29.280> consultants 00:20:30.789 --> 00:20:30.799 align:start position:0% array of consultants 00:20:30.799 --> 00:20:33.029 align:start position:0% array of consultants the<00:20:31.120> next<00:20:31.600> question<00:20:32.000> that<00:20:32.240> i<00:20:32.320> am<00:20:32.480> going<00:20:32.799> to 00:20:33.029 --> 00:20:33.039 align:start position:0% the next question that i am going to 00:20:33.039 --> 00:20:35.190 align:start position:0% the next question that i am going to address 00:20:35.190 --> 00:20:35.200 align:start position:0% address 00:20:35.200 --> 00:20:37.270 align:start position:0% address how<00:20:35.360> does<00:20:35.600> the<00:20:35.760> county<00:20:36.240> see<00:20:36.559> tangible 00:20:37.270 --> 00:20:37.280 align:start position:0% how does the county see tangible 00:20:37.280 --> 00:20:39.909 align:start position:0% how does the county see tangible progress<00:20:38.159> being<00:20:38.400> made<00:20:38.720> toward<00:20:38.960> a<00:20:39.200> complex<00:20:39.760> and 00:20:39.909 --> 00:20:39.919 align:start position:0% progress being made toward a complex and 00:20:39.919 --> 00:20:42.230 align:start position:0% progress being made toward a complex and challenging<00:20:40.480> goal<00:20:41.200> of<00:20:41.360> substantial<00:20:42.000> public 00:20:42.230 --> 00:20:42.240 align:start position:0% challenging goal of substantial public 00:20:42.240 --> 00:20:44.470 align:start position:0% challenging goal of substantial public involvement<00:20:43.039> in<00:20:43.200> a<00:20:43.280> three-year<00:20:43.679> time<00:20:43.919> frame 00:20:44.470 --> 00:20:44.480 align:start position:0% involvement in a three-year time frame 00:20:44.480 --> 00:20:45.510 align:start position:0% involvement in a three-year time frame yeah 00:20:45.510 --> 00:20:45.520 align:start position:0% yeah 00:20:45.520 --> 00:20:47.430 align:start position:0% yeah i<00:20:45.600> like<00:20:45.760> this<00:20:46.000> phrase<00:20:46.240> jack<00:20:46.559> says<00:20:46.880> it's<00:20:47.120> gonna 00:20:47.430 --> 00:20:47.440 align:start position:0% i like this phrase jack says it's gonna 00:20:47.440 --> 00:20:49.590 align:start position:0% i like this phrase jack says it's gonna be<00:20:47.600> a<00:20:47.760> trick<00:20:48.240> right<00:20:48.559> we<00:20:48.720> have<00:20:48.880> a<00:20:48.960> lot<00:20:49.200> to<00:20:49.280> do<00:20:49.440> but 00:20:49.590 --> 00:20:49.600 align:start position:0% be a trick right we have a lot to do but 00:20:49.600 --> 00:20:51.590 align:start position:0% be a trick right we have a lot to do but we<00:20:49.760> do<00:20:49.919> have<00:20:50.080> a<00:20:50.240> sense<00:20:50.480> of<00:20:50.640> what<00:20:50.880> we<00:20:51.039> mean<00:20:51.280> by 00:20:51.590 --> 00:20:51.600 align:start position:0% we do have a sense of what we mean by 00:20:51.600 --> 00:20:54.070 align:start position:0% we do have a sense of what we mean by tangible<00:20:52.159> progress<00:20:52.960> i<00:20:53.039> think<00:20:53.280> it's<00:20:53.440> really 00:20:54.070 --> 00:20:54.080 align:start position:0% tangible progress i think it's really 00:20:54.080 --> 00:20:55.750 align:start position:0% tangible progress i think it's really you<00:20:54.159> know<00:20:54.559> threefold<00:20:55.120> things<00:20:55.440> and<00:20:55.520> then<00:20:55.679> i'll 00:20:55.750 --> 00:20:55.760 align:start position:0% you know threefold things and then i'll 00:20:55.760 --> 00:20:57.350 align:start position:0% you know threefold things and then i'll turn<00:20:56.000> it<00:20:56.159> over<00:20:56.320> to<00:20:56.480> jack 00:20:57.350 --> 00:20:57.360 align:start position:0% turn it over to jack 00:20:57.360 --> 00:20:59.029 align:start position:0% turn it over to jack i<00:20:57.600> see<00:20:57.840> it<00:20:58.080> as 00:20:59.029 --> 00:20:59.039 align:start position:0% i see it as 00:20:59.039 --> 00:21:00.549 align:start position:0% i see it as tangible<00:20:59.440> progress 00:21:00.549 --> 00:21:00.559 align:start position:0% tangible progress 00:21:00.559 --> 00:21:04.149 align:start position:0% tangible progress is<00:21:01.200> our<00:21:01.440> process<00:21:02.240> supports<00:21:02.880> informed<00:21:03.919> and 00:21:04.149 --> 00:21:04.159 align:start position:0% is our process supports informed and 00:21:04.159 --> 00:21:07.270 align:start position:0% is our process supports informed and sustained<00:21:04.880> engagement<00:21:05.840> of<00:21:06.080> a<00:21:06.159> diversity<00:21:07.200> of 00:21:07.270 --> 00:21:07.280 align:start position:0% sustained engagement of a diversity of 00:21:07.280 --> 00:21:09.110 align:start position:0% sustained engagement of a diversity of stinson<00:21:07.679> beach<00:21:07.919> stakeholders<00:21:08.720> in<00:21:08.880> an 00:21:09.110 --> 00:21:09.120 align:start position:0% stinson beach stakeholders in an 00:21:09.120 --> 00:21:11.430 align:start position:0% stinson beach stakeholders in an adaptation<00:21:09.679> planning<00:21:10.080> process<00:21:10.880> over<00:21:11.200> three 00:21:11.430 --> 00:21:11.440 align:start position:0% adaptation planning process over three 00:21:11.440 --> 00:21:12.549 align:start position:0% adaptation planning process over three years 00:21:12.549 --> 00:21:12.559 align:start position:0% years 00:21:12.559 --> 00:21:14.470 align:start position:0% years so<00:21:12.880> we've<00:21:13.120> gotten<00:21:13.520> people 00:21:14.470 --> 00:21:14.480 align:start position:0% so we've gotten people 00:21:14.480 --> 00:21:16.470 align:start position:0% so we've gotten people we've<00:21:14.960> developed<00:21:15.440> a<00:21:15.600> shared<00:21:16.000> level<00:21:16.320> of 00:21:16.470 --> 00:21:16.480 align:start position:0% we've developed a shared level of 00:21:16.480 --> 00:21:18.870 align:start position:0% we've developed a shared level of knowledge<00:21:17.360> and<00:21:17.520> they're<00:21:17.840> still<00:21:18.080> at<00:21:18.159> the<00:21:18.400> table 00:21:18.870 --> 00:21:18.880 align:start position:0% knowledge and they're still at the table 00:21:18.880 --> 00:21:21.270 align:start position:0% knowledge and they're still at the table and<00:21:19.039> engaging<00:21:19.760> and 00:21:21.270 --> 00:21:21.280 align:start position:0% and engaging and 00:21:21.280 --> 00:21:23.270 align:start position:0% and engaging and feeling<00:21:21.679> involved<00:21:22.240> and<00:21:22.400> heard 00:21:23.270 --> 00:21:23.280 align:start position:0% feeling involved and heard 00:21:23.280 --> 00:21:25.270 align:start position:0% feeling involved and heard three<00:21:23.520> years<00:21:23.760> in<00:21:24.320> um<00:21:24.559> and<00:21:24.720> i<00:21:24.799> think<00:21:24.960> that's 00:21:25.270 --> 00:21:25.280 align:start position:0% three years in um and i think that's 00:21:25.280 --> 00:21:26.549 align:start position:0% three years in um and i think that's that's<00:21:25.600> that's<00:21:25.840> a<00:21:25.919> pretty<00:21:26.159> big<00:21:26.320> goal<00:21:26.480> and 00:21:26.549 --> 00:21:26.559 align:start position:0% that's that's a pretty big goal and 00:21:26.559 --> 00:21:28.070 align:start position:0% that's that's a pretty big goal and that'd<00:21:26.720> be<00:21:26.799> a<00:21:26.880> big<00:21:27.120> progress 00:21:28.070 --> 00:21:28.080 align:start position:0% that'd be a big progress 00:21:28.080 --> 00:21:29.430 align:start position:0% that'd be a big progress a<00:21:28.320> second<00:21:28.640> thing 00:21:29.430 --> 00:21:29.440 align:start position:0% a second thing 00:21:29.440 --> 00:21:30.390 align:start position:0% a second thing um 00:21:30.390 --> 00:21:30.400 align:start position:0% um 00:21:30.400 --> 00:21:32.630 align:start position:0% um tangible<00:21:30.960> progress<00:21:31.600> would<00:21:31.840> be 00:21:32.630 --> 00:21:32.640 align:start position:0% tangible progress would be 00:21:32.640 --> 00:21:34.230 align:start position:0% tangible progress would be a<00:21:32.960> clear 00:21:34.230 --> 00:21:34.240 align:start position:0% a clear 00:21:34.240 --> 00:21:36.630 align:start position:0% a clear documentable<00:21:35.679> quantitative<00:21:36.480> and 00:21:36.630 --> 00:21:36.640 align:start position:0% documentable quantitative and 00:21:36.640 --> 00:21:38.710 align:start position:0% documentable quantitative and qualitative<00:21:37.360> understanding<00:21:38.320> of<00:21:38.480> how 00:21:38.710 --> 00:21:38.720 align:start position:0% qualitative understanding of how 00:21:38.720 --> 00:21:41.350 align:start position:0% qualitative understanding of how specific<00:21:39.440> adaptation<00:21:40.159> strategies 00:21:41.350 --> 00:21:41.360 align:start position:0% specific adaptation strategies 00:21:41.360 --> 00:21:44.310 align:start position:0% specific adaptation strategies might<00:21:41.600> perform<00:21:42.080> over<00:21:42.400> time<00:21:43.200> for<00:21:43.360> the<00:21:43.520> specific 00:21:44.310 --> 00:21:44.320 align:start position:0% might perform over time for the specific 00:21:44.320 --> 00:21:46.549 align:start position:0% might perform over time for the specific coastal<00:21:44.720> hazard<00:21:45.120> conditions<00:21:45.919> at<00:21:46.080> stinton 00:21:46.549 --> 00:21:46.559 align:start position:0% coastal hazard conditions at stinton 00:21:46.559 --> 00:21:47.430 align:start position:0% coastal hazard conditions at stinton beach 00:21:47.430 --> 00:21:47.440 align:start position:0% beach 00:21:47.440 --> 00:21:49.909 align:start position:0% beach so<00:21:48.000> starting<00:21:48.400> today<00:21:48.960> we<00:21:49.039> have<00:21:49.200> a<00:21:49.360> lot<00:21:49.600> of<00:21:49.679> good 00:21:49.909 --> 00:21:49.919 align:start position:0% so starting today we have a lot of good 00:21:49.919 --> 00:21:52.630 align:start position:0% so starting today we have a lot of good data<00:21:50.799> we've<00:21:50.960> got<00:21:51.200> a<00:21:51.280> vulnerability<00:21:51.919> analysis 00:21:52.630 --> 00:21:52.640 align:start position:0% data we've got a vulnerability analysis 00:21:52.640 --> 00:21:55.430 align:start position:0% data we've got a vulnerability analysis that<00:21:53.039> identified<00:21:53.600> the<00:21:53.760> assets<00:21:54.240> at<00:21:54.480> risk 00:21:55.430 --> 00:21:55.440 align:start position:0% that identified the assets at risk 00:21:55.440 --> 00:21:57.190 align:start position:0% that identified the assets at risk looked<00:21:55.679> at<00:21:55.840> sea<00:21:56.000> level<00:21:56.400> some<00:21:56.640> sea<00:21:56.799> level<00:21:57.039> rise 00:21:57.190 --> 00:21:57.200 align:start position:0% looked at sea level some sea level rise 00:21:57.200 --> 00:21:59.669 align:start position:0% looked at sea level some sea level rise scenarios<00:21:58.240> we<00:21:58.400> had<00:21:58.640> adaptation<00:21:59.280> planning 00:21:59.669 --> 00:21:59.679 align:start position:0% scenarios we had adaptation planning 00:21:59.679 --> 00:22:02.870 align:start position:0% scenarios we had adaptation planning that<00:21:59.919> broadly<00:22:00.400> spoke<00:22:00.720> to<00:22:00.880> some<00:22:01.120> county<00:22:01.600> values 00:22:02.870 --> 00:22:02.880 align:start position:0% that broadly spoke to some county values 00:22:02.880 --> 00:22:05.750 align:start position:0% that broadly spoke to some county values areas<00:22:03.280> of<00:22:03.440> opportunity<00:22:04.400> possible<00:22:05.039> policy<00:22:05.600> and 00:22:05.750 --> 00:22:05.760 align:start position:0% areas of opportunity possible policy and 00:22:05.760 --> 00:22:07.750 align:start position:0% areas of opportunity possible policy and project<00:22:06.320> levers 00:22:07.750 --> 00:22:07.760 align:start position:0% project levers 00:22:07.760 --> 00:22:09.430 align:start position:0% project levers tangible<00:22:08.240> progress<00:22:08.640> would<00:22:08.799> be<00:22:08.960> starting<00:22:09.280> to 00:22:09.430 --> 00:22:09.440 align:start position:0% tangible progress would be starting to 00:22:09.440 --> 00:22:12.310 align:start position:0% tangible progress would be starting to dial<00:22:09.919> that<00:22:10.159> down<00:22:10.559> really<00:22:11.120> specific<00:22:11.840> to<00:22:12.159> the 00:22:12.310 --> 00:22:12.320 align:start position:0% dial that down really specific to the 00:22:12.320 --> 00:22:14.789 align:start position:0% dial that down really specific to the stinson<00:22:12.799> beach<00:22:13.280> context 00:22:14.789 --> 00:22:14.799 align:start position:0% stinson beach context 00:22:14.799 --> 00:22:16.470 align:start position:0% stinson beach context and<00:22:14.880> then<00:22:15.039> the<00:22:15.200> third<00:22:15.520> point<00:22:15.840> to<00:22:16.000> me<00:22:16.159> that 00:22:16.470 --> 00:22:16.480 align:start position:0% and then the third point to me that 00:22:16.480 --> 00:22:18.149 align:start position:0% and then the third point to me that tangible<00:22:16.960> progress 00:22:18.149 --> 00:22:18.159 align:start position:0% tangible progress 00:22:18.159 --> 00:22:19.270 align:start position:0% tangible progress is<00:22:18.400> having 00:22:19.270 --> 00:22:19.280 align:start position:0% is having 00:22:19.280 --> 00:22:21.190 align:start position:0% is having demonstrated<00:22:20.000> experience<00:22:20.640> working<00:22:20.960> with 00:22:21.190 --> 00:22:21.200 align:start position:0% demonstrated experience working with 00:22:21.200 --> 00:22:23.430 align:start position:0% demonstrated experience working with adaptation<00:22:21.840> pathways<00:22:22.400> planning<00:22:22.880> for<00:22:23.039> coastal 00:22:23.430 --> 00:22:23.440 align:start position:0% adaptation pathways planning for coastal 00:22:23.440 --> 00:22:25.270 align:start position:0% adaptation pathways planning for coastal hazards<00:22:23.840> in<00:22:23.919> marin<00:22:24.240> county 00:22:25.270 --> 00:22:25.280 align:start position:0% hazards in marin county 00:22:25.280 --> 00:22:26.950 align:start position:0% hazards in marin county i<00:22:25.360> think<00:22:25.520> that<00:22:25.520> that<00:22:26.000> is<00:22:26.159> going<00:22:26.240> to<00:22:26.320> be<00:22:26.559> a<00:22:26.720> real 00:22:26.950 --> 00:22:26.960 align:start position:0% i think that that is going to be a real 00:22:26.960 --> 00:22:29.190 align:start position:0% i think that that is going to be a real point<00:22:27.200> of<00:22:27.360> progress<00:22:27.840> for<00:22:28.000> us<00:22:28.400> thinking<00:22:28.799> more 00:22:29.190 --> 00:22:29.200 align:start position:0% point of progress for us thinking more 00:22:29.200 --> 00:22:30.149 align:start position:0% point of progress for us thinking more about 00:22:30.149 --> 00:22:30.159 align:start position:0% about 00:22:30.159 --> 00:22:32.310 align:start position:0% about what<00:22:30.400> our<00:22:30.799> decision<00:22:31.280> timelines<00:22:31.840> are<00:22:32.080> and<00:22:32.159> our 00:22:32.310 --> 00:22:32.320 align:start position:0% what our decision timelines are and our 00:22:32.320 --> 00:22:33.909 align:start position:0% what our decision timelines are and our trigger<00:22:32.720> points<00:22:32.960> for<00:22:33.120> adaptation<00:22:33.760> that's 00:22:33.909 --> 00:22:33.919 align:start position:0% trigger points for adaptation that's 00:22:33.919 --> 00:22:35.350 align:start position:0% trigger points for adaptation that's where<00:22:34.080> we<00:22:34.240> have<00:22:34.400> some<00:22:34.559> growth<00:22:34.880> this<00:22:35.120> can<00:22:35.280> be 00:22:35.350 --> 00:22:35.360 align:start position:0% where we have some growth this can be 00:22:35.360 --> 00:22:37.830 align:start position:0% where we have some growth this can be really<00:22:35.600> valuable<00:22:36.320> so<00:22:36.720> jack<00:22:37.039> over<00:22:37.200> to<00:22:37.360> you<00:22:37.520> on 00:22:37.830 --> 00:22:37.840 align:start position:0% really valuable so jack over to you on 00:22:37.840 --> 00:22:40.070 align:start position:0% really valuable so jack over to you on tangible<00:22:38.320> progress 00:22:40.070 --> 00:22:40.080 align:start position:0% tangible progress 00:22:40.080 --> 00:22:41.510 align:start position:0% tangible progress i<00:22:40.240> think<00:22:40.480> the 00:22:41.510 --> 00:22:41.520 align:start position:0% i think the 00:22:41.520 --> 00:22:43.590 align:start position:0% i think the main<00:22:41.760> thing<00:22:42.000> that<00:22:42.159> we're<00:22:42.320> trying<00:22:42.640> to<00:22:42.880> achieve 00:22:43.590 --> 00:22:43.600 align:start position:0% main thing that we're trying to achieve 00:22:43.600 --> 00:22:45.190 align:start position:0% main thing that we're trying to achieve is 00:22:45.190 --> 00:22:45.200 align:start position:0% is 00:22:45.200 --> 00:22:46.870 align:start position:0% is let<00:22:45.440> people<00:22:45.840> know 00:22:46.870 --> 00:22:46.880 align:start position:0% let people know 00:22:46.880 --> 00:22:49.350 align:start position:0% let people know what's<00:22:47.200> coming<00:22:47.520> down<00:22:47.760> the<00:22:48.000> pike<00:22:48.320> at<00:22:48.480> them 00:22:49.350 --> 00:22:49.360 align:start position:0% what's coming down the pike at them 00:22:49.360 --> 00:22:52.830 align:start position:0% what's coming down the pike at them so<00:22:49.520> there's<00:22:49.840> a<00:22:50.000> common<00:22:50.400> understanding 00:22:52.830 --> 00:22:52.840 align:start position:0% so there's a common understanding 00:22:52.840 --> 00:22:54.390 align:start position:0% so there's a common understanding among 00:22:54.390 --> 00:22:54.400 align:start position:0% among 00:22:54.400 --> 00:22:57.590 align:start position:0% among the<00:22:54.640> entire<00:22:55.120> community<00:22:56.159> within<00:22:56.640> and<00:22:56.799> without 00:22:57.590 --> 00:22:57.600 align:start position:0% the entire community within and without 00:22:57.600 --> 00:23:00.630 align:start position:0% the entire community within and without the<00:22:57.840> area<00:22:58.400> of<00:22:58.880> stinson<00:22:59.440> beach 00:23:00.630 --> 00:23:00.640 align:start position:0% the area of stinson beach 00:23:00.640 --> 00:23:01.669 align:start position:0% the area of stinson beach uh 00:23:01.669 --> 00:23:01.679 align:start position:0% uh 00:23:01.679 --> 00:23:03.750 align:start position:0% uh and<00:23:01.919> then 00:23:03.750 --> 00:23:03.760 align:start position:0% and then 00:23:03.760 --> 00:23:05.430 align:start position:0% and then take<00:23:04.080> that 00:23:05.430 --> 00:23:05.440 align:start position:0% take that 00:23:05.440 --> 00:23:06.950 align:start position:0% take that and<00:23:05.679> let<00:23:05.840> them<00:23:06.080> know<00:23:06.320> about<00:23:06.559> what<00:23:06.799> the 00:23:06.950 --> 00:23:06.960 align:start position:0% and let them know about what the 00:23:06.960 --> 00:23:10.230 align:start position:0% and let them know about what the possibilities<00:23:08.320> are<00:23:08.960> for<00:23:09.360> for<00:23:09.600> dealing<00:23:10.000> with 00:23:10.230 --> 00:23:10.240 align:start position:0% possibilities are for for dealing with 00:23:10.240 --> 00:23:12.630 align:start position:0% possibilities are for for dealing with that<00:23:10.880> that<00:23:11.120> situation<00:23:11.840> that's<00:23:12.080> coming<00:23:12.480> at 00:23:12.630 --> 00:23:12.640 align:start position:0% that that situation that's coming at 00:23:12.640 --> 00:23:15.830 align:start position:0% that that situation that's coming at them<00:23:13.360> and<00:23:13.520> what<00:23:13.760> those<00:23:14.080> alternatives<00:23:14.960> are 00:23:15.830 --> 00:23:15.840 align:start position:0% them and what those alternatives are 00:23:15.840 --> 00:23:18.149 align:start position:0% them and what those alternatives are so<00:23:16.080> that<00:23:16.799> we 00:23:18.149 --> 00:23:18.159 align:start position:0% so that we 00:23:18.159 --> 00:23:19.029 align:start position:0% so that we you<00:23:18.320> know 00:23:19.029 --> 00:23:19.039 align:start position:0% you know 00:23:19.039 --> 00:23:22.470 align:start position:0% you know people<00:23:19.360> can<00:23:19.520> make<00:23:20.320> informed<00:23:21.039> choices<00:23:21.919> about 00:23:22.470 --> 00:23:22.480 align:start position:0% people can make informed choices about 00:23:22.480 --> 00:23:25.590 align:start position:0% people can make informed choices about what<00:23:22.640> they<00:23:22.799> want<00:23:23.039> to<00:23:23.200> do<00:23:23.760> going<00:23:24.159> forward 00:23:25.590 --> 00:23:25.600 align:start position:0% what they want to do going forward 00:23:25.600 --> 00:23:28.870 align:start position:0% what they want to do going forward um<00:23:26.320> that's<00:23:26.799> that's<00:23:27.120> my<00:23:27.440> feeling<00:23:28.080> um 00:23:28.870 --> 00:23:28.880 align:start position:0% um that's that's my feeling um 00:23:28.880 --> 00:23:30.149 align:start position:0% um that's that's my feeling um and<00:23:29.280> uh 00:23:30.149 --> 00:23:30.159 align:start position:0% and uh 00:23:30.159 --> 00:23:32.230 align:start position:0% and uh certainly<00:23:30.799> i 00:23:32.230 --> 00:23:32.240 align:start position:0% certainly i 00:23:32.240 --> 00:23:34.549 align:start position:0% certainly i we'd<00:23:32.720> love<00:23:32.960> to<00:23:33.120> hear<00:23:33.360> your 00:23:34.549 --> 00:23:34.559 align:start position:0% we'd love to hear your 00:23:34.559 --> 00:23:37.750 align:start position:0% we'd love to hear your uh<00:23:35.200> your<00:23:35.440> take<00:23:35.679> on<00:23:35.840> that<00:23:36.080> on<00:23:36.320> that<00:23:36.640> issue 00:23:37.750 --> 00:23:37.760 align:start position:0% uh your take on that on that issue 00:23:37.760 --> 00:23:42.390 align:start position:0% uh your take on that on that issue so 00:23:42.390 --> 00:23:42.400 align:start position:0% 00:23:42.400 --> 00:23:44.549 align:start position:0% all<00:23:42.559> right<00:23:42.720> next<00:23:43.039> question<00:23:43.679> i'm<00:23:43.840> sure<00:23:44.080> jack 00:23:44.549 --> 00:23:44.559 align:start position:0% all right next question i'm sure jack 00:23:44.559 --> 00:23:46.310 align:start position:0% all right next question i'm sure jack just<00:23:44.880> clarified<00:23:45.440> everything<00:23:45.840> beautiful<00:23:46.240> and 00:23:46.310 --> 00:23:46.320 align:start position:0% just clarified everything beautiful and 00:23:46.320 --> 00:23:48.149 align:start position:0% just clarified everything beautiful and i<00:23:46.400> can't<00:23:46.559> wait<00:23:46.720> to<00:23:46.880> hear<00:23:47.120> it<00:23:47.200> in<00:23:47.279> the<00:23:47.360> recording 00:23:48.149 --> 00:23:48.159 align:start position:0% i can't wait to hear it in the recording 00:23:48.159 --> 00:23:48.950 align:start position:0% i can't wait to hear it in the recording so 00:23:48.950 --> 00:23:48.960 align:start position:0% so 00:23:48.960 --> 00:23:50.789 align:start position:0% so what<00:23:49.279> level<00:23:49.520> of<00:23:49.679> engineering<00:23:50.159> detail<00:23:50.640> is 00:23:50.789 --> 00:23:50.799 align:start position:0% what level of engineering detail is 00:23:50.799 --> 00:23:52.950 align:start position:0% what level of engineering detail is expected<00:23:51.440> will<00:23:51.679> conceptual<00:23:52.320> models<00:23:52.640> be<00:23:52.799> the 00:23:52.950 --> 00:23:52.960 align:start position:0% expected will conceptual models be the 00:23:52.960 --> 00:23:55.990 align:start position:0% expected will conceptual models be the expectation<00:23:53.679> or<00:23:53.919> more<00:23:54.159> detailed<00:23:54.640> plan<00:23:54.960> sets 00:23:55.990 --> 00:23:56.000 align:start position:0% expectation or more detailed plan sets 00:23:56.000 --> 00:23:57.909 align:start position:0% expectation or more detailed plan sets so<00:23:56.240> we<00:23:56.480> are<00:23:56.640> very<00:23:56.880> aware<00:23:57.200> this<00:23:57.360> is<00:23:57.440> a<00:23:57.520> limited 00:23:57.909 --> 00:23:57.919 align:start position:0% so we are very aware this is a limited 00:23:57.919 --> 00:24:00.070 align:start position:0% so we are very aware this is a limited budget<00:23:58.320> for<00:23:58.480> what<00:23:58.640> we<00:23:58.799> are<00:23:58.960> asking<00:23:59.760> and 00:24:00.070 --> 00:24:00.080 align:start position:0% budget for what we are asking and 00:24:00.080 --> 00:24:01.750 align:start position:0% budget for what we are asking and conceptual<00:24:00.640> designs<00:24:01.039> would<00:24:01.200> be<00:24:01.360> the<00:24:01.440> level 00:24:01.750 --> 00:24:01.760 align:start position:0% conceptual designs would be the level 00:24:01.760 --> 00:24:03.110 align:start position:0% conceptual designs would be the level that<00:24:01.919> we<00:24:02.080> would<00:24:02.240> expect<00:24:02.480> to<00:24:02.640> resolve<00:24:02.960> from 00:24:03.110 --> 00:24:03.120 align:start position:0% that we would expect to resolve from 00:24:03.120 --> 00:24:04.710 align:start position:0% that we would expect to resolve from this<00:24:03.279> planning<00:24:03.600> process 00:24:04.710 --> 00:24:04.720 align:start position:0% this planning process 00:24:04.720 --> 00:24:07.029 align:start position:0% this planning process that<00:24:05.039> said<00:24:05.760> if<00:24:05.919> there's<00:24:06.320> more<00:24:06.559> detailed 00:24:07.029 --> 00:24:07.039 align:start position:0% that said if there's more detailed 00:24:07.039 --> 00:24:11.029 align:start position:0% that said if there's more detailed engineering<00:24:07.600> data<00:24:08.240> or<00:24:08.799> detail<00:24:09.520> available 00:24:11.029 --> 00:24:11.039 align:start position:0% engineering data or detail available 00:24:11.039 --> 00:24:12.470 align:start position:0% engineering data or detail available thinking<00:24:11.360> about<00:24:11.520> that<00:24:11.679> big<00:24:11.919> universe<00:24:12.400> of 00:24:12.470 --> 00:24:12.480 align:start position:0% thinking about that big universe of 00:24:12.480 --> 00:24:14.070 align:start position:0% thinking about that big universe of projects<00:24:12.880> i<00:24:12.960> showed<00:24:13.200> there<00:24:13.360> are<00:24:13.440> some<00:24:13.679> things 00:24:14.070 --> 00:24:14.080 align:start position:0% projects i showed there are some things 00:24:14.080 --> 00:24:15.830 align:start position:0% projects i showed there are some things where<00:24:14.320> we<00:24:14.480> do<00:24:14.640> have<00:24:14.880> some<00:24:15.039> more<00:24:15.279> information 00:24:15.830 --> 00:24:15.840 align:start position:0% where we do have some more information 00:24:15.840 --> 00:24:17.430 align:start position:0% where we do have some more information that<00:24:16.000> could<00:24:16.159> be<00:24:16.320> incorporated<00:24:17.120> in<00:24:17.279> and 00:24:17.430 --> 00:24:17.440 align:start position:0% that could be incorporated in and 00:24:17.440 --> 00:24:18.549 align:start position:0% that could be incorporated in and reflected 00:24:18.549 --> 00:24:18.559 align:start position:0% reflected 00:24:18.559 --> 00:24:19.430 align:start position:0% reflected um 00:24:19.430 --> 00:24:19.440 align:start position:0% um 00:24:19.440 --> 00:24:20.950 align:start position:0% um then<00:24:19.600> that<00:24:19.760> would<00:24:19.919> work<00:24:20.159> well<00:24:20.400> so<00:24:20.640> maybe 00:24:20.950 --> 00:24:20.960 align:start position:0% then that would work well so maybe 00:24:20.960 --> 00:24:23.430 align:start position:0% then that would work well so maybe things<00:24:21.279> don't<00:24:21.520> all<00:24:21.760> achieve<00:24:22.240> the<00:24:22.480> same<00:24:23.039> level 00:24:23.430 --> 00:24:23.440 align:start position:0% things don't all achieve the same level 00:24:23.440 --> 00:24:25.830 align:start position:0% things don't all achieve the same level of<00:24:23.600> detail<00:24:24.320> in<00:24:24.480> the<00:24:24.559> resulting<00:24:25.120> adaptation 00:24:25.830 --> 00:24:25.840 align:start position:0% of detail in the resulting adaptation 00:24:25.840 --> 00:24:27.269 align:start position:0% of detail in the resulting adaptation strategies 00:24:27.269 --> 00:24:27.279 align:start position:0% strategies 00:24:27.279 --> 00:24:28.310 align:start position:0% strategies roadmap 00:24:28.310 --> 00:24:28.320 align:start position:0% roadmap 00:24:28.320 --> 00:24:30.390 align:start position:0% roadmap but<00:24:28.720> we<00:24:28.880> do<00:24:29.039> recognize<00:24:29.600> our<00:24:29.679> budget<00:24:30.000> limits 00:24:30.390 --> 00:24:30.400 align:start position:0% but we do recognize our budget limits 00:24:30.400 --> 00:24:32.149 align:start position:0% but we do recognize our budget limits and<00:24:30.480> that<00:24:30.640> that<00:24:31.120> puts<00:24:31.360> us<00:24:31.520> in<00:24:31.600> the<00:24:31.760> realm<00:24:32.000> of 00:24:32.149 --> 00:24:32.159 align:start position:0% and that that puts us in the realm of 00:24:32.159 --> 00:24:37.350 align:start position:0% and that that puts us in the realm of conceptual<00:24:32.799> designs 00:24:37.350 --> 00:24:37.360 align:start position:0% 00:24:37.360 --> 00:24:40.149 align:start position:0% all<00:24:37.520> right<00:24:37.679> i'm<00:24:37.760> gonna<00:24:38.640> finish<00:24:39.120> this<00:24:39.520> oh<00:24:39.919> great 00:24:40.149 --> 00:24:40.159 align:start position:0% all right i'm gonna finish this oh great 00:24:40.159 --> 00:24:42.149 align:start position:0% all right i'm gonna finish this oh great thank<00:24:40.320> you<00:24:40.880> um 00:24:42.149 --> 00:24:42.159 align:start position:0% thank you um 00:24:42.159 --> 00:24:43.909 align:start position:0% thank you um i<00:24:42.320> see<00:24:42.480> a<00:24:42.640> question<00:24:42.880> just<00:24:43.120> came<00:24:43.360> in<00:24:43.440> will<00:24:43.600> any 00:24:43.909 --> 00:24:43.919 align:start position:0% i see a question just came in will any 00:24:43.919 --> 00:24:45.909 align:start position:0% i see a question just came in will any previously<00:24:44.559> developed<00:24:45.120> site-specific 00:24:45.909 --> 00:24:45.919 align:start position:0% previously developed site-specific 00:24:45.919 --> 00:24:48.470 align:start position:0% previously developed site-specific models<00:24:46.240> be<00:24:46.400> made<00:24:46.640> available<00:24:47.200> yes<00:24:48.000> so<00:24:48.240> the 00:24:48.470 --> 00:24:48.480 align:start position:0% models be made available yes so the 00:24:48.480 --> 00:24:50.789 align:start position:0% models be made available yes so the county<00:24:49.039> what<00:24:49.200> the<00:24:49.360> county 00:24:50.789 --> 00:24:50.799 align:start position:0% county what the county 00:24:50.799 --> 00:24:52.470 align:start position:0% county what the county has<00:24:51.279> in<00:24:51.440> its 00:24:52.470 --> 00:24:52.480 align:start position:0% has in its 00:24:52.480 --> 00:24:53.510 align:start position:0% has in its current 00:24:53.510 --> 00:24:53.520 align:start position:0% current 00:24:53.520 --> 00:24:55.750 align:start position:0% current purview<00:24:54.080> from<00:24:54.320> prior<00:24:54.799> studies<00:24:55.200> would<00:24:55.360> be<00:24:55.600> able 00:24:55.750 --> 00:24:55.760 align:start position:0% purview from prior studies would be able 00:24:55.760 --> 00:24:57.830 align:start position:0% purview from prior studies would be able to<00:24:55.919> be<00:24:56.159> used<00:24:57.039> um 00:24:57.830 --> 00:24:57.840 align:start position:0% to be used um 00:24:57.840 --> 00:24:59.110 align:start position:0% to be used um i<00:24:58.000> think<00:24:58.240> there's 00:24:59.110 --> 00:24:59.120 align:start position:0% i think there's 00:24:59.120 --> 00:25:00.950 align:start position:0% i think there's something<00:24:59.440> to<00:24:59.520> this<00:24:59.679> question<00:25:00.080> i'm<00:25:00.240> not<00:25:00.400> quite 00:25:00.950 --> 00:25:00.960 align:start position:0% something to this question i'm not quite 00:25:00.960 --> 00:25:03.029 align:start position:0% something to this question i'm not quite quite<00:25:01.279> getting<00:25:01.520> the<00:25:01.679> nugget<00:25:02.000> of<00:25:02.159> so<00:25:02.559> dave<00:25:02.880> feel 00:25:03.029 --> 00:25:03.039 align:start position:0% quite getting the nugget of so dave feel 00:25:03.039 --> 00:25:05.110 align:start position:0% quite getting the nugget of so dave feel free<00:25:03.200> to<00:25:03.360> clarify<00:25:03.840> at<00:25:03.919> me<00:25:04.159> but 00:25:05.110 --> 00:25:05.120 align:start position:0% free to clarify at me but 00:25:05.120 --> 00:25:06.630 align:start position:0% free to clarify at me but um 00:25:06.630 --> 00:25:06.640 align:start position:0% um 00:25:06.640 --> 00:25:10.070 align:start position:0% um we<00:25:06.799> did<00:25:06.960> do<00:25:07.279> significant<00:25:08.400> work<00:25:08.960> with<00:25:09.520> um 00:25:10.070 --> 00:25:10.080 align:start position:0% we did do significant work with um 00:25:10.080 --> 00:25:12.230 align:start position:0% we did do significant work with um cosmos<00:25:10.640> sea<00:25:10.799> level<00:25:11.039> rise<00:25:11.279> scenarios<00:25:12.080> out<00:25:12.159> of 00:25:12.230 --> 00:25:12.240 align:start position:0% cosmos sea level rise scenarios out of 00:25:12.240 --> 00:25:15.750 align:start position:0% cosmos sea level rise scenarios out of the<00:25:12.320> usgs<00:25:13.039> data<00:25:13.919> um<00:25:14.640> so<00:25:14.799> we'll<00:25:15.039> have<00:25:15.279> access<00:25:15.600> to 00:25:15.750 --> 00:25:15.760 align:start position:0% the usgs data um so we'll have access to 00:25:15.760 --> 00:25:17.430 align:start position:0% the usgs data um so we'll have access to that<00:25:16.000> prior<00:25:16.320> work<00:25:16.559> that<00:25:16.720> was<00:25:16.880> done<00:25:17.200> that 00:25:17.430 --> 00:25:17.440 align:start position:0% that prior work that was done that 00:25:17.440 --> 00:25:19.830 align:start position:0% that prior work that was done that identified<00:25:18.000> vulnerable<00:25:18.559> assets 00:25:19.830 --> 00:25:19.840 align:start position:0% identified vulnerable assets 00:25:19.840 --> 00:25:21.510 align:start position:0% identified vulnerable assets we'll<00:25:20.000> be<00:25:20.159> refining<00:25:20.720> some<00:25:20.880> of<00:25:20.960> the<00:25:21.120> selected 00:25:21.510 --> 00:25:21.520 align:start position:0% we'll be refining some of the selected 00:25:21.520 --> 00:25:24.390 align:start position:0% we'll be refining some of the selected sea<00:25:21.760> level<00:25:22.000> rise<00:25:22.320> scenarios<00:25:23.279> for<00:25:23.520> this<00:25:24.080> next 00:25:24.390 --> 00:25:24.400 align:start position:0% sea level rise scenarios for this next 00:25:24.400 --> 00:25:26.070 align:start position:0% sea level rise scenarios for this next phase<00:25:24.640> of<00:25:24.799> adaptation<00:25:25.440> planning<00:25:25.760> but<00:25:25.919> there 00:25:26.070 --> 00:25:26.080 align:start position:0% phase of adaptation planning but there 00:25:26.080 --> 00:25:30.630 align:start position:0% phase of adaptation planning but there will<00:25:26.240> be<00:25:26.400> access<00:25:26.720> to<00:25:26.880> that 00:25:30.630 --> 00:25:30.640 align:start position:0% 00:25:30.640 --> 00:25:32.310 align:start position:0% all<00:25:30.720> right 00:25:32.310 --> 00:25:32.320 align:start position:0% all right 00:25:32.320 --> 00:25:34.390 align:start position:0% all right another<00:25:32.720> question<00:25:33.039> that<00:25:33.200> came<00:25:33.440> in<00:25:33.600> was 00:25:34.390 --> 00:25:34.400 align:start position:0% another question that came in was 00:25:34.400 --> 00:25:35.190 align:start position:0% another question that came in was for 00:25:35.190 --> 00:25:35.200 align:start position:0% for 00:25:35.200 --> 00:25:38.630 align:start position:0% for task<00:25:35.600> 3<00:25:36.240> the<00:25:36.480> adaptation<00:25:37.120> planning<00:25:37.600> task<00:25:38.480> will 00:25:38.630 --> 00:25:38.640 align:start position:0% task 3 the adaptation planning task will 00:25:38.640 --> 00:25:40.549 align:start position:0% task 3 the adaptation planning task will a<00:25:38.799> single<00:25:39.120> deliverable<00:25:39.600> be<00:25:39.760> expected<00:25:40.320> for 00:25:40.549 --> 00:25:40.559 align:start position:0% a single deliverable be expected for 00:25:40.559 --> 00:25:43.350 align:start position:0% a single deliverable be expected for each<00:25:40.840> subtask<00:25:41.679> good<00:25:41.919> question<00:25:42.720> deliverables 00:25:43.350 --> 00:25:43.360 align:start position:0% each subtask good question deliverables 00:25:43.360 --> 00:25:45.750 align:start position:0% each subtask good question deliverables are<00:25:43.440> expected<00:25:43.919> as<00:25:44.080> part<00:25:44.320> of<00:25:44.400> task<00:25:44.720> three 00:25:45.750 --> 00:25:45.760 align:start position:0% are expected as part of task three 00:25:45.760 --> 00:25:49.510 align:start position:0% are expected as part of task three so<00:25:46.400> cda<00:25:46.960> is<00:25:47.039> flexible<00:25:48.000> on<00:25:48.720> what 00:25:49.510 --> 00:25:49.520 align:start position:0% so cda is flexible on what 00:25:49.520 --> 00:25:51.990 align:start position:0% so cda is flexible on what deliverables<00:25:50.640> happen<00:25:51.039> where<00:25:51.279> within<00:25:51.679> task 00:25:51.990 --> 00:25:52.000 align:start position:0% deliverables happen where within task 00:25:52.000 --> 00:25:53.350 align:start position:0% deliverables happen where within task three 00:25:53.350 --> 00:25:53.360 align:start position:0% three 00:25:53.360 --> 00:25:55.590 align:start position:0% three what<00:25:53.600> is<00:25:53.840> critical 00:25:55.590 --> 00:25:55.600 align:start position:0% what is critical 00:25:55.600 --> 00:25:57.110 align:start position:0% what is critical is<00:25:55.760> that<00:25:55.919> the<00:25:56.000> consultant's<00:25:56.640> approach 00:25:57.110 --> 00:25:57.120 align:start position:0% is that the consultant's approach 00:25:57.120 --> 00:25:59.990 align:start position:0% is that the consultant's approach provides<00:25:57.760> some<00:25:58.159> interim<00:25:58.720> work<00:25:59.039> products<00:25:59.760> that 00:25:59.990 --> 00:26:00.000 align:start position:0% provides some interim work products that 00:26:00.000 --> 00:26:01.590 align:start position:0% provides some interim work products that allow<00:26:00.720> us 00:26:01.590 --> 00:26:01.600 align:start position:0% allow us 00:26:01.600 --> 00:26:02.390 align:start position:0% allow us to 00:26:02.390 --> 00:26:02.400 align:start position:0% to 00:26:02.400 --> 00:26:05.110 align:start position:0% to go<00:26:02.960> have<00:26:03.200> constructive<00:26:03.840> public<00:26:04.159> dialogue<00:26:04.880> and 00:26:05.110 --> 00:26:05.120 align:start position:0% go have constructive public dialogue and 00:26:05.120 --> 00:26:06.950 align:start position:0% go have constructive public dialogue and solicit<00:26:05.679> input<00:26:06.080> into<00:26:06.320> the<00:26:06.400> adaptation 00:26:06.950 --> 00:26:06.960 align:start position:0% solicit input into the adaptation 00:26:06.960 --> 00:26:10.070 align:start position:0% solicit input into the adaptation planning<00:26:07.279> process<00:26:08.159> so<00:26:08.640> we<00:26:08.880> need<00:26:09.360> some<00:26:09.760> things 00:26:10.070 --> 00:26:10.080 align:start position:0% planning process so we need some things 00:26:10.080 --> 00:26:11.510 align:start position:0% planning process so we need some things that<00:26:10.159> we're<00:26:10.400> able<00:26:10.640> to<00:26:10.799> take<00:26:10.960> to<00:26:11.120> the<00:26:11.200> public 00:26:11.510 --> 00:26:11.520 align:start position:0% that we're able to take to the public 00:26:11.520 --> 00:26:12.630 align:start position:0% that we're able to take to the public that<00:26:11.679> they<00:26:11.840> can 00:26:12.630 --> 00:26:12.640 align:start position:0% that they can 00:26:12.640 --> 00:26:15.909 align:start position:0% that they can react<00:26:13.200> against<00:26:13.840> and<00:26:14.159> respond<00:26:14.960> to 00:26:15.909 --> 00:26:15.919 align:start position:0% react against and respond to 00:26:15.919 --> 00:26:16.789 align:start position:0% react against and respond to um 00:26:16.789 --> 00:26:16.799 align:start position:0% um 00:26:16.799 --> 00:26:19.430 align:start position:0% um but<00:26:16.960> we<00:26:17.120> are<00:26:17.279> not<00:26:17.520> prescribing<00:26:18.240> that<00:26:18.480> at 00:26:19.430 --> 00:26:19.440 align:start position:0% but we are not prescribing that at 00:26:19.440 --> 00:26:21.510 align:start position:0% but we are not prescribing that at each<00:26:19.760> step<00:26:20.080> there's<00:26:20.320> a<00:26:20.400> completely<00:26:21.200> unique 00:26:21.510 --> 00:26:21.520 align:start position:0% each step there's a completely unique 00:26:21.520 --> 00:26:23.830 align:start position:0% each step there's a completely unique deliverable<00:26:22.080> being<00:26:22.320> handed<00:26:23.120> that<00:26:23.360> is<00:26:23.520> part<00:26:23.760> of 00:26:23.830 --> 00:26:23.840 align:start position:0% deliverable being handed that is part of 00:26:23.840 --> 00:26:25.430 align:start position:0% deliverable being handed that is part of what<00:26:24.080> we<00:26:24.240> are<00:26:24.400> asking 00:26:25.430 --> 00:26:25.440 align:start position:0% what we are asking 00:26:25.440 --> 00:26:28.870 align:start position:0% what we are asking in<00:26:26.000> the<00:26:26.400> applications<00:26:27.600> that<00:26:27.919> you 00:26:28.870 --> 00:26:28.880 align:start position:0% in the applications that you 00:26:28.880 --> 00:26:30.470 align:start position:0% in the applications that you clarify<00:26:29.520> you<00:26:29.600> know<00:26:29.760> this<00:26:30.080> would<00:26:30.240> be<00:26:30.320> an 00:26:30.470 --> 00:26:30.480 align:start position:0% clarify you know this would be an 00:26:30.480 --> 00:26:32.310 align:start position:0% clarify you know this would be an opportunity<00:26:31.120> for<00:26:31.360> a<00:26:31.440> type<00:26:31.679> of<00:26:31.760> deliverable 00:26:32.310 --> 00:26:32.320 align:start position:0% opportunity for a type of deliverable 00:26:32.320 --> 00:26:34.560 align:start position:0% opportunity for a type of deliverable here<00:26:33.120> and<00:26:33.200> maybe<00:26:33.520> at<00:26:33.679> this<00:26:33.919> step<00:26:34.159> you<00:26:34.320> can 00:26:34.560 --> 00:26:34.570 align:start position:0% here and maybe at this step you can 00:26:34.570 --> 00:26:36.470 align:start position:0% here and maybe at this step you can [Music] 00:26:36.470 --> 00:26:36.480 align:start position:0% [Music] 00:26:36.480 --> 00:26:38.390 align:start position:0% [Music] fold<00:26:36.720> these<00:26:36.960> things<00:26:37.360> together<00:26:37.840> and<00:26:38.000> move<00:26:38.240> it 00:26:38.390 --> 00:26:38.400 align:start position:0% fold these things together and move it 00:26:38.400 --> 00:26:39.430 align:start position:0% fold these things together and move it forward 00:26:39.430 --> 00:26:39.440 align:start position:0% forward 00:26:39.440 --> 00:26:41.350 align:start position:0% forward um<00:26:40.000> some<00:26:40.159> things<00:26:40.400> that<00:26:40.480> do<00:26:40.640> spring<00:26:40.880> to<00:26:41.039> mind<00:26:41.279> to 00:26:41.350 --> 00:26:41.360 align:start position:0% um some things that do spring to mind to 00:26:41.360 --> 00:26:43.110 align:start position:0% um some things that do spring to mind to me<00:26:41.600> when<00:26:41.760> i<00:26:41.919> say<00:26:42.159> possible<00:26:42.720> interim 00:26:43.110 --> 00:26:43.120 align:start position:0% me when i say possible interim 00:26:43.120 --> 00:26:44.630 align:start position:0% me when i say possible interim deliverables 00:26:44.630 --> 00:26:44.640 align:start position:0% deliverables 00:26:44.640 --> 00:26:46.789 align:start position:0% deliverables compelling<00:26:45.440> accessible 00:26:46.789 --> 00:26:46.799 align:start position:0% compelling accessible 00:26:46.799 --> 00:26:48.789 align:start position:0% compelling accessible visuals<00:26:47.279> and<00:26:47.440> communication<00:26:48.240> when<00:26:48.400> we<00:26:48.559> get<00:26:48.640> to 00:26:48.789 --> 00:26:48.799 align:start position:0% visuals and communication when we get to 00:26:48.799 --> 00:26:50.549 align:start position:0% visuals and communication when we get to evaluation<00:26:49.440> criteria<00:26:49.919> that<00:26:50.080> lay<00:26:50.240> out<00:26:50.400> what 00:26:50.549 --> 00:26:50.559 align:start position:0% evaluation criteria that lay out what 00:26:50.559 --> 00:26:52.230 align:start position:0% evaluation criteria that lay out what they<00:26:50.720> are<00:26:51.039> you<00:26:51.120> know<00:26:51.200> maybe<00:26:51.440> that's<00:26:51.679> a<00:26:51.760> matrix 00:26:52.230 --> 00:26:52.240 align:start position:0% they are you know maybe that's a matrix 00:26:52.240 --> 00:26:53.750 align:start position:0% they are you know maybe that's a matrix people<00:26:52.480> can<00:26:52.720> understand<00:26:53.200> to<00:26:53.360> see<00:26:53.520> all<00:26:53.600> the 00:26:53.750 --> 00:26:53.760 align:start position:0% people can understand to see all the 00:26:53.760 --> 00:26:55.029 align:start position:0% people can understand to see all the different<00:26:54.000> things 00:26:55.029 --> 00:26:55.039 align:start position:0% different things 00:26:55.039 --> 00:26:56.630 align:start position:0% different things considerations<00:26:55.840> that<00:26:55.919> we're<00:26:56.159> weighing<00:26:56.559> and 00:26:56.630 --> 00:26:56.640 align:start position:0% considerations that we're weighing and 00:26:56.640 --> 00:26:58.789 align:start position:0% considerations that we're weighing and be<00:26:56.799> able<00:26:56.960> to<00:26:57.039> respond<00:26:57.679> to<00:26:57.840> that 00:26:58.789 --> 00:26:58.799 align:start position:0% be able to respond to that 00:26:58.799 --> 00:27:01.350 align:start position:0% be able to respond to that um<00:26:59.360> graphics<00:27:00.080> that<00:27:00.240> convey<00:27:00.640> adaptation 00:27:01.350 --> 00:27:01.360 align:start position:0% um graphics that convey adaptation 00:27:01.360 --> 00:27:02.710 align:start position:0% um graphics that convey adaptation pathways<00:27:01.919> we're<00:27:02.080> going<00:27:02.240> to<00:27:02.320> need<00:27:02.480> help 00:27:02.710 --> 00:27:02.720 align:start position:0% pathways we're going to need help 00:27:02.720 --> 00:27:04.470 align:start position:0% pathways we're going to need help communicating<00:27:03.360> that<00:27:03.520> it's<00:27:04.080> i<00:27:04.240> think<00:27:04.400> it's 00:27:04.470 --> 00:27:04.480 align:start position:0% communicating that it's i think it's 00:27:04.480 --> 00:27:06.310 align:start position:0% communicating that it's i think it's pretty<00:27:04.640> complicated<00:27:05.279> concept<00:27:05.840> for<00:27:06.000> folks<00:27:06.240> who 00:27:06.310 --> 00:27:06.320 align:start position:0% pretty complicated concept for folks who 00:27:06.320 --> 00:27:08.230 align:start position:0% pretty complicated concept for folks who are<00:27:06.480> new<00:27:06.640> to<00:27:06.720> the<00:27:06.880> idea<00:27:07.360> so<00:27:07.600> some<00:27:07.840> interim 00:27:08.230 --> 00:27:08.240 align:start position:0% are new to the idea so some interim 00:27:08.240 --> 00:27:10.390 align:start position:0% are new to the idea so some interim deliverables<00:27:08.799> that<00:27:08.960> help<00:27:09.200> us<00:27:09.840> carry<00:27:10.159> those 00:27:10.390 --> 00:27:10.400 align:start position:0% deliverables that help us carry those 00:27:10.400 --> 00:27:13.510 align:start position:0% deliverables that help us carry those conversations<00:27:11.360> and<00:27:11.679> solicit<00:27:12.799> uh<00:27:13.120> public 00:27:13.510 --> 00:27:13.520 align:start position:0% conversations and solicit uh public 00:27:13.520 --> 00:27:16.390 align:start position:0% conversations and solicit uh public input<00:27:13.840> are<00:27:13.919> going<00:27:14.000> to<00:27:14.159> be<00:27:14.320> really<00:27:14.640> important 00:27:16.390 --> 00:27:16.400 align:start position:0% input are going to be really important 00:27:16.400 --> 00:27:21.909 align:start position:0% input are going to be really important jack<00:27:16.640> anything<00:27:16.960> you<00:27:17.039> want<00:27:17.120> to<00:27:17.279> add<00:27:17.440> there 00:27:21.909 --> 00:27:21.919 align:start position:0% 00:27:21.919 --> 00:27:24.630 align:start position:0% i<00:27:22.080> would<00:27:22.320> say<00:27:22.559> that<00:27:23.200> um 00:27:24.630 --> 00:27:24.640 align:start position:0% i would say that um 00:27:24.640 --> 00:27:27.269 align:start position:0% i would say that um cost<00:27:25.039> criteria<00:27:25.679> too<00:27:26.000> you<00:27:26.080> know 00:27:27.269 --> 00:27:27.279 align:start position:0% cost criteria too you know 00:27:27.279 --> 00:27:29.430 align:start position:0% cost criteria too you know basically 00:27:29.430 --> 00:27:29.440 align:start position:0% basically 00:27:29.440 --> 00:27:31.350 align:start position:0% basically estimates<00:27:30.080> of<00:27:30.559> how<00:27:30.720> much<00:27:31.039> different 00:27:31.350 --> 00:27:31.360 align:start position:0% estimates of how much different 00:27:31.360 --> 00:27:33.350 align:start position:0% estimates of how much different adaptation 00:27:33.350 --> 00:27:33.360 align:start position:0% adaptation 00:27:33.360 --> 00:27:36.710 align:start position:0% adaptation approaches<00:27:34.080> might<00:27:34.640> might<00:27:34.960> cost 00:27:36.710 --> 00:27:36.720 align:start position:0% approaches might might cost 00:27:36.720 --> 00:27:39.350 align:start position:0% approaches might might cost in<00:27:36.880> terms<00:27:37.279> of<00:27:37.840> you<00:27:38.000> know<00:27:38.159> upfront<00:27:38.640> cost<00:27:39.039> and 00:27:39.350 --> 00:27:39.360 align:start position:0% in terms of you know upfront cost and 00:27:39.360 --> 00:27:42.870 align:start position:0% in terms of you know upfront cost and operation<00:27:40.000> and<00:27:40.159> maintenance<00:27:40.880> of<00:27:41.120> those 00:27:42.870 --> 00:27:42.880 align:start position:0% operation and maintenance of those 00:27:42.880 --> 00:27:49.269 align:start position:0% operation and maintenance of those those<00:27:43.200> items 00:27:49.269 --> 00:27:49.279 align:start position:0% 00:27:49.279 --> 00:27:51.350 align:start position:0% okay<00:27:49.679> question<00:27:50.000> just<00:27:50.240> came<00:27:50.480> in 00:27:51.350 --> 00:27:51.360 align:start position:0% okay question just came in 00:27:51.360 --> 00:27:53.190 align:start position:0% okay question just came in cosmos<00:27:52.000> and<00:27:52.080> most<00:27:52.399> other<00:27:52.559> sea<00:27:52.720> level<00:27:52.960> rise 00:27:53.190 --> 00:27:53.200 align:start position:0% cosmos and most other sea level rise 00:27:53.200 --> 00:27:55.269 align:start position:0% cosmos and most other sea level rise models<00:27:53.600> are<00:27:53.760> fine<00:27:54.000> planning<00:27:54.320> tools<00:27:55.039> not 00:27:55.269 --> 00:27:55.279 align:start position:0% models are fine planning tools not 00:27:55.279 --> 00:27:56.870 align:start position:0% models are fine planning tools not suitable<00:27:55.679> for<00:27:55.840> detailed<00:27:56.240> site-specific 00:27:56.870 --> 00:27:56.880 align:start position:0% suitable for detailed site-specific 00:27:56.880 --> 00:27:59.029 align:start position:0% suitable for detailed site-specific analysis<00:27:57.440> typically<00:27:58.320> i'm<00:27:58.480> usually<00:27:58.720> not<00:27:58.880> that 00:27:59.029 --> 00:27:59.039 align:start position:0% analysis typically i'm usually not that 00:27:59.039 --> 00:28:00.630 align:start position:0% analysis typically i'm usually not that helpful<00:27:59.360> for<00:27:59.520> evaluating<00:28:00.080> adaptation 00:28:00.630 --> 00:28:00.640 align:start position:0% helpful for evaluating adaptation 00:28:00.640 --> 00:28:02.070 align:start position:0% helpful for evaluating adaptation strategies<00:28:01.120> not<00:28:01.279> sure<00:28:01.440> if<00:28:01.520> more<00:28:01.679> detailed 00:28:02.070 --> 00:28:02.080 align:start position:0% strategies not sure if more detailed 00:28:02.080 --> 00:28:03.750 align:start position:0% strategies not sure if more detailed modeling<00:28:02.399> was<00:28:02.640> done<00:28:02.960> for<00:28:03.120> some<00:28:03.279> of<00:28:03.360> the<00:28:03.520> sub 00:28:03.750 --> 00:28:03.760 align:start position:0% modeling was done for some of the sub 00:28:03.760 --> 00:28:06.149 align:start position:0% modeling was done for some of the sub area<00:28:04.159> planning<00:28:04.480> efforts 00:28:06.149 --> 00:28:06.159 align:start position:0% area planning efforts 00:28:06.159 --> 00:28:08.470 align:start position:0% area planning efforts good<00:28:06.399> question<00:28:06.799> there<00:28:07.120> is<00:28:07.440> some<00:28:07.840> additional 00:28:08.470 --> 00:28:08.480 align:start position:0% good question there is some additional 00:28:08.480 --> 00:28:10.149 align:start position:0% good question there is some additional modeling<00:28:09.120> done 00:28:10.149 --> 00:28:10.159 align:start position:0% modeling done 00:28:10.159 --> 00:28:12.870 align:start position:0% modeling done being<00:28:10.399> completed<00:28:11.039> by<00:28:11.360> national<00:28:11.679> park<00:28:12.000> service 00:28:12.870 --> 00:28:12.880 align:start position:0% being completed by national park service 00:28:12.880 --> 00:28:13.750 align:start position:0% being completed by national park service for 00:28:13.750 --> 00:28:13.760 align:start position:0% for 00:28:13.760 --> 00:28:16.230 align:start position:0% for fluvial<00:28:14.480> flooding<00:28:15.039> out<00:28:15.120> of<00:28:15.279> east<00:28:15.600> cook<00:28:15.919> creek 00:28:16.230 --> 00:28:16.240 align:start position:0% fluvial flooding out of east cook creek 00:28:16.240 --> 00:28:18.389 align:start position:0% fluvial flooding out of east cook creek which<00:28:16.480> is<00:28:16.640> one<00:28:16.799> of<00:28:16.880> the<00:28:17.120> the<00:28:17.279> main<00:28:17.520> drainages 00:28:18.389 --> 00:28:18.399 align:start position:0% which is one of the the main drainages 00:28:18.399 --> 00:28:21.590 align:start position:0% which is one of the the main drainages that's<00:28:18.720> been<00:28:18.960> a<00:28:19.600> big<00:28:19.919> flooding 00:28:21.590 --> 00:28:21.600 align:start position:0% that's been a big flooding 00:28:21.600 --> 00:28:25.190 align:start position:0% that's been a big flooding source<00:28:22.240> over<00:28:22.480> the<00:28:22.960> decades<00:28:23.600> if<00:28:23.760> not<00:28:24.000> centuries 00:28:25.190 --> 00:28:25.200 align:start position:0% source over the decades if not centuries 00:28:25.200 --> 00:28:27.190 align:start position:0% source over the decades if not centuries um 00:28:27.190 --> 00:28:27.200 align:start position:0% um 00:28:27.200 --> 00:28:28.870 align:start position:0% um maybe<00:28:27.600> jack<00:28:27.840> can<00:28:27.919> speak<00:28:28.159> to<00:28:28.320> this<00:28:28.480> further<00:28:28.799> and 00:28:28.870 --> 00:28:28.880 align:start position:0% maybe jack can speak to this further and 00:28:28.880 --> 00:28:31.510 align:start position:0% maybe jack can speak to this further and admit<00:28:29.200> but<00:28:29.360> i<00:28:29.440> will<00:28:29.679> say<00:28:29.919> i<00:28:30.000> think<00:28:30.240> what 00:28:31.510 --> 00:28:31.520 align:start position:0% admit but i will say i think what 00:28:31.520 --> 00:28:33.909 align:start position:0% admit but i will say i think what what<00:28:31.760> cosmos<00:28:32.320> does<00:28:32.640> get<00:28:32.880> us<00:28:33.039> and 00:28:33.909 --> 00:28:33.919 align:start position:0% what cosmos does get us and 00:28:33.919 --> 00:28:35.430 align:start position:0% what cosmos does get us and recognize<00:28:34.480> there<00:28:34.720> are<00:28:34.880> definitely 00:28:35.430 --> 00:28:35.440 align:start position:0% recognize there are definitely 00:28:35.440 --> 00:28:37.510 align:start position:0% recognize there are definitely limitations<00:28:36.320> on<00:28:36.480> that<00:28:36.640> modeling<00:28:37.120> but<00:28:37.279> it's 00:28:37.510 --> 00:28:37.520 align:start position:0% limitations on that modeling but it's 00:28:37.520 --> 00:28:39.750 align:start position:0% limitations on that modeling but it's enough<00:28:37.919> to<00:28:38.159> say 00:28:39.750 --> 00:28:39.760 align:start position:0% enough to say 00:28:39.760 --> 00:28:41.669 align:start position:0% enough to say septics<00:28:40.640> are<00:28:40.799> going 00:28:41.669 --> 00:28:41.679 align:start position:0% septics are going 00:28:41.679 --> 00:28:44.710 align:start position:0% septics are going here<00:28:42.480> and<00:28:42.880> this<00:28:43.200> road<00:28:43.600> is<00:28:43.679> significant 00:28:44.710 --> 00:28:44.720 align:start position:0% here and this road is significant 00:28:44.720 --> 00:28:47.110 align:start position:0% here and this road is significant experiencing<00:28:45.760> significant<00:28:46.559> depth<00:28:46.960> and 00:28:47.110 --> 00:28:47.120 align:start position:0% experiencing significant depth and 00:28:47.120 --> 00:28:49.029 align:start position:0% experiencing significant depth and duration<00:28:47.679> of<00:28:47.760> flooding<00:28:48.159> impacts<00:28:48.559> by<00:28:48.799> this 00:28:49.029 --> 00:28:49.039 align:start position:0% duration of flooding impacts by this 00:28:49.039 --> 00:28:51.430 align:start position:0% duration of flooding impacts by this juncture<00:28:49.600> so 00:28:51.430 --> 00:28:51.440 align:start position:0% juncture so 00:28:51.440 --> 00:28:53.510 align:start position:0% juncture so agreed<00:28:51.919> not<00:28:52.159> enough<00:28:52.399> to<00:28:52.559> carry<00:28:52.880> like<00:28:53.120> a 00:28:53.510 --> 00:28:53.520 align:start position:0% agreed not enough to carry like a 00:28:53.520 --> 00:28:55.830 align:start position:0% agreed not enough to carry like a detailed<00:28:54.559> high<00:28:54.880> level<00:28:55.200> of<00:28:55.360> engineering 00:28:55.830 --> 00:28:55.840 align:start position:0% detailed high level of engineering 00:28:55.840 --> 00:28:57.190 align:start position:0% detailed high level of engineering design<00:28:56.240> but<00:28:56.399> since<00:28:56.640> we're<00:28:56.799> going<00:28:56.960> for 00:28:57.190 --> 00:28:57.200 align:start position:0% design but since we're going for 00:28:57.200 --> 00:28:59.269 align:start position:0% design but since we're going for conceptual<00:28:57.760> design<00:28:58.240> i'm<00:28:58.480> i'm<00:28:58.640> hopeful<00:28:59.120> that 00:28:59.269 --> 00:28:59.279 align:start position:0% conceptual design i'm i'm hopeful that 00:28:59.279 --> 00:29:00.230 align:start position:0% conceptual design i'm i'm hopeful that it's 00:29:00.230 --> 00:29:00.240 align:start position:0% it's 00:29:00.240 --> 00:29:01.830 align:start position:0% it's helping<00:29:00.559> us<00:29:00.720> arrive<00:29:01.039> at<00:29:01.120> the<00:29:01.200> right<00:29:01.520> level 00:29:01.830 --> 00:29:01.840 align:start position:0% helping us arrive at the right level 00:29:01.840 --> 00:29:04.470 align:start position:0% helping us arrive at the right level there<00:29:02.159> um<00:29:02.320> and<00:29:02.480> i'll<00:29:02.559> turn<00:29:02.799> it<00:29:02.880> over<00:29:03.039> to<00:29:03.200> jack 00:29:04.470 --> 00:29:04.480 align:start position:0% there um and i'll turn it over to jack 00:29:04.480 --> 00:29:07.430 align:start position:0% there um and i'll turn it over to jack yeah<00:29:04.720> i<00:29:05.120> um<00:29:05.840> i<00:29:06.000> agree<00:29:06.320> that<00:29:06.720> we're<00:29:06.960> not<00:29:07.200> we're 00:29:07.430 --> 00:29:07.440 align:start position:0% yeah i um i agree that we're not we're 00:29:07.440 --> 00:29:08.630 align:start position:0% yeah i um i agree that we're not we're not<00:29:07.679> trying<00:29:07.919> to 00:29:08.630 --> 00:29:08.640 align:start position:0% not trying to 00:29:08.640 --> 00:29:10.470 align:start position:0% not trying to design<00:29:09.360> projects 00:29:10.470 --> 00:29:10.480 align:start position:0% design projects 00:29:10.480 --> 00:29:12.950 align:start position:0% design projects whose<00:29:10.960> next<00:29:11.200> step<00:29:11.600> will<00:29:11.760> be<00:29:12.080> implementation 00:29:12.950 --> 00:29:12.960 align:start position:0% whose next step will be implementation 00:29:12.960 --> 00:29:15.029 align:start position:0% whose next step will be implementation or<00:29:13.120> the<00:29:13.279> building<00:29:13.600> of<00:29:13.760> the<00:29:13.840> projects<00:29:14.799> we're 00:29:15.029 --> 00:29:15.039 align:start position:0% or the building of the projects we're 00:29:15.039 --> 00:29:19.750 align:start position:0% or the building of the projects we're trying<00:29:15.279> to<00:29:15.440> get<00:29:15.840> an<00:29:16.080> idea<00:29:16.640> of<00:29:17.120> uh<00:29:17.760> comparable 00:29:19.750 --> 00:29:19.760 align:start position:0% trying to get an idea of uh comparable 00:29:19.760 --> 00:29:22.310 align:start position:0% trying to get an idea of uh comparable information<00:29:20.480> between<00:29:20.960> different<00:29:21.360> approaches 00:29:22.310 --> 00:29:22.320 align:start position:0% information between different approaches 00:29:22.320 --> 00:29:23.510 align:start position:0% information between different approaches and 00:29:23.510 --> 00:29:23.520 align:start position:0% and 00:29:23.520 --> 00:29:26.470 align:start position:0% and where<00:29:23.919> that<00:29:24.159> will<00:29:24.480> point<00:29:24.880> us<00:29:25.279> in<00:29:25.440> the<00:29:25.600> future 00:29:26.470 --> 00:29:26.480 align:start position:0% where that will point us in the future 00:29:26.480 --> 00:29:27.669 align:start position:0% where that will point us in the future so 00:29:27.669 --> 00:29:27.679 align:start position:0% so 00:29:27.679 --> 00:29:29.350 align:start position:0% so again<00:29:28.000> as<00:29:28.320> uh 00:29:29.350 --> 00:29:29.360 align:start position:0% again as uh 00:29:29.360 --> 00:29:31.510 align:start position:0% again as uh julia<00:29:29.840> said<00:29:30.080> this<00:29:30.399> it's<00:29:31.039> more<00:29:31.279> at<00:29:31.440> a 00:29:31.510 --> 00:29:31.520 align:start position:0% julia said this it's more at a 00:29:31.520 --> 00:29:33.269 align:start position:0% julia said this it's more at a conceptual<00:29:32.399> level 00:29:33.269 --> 00:29:33.279 align:start position:0% conceptual level 00:29:33.279 --> 00:29:34.630 align:start position:0% conceptual level not<00:29:33.520> at<00:29:33.840> a 00:29:34.630 --> 00:29:34.640 align:start position:0% not at a 00:29:34.640 --> 00:29:40.870 align:start position:0% not at a design<00:29:35.279> construction<00:29:36.159> level 00:29:40.870 --> 00:29:40.880 align:start position:0% 00:29:40.880 --> 00:29:42.710 align:start position:0% all<00:29:41.039> right<00:29:41.279> next<00:29:41.600> question 00:29:42.710 --> 00:29:42.720 align:start position:0% all right next question 00:29:42.720 --> 00:29:45.110 align:start position:0% all right next question what<00:29:43.039> gis<00:29:43.679> information<00:29:44.320> are<00:29:44.480> available<00:29:44.960> for 00:29:45.110 --> 00:29:45.120 align:start position:0% what gis information are available for 00:29:45.120 --> 00:29:47.190 align:start position:0% what gis information are available for utilities<00:29:45.679> in<00:29:45.760> stinson<00:29:46.159> beach<00:29:46.559> electrical 00:29:47.190 --> 00:29:47.200 align:start position:0% utilities in stinson beach electrical 00:29:47.200 --> 00:29:49.430 align:start position:0% utilities in stinson beach electrical gas<00:29:47.520> telecommunications<00:29:48.559> water<00:29:48.799> wastewater 00:29:49.430 --> 00:29:49.440 align:start position:0% gas telecommunications water wastewater 00:29:49.440 --> 00:29:51.190 align:start position:0% gas telecommunications water wastewater others 00:29:51.190 --> 00:29:51.200 align:start position:0% others 00:29:51.200 --> 00:29:52.950 align:start position:0% others excellent<00:29:51.840> question 00:29:52.950 --> 00:29:52.960 align:start position:0% excellent question 00:29:52.960 --> 00:29:56.230 align:start position:0% excellent question that<00:29:53.279> is<00:29:53.440> something<00:29:54.000> that<00:29:54.559> we<00:29:54.960> cda<00:29:55.679> are<00:29:55.919> taking 00:29:56.230 --> 00:29:56.240 align:start position:0% that is something that we cda are taking 00:29:56.240 --> 00:29:58.789 align:start position:0% that is something that we cda are taking on<00:29:56.559> now<00:29:57.200> there<00:29:57.440> is<00:29:57.600> actually<00:29:58.080> a<00:29:58.399> data 00:29:58.789 --> 00:29:58.799 align:start position:0% on now there is actually a data 00:29:58.799 --> 00:30:00.789 align:start position:0% on now there is actually a data compilation<00:29:59.520> effort<00:29:59.919> being<00:30:00.159> wrapped<00:30:00.480> up<00:30:00.640> for 00:30:00.789 --> 00:30:00.799 align:start position:0% compilation effort being wrapped up for 00:30:00.799 --> 00:30:03.110 align:start position:0% compilation effort being wrapped up for the<00:30:01.120> safety<00:30:01.840> element<00:30:02.399> of<00:30:02.480> the<00:30:02.559> county-wide 00:30:03.110 --> 00:30:03.120 align:start position:0% the safety element of the county-wide 00:30:03.120 --> 00:30:05.830 align:start position:0% the safety element of the county-wide plan<00:30:03.440> which<00:30:03.679> is<00:30:03.840> creating<00:30:04.240> a<00:30:04.399> data<00:30:04.799> atlas<00:30:05.600> so 00:30:05.830 --> 00:30:05.840 align:start position:0% plan which is creating a data atlas so 00:30:05.840 --> 00:30:07.350 align:start position:0% plan which is creating a data atlas so we're<00:30:06.080> talking<00:30:06.399> with<00:30:06.640> the<00:30:06.799> staff<00:30:07.039> leading 00:30:07.350 --> 00:30:07.360 align:start position:0% we're talking with the staff leading 00:30:07.360 --> 00:30:08.389 align:start position:0% we're talking with the staff leading that<00:30:07.600> effort 00:30:08.389 --> 00:30:08.399 align:start position:0% that effort 00:30:08.399 --> 00:30:09.990 align:start position:0% that effort to<00:30:08.559> figure<00:30:08.880> out<00:30:08.960> what<00:30:09.120> there<00:30:09.360> is<00:30:09.600> and<00:30:09.679> how<00:30:09.919> we 00:30:09.990 --> 00:30:10.000 align:start position:0% to figure out what there is and how we 00:30:10.000 --> 00:30:12.310 align:start position:0% to figure out what there is and how we can<00:30:10.159> compile<00:30:10.640> it<00:30:10.880> up<00:30:11.200> i<00:30:11.360> realize<00:30:11.679> that<00:30:11.919> is<00:30:12.080> not 00:30:12.310 --> 00:30:12.320 align:start position:0% can compile it up i realize that is not 00:30:12.320 --> 00:30:14.230 align:start position:0% can compile it up i realize that is not helpful<00:30:12.720> to<00:30:12.880> you<00:30:13.120> right<00:30:13.360> now<00:30:13.760> as<00:30:14.000> you 00:30:14.230 --> 00:30:14.240 align:start position:0% helpful to you right now as you 00:30:14.240 --> 00:30:15.350 align:start position:0% helpful to you right now as you understand 00:30:15.350 --> 00:30:15.360 align:start position:0% understand 00:30:15.360 --> 00:30:17.350 align:start position:0% understand what<00:30:15.600> you're<00:30:15.760> coming<00:30:16.080> into<00:30:16.880> when<00:30:17.039> you<00:30:17.120> write 00:30:17.350 --> 00:30:17.360 align:start position:0% what you're coming into when you write 00:30:17.360 --> 00:30:18.710 align:start position:0% what you're coming into when you write this<00:30:17.520> proposal 00:30:18.710 --> 00:30:18.720 align:start position:0% this proposal 00:30:18.720 --> 00:30:20.230 align:start position:0% this proposal um 00:30:20.230 --> 00:30:20.240 align:start position:0% um 00:30:20.240 --> 00:30:21.669 align:start position:0% um i'll<00:30:20.399> turn<00:30:20.640> it<00:30:20.720> over<00:30:20.880> to<00:30:21.039> jack<00:30:21.279> in<00:30:21.360> a<00:30:21.440> second 00:30:21.669 --> 00:30:21.679 align:start position:0% i'll turn it over to jack in a second 00:30:21.679 --> 00:30:23.350 align:start position:0% i'll turn it over to jack in a second but<00:30:21.840> i<00:30:21.919> just<00:30:22.080> do<00:30:22.240> want<00:30:22.399> to<00:30:22.559> clarify<00:30:23.039> it's<00:30:23.200> one 00:30:23.350 --> 00:30:23.360 align:start position:0% but i just do want to clarify it's one 00:30:23.360 --> 00:30:25.029 align:start position:0% but i just do want to clarify it's one of<00:30:23.440> those<00:30:23.679> areas<00:30:24.080> where 00:30:25.029 --> 00:30:25.039 align:start position:0% of those areas where 00:30:25.039 --> 00:30:26.789 align:start position:0% of those areas where we<00:30:25.279> recognize<00:30:25.679> that's<00:30:25.919> a<00:30:26.000> need<00:30:26.399> and<00:30:26.559> we're 00:30:26.789 --> 00:30:26.799 align:start position:0% we recognize that's a need and we're 00:30:26.799 --> 00:30:28.470 align:start position:0% we recognize that's a need and we're putting<00:30:27.039> our<00:30:27.200> staff<00:30:27.440> time<00:30:27.679> in<00:30:27.840> now<00:30:28.159> so<00:30:28.320> that 00:30:28.470 --> 00:30:28.480 align:start position:0% putting our staff time in now so that 00:30:28.480 --> 00:30:30.470 align:start position:0% putting our staff time in now so that when<00:30:28.640> a<00:30:28.720> firm<00:30:28.960> does<00:30:29.200> come<00:30:29.440> on<00:30:29.600> board<00:30:30.240> you're 00:30:30.470 --> 00:30:30.480 align:start position:0% when a firm does come on board you're 00:30:30.480 --> 00:30:32.870 align:start position:0% when a firm does come on board you're not<00:30:30.720> having<00:30:30.960> to<00:30:31.120> spend<00:30:31.840> a<00:30:31.919> significant<00:30:32.559> amount 00:30:32.870 --> 00:30:32.880 align:start position:0% not having to spend a significant amount 00:30:32.880 --> 00:30:33.830 align:start position:0% not having to spend a significant amount of<00:30:32.960> time 00:30:33.830 --> 00:30:33.840 align:start position:0% of time 00:30:33.840 --> 00:30:35.669 align:start position:0% of time digging<00:30:34.159> up<00:30:34.320> and<00:30:34.559> finding<00:30:34.960> that<00:30:35.200> data<00:30:35.520> that 00:30:35.669 --> 00:30:35.679 align:start position:0% digging up and finding that data that 00:30:35.679 --> 00:30:37.190 align:start position:0% digging up and finding that data that we're<00:30:35.919> able<00:30:36.240> to 00:30:37.190 --> 00:30:37.200 align:start position:0% we're able to 00:30:37.200 --> 00:30:40.870 align:start position:0% we're able to here's<00:30:37.520> what<00:30:37.600> we've<00:30:37.840> got<00:30:38.159> moving<00:30:38.640> forward 00:30:40.870 --> 00:30:40.880 align:start position:0% here's what we've got moving forward 00:30:40.880 --> 00:30:43.830 align:start position:0% here's what we've got moving forward yeah<00:30:41.039> the<00:30:41.520> um<00:30:42.000> as<00:30:42.240> i'm<00:30:42.880> writing<00:30:43.200> into<00:30:43.440> the<00:30:43.520> chat 00:30:43.830 --> 00:30:43.840 align:start position:0% yeah the um as i'm writing into the chat 00:30:43.840 --> 00:30:46.230 align:start position:0% yeah the um as i'm writing into the chat right<00:30:44.000> now<00:30:44.640> there<00:30:44.880> really<00:30:45.120> hasn't<00:30:45.440> been 00:30:46.230 --> 00:30:46.240 align:start position:0% right now there really hasn't been 00:30:46.240 --> 00:30:47.669 align:start position:0% right now there really hasn't been um 00:30:47.669 --> 00:30:47.679 align:start position:0% um 00:30:47.679 --> 00:30:49.750 align:start position:0% um significant<00:30:48.480> change 00:30:49.750 --> 00:30:49.760 align:start position:0% significant change 00:30:49.760 --> 00:30:53.350 align:start position:0% significant change in<00:30:50.320> in<00:30:50.559> the<00:30:50.720> condition<00:30:51.200> of<00:30:51.360> the<00:30:51.760> assets<00:30:52.399> so 00:30:53.350 --> 00:30:53.360 align:start position:0% in in the condition of the assets so 00:30:53.360 --> 00:30:54.389 align:start position:0% in in the condition of the assets so uh 00:30:54.389 --> 00:30:54.399 align:start position:0% uh 00:30:54.399 --> 00:30:55.909 align:start position:0% uh like<00:30:54.559> we<00:30:54.720> say<00:30:54.880> it's 00:30:55.909 --> 00:30:55.919 align:start position:0% like we say it's 00:30:55.919 --> 00:30:57.669 align:start position:0% like we say it's close<00:30:56.159> enough<00:30:56.399> for<00:30:56.559> government<00:30:56.960> work<00:30:57.279> at<00:30:57.440> this 00:30:57.669 --> 00:30:57.679 align:start position:0% close enough for government work at this 00:30:57.679 --> 00:30:59.110 align:start position:0% close enough for government work at this point<00:30:58.080> so<00:30:58.399> we 00:30:59.110 --> 00:30:59.120 align:start position:0% point so we 00:30:59.120 --> 00:31:01.190 align:start position:0% point so we at<00:30:59.279> the<00:30:59.440> conceptual<00:31:00.080> level<00:31:00.720> we're<00:31:00.880> not<00:31:01.039> going 00:31:01.190 --> 00:31:01.200 align:start position:0% at the conceptual level we're not going 00:31:01.200 --> 00:31:03.269 align:start position:0% at the conceptual level we're not going to<00:31:01.279> spend<00:31:01.519> a<00:31:01.600> lot<00:31:01.760> of<00:31:01.919> our<00:31:02.080> time 00:31:03.269 --> 00:31:03.279 align:start position:0% to spend a lot of our time 00:31:03.279 --> 00:31:04.870 align:start position:0% to spend a lot of our time and<00:31:03.440> we<00:31:03.600> don't<00:31:03.760> want<00:31:04.000> you<00:31:04.240> spending<00:31:04.559> a<00:31:04.640> lot<00:31:04.799> of 00:31:04.870 --> 00:31:04.880 align:start position:0% and we don't want you spending a lot of 00:31:04.880 --> 00:31:05.909 align:start position:0% and we don't want you spending a lot of your<00:31:05.120> time 00:31:05.909 --> 00:31:05.919 align:start position:0% your time 00:31:05.919 --> 00:31:09.269 align:start position:0% your time specifying<00:31:06.960> uh<00:31:07.600> you<00:31:07.760> know 00:31:09.269 --> 00:31:09.279 align:start position:0% specifying uh you know 00:31:09.279 --> 00:31:11.350 align:start position:0% specifying uh you know new<00:31:09.600> information<00:31:10.240> because<00:31:10.720> we<00:31:10.960> just<00:31:11.120> don't 00:31:11.350 --> 00:31:11.360 align:start position:0% new information because we just don't 00:31:11.360 --> 00:31:13.430 align:start position:0% new information because we just don't think<00:31:11.600> that<00:31:12.080> there's<00:31:12.399> that<00:31:12.640> much<00:31:12.880> of<00:31:13.039> it<00:31:13.279> and 00:31:13.430 --> 00:31:13.440 align:start position:0% think that there's that much of it and 00:31:13.440 --> 00:31:19.990 align:start position:0% think that there's that much of it and we<00:31:13.600> will<00:31:13.840> try<00:31:14.080> to<00:31:14.399> supply<00:31:14.880> that 00:31:19.990 --> 00:31:20.000 align:start position:0% 00:31:20.000 --> 00:31:23.110 align:start position:0% question<00:31:20.480> on<00:31:20.799> task<00:31:21.279> 3.1<00:31:22.080> the<00:31:22.240> first<00:31:22.559> step<00:31:22.960> in 00:31:23.110 --> 00:31:23.120 align:start position:0% question on task 3.1 the first step in 00:31:23.120 --> 00:31:25.430 align:start position:0% question on task 3.1 the first step in our<00:31:23.279> adaptation<00:31:24.080> planning<00:31:24.480> process<00:31:24.960> as<00:31:25.120> we 00:31:25.430 --> 00:31:25.440 align:start position:0% our adaptation planning process as we 00:31:25.440 --> 00:31:27.909 align:start position:0% our adaptation planning process as we anticipated<00:31:26.320> it<00:31:26.559> in<00:31:26.720> our<00:31:26.960> scope<00:31:27.279> of<00:31:27.440> work<00:31:27.840> in 00:31:27.909 --> 00:31:27.919 align:start position:0% anticipated it in our scope of work in 00:31:27.919 --> 00:31:30.549 align:start position:0% anticipated it in our scope of work in the<00:31:28.080> rfp<00:31:28.960> what<00:31:29.200> specific<00:31:29.679> asset<00:31:30.159> updates<00:31:30.480> are 00:31:30.549 --> 00:31:30.559 align:start position:0% the rfp what specific asset updates are 00:31:30.559 --> 00:31:32.470 align:start position:0% the rfp what specific asset updates are needed<00:31:30.880> since<00:31:31.120> 2016.<00:31:31.919> another<00:31:32.240> great 00:31:32.470 --> 00:31:32.480 align:start position:0% needed since 2016. another great 00:31:32.480 --> 00:31:33.750 align:start position:0% needed since 2016. another great question 00:31:33.750 --> 00:31:33.760 align:start position:0% question 00:31:33.760 --> 00:31:37.029 align:start position:0% question probably<00:31:34.320> not<00:31:34.559> a<00:31:34.720> whole<00:31:35.039> lot<00:31:35.760> um<00:31:36.320> we<00:31:36.559> put<00:31:36.720> that 00:31:37.029 --> 00:31:37.039 align:start position:0% probably not a whole lot um we put that 00:31:37.039 --> 00:31:38.870 align:start position:0% probably not a whole lot um we put that in<00:31:37.200> there 00:31:38.870 --> 00:31:38.880 align:start position:0% in there 00:31:38.880 --> 00:31:40.789 align:start position:0% in there we<00:31:39.039> want<00:31:39.200> to<00:31:39.279> make<00:31:39.519> sure<00:31:39.840> we're<00:31:40.080> not<00:31:40.399> missing 00:31:40.789 --> 00:31:40.799 align:start position:0% we want to make sure we're not missing 00:31:40.799 --> 00:31:42.789 align:start position:0% we want to make sure we're not missing anything<00:31:41.279> when<00:31:41.440> we<00:31:41.679> start<00:31:41.919> this<00:31:42.159> process<00:31:42.640> that 00:31:42.789 --> 00:31:42.799 align:start position:0% anything when we start this process that 00:31:42.799 --> 00:31:44.389 align:start position:0% anything when we start this process that said<00:31:43.039> there<00:31:43.200> was<00:31:43.279> significant<00:31:44.080> asset 00:31:44.389 --> 00:31:44.399 align:start position:0% said there was significant asset 00:31:44.399 --> 00:31:47.110 align:start position:0% said there was significant asset identification<00:31:45.360> done<00:31:46.320> in<00:31:46.480> support<00:31:46.880> of<00:31:47.039> the 00:31:47.110 --> 00:31:47.120 align:start position:0% identification done in support of the 00:31:47.120 --> 00:31:49.350 align:start position:0% identification done in support of the 2016<00:31:47.760> vulnerability<00:31:48.399> analysis<00:31:48.880> so<00:31:49.039> likely 00:31:49.350 --> 00:31:49.360 align:start position:0% 2016 vulnerability analysis so likely 00:31:49.360 --> 00:31:53.029 align:start position:0% 2016 vulnerability analysis so likely there's<00:31:49.679> not<00:31:49.840> much<00:31:50.159> new<00:31:50.960> we<00:31:51.120> do<00:31:51.360> see<00:31:51.600> it<00:31:51.760> as<00:31:51.919> a 00:31:53.029 --> 00:31:53.039 align:start position:0% there's not much new we do see it as a 00:31:53.039 --> 00:31:56.230 align:start position:0% there's not much new we do see it as a a<00:31:53.440> good<00:31:53.840> opening<00:31:54.320> point<00:31:54.880> to<00:31:55.200> involving<00:31:55.840> public 00:31:56.230 --> 00:31:56.240 align:start position:0% a good opening point to involving public 00:31:56.240 --> 00:31:58.710 align:start position:0% a good opening point to involving public inviting<00:31:56.799> if<00:31:56.880> there<00:31:57.200> are<00:31:57.760> additional<00:31:58.320> things 00:31:58.710 --> 00:31:58.720 align:start position:0% inviting if there are additional things 00:31:58.720 --> 00:32:01.430 align:start position:0% inviting if there are additional things that<00:31:59.120> folks<00:31:59.440> felt<00:31:59.679> were<00:31:59.919> missed<00:32:00.320> back<00:32:00.559> in<00:32:00.720> 2016 00:32:01.430 --> 00:32:01.440 align:start position:0% that folks felt were missed back in 2016 00:32:01.440 --> 00:32:03.750 align:start position:0% that folks felt were missed back in 2016 this<00:32:01.600> is<00:32:01.760> an<00:32:01.840> opportunity<00:32:02.480> to<00:32:03.120> to<00:32:03.279> open<00:32:03.519> that 00:32:03.750 --> 00:32:03.760 align:start position:0% this is an opportunity to to open that 00:32:03.760 --> 00:32:05.190 align:start position:0% this is an opportunity to to open that space<00:32:04.159> up<00:32:04.320> and<00:32:04.399> see<00:32:04.559> if<00:32:04.640> there's<00:32:04.880> anything 00:32:05.190 --> 00:32:05.200 align:start position:0% space up and see if there's anything 00:32:05.200 --> 00:32:06.870 align:start position:0% space up and see if there's anything there<00:32:05.440> but<00:32:05.840> we<00:32:06.080> at<00:32:06.159> the<00:32:06.320> county<00:32:06.640> don't 00:32:06.870 --> 00:32:06.880 align:start position:0% there but we at the county don't 00:32:06.880 --> 00:32:08.870 align:start position:0% there but we at the county don't anticipate<00:32:07.919> um 00:32:08.870 --> 00:32:08.880 align:start position:0% anticipate um 00:32:08.880 --> 00:32:11.350 align:start position:0% anticipate um specific<00:32:09.760> much<00:32:10.080> in<00:32:10.159> the<00:32:10.240> way<00:32:10.480> of<00:32:10.720> new<00:32:10.960> asset 00:32:11.350 --> 00:32:11.360 align:start position:0% specific much in the way of new asset 00:32:11.360 --> 00:32:14.710 align:start position:0% specific much in the way of new asset updates 00:32:14.710 --> 00:32:14.720 align:start position:0% 00:32:14.720 --> 00:32:17.029 align:start position:0% um<00:32:15.039> and<00:32:15.120> there's<00:32:15.440> one<00:32:15.600> more<00:32:15.840> question 00:32:17.029 --> 00:32:17.039 align:start position:0% um and there's one more question 00:32:17.039 --> 00:32:18.870 align:start position:0% um and there's one more question received<00:32:17.519> by<00:32:17.760> email<00:32:18.080> i'm<00:32:18.240> going<00:32:18.320> to<00:32:18.399> put<00:32:18.559> it<00:32:18.720> in 00:32:18.870 --> 00:32:18.880 align:start position:0% received by email i'm going to put it in 00:32:18.880 --> 00:32:20.630 align:start position:0% received by email i'm going to put it in i'm<00:32:18.960> not<00:32:19.200> sure<00:32:19.519> if<00:32:19.679> i<00:32:19.760> spoke<00:32:20.080> to<00:32:20.240> it<00:32:20.320> yet<00:32:20.480> so 00:32:20.630 --> 00:32:20.640 align:start position:0% i'm not sure if i spoke to it yet so 00:32:20.640 --> 00:32:23.269 align:start position:0% i'm not sure if i spoke to it yet so it's<00:32:20.880> probably<00:32:21.200> worth<00:32:21.519> reiterating<00:32:22.640> in<00:32:22.799> task 00:32:23.269 --> 00:32:23.279 align:start position:0% it's probably worth reiterating in task 00:32:23.279 --> 00:32:24.549 align:start position:0% it's probably worth reiterating in task two 00:32:24.549 --> 00:32:24.559 align:start position:0% two 00:32:24.559 --> 00:32:26.310 align:start position:0% two there's<00:32:24.880> understanding<00:32:25.440> that<00:32:25.600> the<00:32:25.679> counties 00:32:26.310 --> 00:32:26.320 align:start position:0% there's understanding that the counties 00:32:26.320 --> 00:32:28.870 align:start position:0% there's understanding that the counties contracted<00:32:27.440> rainwater<00:32:28.159> as<00:32:28.320> an<00:32:28.480> engagement 00:32:28.870 --> 00:32:28.880 align:start position:0% contracted rainwater as an engagement 00:32:28.880 --> 00:32:30.230 align:start position:0% contracted rainwater as an engagement consultant 00:32:30.230 --> 00:32:30.240 align:start position:0% consultant 00:32:30.240 --> 00:32:32.149 align:start position:0% consultant the<00:32:30.399> facilitation<00:32:31.200> text<00:32:31.440> from<00:32:31.600> the<00:32:31.679> rfp 00:32:32.149 --> 00:32:32.159 align:start position:0% the facilitation text from the rfp 00:32:32.159 --> 00:32:33.350 align:start position:0% the facilitation text from the rfp describing<00:32:32.640> the<00:32:32.720> proposer's 00:32:33.350 --> 00:32:33.360 align:start position:0% describing the proposer's 00:32:33.360 --> 00:32:34.710 align:start position:0% describing the proposer's responsibilities<00:32:34.159> in<00:32:34.240> addition<00:32:34.559> to<00:32:34.640> the 00:32:34.710 --> 00:32:34.720 align:start position:0% responsibilities in addition to the 00:32:34.720 --> 00:32:36.230 align:start position:0% responsibilities in addition to the engagement<00:32:35.120> consultant<00:32:35.679> all<00:32:35.760> right<00:32:35.919> so<00:32:36.080> the 00:32:36.230 --> 00:32:36.240 align:start position:0% engagement consultant all right so the 00:32:36.240 --> 00:32:39.029 align:start position:0% engagement consultant all right so the rfp<00:32:36.799> said<00:32:37.440> a<00:32:37.600> consultant<00:32:38.320> who<00:32:38.559> we're<00:32:38.720> looking 00:32:39.029 --> 00:32:39.039 align:start position:0% rfp said a consultant who we're looking 00:32:39.039 --> 00:32:40.710 align:start position:0% rfp said a consultant who we're looking for<00:32:39.279> under<00:32:39.440> this<00:32:39.679> rfp 00:32:40.710 --> 00:32:40.720 align:start position:0% for under this rfp 00:32:40.720 --> 00:32:43.269 align:start position:0% for under this rfp shall<00:32:41.039> lead<00:32:41.360> on<00:32:41.600> developing<00:32:42.399> creative 00:32:43.269 --> 00:32:43.279 align:start position:0% shall lead on developing creative 00:32:43.279 --> 00:32:45.909 align:start position:0% shall lead on developing creative engagement<00:32:43.919> activities<00:32:44.720> and<00:32:45.039> tools<00:32:45.600> for 00:32:45.909 --> 00:32:45.919 align:start position:0% engagement activities and tools for 00:32:45.919 --> 00:32:48.470 align:start position:0% engagement activities and tools for soliciting<00:32:46.559> input<00:32:47.039> during<00:32:47.360> public<00:32:47.679> meetings 00:32:48.470 --> 00:32:48.480 align:start position:0% soliciting input during public meetings 00:32:48.480 --> 00:32:50.789 align:start position:0% soliciting input during public meetings and<00:32:48.640> ongoing<00:32:49.120> stakeholder<00:32:49.679> engagement 00:32:50.789 --> 00:32:50.799 align:start position:0% and ongoing stakeholder engagement 00:32:50.799 --> 00:32:52.230 align:start position:0% and ongoing stakeholder engagement developing<00:32:51.279> and<00:32:51.360> delivering<00:32:51.840> technical 00:32:52.230 --> 00:32:52.240 align:start position:0% developing and delivering technical 00:32:52.240 --> 00:32:53.509 align:start position:0% developing and delivering technical presentations 00:32:53.509 --> 00:32:53.519 align:start position:0% presentations 00:32:53.519 --> 00:32:55.190 align:start position:0% presentations clearly<00:32:53.919> documenting<00:32:54.399> public<00:32:54.720> input<00:32:55.039> and 00:32:55.190 --> 00:32:55.200 align:start position:0% clearly documenting public input and 00:32:55.200 --> 00:32:57.110 align:start position:0% clearly documenting public input and providing<00:32:55.679> meeting<00:32:56.000> notes 00:32:57.110 --> 00:32:57.120 align:start position:0% providing meeting notes 00:32:57.120 --> 00:32:59.909 align:start position:0% providing meeting notes great<00:32:57.440> question 00:32:59.909 --> 00:32:59.919 align:start position:0% 00:32:59.919 --> 00:33:02.230 align:start position:0% we<00:33:00.159> are<00:33:00.320> looking<00:33:00.799> for<00:33:01.120> that 00:33:02.230 --> 00:33:02.240 align:start position:0% we are looking for that 00:33:02.240 --> 00:33:06.070 align:start position:0% we are looking for that creative<00:33:03.440> engagement<00:33:04.080> activities<00:33:04.640> and<00:33:04.799> tools 00:33:06.070 --> 00:33:06.080 align:start position:0% creative engagement activities and tools 00:33:06.080 --> 00:33:08.149 align:start position:0% creative engagement activities and tools we<00:33:06.240> welcome<00:33:06.559> them<00:33:06.880> anywhere<00:33:07.360> on<00:33:07.519> our<00:33:07.679> process 00:33:08.149 --> 00:33:08.159 align:start position:0% we welcome them anywhere on our process 00:33:08.159 --> 00:33:11.190 align:start position:0% we welcome them anywhere on our process the<00:33:08.399> more<00:33:08.720> the<00:33:08.880> better<00:33:09.600> we<00:33:09.919> really<00:33:10.320> need<00:33:10.640> them 00:33:11.190 --> 00:33:11.200 align:start position:0% the more the better we really need them 00:33:11.200 --> 00:33:13.110 align:start position:0% the more the better we really need them at<00:33:11.360> those<00:33:11.760> key<00:33:12.159> junctures<00:33:12.799> through<00:33:12.960> the 00:33:13.110 --> 00:33:13.120 align:start position:0% at those key junctures through the 00:33:13.120 --> 00:33:15.029 align:start position:0% at those key junctures through the adaptation<00:33:13.760> planning<00:33:14.080> process<00:33:14.640> which<00:33:14.880> we 00:33:15.029 --> 00:33:15.039 align:start position:0% adaptation planning process which we 00:33:15.039 --> 00:33:17.509 align:start position:0% adaptation planning process which we anticipated<00:33:15.760> with<00:33:15.919> a<00:33:16.080> series<00:33:16.480> of<00:33:16.640> six<00:33:17.120> public 00:33:17.509 --> 00:33:17.519 align:start position:0% anticipated with a series of six public 00:33:17.519 --> 00:33:19.669 align:start position:0% anticipated with a series of six public meetings<00:33:18.399> whose<00:33:18.640> themes<00:33:18.960> are<00:33:19.039> flexible<00:33:19.519> we 00:33:19.669 --> 00:33:19.679 align:start position:0% meetings whose themes are flexible we 00:33:19.679 --> 00:33:21.509 align:start position:0% meetings whose themes are flexible we put<00:33:19.919> ideas<00:33:20.240> in<00:33:20.399> the<00:33:20.480> rfp 00:33:21.509 --> 00:33:21.519 align:start position:0% put ideas in the rfp 00:33:21.519 --> 00:33:23.669 align:start position:0% put ideas in the rfp but<00:33:21.679> we<00:33:21.840> really<00:33:22.080> need<00:33:22.320> those<00:33:22.720> big<00:33:23.279> public 00:33:23.669 --> 00:33:23.679 align:start position:0% but we really need those big public 00:33:23.679 --> 00:33:25.190 align:start position:0% but we really need those big public touch<00:33:24.080> points<00:33:24.480> that's<00:33:24.720> where<00:33:24.880> we're<00:33:24.960> going<00:33:25.039> to 00:33:25.190 --> 00:33:25.200 align:start position:0% touch points that's where we're going to 00:33:25.200 --> 00:33:26.950 align:start position:0% touch points that's where we're going to need<00:33:25.360> a<00:33:25.440> lot<00:33:25.679> of<00:33:25.840> consultant<00:33:26.399> support<00:33:26.799> i'm 00:33:26.950 --> 00:33:26.960 align:start position:0% need a lot of consultant support i'm 00:33:26.960 --> 00:33:28.310 align:start position:0% need a lot of consultant support i'm thinking<00:33:27.279> about 00:33:28.310 --> 00:33:28.320 align:start position:0% thinking about 00:33:28.320 --> 00:33:30.389 align:start position:0% thinking about how<00:33:28.480> do<00:33:28.640> we<00:33:28.720> get<00:33:28.880> in<00:33:28.960> a<00:33:29.039> room<00:33:29.279> and<00:33:29.440> not<00:33:29.679> just<00:33:29.919> say 00:33:30.389 --> 00:33:30.399 align:start position:0% how do we get in a room and not just say 00:33:30.399 --> 00:33:32.470 align:start position:0% how do we get in a room and not just say here's<00:33:30.720> where<00:33:30.880> we<00:33:31.120> are<00:33:31.679> hand<00:33:31.919> it<00:33:32.080> back<00:33:32.320> you 00:33:32.470 --> 00:33:32.480 align:start position:0% here's where we are hand it back you 00:33:32.480 --> 00:33:35.029 align:start position:0% here's where we are hand it back you know<00:33:32.960> we're<00:33:33.200> looking<00:33:33.519> for<00:33:34.080> some<00:33:34.320> creativity 00:33:35.029 --> 00:33:35.039 align:start position:0% know we're looking for some creativity 00:33:35.039 --> 00:33:36.389 align:start position:0% know we're looking for some creativity there<00:33:35.519> um 00:33:36.389 --> 00:33:36.399 align:start position:0% there um 00:33:36.399 --> 00:33:38.070 align:start position:0% there um we<00:33:36.559> would<00:33:36.720> be<00:33:36.880> looking<00:33:37.120> to<00:33:37.279> the<00:33:37.360> consultants 00:33:38.070 --> 00:33:38.080 align:start position:0% we would be looking to the consultants 00:33:38.080 --> 00:33:39.990 align:start position:0% we would be looking to the consultants to<00:33:38.480> do<00:33:38.640> the<00:33:38.799> meeting<00:33:39.039> notes<00:33:39.360> for<00:33:39.519> those<00:33:39.679> large 00:33:39.990 --> 00:33:40.000 align:start position:0% to do the meeting notes for those large 00:33:40.000 --> 00:33:42.070 align:start position:0% to do the meeting notes for those large public<00:33:40.320> meetings<00:33:41.120> um<00:33:41.440> in<00:33:41.600> addition<00:33:41.919> to 00:33:42.070 --> 00:33:42.080 align:start position:0% public meetings um in addition to 00:33:42.080 --> 00:33:44.310 align:start position:0% public meetings um in addition to support<00:33:42.399> from<00:33:42.559> county<00:33:42.880> staff<00:33:43.279> that<00:33:43.519> is<00:33:43.679> not<00:33:44.159> a 00:33:44.310 --> 00:33:44.320 align:start position:0% support from county staff that is not a 00:33:44.320 --> 00:33:46.230 align:start position:0% support from county staff that is not a role<00:33:44.559> we're<00:33:44.720> putting<00:33:45.039> on<00:33:45.279> our<00:33:45.840> hired 00:33:46.230 --> 00:33:46.240 align:start position:0% role we're putting on our hired 00:33:46.240 --> 00:33:48.389 align:start position:0% role we're putting on our hired facilitator<00:33:47.200> the<00:33:47.360> facilitator<00:33:48.080> could<00:33:48.240> be 00:33:48.389 --> 00:33:48.399 align:start position:0% facilitator the facilitator could be 00:33:48.399 --> 00:33:49.909 align:start position:0% facilitator the facilitator could be brought<00:33:48.720> into<00:33:48.960> a<00:33:49.039> public<00:33:49.360> meeting<00:33:49.679> if<00:33:49.760> we 00:33:49.909 --> 00:33:49.919 align:start position:0% brought into a public meeting if we 00:33:49.919 --> 00:33:52.549 align:start position:0% brought into a public meeting if we anticipate<00:33:50.880> um<00:33:51.600> it<00:33:51.679> being<00:33:52.000> one<00:33:52.159> of<00:33:52.240> the<00:33:52.320> more 00:33:52.549 --> 00:33:52.559 align:start position:0% anticipate um it being one of the more 00:33:52.559 --> 00:33:55.029 align:start position:0% anticipate um it being one of the more difficult<00:33:53.039> conversations 00:33:55.029 --> 00:33:55.039 align:start position:0% difficult conversations 00:33:55.039 --> 00:33:56.789 align:start position:0% difficult conversations perhaps<00:33:55.440> where<00:33:55.600> there's<00:33:55.840> some<00:33:56.159> decisions 00:33:56.789 --> 00:33:56.799 align:start position:0% perhaps where there's some decisions 00:33:56.799 --> 00:33:59.190 align:start position:0% perhaps where there's some decisions being<00:33:57.200> made<00:33:57.919> or 00:33:59.190 --> 00:33:59.200 align:start position:0% being made or 00:33:59.200 --> 00:34:02.470 align:start position:0% being made or difficult<00:33:59.760> trade-offs<00:34:00.399> under<00:34:00.640> discussion 00:34:02.470 --> 00:34:02.480 align:start position:0% difficult trade-offs under discussion 00:34:02.480 --> 00:34:04.230 align:start position:0% difficult trade-offs under discussion the<00:34:02.640> facilitator<00:34:03.279> could<00:34:03.440> be<00:34:03.600> a<00:34:03.760> tool<00:34:04.080> there 00:34:04.230 --> 00:34:04.240 align:start position:0% the facilitator could be a tool there 00:34:04.240 --> 00:34:05.750 align:start position:0% the facilitator could be a tool there but<00:34:04.399> we<00:34:04.559> are<00:34:04.720> looking<00:34:04.960> to<00:34:05.039> the<00:34:05.120> consultants 00:34:05.750 --> 00:34:05.760 align:start position:0% but we are looking to the consultants 00:34:05.760 --> 00:34:07.350 align:start position:0% but we are looking to the consultants for<00:34:06.000> ideas<00:34:06.480> of 00:34:07.350 --> 00:34:07.360 align:start position:0% for ideas of 00:34:07.360 --> 00:34:10.069 align:start position:0% for ideas of how<00:34:07.600> to<00:34:08.000> go<00:34:08.320> into<00:34:08.560> those<00:34:08.879> meetings<00:34:09.599> deliver 00:34:10.069 --> 00:34:10.079 align:start position:0% how to go into those meetings deliver 00:34:10.079 --> 00:34:13.430 align:start position:0% how to go into those meetings deliver technical<00:34:10.639> information<00:34:11.280> but<00:34:11.440> also<00:34:11.760> solicit 00:34:13.430 --> 00:34:13.440 align:start position:0% technical information but also solicit 00:34:13.440 --> 00:34:18.230 align:start position:0% technical information but also solicit back<00:34:13.679> anything<00:34:14.000> further<00:34:14.320> from<00:34:14.480> you 00:34:18.230 --> 00:34:18.240 align:start position:0% 00:34:18.240 --> 00:34:20.629 align:start position:0% i<00:34:18.320> would<00:34:18.560> just<00:34:18.800> uh<00:34:19.119> clarify<00:34:19.679> that 00:34:20.629 --> 00:34:20.639 align:start position:0% i would just uh clarify that 00:34:20.639 --> 00:34:23.829 align:start position:0% i would just uh clarify that the<00:34:20.879> role<00:34:21.200> of<00:34:21.440> the<00:34:21.919> consultant<00:34:22.879> at<00:34:23.359> in<00:34:23.520> those 00:34:23.829 --> 00:34:23.839 align:start position:0% the role of the consultant at in those 00:34:23.839 --> 00:34:26.069 align:start position:0% the role of the consultant at in those public<00:34:24.240> meetings<00:34:24.800> is<00:34:24.960> to 00:34:26.069 --> 00:34:26.079 align:start position:0% public meetings is to 00:34:26.079 --> 00:34:29.109 align:start position:0% public meetings is to provide<00:34:26.560> the<00:34:26.800> technical<00:34:27.520> information<00:34:28.399> to<00:34:28.960> be 00:34:29.109 --> 00:34:29.119 align:start position:0% provide the technical information to be 00:34:29.119 --> 00:34:31.270 align:start position:0% provide the technical information to be able<00:34:29.280> to<00:34:29.520> explain<00:34:30.399> the<00:34:30.639> technical 00:34:31.270 --> 00:34:31.280 align:start position:0% able to explain the technical 00:34:31.280 --> 00:34:33.669 align:start position:0% able to explain the technical information 00:34:33.669 --> 00:34:33.679 align:start position:0% information 00:34:33.679 --> 00:34:34.790 align:start position:0% information uh 00:34:34.790 --> 00:34:34.800 align:start position:0% uh 00:34:34.800 --> 00:34:38.869 align:start position:0% uh let's<00:34:35.119> say<00:34:35.520> someone<00:34:36.240> is<00:34:36.560> challenged<00:34:37.599> um 00:34:38.869 --> 00:34:38.879 align:start position:0% let's say someone is challenged um 00:34:38.879 --> 00:34:42.710 align:start position:0% let's say someone is challenged um and<00:34:39.520> then<00:34:40.000> our<00:34:40.639> facilitator<00:34:41.760> will 00:34:42.710 --> 00:34:42.720 align:start position:0% and then our facilitator will 00:34:42.720 --> 00:34:44.069 align:start position:0% and then our facilitator will step<00:34:43.119> in 00:34:44.069 --> 00:34:44.079 align:start position:0% step in 00:34:44.079 --> 00:34:45.109 align:start position:0% step in and 00:34:45.109 --> 00:34:45.119 align:start position:0% and 00:34:45.119 --> 00:34:46.869 align:start position:0% and divert<00:34:45.760> or 00:34:46.869 --> 00:34:46.879 align:start position:0% divert or 00:34:46.879 --> 00:34:49.669 align:start position:0% divert or otherwise<00:34:47.520> deal<00:34:47.839> with<00:34:48.399> will<00:34:48.800> with<00:34:48.960> that<00:34:49.280> issue 00:34:49.669 --> 00:34:49.679 align:start position:0% otherwise deal with will with that issue 00:34:49.679 --> 00:34:50.550 align:start position:0% otherwise deal with will with that issue but 00:34:50.550 --> 00:34:50.560 align:start position:0% but 00:34:50.560 --> 00:34:53.419 align:start position:0% but uh<00:34:50.960> it's<00:34:51.280> the<00:34:51.520> substantive 00:34:53.419 --> 00:34:53.429 align:start position:0% uh it's the substantive 00:34:53.429 --> 00:34:54.629 align:start position:0% uh it's the substantive [Music] 00:34:54.629 --> 00:34:54.639 align:start position:0% [Music] 00:34:54.639 --> 00:34:56.629 align:start position:0% [Music] data<00:34:55.119> that<00:34:55.440> that<00:34:55.679> we're<00:34:55.919> looking<00:34:56.240> for<00:34:56.480> from 00:34:56.629 --> 00:34:56.639 align:start position:0% data that that we're looking for from 00:34:56.639 --> 00:34:59.430 align:start position:0% data that that we're looking for from the<00:34:56.800> consultant 00:34:59.430 --> 00:34:59.440 align:start position:0% 00:34:59.440 --> 00:35:00.230 align:start position:0% okay 00:35:00.230 --> 00:35:00.240 align:start position:0% okay 00:35:00.240 --> 00:35:01.990 align:start position:0% okay and<00:35:00.480> i<00:35:00.720> see<00:35:00.880> one<00:35:01.040> that<00:35:01.200> was<00:35:01.440> answered<00:35:01.760> in<00:35:01.920> the 00:35:01.990 --> 00:35:02.000 align:start position:0% and i see one that was answered in the 00:35:02.000 --> 00:35:03.270 align:start position:0% and i see one that was answered in the chat<00:35:02.240> but<00:35:02.400> i'm<00:35:02.480> just<00:35:02.640> going<00:35:02.720> to<00:35:02.800> read<00:35:03.040> it<00:35:03.119> to 00:35:03.270 --> 00:35:03.280 align:start position:0% chat but i'm just going to read it to 00:35:03.280 --> 00:35:04.870 align:start position:0% chat but i'm just going to read it to folks<00:35:03.760> given<00:35:04.000> that<00:35:04.160> the<00:35:04.240> vulnerability 00:35:04.870 --> 00:35:04.880 align:start position:0% folks given that the vulnerability 00:35:04.880 --> 00:35:07.750 align:start position:0% folks given that the vulnerability assessment<00:35:05.440> is<00:35:05.599> based<00:35:05.920> on<00:35:06.359> 2015-2016<00:35:07.440> asset 00:35:07.750 --> 00:35:07.760 align:start position:0% assessment is based on 2015-2016 asset 00:35:07.760 --> 00:35:10.550 align:start position:0% assessment is based on 2015-2016 asset data<00:35:08.480> will<00:35:08.720> current<00:35:09.119> and<00:35:09.359> historical<00:35:09.920> gis 00:35:10.550 --> 00:35:10.560 align:start position:0% data will current and historical gis 00:35:10.560 --> 00:35:13.349 align:start position:0% data will current and historical gis that's<00:35:11.200> data<00:35:11.520> sets<00:35:11.839> excuse<00:35:12.240> me<00:35:12.720> be<00:35:12.880> available 00:35:13.349 --> 00:35:13.359 align:start position:0% that's data sets excuse me be available 00:35:13.359 --> 00:35:15.430 align:start position:0% that's data sets excuse me be available to<00:35:13.520> identify<00:35:14.079> any<00:35:14.320> changes<00:35:14.640> in<00:35:14.800> exposure 00:35:15.430 --> 00:35:15.440 align:start position:0% to identify any changes in exposure 00:35:15.440 --> 00:35:17.030 align:start position:0% to identify any changes in exposure since<00:35:15.680> that<00:35:15.920> time 00:35:17.030 --> 00:35:17.040 align:start position:0% since that time 00:35:17.040 --> 00:35:18.550 align:start position:0% since that time and<00:35:17.119> the<00:35:17.200> answer<00:35:17.520> provided<00:35:18.000> is<00:35:18.160> we<00:35:18.240> will<00:35:18.400> do 00:35:18.550 --> 00:35:18.560 align:start position:0% and the answer provided is we will do 00:35:18.560 --> 00:35:20.230 align:start position:0% and the answer provided is we will do some<00:35:18.800> updating<00:35:19.200> but<00:35:19.359> we<00:35:19.520> recognize<00:35:20.079> there's 00:35:20.230 --> 00:35:20.240 align:start position:0% some updating but we recognize there's 00:35:20.240 --> 00:35:21.670 align:start position:0% some updating but we recognize there's not<00:35:20.400> been<00:35:20.480> a<00:35:20.560> great<00:35:20.720> deal<00:35:20.880> of<00:35:21.040> change<00:35:21.440> as<00:35:21.599> i 00:35:21.670 --> 00:35:21.680 align:start position:0% not been a great deal of change as i 00:35:21.680 --> 00:35:23.910 align:start position:0% not been a great deal of change as i said<00:35:22.240> um<00:35:22.640> we<00:35:22.800> can<00:35:22.960> solicit<00:35:23.359> more<00:35:23.520> information 00:35:23.910 --> 00:35:23.920 align:start position:0% said um we can solicit more information 00:35:23.920 --> 00:35:26.150 align:start position:0% said um we can solicit more information from<00:35:24.079> the<00:35:24.160> public<00:35:24.720> again<00:35:24.960> we're<00:35:25.119> going<00:35:25.920> that 00:35:26.150 --> 00:35:26.160 align:start position:0% from the public again we're going that 00:35:26.160 --> 00:35:28.069 align:start position:0% from the public again we're going that means<00:35:26.480> of<00:35:26.640> engaging<00:35:27.119> and<00:35:27.280> asking<00:35:27.680> if<00:35:27.839> there's 00:35:28.069 --> 00:35:28.079 align:start position:0% means of engaging and asking if there's 00:35:28.079 --> 00:35:30.230 align:start position:0% means of engaging and asking if there's anything<00:35:28.480> that<00:35:28.640> folks<00:35:28.960> want<00:35:29.200> to<00:35:29.359> see<00:35:29.760> added<00:35:30.160> in 00:35:30.230 --> 00:35:30.240 align:start position:0% anything that folks want to see added in 00:35:30.240 --> 00:35:31.910 align:start position:0% anything that folks want to see added in terms<00:35:30.560> of<00:35:30.640> vulnerable<00:35:31.040> assets<00:35:31.440> we<00:35:31.599> do<00:35:31.760> think 00:35:31.910 --> 00:35:31.920 align:start position:0% terms of vulnerable assets we do think 00:35:31.920 --> 00:35:33.670 align:start position:0% terms of vulnerable assets we do think there's<00:35:32.160> value<00:35:32.480> there<00:35:32.800> that<00:35:33.119> has<00:35:33.280> gone<00:35:33.520> well 00:35:33.670 --> 00:35:33.680 align:start position:0% there's value there that has gone well 00:35:33.680 --> 00:35:35.510 align:start position:0% there's value there that has gone well for<00:35:33.920> us<00:35:34.079> previously<00:35:34.800> working<00:35:35.119> with<00:35:35.280> the 00:35:35.510 --> 00:35:35.520 align:start position:0% for us previously working with the 00:35:35.520 --> 00:35:37.109 align:start position:0% for us previously working with the western 00:35:37.109 --> 00:35:37.119 align:start position:0% western 00:35:37.119 --> 00:35:37.460 align:start position:0% western um 00:35:37.460 --> 00:35:37.470 align:start position:0% um 00:35:37.470 --> 00:35:39.030 align:start position:0% um [Music] 00:35:39.030 --> 00:35:39.040 align:start position:0% [Music] 00:35:39.040 --> 00:35:40.790 align:start position:0% [Music] all<00:35:39.200> right<00:35:39.680> well 00:35:40.790 --> 00:35:40.800 align:start position:0% all right well 00:35:40.800 --> 00:35:42.550 align:start position:0% all right well i'm<00:35:41.040> gonna<00:35:41.280> just<00:35:41.520> scan<00:35:41.839> through<00:35:42.079> the<00:35:42.160> chat<00:35:42.400> one 00:35:42.550 --> 00:35:42.560 align:start position:0% i'm gonna just scan through the chat one 00:35:42.560 --> 00:35:44.630 align:start position:0% i'm gonna just scan through the chat one more<00:35:42.720> time<00:35:42.960> to<00:35:43.040> make<00:35:43.280> sure<00:35:43.599> i 00:35:44.630 --> 00:35:44.640 align:start position:0% more time to make sure i 00:35:44.640 --> 00:35:46.950 align:start position:0% more time to make sure i got<00:35:45.520> everything<00:35:46.000> if<00:35:46.240> anything<00:35:46.560> else<00:35:46.800> is<00:35:46.880> on 00:35:46.950 --> 00:35:46.960 align:start position:0% got everything if anything else is on 00:35:46.960 --> 00:35:49.510 align:start position:0% got everything if anything else is on your<00:35:47.119> mind<00:35:47.280> you<00:35:47.440> still<00:35:47.599> have<00:35:47.839> 14<00:35:48.480> minutes 00:35:49.510 --> 00:35:49.520 align:start position:0% your mind you still have 14 minutes 00:35:49.520 --> 00:36:00.710 align:start position:0% your mind you still have 14 minutes um 00:36:00.710 --> 00:36:00.720 align:start position:0% 00:36:00.720 --> 00:36:03.990 align:start position:0% all<00:36:00.880> right 00:36:03.990 --> 00:36:04.000 align:start position:0% 00:36:04.000 --> 00:36:05.750 align:start position:0% all<00:36:04.160> right<00:36:04.720> it's<00:36:04.800> looking<00:36:05.119> to<00:36:05.200> me<00:36:05.359> like<00:36:05.520> we<00:36:05.599> got 00:36:05.750 --> 00:36:05.760 align:start position:0% all right it's looking to me like we got 00:36:05.760 --> 00:36:07.670 align:start position:0% all right it's looking to me like we got the<00:36:05.920> questions<00:36:06.560> again<00:36:06.960> i<00:36:07.200> really<00:36:07.440> want<00:36:07.599> to 00:36:07.670 --> 00:36:07.680 align:start position:0% the questions again i really want to 00:36:07.680 --> 00:36:09.589 align:start position:0% the questions again i really want to thank<00:36:07.920> everyone<00:36:08.240> for<00:36:08.400> taking<00:36:08.640> the<00:36:08.800> time<00:36:09.440> for 00:36:09.589 --> 00:36:09.599 align:start position:0% thank everyone for taking the time for 00:36:09.599 --> 00:36:13.109 align:start position:0% thank everyone for taking the time for participating<00:36:10.240> in<00:36:10.320> the<00:36:10.400> most<00:36:11.119> cough<00:36:11.440> cask<00:36:12.000> q<00:36:12.320> a 00:36:13.109 --> 00:36:13.119 align:start position:0% participating in the most cough cask q a 00:36:13.119 --> 00:36:14.150 align:start position:0% participating in the most cough cask q a um 00:36:14.150 --> 00:36:14.160 align:start position:0% um 00:36:14.160 --> 00:36:16.710 align:start position:0% um really<00:36:14.560> appreciate<00:36:15.040> your<00:36:15.680> interest<00:36:16.560> we're 00:36:16.710 --> 00:36:16.720 align:start position:0% really appreciate your interest we're 00:36:16.720 --> 00:36:19.910 align:start position:0% really appreciate your interest we're very<00:36:16.960> excited<00:36:17.440> we<00:36:17.760> do<00:36:18.000> welcome<00:36:18.400> the<00:36:18.800> creative 00:36:19.910 --> 00:36:19.920 align:start position:0% very excited we do welcome the creative 00:36:19.920 --> 00:36:22.390 align:start position:0% very excited we do welcome the creative you<00:36:20.079> know<00:36:20.320> bring<00:36:20.800> your<00:36:21.119> ideas<00:36:21.680> your<00:36:22.000> approach 00:36:22.390 --> 00:36:22.400 align:start position:0% you know bring your ideas your approach 00:36:22.400 --> 00:36:24.550 align:start position:0% you know bring your ideas your approach we<00:36:22.560> recognize<00:36:23.359> that<00:36:23.599> um<00:36:24.160> we're<00:36:24.320> really 00:36:24.550 --> 00:36:24.560 align:start position:0% we recognize that um we're really 00:36:24.560 --> 00:36:25.910 align:start position:0% we recognize that um we're really excited<00:36:24.960> to<00:36:25.040> be<00:36:25.119> leaning<00:36:25.440> this<00:36:25.599> effort<00:36:25.839> we 00:36:25.910 --> 00:36:25.920 align:start position:0% excited to be leaning this effort we 00:36:25.920 --> 00:36:27.829 align:start position:0% excited to be leaning this effort we know<00:36:26.079> we<00:36:26.160> have<00:36:26.240> a<00:36:26.240> lot<00:36:26.400> to<00:36:26.560> learn<00:36:26.800> as<00:36:26.880> well<00:36:27.200> so 00:36:27.829 --> 00:36:27.839 align:start position:0% know we have a lot to learn as well so 00:36:27.839 --> 00:36:30.630 align:start position:0% know we have a lot to learn as well so we're<00:36:28.079> excited<00:36:28.640> to<00:36:29.040> see<00:36:29.280> your<00:36:29.440> submittals 00:36:30.630 --> 00:36:30.640 align:start position:0% we're excited to see your submittals 00:36:30.640 --> 00:36:32.390 align:start position:0% we're excited to see your submittals and<00:36:31.280> um 00:36:32.390 --> 00:36:32.400 align:start position:0% and um 00:36:32.400 --> 00:36:33.990 align:start position:0% and um thank<00:36:32.640> you<00:36:32.720> so<00:36:32.880> much<00:36:33.040> for<00:36:33.200> joining<00:36:33.520> today<00:36:33.839> so 00:36:33.990 --> 00:36:34.000 align:start position:0% thank you so much for joining today so 00:36:34.000 --> 00:36:35.829 align:start position:0% thank you so much for joining today so i'm<00:36:34.160> gonna<00:36:34.480> stop<00:36:34.720> this<00:36:34.880> recording<00:36:35.520> and<00:36:35.680> we 00:36:35.829 --> 00:36:35.839 align:start position:0% i'm gonna stop this recording and we 00:36:35.839 --> 00:36:37.589 align:start position:0% i'm gonna stop this recording and we will<00:36:36.079> be<00:36:36.400> i'll<00:36:36.640> turn<00:36:36.880> it<00:36:36.960> over<00:36:37.119> to<00:36:37.280> jack<00:36:37.440> to 00:36:37.589 --> 00:36:37.599 align:start position:0% will be i'll turn it over to jack to 00:36:37.599 --> 00:36:39.030 align:start position:0% will be i'll turn it over to jack to close<00:36:37.839> this<00:36:38.000> out<00:36:38.160> and<00:36:38.240> then<00:36:38.400> i<00:36:38.480> will<00:36:38.720> stop<00:36:38.880> the 00:36:39.030 --> 00:36:39.040 align:start position:0% close this out and then i will stop the 00:36:39.040 --> 00:36:40.950 align:start position:0% close this out and then i will stop the recording<00:36:39.839> so<00:36:40.079> again<00:36:40.240> thanks<00:36:40.480> for<00:36:40.560> joining 00:36:40.950 --> 00:36:40.960 align:start position:0% recording so again thanks for joining 00:36:40.960 --> 00:36:42.710 align:start position:0% recording so again thanks for joining and<00:36:41.119> over<00:36:41.359> to<00:36:41.440> you<00:36:41.599> jack 00:36:42.710 --> 00:36:42.720 align:start position:0% and over to you jack 00:36:42.720 --> 00:36:44.230 align:start position:0% and over to you jack thank<00:36:42.960> you<00:36:43.200> for 00:36:44.230 --> 00:36:44.240 align:start position:0% thank you for 00:36:44.240 --> 00:36:46.069 align:start position:0% thank you for sticking<00:36:44.720> with<00:36:44.960> us<00:36:45.200> through<00:36:45.440> this<00:36:45.680> rather 00:36:46.069 --> 00:36:46.079 align:start position:0% sticking with us through this rather 00:36:46.079 --> 00:36:49.190 align:start position:0% sticking with us through this rather difficult<00:36:46.720> uh<00:36:47.359> um<00:36:47.920> arrangement<00:36:48.560> we're<00:36:48.720> gonna 00:36:49.190 --> 00:36:49.200 align:start position:0% difficult uh um arrangement we're gonna 00:36:49.200 --> 00:36:50.950 align:start position:0% difficult uh um arrangement we're gonna figure<00:36:49.520> out<00:36:49.680> what's<00:36:50.079> what's<00:36:50.320> going<00:36:50.640> on<00:36:50.880> i 00:36:50.950 --> 00:36:50.960 align:start position:0% figure out what's what's going on i 00:36:50.960 --> 00:36:52.870 align:start position:0% figure out what's what's going on i think<00:36:51.200> there's<00:36:51.440> a<00:36:51.520> problem<00:36:51.920> at<00:36:52.079> the<00:36:52.320> county 00:36:52.870 --> 00:36:52.880 align:start position:0% think there's a problem at the county 00:36:52.880 --> 00:36:55.030 align:start position:0% think there's a problem at the county throughout<00:36:53.200> the<00:36:53.359> county<00:36:53.680> but 00:36:55.030 --> 00:36:55.040 align:start position:0% throughout the county but 00:36:55.040 --> 00:36:56.069 align:start position:0% throughout the county but again<00:36:55.359> if 00:36:56.069 --> 00:36:56.079 align:start position:0% again if 00:36:56.079 --> 00:36:59.190 align:start position:0% again if uh<00:36:56.400> we<00:36:56.720> we<00:36:56.960> said<00:36:57.359> that<00:36:57.760> uh<00:36:58.320> we're<00:36:58.720> not<00:36:58.880> gonna 00:36:59.190 --> 00:36:59.200 align:start position:0% uh we we said that uh we're not gonna 00:36:59.200 --> 00:37:02.310 align:start position:0% uh we we said that uh we're not gonna take<00:36:59.440> any<00:36:59.680> questions<00:37:00.560> uh<00:37:01.119> after<00:37:01.520> this<00:37:01.920> but 00:37:02.310 --> 00:37:02.320 align:start position:0% take any questions uh after this but 00:37:02.320 --> 00:37:04.630 align:start position:0% take any questions uh after this but considering<00:37:02.880> what<00:37:03.040> we<00:37:03.200> have<00:37:03.440> here<00:37:04.079> we'll<00:37:04.320> take 00:37:04.630 --> 00:37:04.640 align:start position:0% considering what we have here we'll take 00:37:04.640 --> 00:37:06.230 align:start position:0% considering what we have here we'll take questions<00:37:05.119> to<00:37:05.280> the<00:37:05.520> end<00:37:05.680> of<00:37:05.760> the<00:37:05.839> week<00:37:06.079> and 00:37:06.230 --> 00:37:06.240 align:start position:0% questions to the end of the week and 00:37:06.240 --> 00:37:09.190 align:start position:0% questions to the end of the week and share<00:37:06.480> those<00:37:06.800> with<00:37:07.119> with<00:37:07.359> everyone<00:37:07.760> else<00:37:08.240> and 00:37:09.190 --> 00:37:09.200 align:start position:0% share those with with everyone else and 00:37:09.200 --> 00:37:11.670 align:start position:0% share those with with everyone else and i'll<00:37:09.440> let<00:37:09.680> julia<00:37:10.160> know<00:37:10.400> that<00:37:10.640> because<00:37:10.960> she 00:37:11.670 --> 00:37:11.680 align:start position:0% i'll let julia know that because she 00:37:11.680 --> 00:37:15.910 align:start position:0% i'll let julia know that because she didn't<00:37:12.000> hear<00:37:12.240> me<00:37:12.480> so<00:37:13.119> thanks<00:37:13.440> again<00:37:14.079> and<00:37:14.560> uh 00:37:15.910 --> 00:37:15.920 align:start position:0% didn't hear me so thanks again and uh 00:37:15.920 --> 00:37:17.349 align:start position:0% didn't hear me so thanks again and uh have<00:37:16.160> a<00:37:16.240> great<00:37:16.400> day 00:37:17.349 --> 00:37:17.359 align:start position:0% have a great day 00:37:17.359 --> 00:37:19.990 align:start position:0% have a great day bye-bye 00:37:19.990 --> 00:37:20.000 align:start position:0% 00:37:20.000 --> 00:37:23.320 align:start position:0% thank<00:37:20.240> you<00:37:20.320> everyone