The issue as I see it is that Google is a double edged sword. They provide a high quality data source, which as developers we have little control over; i.e. we're at google's mercy for what they provide and when. This is obviously the case with all major third party data sources. So as I see it, we are faced with the choice of taking what's free, or undertaking the task of providing our own base layers which adds additional programming and data requirements. Ultimately, I'd have to say it's application specific.
Sent from my mobile device On Jun 14, 2012, at 9:11 AM, Luís de Sousa <[email protected]> wrote: > Thank you Andreas, it worked like a charm. > > I still would like to hear the thoughts of peer developers on the usage of > Google Maps. Reliable or not? > > Thank you and regards, > > Luís > > > Andreas Hocevar-2 wrote >> >> Hi, >> >> yes, this is fixed in current master and 2.12-rc7. And here is an >> explanation on how to apply a hotfix to applications that use 2.11: >> http://trac.osgeo.org/openlayers/wiki/Release/2.11/GoogleMaps37 >> >> Andreas. >> > > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/Google-map-v3-popup-again-tp4975258p4981430.html > Sent from the OpenLayers Users mailing list archive at Nabble.com. > _______________________________________________ > Users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/openlayers-users _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
