degrees (
https://en.wikipedia.org/wiki/Decimal_degrees), you multiply by 1,000,000
and round to the nearest integer value. It's important to have 7 decimal
places of precision so you can round to 6.
Thanks again!
On Monday, May 2, 2016 at 3:37:39 PM UTC-7, Day Davis Waterbury wrote:
>
> Thank you. T
Thank you. That's very helpful. I will try that and post a follow-up.
Thanks again!
On Monday, May 2, 2016 at 3:11:24 PM UTC-7, Shwetha Vastrad (AdWords API
Team) wrote:
>
> Hi,
>
> You are probably receiving this error because of the longitude value being
> passed, not because of the latitude
What exact format is expected the latitudeInMicroDegrees and
longitudeInMicroDegrees when creating a geoPoint for a Proximity
CampaignCriterion?
For example, when I have a latitude in decimal degrees of 45.3911638 and I
convert it to microdegrees as 45391163, I am seeing the following error:
What exact format is expected the latitudeInMicroDegrees and
longitudeInMicroDegrees when creating a geoPoint for a Proximity
CampaignCriterion?
For example, when I have a latitude in decimal degrees of 45.3911638 and I
convert it to microdegrees as 45391163, I am seeing the following error:
