On Wed, Sep 7, 2011 at 4:33 PM, Matthew Mulbrandon <mulbran@hotmail.com> wrote:
Hi,
Get nebulous error with data set from lee county. Bot dot data and parcel
data when importing.
v.in.org dsn="filepath" I don't want to write the whole thing.
"Projection of input dataset and current location appear to match.
output = dfds min_aria=0.0001 snap = -1
Layer: Lee-parcel
Counting polygons for 526085 features
Importing map 526085 features...
dbmi: Protocol error"
This happens about about 75 percent for the point map. 95 percent for the
parcel map.
I can open the dot file in qgis and the are 0 errors. I can clip and import
fine into grass.
So I think there might be a null value or maybe some other values that is
killing the import.
Any help would be appreciated.
Can you please provide information about the GRASS version you use,
the operating system and which database driver you are using (output
of db.connect -p)?
On Wed, Sep 7, 2011 at 4:33 PM, Matthew Mulbrandon mulbran@hotmail.com wrote:
Hi,
Get nebulous error with data set from lee county. Bot dot data and parcel
data when importing.
v.in.org dsn=“filepath” I don’t want to write the whole thing.
"Projection of input dataset and current location appear to match.
output = dfds min_aria=0.0001 snap = -1
Layer: Lee-parcel
Counting polygons for 526085 features
Importing map 526085 features…
dbmi: Protocol error"
This happens about about 75 percent for the point map. 95 percent for the
parcel map.
I can open the dot file in qgis and the are 0 errors. I can clip and import
fine into grass.
So I think there might be a null value or maybe some other values that is
killing the import.
Any help would be appreciated.
Can you please provide information about the GRASS version you use,
the operating system and which database driver you are using (output
of db.connect -p)?
and the data set is called 'parcel and condo points' about 150 mb.
GRASS 6.4.2svn (florida):/tmp/dd > v.in.ogr
ParcelCondoAddressPoints20110831.shp
out=ParcelCondoAddressPoints20110831
Projection of input dataset and current location appear to match
Layer: ParcelCondoAddressPoints20110831
Counting polygons for 526067 features...
Importing map 526067 features...
100%
-----------------------------------------------------
Building topology for vector map <ParcelCondoAddressPoints20110831_tmp>...
Registering primitives...
526067 primitives registered
526067 vertices registered
Number of nodes: 451626
Number of primitives: 526067
Number of points: 526067
Number of lines: 0
Number of boundaries: 0
Number of centroids: 0
Number of areas: -
Number of isles: -
Building topology for vector map <ParcelCondoAddressPoints20110831>...
Registering primitives...
526067 primitives registered
526067 vertices registered
Building areas...
100%
0 areas built
0 isles built
Attaching islands...
Attaching centroids...
100%
Number of nodes: 451626
Number of primitives: 526067
Number of points: 526067
Number of lines: 0
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0
For me it works fine in GRASS 6.4.svn. So, you may either update or wait for
the official 6.4.2 release hopefully in October.
On Wed, Sep 7, 2011 at 4:33 PM, Matthew Mulbrandon <mulbran@hotmail.com>
wrote:
> Hi,
>
> Get nebulous error with data set from lee county. Bot dot data and
> parcel
> data when importing.
>
> v.in.org dsn="filepath" I don't want to write the whole thing.
>
> "Projection of input dataset and current location appear to match.
>
> output = dfds min_aria=0.0001 snap = -1
>
> Layer: Lee-parcel
>
> Counting polygons for 526085 features
>
> Importing map 526085 features...
>
> dbmi: Protocol error"
>
> This happens about about 75 percent for the point map. 95 percent for
> the
> parcel map.
>
> I can open the dot file in qgis and the are 0 errors. I can clip and
> import
> fine into grass.
>
> So I think there might be a null value or maybe some other values that
> is
> killing the import.
>
> Any help would be appreciated.
>
Can you please provide information about the GRASS version you use,
the operating system and which database driver you are using (output
of db.connect -p)?
For me it works fine in GRASS 6.4.svn. So, you may either update or wait for
the official 6.4.2 release hopefully in October.
A correction: I have made the location from the SHAPE file using the
GRASS7 startup script. Hence the location is set to use SQLite as
backend... so essentially I made the successful test with the SQLite
backend.