We're developing an REST API to query our location data as KML and integrate it via maps. I just realized that I used the NW/SE corners for definint the boundary in contrast to the Google-Maps-API.
Right then it seemed reasonable to choose NW/SE, since we always have latNW > latSE && lonNW > lonSW, so I used that to normalize the query. Is there any particular reason I might want to switch to NE/SW despite to be consistent with Google? Thanks in advance, Adrian -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
