While this is a few days away, I know we'll need to start tackling how to plot the overview map efficiently with all the data points possible. Could someone send me a dump of the mappoints table from the davis wiki, or post it where I can download it.
I'd like to use that for testing. I'm thinking possibly of http://dev.openlayers.org/sandbox/vector-behavior/examples/strategy-cluster.html or some type of caching. Thanks, Alex Alex Mandel wrote: > Progress has been made(from commit log): > OSM tiles now loading with wiki data points > TODO: Get popup bubble with wiki page link working. > TODO: Optimizations for speed and load. > Note: X,Y in Database are reverse of real world X is the long way around > the equator = longitude 0-180 pos and neg, Y is the lateral (up/down) = > latitude 0-90 pos, neg. - if we fix the database we'll need to fix the > code since the SQL query will change. > > more: http://www.projectsycamore.org/Mapping > > Code Branch > http://sycamore.devjavu.com/browser/branches/mapping > > Currently there is no limit on returned records, since I'm only testing > with 2 points right now I have no idea what a sane max is and how to > choose how many points to put on the overview map. Ideally I actually > think we should create something like a GeoRSS, GML or KML file and use > that to server the map. It could be updated via diffs when the database > triggers on a location change. > That way we could cache the points for loading. > > Alternate idea would be to bundle Featureserver python WFS service with > Sycamore. > > More on that later. > > Cheers, > Alex > > Alex Mandel wrote: >> Well, it doesn't look like we'll be having a code sprint to work on it >> so I went ahead and started working on it. >> >> After trying to guess my way through creating a new macro, I now have an >> example helloworld for any future people who don't know where to start. >> But more importantly I have and OpenLayers based map running properly >> (see screenshot on http://www.projectsycamore.org/Mapping), the code >> will work as is on any existing >> sycamore site that has a google api key. >> >> Code can be found at http://sycamore.devjavu.com/changeset/974 >> >> Next steps: >> 1. Fix OpenStreetMap tiling which was giving me issues tonight, probably >> because I didn't implement projections yet. >> 2. Plot local data points on map with markers, pop-bubbles and link to >> their pages within the wiki. >> 3. Overhaul mini maps to use OSM as default >> 4. Allow for wiki admins to add other wms, wfs layers easily (Airphotos, >> example for Davis) >> >> If you want to help just shoot me an email, >> Alex >> >> _______________________________________________ >> Sycamore-Dev mailing list >> [EMAIL PROTECTED] >> http://www.projectsycamore.org/ >> https://tools.cernio.com/mailman/listinfo/sycamore-dev > > _______________________________________________ > Sycamore-Dev mailing list > [EMAIL PROTECTED] > http://www.projectsycamore.org/ > https://tools.cernio.com/mailman/listinfo/sycamore-dev _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
