Google Maps Keyhaven

[Keri Gamrath]

TheBuilding Department has collaborated with Forerunner Industries to offer property owners an interactive flood map that combines officially adopted and preliminary flood maps. This map includes property value assessments, relevant floodplain documents like elevation certificates, and comprehensive substantial improvement and damage tracking. To access this valuable resource, please click on the image provided.

Coastal Flood Maps, otherwise known as Flood Insurance Rate Maps (FIRMs) are used to determine the minimum elevation needed for construction to reduce the chances of flooding, as well as construction methods required in certain zones.

PLEASE NOTE: This application does not search for properties by Address; and the data in this application is ONLY for Unincorporated Monroe County and does not reflect any of the incorporated municipalities in Monroe County.

The County has hired a consultant to analyze how flood risks are changing in Unincorporated Monroe County based on the provided studies using updated information and the best available science and technology. The technical consultant will also be reviewing the maps and modeling conducted by FEMA and is prepared to appeal any of the maps that do not appear to be correct.

FEMA use of a single Coastal Reference Point (CRP) in Miami-Dade County to establish a set of synthetic storms for modeling is not representative of the Keys (see picture below). The storms defined using this single CRP are not realistic for Monroe County in terms of storm rate and intensity. The adjacent Southwest Florida RiskMap study used spatially varied storm rates and storm parameters; this type of analysis would be more appropriate for the Keys. It also appears that the synthetic storms did not include attenuation caused by landmasses.

A non-standard analysis that combined storm sets from the east and west was used to develop the 1 percent water levels (see picture below). The Combined Probability Analysis (CPS) assumed the storm sets were independent even though both sets have Atlantic and Caribbean genesis storms, potentially leading to inflated 1 percent water levels on the ocean side of the Keys. Additionally, the study did not include measurements errors in the statistical analysis, which is inconsistent with other FEMA RiskMap studies.

Documentation for the South Florida RiskMap study indicates the wave model was not validated against measured data, citing the lack of available data as the reason. However, a review of wave data collected by the NOAA National Data Buoy Center shows measured data at three buoys for storms impacting the Keys (see picture below). A comparison of model results against data collected during Hurricane Andrew shows an overprediction of wave height and period during the peak of the hurricane.

Errors in the development of the hydrodynamic/wave model mesh were identified at seven-channel locations throughout the Keys. The mesh resolution was not fine enough to allow the conveyance of storm surge and waves during all simulated storms (see picture below).

When considering reefs in the hydrodynamic/wave model, FEMA used friction values lower than recommended by the scientific literature (Figure 5). Since friction created by the reefs acts to dissipate the amount of wave energy reaching the shoreline, this issue could have an impact on the overland wave modeling and flood zone mapping.

Transect spacing in Monroe County is 2.2 to 2.7 times greater than the transect spacing in the neighboring counties of Palm Beach and Broward. Given the irregular nature of the shoreline in the Keys, as well as variations in development and vegetation, the transect spacing in Monroe County should be reduced. This will help to characterize irregularities in the shoreline and improve the accuracy of flood zone mapping between transects.

Topography used by FEMA for modeling and mapping differs from Monroe County mobile LiDAR data collected post-hurricane Irma in seven areas throughout Monroe County. In these specific areas, the FEMA topography is lower than the mobile LiDAR data by 0.5 to 1 ft (see picture below). Since the ground elevations influence the extent of flooding and wave action along the coast, this issue could have an impact on the overland wave modeling and flood zone mapping.

Woods Hole Group is currently working to further investigate the influence of these areas of concern on the FIRMs, and to develop the technical information necessary for an appeal of the December 2019 maps.

Monroe County wants to ensure all residents and business owners are aware of the potential for a change in flood risk for their property so that they can be more proactive in reducing their flood risk.

This is intended to help homeowners understand that what they might be proposing to build today, under the existing flood maps, could become non-conforming after the maps are changed, thereby making their flood risk and insurance costs greater. Owners should think about designing their improvements to meet the proposed PRELIMINARY maps to assure they are addressing potential future risks.

During the week of January 27, 2020, FEMA held Community meetings throughout the Keys, offering the public an opportunity to view and comment in person on the proposed PRELIMINARY Flood Insurance Rate Maps. Following this, Monroe County, through its Consultant, examined the maps and the accompanying Flood Insurance Studies provided by FEMA.

When that happens, the county will formally adopt the maps by ordinance and the maps will be used when reviewing permits; and the final maps will establish what a finished floor elevation needs to be and determine building and site design requirements to reduce future risk of flooding. New lender requirements may go into effect along with flood insurance requirements, as well as changes in flood insurance rates as a result of map changes.

For more information about the FEMA mapping process, email Floo...@MonroeCounty-FL.gov or call 305-453-8759. To learn more about flood insurance, talk to your insurance agent, or visit FloodSmart.gov.

So for you guys who installed mdekker's code, if you decide to edit /controllers/front/StoresController.php and add the key there it will not work with this module installed and the key field in the module config empty. You will have to unisntall first and clear the smarty or other cache.

More: I started developing shop with test domain before changes in Google maps. So with test domain I can test both: with and without api key. Without api key all works. When I add api key map is displayed correctly but searching is broken. The only change in code and database is in StoresController. So definitely adding api key solves problem with map but breaks searching.

I am totally lost. I have set up the browser api key and enabled three apis including the javascript one. I copied the key to the google map fix module. Not working. Then I manually added it to the controllers/front/StoresController.php. Still not working. Any suggestion? the url is

Good evening, I'm having the same problem on the maps . already created the api key and put on file /controllers/front/StoresController.php put the map appears and disappears then with the message " Oops ! Something went wrong. This page did not load Google Maps correctly. See the JavaScript console to see technical details . " My version of prestashop is 1.6.1.6 . I have another store on the same server and does not occur this problem . I do not know what to do. I appreciate any help .

Reading the thread some comment said that It would be some problem of the theme... so I have notice that using both solutions in this thread nothing change on the mesages I saw in my Javascript console. I went to the theme support and found that in my case, the theme called Google Maps byself not using StoresController.php so I found the file in my theme (who was a module by my themes author) and changed there the API Key.

Ah! the varible "sensor is deprecated and not used anymore so use:

Try read more carefuly next time You've assigned your api key to region instead key and that's why google is still blocking your map generation. So to fix this just change

3a8082e126