The bottom line is if you're using markers, you're making the data available to anyone with the technical capability to take it.
There are a couple of ways you can reduce your exposure though. Only pass marker data for the visible map. Pass generalized markers for high zoom levels (see marker manager for details on that). Limit the number of pulls on your database to a maximum number a human would do, any more than the typical human rate, lock that IP from using your application. I use this method with great success. It doesn't bother actual human users but it thwarts robots from harvesting my databases. Another way is to eliminate markers all together and instead use tiles with markers drawn on them. When a user clicks on a pseudo marker, send the point to your database to be queried to see if it's in fact a marker, and if so, return the marker data. That way, only a human clicking on the map could possibly be sending the coordinate to your database. This method also cuts down on the traffic between your server and the client. It may be pointless to even try if your data is either too valuable or you have a person who is too determined to get around your security. The alternative is to simply offer your database for license at a reasonable cost. Just like music downloads, if the price is right, most people would rather comply with the rules than break them. -John Coryat http://maps.huge.info http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
