Hi Kevin,

Love the module and I use it for a couple of clients here. One thing though: there is a pretty serious issue with lat/long conversions that won't become aparent unless you start building multilingual sites. The problem is the fact that the decimal point is a decimal comma in some cultures. So (de)serializations should always make sure that they use the System.Globalization.CultureInfo.InvariantCulture. For probably very good reasons you've chosen to leave Latitude and Longitude in the map config as strings. But the conversion is culture sensitive. So someone that edits the map in en-US and sets a longitude of 6.87027, that will not parse out in fr-FR. So IsNumeric(_Longitude) (configuration.vb, line 70, v.01.00.09) will fail and 0.0 will be returned. The net result is that while on my map the central location is shown well in us-EN, as soon as a fr-FR visitor comes to the site, the central location is off the coast of Africa (0.0, 0.0).

You'll need to do the following:

1. You type specify the lat and long to be doubles in configuration.vb
2. You handle conversions of string to double and reverse using the InvariantCulture.

Cheers,

Peter