You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most significant change is the addition of the iterShapeRecords()
method which is the same as the shapeRecords() method using iterators
for large files. Also removed the html and pdf versions of the README
file.
Creating attributes involves two steps. Step 1 is to create fields to contain
437
442
attribute values and step 2 is to populate the fields with values for each
438
443
shape record.
439
444
440
-
The following attempts to create a complete shapefile:
445
+
The following attempts to create a complete shapefile. The attribute and field names are not very creative:
441
446
442
447
443
448
>>> w = shapefile.Writer(shapefile.POINT)
@@ -483,13 +488,13 @@ names.
483
488
### File Names
484
489
485
490
File extensions are optional when reading or writing shapfiles. If you specify
486
-
them Pyshp ignores them anyway. When you save files you can specify a base
491
+
them PyShp ignores them anyway. When you save files you can specify a base
487
492
file name that is used for all three file types. Or you can specify a nmae for
488
493
one or more file types. In that case, any file types not assigned will not
489
494
save and only file types with file names will be saved. If you do not specify
490
495
any file names (i.e. save()), then a unique file name is generated with the
491
496
prefix "shapefile_" followed by random characters which is used for all three
492
-
files. The unique file name is returned as a string. _
497
+
files. The unique file name is returned as a string.
493
498
494
499
495
500
>>> targetName = w.save()
@@ -517,7 +522,7 @@ write them.
517
522
## Editing Shapefiles
518
523
519
524
The Editor class attempts to make changing existing shapefiles easier by
520
-
handling the reading and writing details behind the scenes.
525
+
handling the reading and writing details behind the scenes. This class is experimental and should be avoided for production use. You can do the same thing by reading a shapefile into memory, making changes to the python objects, and write out a new shapefile with the same or different name.
0 commit comments