Lance Dyas wrote: > I just saved this as a web app link on my desktop via the Chrome > Browser... and well... very cool > I want a button for upload and mayhaps a generic url ;-), Ah silly me I missed it hiding under the GPX button.. everything I wanted and more !!! I think having it say Load GeoData might be more intuitive (you could put a KML/GML load in there too) > and cookies > to save state between > visits ;-), > > Bill Chadwick wrote: > >> Hi, >> >> To enable cross domain AJAX reading of GPX files, I have put >> together >> a GPX to GeoJson ( http://www.geojson.org ) converter REST web >> service >> >> >> > Open Layers uses this natively... > >> You can see the converter in action here :- >> >> http://wheresthepath.googlepages.com/wheresthepath.htm?gpx=http://wheresthepath.googlepages.com/swinleyforest.gpx >> >> > Love the example. very very cool you have been building that puppy up as > you go along > wow just looked at the code on that page -- monstrous, intimidating. ;-) > >> I have used a FeatureCollection to represent the set of waypoints, >> routes and tracks in the GPX file. The FeatureCollection's >> 'properties' include the >> gpxversion and creator elements from the GPX file. Then I have used: >> >> 1) 'Point's for way-points with a set of 'properties' corresponding >> to >> the waypoint's descriptive elements (name etc) >> >> 2) 'MultiLineString' for a track (one string of points per track >> segment) with a set of 'properties' corresponding to the >> track's descriptive elements >> >> 3) 'GeometryCollection' for a route (the collection holds the set >> of >> route points as 'Point's) with a set of properties >> corresponding to >> the route's descriptive elements. >> >> The Route presents a bit of a problem. I have put individual route- >> node >> properties on each GeometryCollection child - good JSON but outside >> the GeoJson spec. >> > I really wish a nice hierarchical structure could be done with the > standard geojson > but really its a limit of the GML definition and one advantages KML has > folders > inside of folders inside of... > >> These properties are key for a route e.g. >> "cmt":"turn left for the pub". I had to use a GeometryCollection for >> the Route as a FeatureCollection can't contain a FeatureCollection >> >> > yup limited structure... which was why I suggested creating KJSON > specification a while back. > I decided I really wanted encoded polys in it for Google Maps support so > what I wanted > really wasnt even a true KJSON and by the time I diverged from things > that far well I might > as well do my own thing. > >> You can see example track+waypoint output here >> >> http://gpx2geojson.appspot.com?gpxurl=http://wheresthepath.googlepages.com/swinleyforest.gpx&mime=text/plain >> >> and example route output here >> >> http://gpx2geojson.appspot.com?gpxurl=http://wheresthepath.googlepages.com/route.gpx&mime=text/plain >> >> other parameters are >> >> ele=1 - make 3D coords from 3D input (not compatible >> withOpenLayers) >> >> > > > > > . > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
