As you are from Google, I guess you are ok doing that as per the terms. The normal free API doesnt generally allow that.
Secondly, and you are ok as per the terms, use url encoding. A # will be interpreted as a the separator for a fragment, so the part after # will not reach the server. Or just strip the # out. It likly doesnt provide any useful information to the geocoder. On Mon, May 7, 2012 at 10:42 PM, Romulo Aguilar <[email protected]> wrote: > We generate maps using the static maps api v2 in emails since we are unable > to use javascript in emails. Our data comes from CLU, and addresses that > have a "#" in their address yield 400 errors and in turn give broken links > to images in our emails. Is there a fix to this issue without having to > manually change the data? > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API V2" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-maps-api/-/GgyvLBhl1CcJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-maps-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
