[postgis-devel] Shapefile to PostGIS Importer

[Mark Leslie]

PgAdmin isn't a tool I often use, so I'm glad you thought to test it.
It seems there are higher requirements to running there than
stand-alone.  I've put up a new binary for anyone interested
http://revenant.ca/www/postgis/postgis-loader-20100712.zip
Unfortunately, this has revealed a new segfaulting issue on 64bit
windows.  Still chasing that one down :(

--
Mark

On 6 July 2010 18:30, Paragon Corporation <lr at pcorp.us> wrote:
> Mark,
>
> Thanks for these improvements.  I love the ability to add multiple files at
> a time.
>
> Two issues I noticed off the bat using your windows version.  Haven't tried
> to compile my own yet.
>
> 1) If I try to use this as a plugin in PgAdmin III (which is the way we
> normally use it), it crashes.   Though doesn't seem to crash in stand alone
>
> 2) If we fiddle with the settings in the selected shapefile -- e.g. changing
> the geometry column name or schema or table,  sometimes these settings also
> get thrown in the
>
> DBF file character encoding field and then it gives an error from then on
> invalid character encoding (geom or whatever we had typed  is obviously not
> a valid encoding).
>
> 3) Minor comment -- if you are going to be doing so much work on this, you
> should probably throw your name in the credits too :)
>
> Thanks,
> Regina and Leo
>
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Mark
> Leslie
> Sent: Tuesday, July 06, 2010 2:34 AM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] Shapefile to PostGIS Importer
>
>
> It's been a while since I started this thread, but I've finally managed to
> get it into my schedule.  I've pushed through the upgrades mentioned (no
> budget yet for a port to wxWindows I'm afraid).  Attached is a screen-cap.
>
> Work has been done against the 1.5 branch, and checked into a spike:
> http://svn.osgeo.org/postgis/spike/mleslie/current
> I've also put up a zip for windows:
> http://revenant.ca/www/postgis/postgis-loader-20100629.zip
>
> --
> Mark Leslie
> Geospatial Software Architect
> LISAsoft
>
> -------------------------------------------------------------
> Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61 Suite 112, Jones Bay Wharf
> 19-21 Pirrama Rd Pyrmont NSW 2009
> -------------------------------------------------------------
>
> LISAsoft is part of the A2end Group of Companies http://www.ardec.com.au
> http://www.lisasoft.com http://www.terrapages.com
>
>
> Paul Ramsey wrote:
>> I'm not actually that wedded to not changing the loader/dumper
>> mid-stream. It's not something that other system components depend
>> upon, unlike SQL signatures and so on, so I think we can reasonably
>> work on that part of the code base pretty agressively.
>>
>> Another piece that needs work is a GUI take on the dumper, in
>> particular one that takes a table as as commandline parameter (I'm
>> thinking here of what running within at PgAdmin plugin context would
>> look like.
>>
>> For 2.0 I'd like to look at swapping to another widget set. QT or
>> WxWindows. I'm not so impressed with how well GTK+ is being maintained
>> on non-Linux hosts.
>>
>> P.
>>
>> On Wed, Dec 16, 2009 at 7:31 PM, Mark Leslie <mark.leslie at lisasoft.com>
> wrote:
>>> I'm chasing a bit of work to improve the gui import tool and I'm
>>> looking for some feedback.  I'm thrilled to see how much has been
>>> completed in the last few months, but there are three things I'd like to
> get in.
>>>
>>> The first is to add the drop/append/create/prepare options.  Was
>>> there a reason these were left off the gui?
>>> Second is drag-n-drop capability for selecting files.  This is really
>>> my big win here, but I'm still digging through docs to sort out how
>>> that's going to work.
>>> The third is a batch import capability.  This was actually off my
>>> radar until Paul pointed me at QGIS' import tool, which is slick enough
> emulate.
>>>  Once I actually get the time, I'll put my hand to some screen mocks.
>>>
>>> I'm also not expecting to get a contract signed before christmas, so
>>> this work is likely to happen after the 1.5 release, assuming the
>>> roadmap speaks true.  The batch import is really the only thing on my
>>> list that feels like it should not be in a point release, since it's
>>> a user facing change in functionality.  That then pushes these
>>> changes back to 2.0.  Does it make sense to assume I will be working
>>> towards 2.0, and just backporting the first two bits?
>>>
>>> --
>>> Mark Leslie
>>> Geospatial Software Architect
>>> LISAsoft
>>>
>>> -------------------------------------------------------------
>>> Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61 Suite 112, Jones
>>> Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
>>> -------------------------------------------------------------
>>>
>>> LISAsoft is part of the A2end Group of Companies
>>> http://www.ardec.com.au http://www.lisasoft.com
>>> http://www.terrapages.com
>>> _______________________________________________
>>> postgis-devel mailing list
>>> postgis-devel at postgis.refractions.net
>>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>



-- 
Mark Leslie
Geospatial Software Architect
LISAsoft

-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------

LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com