Hi Duncan, I stopped my project half way through its development as the roadmap I had planned for it needed some big changes to find any kind of a niche'. None of the elevation data was used - I was planning to have the xml file interpreted into a database so that all types of gps formats could be interpreted and outputted in a format of my choice, that example was simply a raw xml file direct from my gps.
I was then going to iterate out the locations from the database into the api - I would of attempted this by now but I had a big project come in so I had to halt all personal projects for the time being. It'll be interesting to see where the gmaps api goes, the new functions i'd like added would be geocoding, distance (not only on poly lines but between markers both 'as the crow flies' and along roads/paths), more 'drawing' features and better support for any non vml rendered shapes. If I do get any spare time i'll attempt this next step and post back my results. One thing I don't want to do is create yet another run of the mill gmaps application, it's turning into the next crazy frog - I can't wait to see people like marumushi.com do something radical with it. I hope i'm not going too off topic with all this gmaps info. Regards, -g On 7/8/05, QAZ3D <[EMAIL PROTECTED]> wrote: > Simon: > > Plotting the place names will probably be added to the api in time, > untill then you can either use one of the many hacks going around or > integrate with some geocoding company - theres many free US ones - > http://www.mapquest.com/features/main.adp?page=geocode > > The google earth integration with flickr is very interesting. I've > mocked up a personal geophoto album which only requires a gps and > normal camera as input - you can either crossreference the two by time > or preprocess them and add metatags to each photo (alike flickr) - > this is all done in php - except preprocessing which is done in an > application. > > There is alot of potential for the google mapping project, if I had > the time i'd of done a basic explode on each bbc news story to try and > grab a location, along with the region mentioned in the URL and then > geocode that story onto the map, i'm just a bit too busy at the > moment. > > Kim: I understand what you were saying with the Melvyn idea, a > personal project i'm working on is a feasible augmented reality system > that is possible with technology we already own and the data > infrastructure we already have, I do have the intention of integrating > BBC data into it at some point so watch this space. > > Regards, > > -g > > On 7/8/05, QAZ3D <[EMAIL PROTECTED]> wrote: > > Hi Duncan, > > > > I have tinkered with the API previously - the xml import is.. 'ok'. > > > > Too many points (in the form of a polyline) and it will crash Safari > > and if i remember correctly firefox too, it works fine on IE as IE > > uses a different method to draw the polylines (VML). > > > > You can be dirty and throw a complete unedited gpx file at it - > > (convert your gps file to gpx - its the best standard for them, google > > gpsbabel): > > > > var request = GXmlHttp.create(); > > request.open("GET", "http://www.coolreflections.co.uk/gmaps/tracks6.xml";, > > true); > > request.onreadystatechange = function() { > > if (request.readyState == 4) { > > var xmlDoc = request.responseXML; > > var markers = xmlDoc.documentElement.getElementsByTagName("trkpt"); > > var points = [] > > for (var i = 0; i < markers.length; i++) { > > points.push(new GPoint(parseFloat(markers[i].getAttribute("lon")), > > parseFloat(markers[i].getAttribute("lat")))); > > } > > map.addOverlay(new GPolyline(points)); > > } > > } > > request.send(null); > > > > > > The xml file it imports is in the format: > > > > <trkpt lat="51.582634" lon="-2.834516"> > > <ele>-13.801758</ele> > > <time>2005-07-02T11:36:47Z</time> > > </trkpt> > > > > This is just a quick and dirty example almost straight from the > > documentation. > > > > Regards, > > > > -g > > > > On 7/8/05, Duncan Barclay <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > That looks really nice, especially the London bombing map. > > > > > > I have been trying to use the Google Maps API, but can't work out how to > > > get javascript to like getting the points and other data from an XML file. > > > I will have to look into it a bit more. > > > > > > It is quite amazing what you can do with the new API isn't it ... > > > > > > Duncan > > > > > > > > > > > > Kosso wrote: > > > hi. > > > I've been knocking up this since the trip to the USA and events yesterday > > > > > > > > > http://geepster.com > > > > > > Currently making it all db-driven and asynchronous - and RSS reading ;) > > > > > > > > > > > > > > > > > > On 7/6/05, Kim Plowright <[EMAIL PROTECTED]> wrote: > > > > > > > > Probably even more off topic, and hello list, sorry, I lurk as I'm *so* > > > not techy enough for most of the conversations... > > > > > > > > But has everyone seen this flickr / google earth mix? Appols if it has > > > done the rounds... > > > > > > > > http://www.flickr.com/groups/topic/50193/ > > > > > > > > And a slightly unrelated note, and a tad off topic.... could anyone shed > > > any light on how easy this would be to achieve... > > > > > > > > In Our Time - Melvyn's weekly newsletter. > > > > He tends to dictate it whilst walking around London - cue much merriment > > > about getting rained on, etc. How easy would it be to strip out location / > > > placename data from the emails, and map 'Where's Melvyn?' on to google > > > maps? > > > Possibly with a link to download/listen again to the episode he talks > > > about? > > > > A very silly idea, I know, but quite cute... I'm interested in ideas > > > > that > > > spatially locate programming and content. You could imagine being stood on > > > waterloo bridge and your mobile suddenly going off, delivering you that > > > week's podcast... > > > > > > > > Kim > > > > (BBC type, project manager in Interactive Drama and Entertainment, can't > > > code for toffee...) > > > > > > > > > - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
