I am not using osm2pgsql to load our data into PostgreSQL because we are not using OpenStreetMaps data. Also the loading column type is "character(n), char(n) fixed-length, blank padded" so I can't eliminate the padding until the data is read out of the database. There are other various places that I have needed to modify in order to get the PostGIS input driver to work with our input data. It appears that the development of this driver has been pushed by the needs of OpenStreetMaps. Should I be trying to convert our data to appear more like OSM data, or try to improve the PostGIS input driver to be more generic?
Thanks, Aron On Wed, Apr 16, 2008 at 1:43 PM, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote: > On Wed, Apr 16, 2008 at 8:15 PM, Aron Bierbaum <[EMAIL PROTECTED]> wrote: > > It appears that during the transition to UnicodeString there were > > various things that were not completely migrated. The first that I > > have run across is that attribute string values coming from PostGIS > > don't remove extra white space. I have attached a patch that should > > work in all use cases. > > Shouldn't this be done by the process loading the data into the DB? I > don' think osm2pgsql does it right now, but I can fix that if you > want... > > Have a nice day, > -- > Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
