Convert WGS84 to Web Mercator Pixel

My google-fu wasn't the best when searching for a way to convert WGS84 to Web Mercator EPSG:3857, which is the common Google Maps and Bing Maps projection. If you have arrived here in search of an answer, the links to explain everything are below.

Essential Background

Take the EPSG WKT from article 1, and use it in the library

The definitive MSDN article

Code from MSDN article that doesn't use the Library

Live Demo (in JavaScript):

And this next section is just to help others search and get here:

Convert WGS84 to Web Mercator
Convert WGS84 to Google Maps
Convert WGS84 to Bing Maps
Convert WGS84 to EPSG:3857

Pixel Grid Images 8x8 pixel grid on 256 pixel image

Working with some images of maps, I had a need for some pixel grid overlays. I couldn't find any with a quick google search so I made these in using the Grid Maker plugin.

Images below

8x8 pixel grid on 256 pixel image

8x8 pixel grid on 1024 pixel image

16x16 pixel grid on 256 pixel image

16x16 pixel grid on 1024 pixel image

Hope this helps,

UTM Zone WGS84 Latitude Longitude Bounding Box

We are using to calculate the UTM Easting/Northing values for a given pair of WGS84 Latitude/Longitude coordinates. But I couldn't find an easy way to determine the correct UTM Zone for a WGS84 coordinate pair. The Zone had to be provided for the library to calculate the Easting/Northing values. I wanted the library to decide the best UTM zone based on the lat/lng coordinates.

To assist with this, I created the following table containing the "bounding box" lat/lng values for each UTM Zone in North America.

Test Code and CSV file:

The easiest way I found to determine these values was to use the centroid point for each UTM Zone, then add +/- 4 degrees Latitude (North/South) and +/- 3 degrees Longitude (East/West).

I have also provided some C# code to convert these into arrays, and then an example using a "point in polygon" function to determine the appropriate UTM Zone.

Hope this helps,

Azure HTTP Web Server Logs to SQL

If you enable File System Web Server logs for your Azure App Service...

Settings > Diagnostics logs > Web server logging > File System

You'll start to see logs on the file system for your app service here:

(you can find your FTP host and credentials in the publish profile file)


Alternatively, you can see these logs through the Kudu UI:


Instead of downloading these one and a time and parsing through them, you can use the following library to assist in loading them into a relational database.

You could even run this as a webjob within your app service.

Get the code here:

**Update: This repo now includes a web project that references the console app as a WebJob.

You may also want to check out the LogParser tool by Microsoft…

Store Amazon SES Delivery Notifications in DynamoDB using SNS and Lambdas

I spent way too much time configuring my Amazon AWS account to store Simple Email Service SES Delivery Notifications to a DynamoDB Table. I thought I'd put this guide together to hopefully help future developers.

This guide does not currently cover these topics, but I may include them in the future:
1. Setting up your Amazon AWS Account.
2. Setting up Amazon SES. (dkim, domain/email identities, etc.)
3. Integration with Amazon SES from your app.
4. SNS Topic creation/configuration.

1. Amazon AWS account has been created/configured.
2. Amazon SES has been created/configured.
3. Amazon SNS Topic has been created/configured.
4. Delivery Notifications for the Amazon SES Domain Identity have been configured to be sent to the SNS Topic.
5. Your app is integrated with Amazon SES and successfully sending email.

Step by Step Guide to Storing SES Delivery Notification messages into a DynamoDB Table:

So at this point, you're successfully integrated with Amazon Simple Email S…