Proceed to GeoCommunity Home Page


SpatialNewsGIS Data DepotGeoImaging ChannelGIS and MappingSoftwareGIS JobsGeoBids-RFPsGeoCommunity MarketplaceGIS Event Listings
HomeLoginAccountsAboutContactAdvertiseSearchFAQsForumsCartFree Newsletter

Sponsored by:


TOPICS
Today's News

Submit News

Feature Articles

Product Reviews

Education

News Affiliates

Discussions

Newsletters

Email Lists

Polls

Editor's Corner


SpatialNews Daily Newswire!
Subscribe now!

Latest Industry Headlines
SiteVision GIS Partnership With City of Roanoke VA Goes Live
Garmin® Introduces Delta™ Upland Remote Trainer with Beeper
Caliper Offers Updated Chile Data for Use with Maptitude 2013
Southampton’s Go! Rhinos Trail Mapped by Ordnance Survey
New Approach to Measuring Coral Growth Offers Valuable Tool for Reef Managers
Topo ly - Tailor-Fit for Companies' Online Mapping Needs

Latest GeoBids-RFPs
Nautical Charts*Poland
Software & Telemetry GPS
Spatial Data Management-DC
Geospatial and Mapping-DC
Next-Gen 911-MO

Recent Job Opportunities
Planner/GIS Specialist
Team Leader- Grape Supply Systems
Geospatial Developer

Recent Discussions
Raster images
cartographic symbology
Telephone Exchange areas in Europe
Problem showcasing Vector map on Windows CE device
Base map

GeoCommunity Mailing List
 
Mailing List Archives

Subject: [gislist] Compressing Lines
Date:  10/24/2005 03:35:01 PM
From:  Bill Thoen



I'm trying compress all the lines in the US Census Bureau's TIGER data
set into as small a space as possible for use with a geocoder, so I'm
looking for ideas on how best to do this. I've managed about 60%
compression by using coordinates clipped to the nearest .00001 degrees
and applying a delta compression techique from there. (To do this I
store the first coordinate as a pair of signed long integers, then I
store the differece between those and the next coordinate as a pair of
bytes, then difference between the next point as a pair of bytes, and so
on. If the difference between subsequent points is greater than 255 in
either x or y, I just store the full coordinate and start again from
there.) I trim the coordinates to 5 decimals because for the purposes of
locating an address, the sixth digit contributes only a few feet to the
precision, and so it is not really necessary.

My question is, is there a better way to approach this problem to get
significantly greater compression, yet still retain good retrieval
performance?

- Bill Thoen

_______________________________________________
gislist mailing list
gislist@lists.geocomm.com
http://lists.geocomm.com/mailman/listinfo/gislist

_________________________________
This list is brought to you by
The GeoCommunity
http://www.geocomm.com/

Sponsored by:

For information
regarding
advertising rates
Click Here!

Copyright© 1995-2012 MindSites Group / Privacy Policy

GeoCommunity™, Wireless Developer Network™, GIS Data Depot®, and Spatial News™
including all logos and other service marks
are registered trademarks and trade communities of
MindSites Group