I’m trying to setup the DotNetNuke map module using DNN 4.9.  When I try to use Find Address on the Data page it always returns “Sorry, we are unable to locate a point for that address. Please try again.”  I’ve tried creating an entry for the address and on the Data page and Execute Geo Coding on the Data Source page but it does not resolve the longitude and latitude.  The address is nothing special: <house number> <street>, <city> <state> <zip> on a house that’s been around for over 50+ years and is easily found via google maps.  When I view the DNN page with the map module it always says “Loading…” at the bottom of the module.  My site is hosted by GoDaddy.

 

The setup: 

General

Map Settings

        Visual Provider: Google.Standard

Source Settings

        Data Provider: DotNetNuke.Map.Basic

        Geocoer: Google.GeoLocator

Interface

        Google License Keys: one entered for web site root address

        Markers: icon & shadow icon selected

        Map Layout: map displays and can be manipulated to zoom in street

        Width 100%, Height 300px, Zoom 14, Type: Map, Control: Visible, Nav Control: Large, Overview: Visible

        Standard Layout Settings: Initial Delay 1000, Retry 500

Data Source: Standard Data Points

<div style='background: white;'>

[DESCRIPTION]<br>

The Place

[ADDRESS] 

</div>

Data: one valid street address (no unit #, po box, etc) 

Geo Locator: include postal code, city & street.  The API Key is entered.

 

Can anyone clue me as to what I’m doing wrong? 

Thanks in advance for any feedback,

Karl

 

 

You probably aren't getting any replies because something is broken with the reply function. It's bumped me many times. Anyway, I am having the same issue. When I click to run geocoding, the screen updates but no errors are written to the log, no messages shown on the page, but no locations are encoded.

I have made the changes that I needed to in order to save the data points. It saves to the database just fine. It just doesn't to do the geoencoding. I looked for posts that mention javascript fixes that may help with encoding, but can't find anything. Can you please provide a link to the post you speak of?