I am attempting to store data from the TIGER/Line shapefiles into a database table, but am having issues with reducing the precision from the 5 decimal places to 3 decimal places.
What I find is that after I dig down and get the coordinates, then eliminate duplicates, I'm left with a list of coordinates something like this (which I call semi-duplicates for lack of a better term): 45.900, 178.353 45.900, 178.355 45.900, 178.361 45.900, 178.363 I end up with the same latitude, but several intermediate longitudes (or vice versa). I don't need all of these intermediate points, but I realize that this is an artifact of brute force rounding. Is there a "better" way to reduce the decimal precision? Jason ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
