Does anyone have some generic python scripts to do such a thing. I'd love to have some examples.
-----Original Message----- From: [EMAIL PROTECTED] on behalf of Fawcett, David Sent: Tue 5/20/2008 4:26 PM To: Jeff Hoffmann; Heather Wirth Cc: [email protected] Subject: RE: [mapserver-users] Using personal geodatabases (.mdb) Sarah, I am not aware of any quantitative numbers, but I would guess that shapefiles will perform better than a personal geodatabase. Since I am guessing that you will not be putting your 'official' copy of your database on your Web server, you will be moving periodic snapshots of your data from behind your firewall onto your Web server. I would suggest writing a simple python script that grabs the feature classes from your personal geodatabase and dumps them to shapefiles. David. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Hoffmann Sent: Tuesday, May 20, 2008 3:12 PM To: Heather Wirth Cc: [email protected] Subject: Re: [mapserver-users] Using personal geodatabases (.mdb) Heather Wirth wrote: > We currently have a functional Geomoose (a front end to MapServer) > site using shapefiles, but thought we may want to migrate to a > personal geodatabase (.mdb) to ease the process of updating map > information. We followed all the instructions on the MapServer site > for using .mdb files, and can get the layer to display. > > The problem we have is that the layer from the .mdb does not "draw" > all features. For testing, we added just one layer, parcels. At the > same time, for comparison purposes, we left the parcels shapefile in > the project. While testing some of the other services, like identify, > we noticed that there were "holes" in the parcel layer from the .mdb, > that aren't in the shapefile generated parcels layer. When I search > the geodatabase for a feature that is not drawing, I find it in the > .mdb. > > Has anyone else had this problem? Does anybody know why it would do > this &/or how to fix it? Any help would be much appreciated. > I believe you're falling prey to a bug in OGR (http://trac.osgeo.org/gdal/ticket/1484). It may be possible to work around it, but I'm sure it'd be a whole lot easier to just find a reliable way to dump the data to a shape file and use it that way. Jeff _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
