Quoting David Bitner <[EMAIL PROTECTED]>: > Alright, > > I've made a couple posts lately about some different datasets > (TIGER/VMAP). My end goal is to pull together some datasets that > will > give me some nice vector reference for a mapserver app that will need > to go from a view of North America down to street level (just US). > There is a lot of public data out there right now in the afore > mentioned datasets as well as others. While there have been various > efforts to try to make suitably processed versions of these datasets > available, they tend to fail because bandwidth+storage=money. > > The idea I have is to create a Wiki (I could host a wiki, but not > data > or CVS) that would contain code snippets for grabbing public datasets > (ie a wget script to get all TIGER files) and would appropriately > post-process the datasets into shapefiles for different resolutions > using tools such as OGR or Grass or anything else free. > > We should pick several resolutions for globe coverage, continental > coverage, country coverage, state/province coverage, regional > coverage, city coverage, neighborhood coverage. For each resolution, > the data should contain an appropriate level of information (only > interstates, no local roads for national coverage; only country > borders, no state borders at globe coverage). Data should also be > appropriately generalized for the particular resolution. > > Initially, the two datasets that I would like to see initially are > administrative boundaries and transportation. > > Additionally, it would be great in the ideal world to have well > nested > attributes for display/labeling in whatever application (for me > mapserver)(ie an interstate would have the same attribute in a "road > type" field regardless of what scale since at some break, there would > likely be different datasets being used to define roads). > > I know this is the type of process that a lot of people regularly > deal > with. Is there any interest in me setting up a Wiki to hold this > type > of information? Is there a better way that we could try to pull this > info together? David Blasby wrote up a lot of his notes when he was going through the process of attempting to set up a public WMS/WFS (which hit many roadblocks of faulty servers, but which we still hope to get up). It's on a wiki, though currently within the GeoServer documentation: http://docs.codehaus.org/display/GEOSDOC/Data+Loading I think if there was a more generic place for us to post this type of information we'd be happy to put it there. It's focused on PostGIS instead of shapefiles, but I think a nice wiki would give people a few options, and discuss the advantages/disadvantages of each. I do think it's a great idea to have a public wiki to post this information, since many people are grappling with the same set of problems.
If you don't want to host the wiki yourself, I imagine we could fairly easily get a new space on codehaus's confluence, which is a really nice wiki, where GeoServer, GeoTools and MapBuilder also live. They could probably also host a subversion repository for scripts. Once The Open Planning Project gets the WMS/WFS up we could consider hosting straight shapefiles as well (though GeoServer can produce Shapefiles through its WFS, so one should be able to get polished shapefiles directly out of it, but we may need some scalability improvements to the server if it becomes popular). best regards, Chris *** Chris Holmes The Open Planning Project thoughts at: http://cholmes.wordpress.com ---------------------------------------------------------- This mail sent through IMP: https://webmail.limegroup.com/ _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
