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