Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-13 Thread Andrew Leach
On 13 July 2011 13:35, Nico Oudshoorn wrote: > $naarposlat = $geo->result->geometry->location->lat; > > the problem is this geo result. In ths example the echo is 51.4945758. But > even if you only multiply it by 1 the result is 51. In the meantime I let > the lat and lng come from the client side

Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-13 Thread Nico Oudshoorn
$naarposlat = $geo->result->geometry->location->lat; the problem is this geo result. In ths example the echo is 51.4945758. But even if you only multiply it by 1 the result is 51. In the meantime I let the lat and lng come from the client side. But I am still wandering why on the server side t

Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-12 Thread Andrew Leach
On 12 July 2011 18:07, Nico Oudshoorn wrote: > > This is from another page where the lat and lng are generated on the server > side: > $url = > "http://maps.googleapis.com/maps/api/geocode/xml?address=".urlencode($zoekpos2)."&sensor=false"; What is the address you are using? What is the XML you a

Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-12 Thread Nico Oudshoorn
Both are version 3 In this page the lat and lng are geberated at the client side and come on the server side from $zoekaklat and $zoekaklng: $naarposlat = $zoekaklat; // = 51.4945758001 $naarposlng = $zoekaklng; // = 4.28716220012 if($naarposlat==0 and $naarposlng==0) { $zoekmessage2

Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-12 Thread Andrew Leach
On 12 July 2011 13:29, Nico Oudshoorn wrote: > I use the same method in my version 2 site. There I don't have this problem. > $zoekafstand isn't the problem. $vanposlat is the problem. If $zoekpos is > zutphen in the netherlands then the result $vanposlat = 52.13. But in > the calculation with

Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-12 Thread Nico Oudshoorn
I use the same method in my version 2 site. There I don't have this problem. $zoekafstand isn't the problem. $vanposlat is the problem. If $zoekpos is zutphen in the netherlands then the result $vanposlat = 52.13. But in the calculation with the result $maxlat, the value of $vanposlat is 52

Re: [Google Maps API v3] loss of lat and lng decimals

2011-07-12 Thread Andrew Leach
On 11 July 2011 19:34, Nico Oudshoorn wrote: > This is from a site of mine. In an example that I tested, the outcome of > $vanposlat was 52.13. $zoekafstand = 15. The result of  $zoekafstand / > (69 * 1.61) = 0,1350256. And surprise surprse $maxlat = 52.1350256 So we > lost the 0.13???

[Google Maps API v3] loss of lat and lng decimals

2011-07-11 Thread Nico Oudshoorn
This is from a site of mine. In an example that I tested, the outcome of $vanposlat was 52.13. $zoekafstand = 15. The result of $zoekafstand / (69 * 1.61) = 0,1350256. And surprise surprse $maxlat = 52.1350256 So we lost the 0.13 However when I echo $vanposlat it = 52.13, bu