[GRASSLIST:4497] thousands of 'PNT_TO_AREA failed'; no labeled counties, yet

Sean Champ schamp at commonwerx.org
Sat Oct 9 15:39:20 EDT 2004


Hello,

First-off, I want to thank the folks who made GRASS. It is a marvelous
work of software. (I guess that that's fairly obvious, already, but it
seemed worth mentioning anyhow.)


Now, I'm having a problem after importing an SDTS DLG file, from the
USGS 2M datasets for California.


Using this:
 http://edcftp.cr.usgs.gov/pub/data/DLG/2M/CA/CA.bound.sdts.tar.gz
along with this
 http://edcftp.cr.usgs.gov/pub/data/DLG/2M/00MASTERDD_2M.SDTS.tar.gz
unpacked in the same directory: I'm encountering a few thousand
PNT_TO_AREA failed messages, on one map. 




The following is a basic transcript of the GRASS session.

With the aforementioned files unzipped in the current directory, and 
GRASS running:

------------------------------------------------ 
GRASS:directory > v.in.sdts map=CALIFORNIA   catd=CABDCATD.DDF \
                            output=boundaries
Processing CATD module
Processing STAT module
Processing IDEN module
Processing XREF module
Processing IREF module
Processing Composite module: CABDFF01.DDF
Processing manifold:
Processing NA module: CABDNA01.DDF
Processing LE module: CABDLE01.DDF . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing PC module: CABDPC01.DDF . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing NO Module: CABDNO01.DDF . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Warning: No Entity Points (NE) Module for this map layer.
Processing GRASS dig_atts
Schema Type = '3'
Processing attribute modules . . .

         TRANSFER SUMMARY
         ----------------

Identification module:  CABDIDEN.DDF

Standard identification:           SPATIAL DATA TRANSFER STANDARD
Standard version:                  1994 JUNE 10
Standard documentation reference:  FIPS PUB 173-1
Profile identification:            SDTS TOPOLOGICAL VECTOR PROFILE
Profile version:                   VERSION 1.0 JUNE 10, 1994
Profile documentation reference:   FIPS 173-1 PART 4
Title:                             CALIFORNIA / BOUNDARIES
Data structure:                    DLG-3
Map date:                          1990
Data set creation date:            19950607
Scale:                              2000000
Comment:                           This transfer requires an external data dict
ionary from the U.S. Geological Survey, National Mapping Division, with a 4-cha
racter code of DLG3, version number  2.00

External Spatial Reference module:  CABDXREF.DDF
Reference System name:                  GEO
Horizontal Datum:                       NAS


Spatial Domain module:  CABDSPDM.DDF
Spatial Domain type:                    MINMAX

Features imported:

  Lines:            10170       (10170 LE + 0 NE + 0 attributed NO)
  Nodes:             6238       (6238 NO + 0 NE)
  Areas:             5031
  Attrib. Objs.:     5318
Done.GRASS:~/system/gis/archive/usgs-geodata/DLG/2M > v.support -s option=build
 map=boundaries
V.SUPPORT:

Selected information from vector header
 Organization:  SDTS IMPORT: CABD
 Map Name:      CALIFORNIA / BOUNDARIES
 Source Date:   1990
 Orig. Scale:   2000000
 Snapping threshold    0.00
Warning: snapping requested by threshold is    0.00
    Reading Vector file 100%
    Building areas 100%
    Building islands 100%
    Attaching labels
PNT_TO_AREA failed: (0.000000, 35.665991) (Category 289)
PNT_TO_AREA failed: (0.000000, 35.630682) (Category 290)
PNT_TO_AREA failed: (0.000000, 34.181679) (Category 291)
PNT_TO_AREA failed: (0.000000, 33.682015) (Category 292)
PNT_TO_AREA failed: (0.000000, 34.074136) (Category 293)
PNT_TO_AREA failed: (0.000000, 34.098041) (Category 294)
PNT_TO_AREA failed: (0.000000, 33.565476) (Category 295)
PNT_TO_AREA failed: (0.000000, 33.645265) (Category 296)
PNT_TO_AREA failed: (0.000000, 33.521328) (Category 297)
PNT_TO_AREA failed: (0.000000, 33.726205) (Category 298)
PNT_TO_AREA failed: (0.000000, 33.893266) (Category 299)
PNT_TO_AREA failed: (0.000000, 33.891574) (Category 300)
PNT_TO_AREA failed: (0.000000, 33.890715) (Category 301)
PNT_TO_AREA failed: (0.000000, 33.688285) (Category 321)
.....continues for a long while..

PNT_TO_AREA failed: (0.000000, 34.614064) (Category 5315)
PNT_TO_AREA failed: (0.000000, 37.555940) (Category 5316)
PNT_TO_AREA failed: (0.000000, 33.165884) (Category 5317)
PNT_TO_AREA failed: (0.000000, 32.728672) (Category 5318)
 Number of lines:   10170
 Number of nodes:   6238
 Number of areas:   5031
 Number of isles:   1107
 Number of atts :   288
 Number of unattached atts :   5030
 Snapped lines  :   0
------------------------------------------------


After that, none of the state's counties appear as being labeled, even
though the file CABDBFPC.DDF seems to contain all of the county labels
for the state.



In case it might be of any help with explaining this, the file
CABDBFPC.DDF looks pretty-much like the following, but with data for
each and every country:


002542L   0600061   3204000001500000102815ATSC04843ATTS10291^^0000;&CABDBFPC^^0100;&DDF RECORD IDENTIFIER^^1600;&ATTRIBUTE SECONDARY^_MODN!RCID^_(A(4),I(6))^^1600;&SECONDARY ATTRIBUTES^_STATE             !COUNTY            !AREA_NAME         ^_(A(2),A(3),A(69))^^00142 R     00049   220400010700ATSC1107ATTS7518^^     1^^BFPC     1^^06001Alameda County

...save for the real ^^ and ^_ control characters in the original.




(It seems like the counties aren't the only things missing labels,
maybe; they are  the only things for which I knew a string to
grep the dataset files for)


When running v.support for the 'boundaries' map, I'd tried using the
'-s' flag and various 'threshold' values -- while blindly guessing at
what to use for it; 2000000 (the scale of the map) sure didn't work; I
am certainly open for suggestions about what might be a better
threshold value, or otherwise.



So, I guess that my questions would be:

  * When importing from SDTS, do I have to do anything 'special', to
    make sure that any labels from the data-set will be appropriately
    applied, for the map? 

  * Why would it be that there are so many "PNT_TO_AREA failed"
    messages coming up, on v.support option=build for the map?


I'll appreciate any help on this. 

    

Thank you,


--
Sean Champ




More information about the grass-user mailing list