On Wednesday 14 May 2008 14:17:30 [EMAIL PROTECTED] wrote:
> On Wed, 14 May 2008 13:15:43 +0200, Frank Broniewski
>
> <[EMAIL PROTECTED]> wrote:
> > On Wednesday 14 May 2008 12:56:10 [EMAIL PROTECTED] wrote:
> >> Hi all.
> >>
> >>
> >>
> >> I'm trying to use mapserver+pmapper to handle a number of differend
> >
> > maps.
> >
> >> But when I'm putting a tables into some schema the pmapper draws a blank
> >>
> >> image. But no errors from pmapper or mapserver.
> >>
> >> The only error from mapserver was fixed as described in
>
> http://postgis.refractions.net/pipermail/postgis-users/2003-March/002214.ht
>
> >>ml
> >>
> >> Any suggestions?
> >>
> >>
> >>
> >> Thank you,
> >>
> >> Ruslan.
> >
> > -------------------------------------------------------------------------
> >
> >> This SF.net email is sponsored by: Microsoft
> >> Defy all challenges. Microsoft(R) Visual Studio 2008.
> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >> _______________________________________________
> >> pmapper-users mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/pmapper-users
> >
> > Well it works at least for me:
> >
> > Connectiontype Postgis
> > Data "ocom_loc from object.common using unique ocom_id"
> >
> > maybe you can be a little more specific on how you define your postgis
> > connection ...
> >
> > Greetings Frank
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > pmapper-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
> Connectiontype postgis
> Data "the_geom from city.parks using unique gid"
>
> I'm importing data to postgis using qgis spit plugin. And when I'm
> specifiyng the correct schema at import - everything is fine.
> But after moving the table from one schema to another....

Maybe this is related to postgis. Postgis keeps a reference to all tables with 
geometry columns in public.geometry_columns. If you don't fix the entry 
there, maybe postgis can't deliver the geometry correctly ... just a guess 
though

Greetings Frank

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
pmapper-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Reply via email to