On Oct 6, 2009, at 4:36 PM, Scott Wilcox wrote:
> On 6 Oct 2009, at 21:43, City IT wrote:
>> I am with city government, we have two url's to get the our city  
>> site,
>> but we recently created a crime map for the police dept.  The API key
>> was generated based on the link:  
>> http://www.shreveportla.gov/dept/police/crimemaps/crimemap.html
>> ,
>> which works wonderfully.   When the other url is used:
>> http://www.ci.shreveport.la.us/dept/police/crimemaps/crimemap.html  
>> the
>> users get the error "The Google Maps API server rejected your
>> request.  This could be because the API key used on this site was
>> registered for a different web site.  You can generate a new key for
>> this web site at http://code.google.com/apls/maps/";.
>>
>> Do I need to generate another API Key  and used them both in my  
>> script
>> or is there so way to redirect to the code already in use?
>>
>> We contracted this portion to another vendor, so I don't know all the
>> details of the script used, but I do have access to the script and  
>> can
>> make changes.
>
> Yes, you'll need a separate key for the www.ci.shreveportla.gov
> subdomain.

Marginally more accurately: api keys fully support subdomains, but  
neither of your two domains are subdomains of the other. They are two  
completely different domains:

www.shreveportla.gov
www.ci.shreveport.la.us

They don't even share the same TLD, and as such will require separate  
keys, as stated by Wilcox. If your domains were actually www.shreveportla.gov 
  and www.ci.shreveportla.gov, of course, you *could* in fact use just  
one key, which would need to be registered for shreveportla.gov.

-G
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to