[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-users
Subject: Re: [postgis-users] pgsql2shp cuts varchar fields
From: "Gustavo Ces" <g.ces () pettra ! es>
Date: 2008-12-18 17:58:38
Message-ID: 00b901c9613a$41681f30$ba03a8c0 () GUS
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
RE: [postgis-users] pgsql2shp cuts varchar fieldsHi,
finally i´ve have done two varchar fields from original one and using both fields \
in mapbook and the result is not so strange ... thanks for your help and info!
Gus
----- Original Message -----
From: Obe, Regina
To: PostGIS Users Discussion
Sent: Thursday, December 18, 2008 6:43 PM
Subject: RE: [postgis-users] pgsql2shp cuts varchar fields
I suppose Map Info tab format or some other format is not an option for MapBook.
Well I'm not sure about the memo field part, but I know around here MapInfo users \
get frustrated when they export from MapInfo to ESRI Shape because of the .dbf 10 \
character field name limitation.
-----Original Message-----
From: postgis-users-bounces@postgis.refractions.net on behalf of David Fawcett
Sent: Thu 12/18/2008 12:32 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] pgsql2shp cuts varchar fields
Other things that you may notice when exporting to shape is that field
names may be truncated, and you are limited to ~256 columns in your
table as well. This goes back to the .dbf spec. Some (column limit)
of the these limitations also show up when you export to the ESRI
Personal Geodatabase as well.
David.
On Thu, Dec 18, 2008 at 10:37 AM, Gustavo Ces <g.ces@pettra.es> wrote:
> Hi Regina,
>
> thanks for answering. You must be right. I´ve tried to export with Gvsig
> to shapefile and cuts the varchar fields... I´ve tried to join with arcgis
> and fields don´t be cutted but when i export joined data to a shapefile ( i
> need this to use Arcgis Mapbook and use those fields as tags), then i´ve got
> cutted fields... So it seems a shape/dbf problem... And i´ve got no option
> now! :(
> Maybe making two fields from all original fields it´s the answer ( i´ve
> got no text larger than 254*2). Any other suggestion will be welcomed...
>
>
> Gus
>
> ----- Original Message -----
> From: Obe, Regina
> To: PostGIS Users Discussion
> Sent: Thursday, December 18, 2008 5:08 PM
> Subject: RE: [postgis-users] pgsql2shp cuts varchar fields
> Not absolutely sure, but I think its a limit in the spec. I think fields >
> 254 are considered to be memo fields in the dbf world and so would be put in
> a .dbt.
> Its been a while since I've done any DBase or Foxpro programming so my
> memory could be wrong.
>
> I've never actually seen .dbt files included with ESRI shape files, so I
> assume ESRI discarded that side of the spec. If its allowed, then we
> probably should implement it.
>
> Hope that helps,
> Regina
>
>
> ________________________________
> From: postgis-users-bounces@postgis.refractions.net
> [mailto:postgis-users-bounces@postgis.refractions.net] On Behalf Of Gustavo
> Ces
> Sent: Thursday, December 18, 2008 10:53 AM
> To: PostGIS Users Discussion
> Subject: [postgis-users] pgsql2shp cuts varchar fields
>
> Hi all,
>
> maybe this is an old issue... I´m trying to export to shapefile some
> geometries, but in the result shapefile varchar fields greater than 255 are
> cutted at this point. I´ve got alternatives but i´d like to know : is there
> any method to export those fields directly with pgsql2shp or is it a
> shapefile-format or pgsql2shp limit?
> Thanks in advance,
>
>
> Gus
>
> ________________________________
>
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure pursuant to
> Massachusetts law. It is intended solely for the addressee. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>
> ________________________________
>
> Help make the earth a greener place. If at all possible resist printing this
> email and join us in saving paper.
>
> ________________________________
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------------------------------------------------------
The substance of this message, including any attachments, may be confidential, \
legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is \
intended solely for the addressee. If you received this in error, please contact the \
sender and delete the material from any computer.
------------------------------------------------------------------------------
Help make the earth a greener place. If at all possible resist printing this email \
and join us in saving paper.
------------------------------------------------------------------------------
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [postgis-users] pgsql2shp cuts varchar fields</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3462" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> finally i´ve have done two
varchar fields from original one and using both fields in mapbook and the result
is not so strange ... thanks for your help and info!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Gus</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 \
2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message \
----- </DIV> <DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=robe.dnd@cityofboston.gov
href="mailto:robe.dnd@cityofboston.gov">Obe, Regina</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=postgis-users@postgis.refractions.net
href="mailto:postgis-users@postgis.refractions.net">PostGIS Users
Discussion</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, December 18, 2008 6:43
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [postgis-users] pgsql2shp
cuts varchar fields</DIV>
<DIV><BR></DIV><!-- Converted from text/plain format -->
<P><FONT size=2>I suppose Map Info tab format or some other format is not an
option for MapBook.<BR><BR>Well I'm not sure about the memo field part, but I
know around here MapInfo users get<BR>frustrated when they export from MapInfo
to ESRI Shape because of the .dbf 10 character field name
limitation.<BR><BR><BR>-----Original Message-----<BR>From: <A
href="mailto:postgis-users-bounces@postgis.refractions.net">postgis-users-bounces@postgis.refractions.net</A> \
on behalf of David Fawcett<BR>Sent: Thu 12/18/2008 12:32 PM<BR>To: PostGIS
Users Discussion<BR>Subject: Re: [postgis-users] pgsql2shp cuts varchar
fields<BR><BR>Other things that you may notice when exporting to shape is that
field<BR>names may be truncated, and you are limited to ~256 columns in
your<BR>table as well. This goes back to the .dbf spec. Some
(column limit)<BR>of the these limitations also show up when you export to the
ESRI<BR>Personal Geodatabase as well.<BR><BR>David.<BR><BR>On Thu, Dec 18,
2008 at 10:37 AM, Gustavo Ces <g.ces@pettra.es> wrote:<BR>> Hi
Regina,<BR>><BR>> thanks for answering. You must
be right. I´ve tried to export with Gvsig<BR>> to shapefile and cuts the
varchar fields... I´ve tried to join with arcgis<BR>> and fields don´t be
cutted but when i export joined data to a shapefile ( i<BR>> need this to
use Arcgis Mapbook and use those fields as tags), then i´ve got<BR>> cutted
fields... So it seems a shape/dbf problem... And i´ve got no option<BR>>
now! :(<BR>> Maybe making two fields from all
original fields it´s the answer ( i´ve<BR>> got no text larger than 254*2).
Any other suggestion will be welcomed...<BR>><BR>><BR>>
Gus<BR>><BR>> ----- Original Message -----<BR>> From: Obe,
Regina<BR>> To: PostGIS Users Discussion<BR>> Sent: Thursday, December
18, 2008 5:08 PM<BR>> Subject: RE: [postgis-users] pgsql2shp cuts varchar
fields<BR>> Not absolutely sure, but I think its a limit in the spec.
I think fields ><BR>> 254 are considered to be memo fields in the dbf
world and so would be put in<BR>> a .dbt.<BR>> Its been a while since
I've done any DBase or Foxpro programming so my<BR>> memory could be
wrong.<BR>><BR>> I've never actually seen .dbt files included with ESRI
shape files, so I<BR>> assume ESRI discarded that side of the spec.
If its allowed, then we<BR>> probably should implement it.<BR>><BR>>
Hope that helps,<BR>> Regina<BR>><BR>><BR>>
________________________________<BR>> From:
postgis-users-bounces@postgis.refractions.net<BR>> [<A
href="mailto:postgis-users-bounces@postgis.refractions.net">mailto:postgis-users-bounces@postgis.refractions.net</A>] \
On Behalf Of Gustavo<BR>> Ces<BR>> Sent: Thursday, December 18, 2008
10:53 AM<BR>> To: PostGIS Users Discussion<BR>> Subject: [postgis-users]
pgsql2shp cuts varchar fields<BR>><BR>> Hi
all,<BR>><BR>> maybe this is an old issue... I´m
trying to export to shapefile some<BR>> geometries, but in the result
shapefile varchar fields greater than 255 are<BR>> cutted at this point.
I´ve got alternatives but i´d like to know : is there<BR>> any method to
export those fields directly with pgsql2shp or is it a<BR>>
shapefile-format or pgsql2shp limit?<BR>> Thanks in
advance,<BR>><BR>><BR>> Gus<BR>><BR>>
________________________________<BR>><BR>> The substance of this
message, including any attachments, may be<BR>> confidential, legally
privileged and/or exempt from disclosure pursuant to<BR>> Massachusetts
law. It is intended solely for the addressee. If you received<BR>> this in
error, please contact the sender and delete the material from any<BR>>
computer.<BR>><BR>> ________________________________<BR>><BR>>
Help make the earth a greener place. If at all possible resist printing
this<BR>> email and join us in saving paper.<BR>><BR>>
________________________________<BR>><BR>>
_______________________________________________<BR>> postgis-users mailing
list<BR>> postgis-users@postgis.refractions.net<BR>> <A
href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A><BR>><BR>> \
_______________________________________________<BR>> postgis-users mailing
list<BR>> postgis-users@postgis.refractions.net<BR>> <A
href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis. \
refractions.net/mailman/listinfo/postgis-users</A><BR>><BR>><BR>_______________________________________________<BR>postgis-users \
mailing list<BR>postgis-users@postgis.refractions.net<BR><A
href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A><BR><BR><BR></FONT></P>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG>The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure pursuant to
Massachusetts law. It is intended solely for the addressee. If you received
this in error, please contact the sender and delete the material from any
computer. </STRONG></P>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG><FONT color=#339900 size=2>Help make the earth a greener place. If
at all possible resist printing this email and join us in saving paper. </P>
<P></FONT></STRONG></P>
<P>
<HR>
<P></P>_______________________________________________<BR>postgis-users
mailing
list<BR>postgis-users@postgis.refractions.net<BR>http://postgis.refractions.net/mailman/listinfo/postgis-users<BR></BLOCKQUOTE></BODY></HTML>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic