<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6001.18248" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=256572202-14062009><FONT face=Arial
color=#0000ff size=2>Oops slight correction. Forget my comment about
pgsql2shp. I just realized what I was thinking doesn't work, so you may
have to dump the geometry tables to shp and then load into SpatiaLite with the
numerous loaders out there.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=256572202-14062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=256572202-14062009><FONT face=Arial
color=#0000ff size=2>I suppose you can chain them like pgsql2shp |
shp2pgsql -w but haven't tried that.</FONT></SPAN><SPAN
class=256572202-14062009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=256572202-14062009><FONT face=Arial
color=#0000ff size=2>It would be nice if OGR2OGR supports this. I assume
that is in the works, but I think it only supports SQLite not SpatiaLite
yet.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=256572202-14062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=256572202-14062009><FONT face=Arial
color=#0000ff size=2>Leo</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>On Behalf Of
</B>Paragon Corporation<BR><B>Sent:</B> Saturday, June 13, 2009 10:22
PM<BR><B>To:</B> 'PostGIS Users Discussion'<BR><B>Subject:</B> Re:
[postgis-users] Moving to SpatiaLite: best practice<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2>Jose,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2>From our experience -- the SQLite SQL syntax compatibility
with PostgreSQL is pretty good, so that your dump idea should more or less work
with minor massaging to load into SQLite. Well it will probably work just
fine for the regular data if you use the -D insert format of PostgreSQL of
pg_dump</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2><A
href="http://www.postgresonline.com/downloads/special_feature/postgresql83_pg_dumprestore_cheatsheet.pdf">http://www.postgresonline.com/downloads/special_feature/postgresql83_pg_dumprestore_cheatsheet.pdf</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2>So the only issue is the geometry output. These will
probably not be compatible. You could use pgsql2shp and output using the
-w switch which will output to WKT.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2><A
href="http://www.bostongis.com/pgsql2shp_shp2pgsql_quickguide.bqg">http://www.bostongis.com/pgsql2shp_shp2pgsql_quickguide.bqg</A></FONT></SPAN></DIV></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2>That may just work. Haven't tried it myself so good
luck and let us know how it turns out.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=488301502-14062009><FONT face=Arial
color=#0000ff size=2>Leo</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>On Behalf Of </B>Jose
Gomez-Dans<BR><B>Sent:</B> Saturday, June 13, 2009 3:44 PM<BR><B>To:</B> PostGIS
Users Discussion<BR><B>Subject:</B> [postgis-users] Moving to SpatiaLite: best
practice<BR></FONT><BR></DIV>
<DIV></DIV>Hi,<BR>I'm doing some very simple PostGIS-related work: I store data
in a table, and from time to time, I do simple stuff with the stored data,
sometimes even actually using the geometry column!!! Anyway, PostGIS has been
very useful so far, but I now have to move away from my work computer, and I
would like to keep on working with my laptop. One way would be to install
PostGIS on my laptop, but I am also thinking of giving my program to other
people, who might not necessarily need or want to install PostGIS. To this end,
spatialite is very handy. It's just a file, and I can use the same PostGIS stuff
I've been using up to now. However, I need to move my tables to SpatialLite. In
essence, I do have a number of tables, most of which relate a field to a
geographical table. It should be trivial to dump schema and SQL and run it pass
sqlite/spatialite. I was just wondering whether anyone had any recommendations
or ideas on "best practice".<BR><BR>Thanks!<BR>Jose<BR></BODY></HTML>