On Wed, Apr 16, 2008 at 10:25 PM, Aron Bierbaum <[EMAIL PROTECTED]> wrote: > 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?
It was just a question. I do wonder why you're using char(n) for columns though, since it usually just adds overhead. It's true that OSM is a major user, but certainly not the only one. If you have patches, do send them. 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
