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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: richard[at]systemeD.net [Added to the original trac issue at 12.27pm, Thursday, 15th December 2005]
The ESRI PDF is the reference I've used when parsing shapefiles before. It's a fairly basic file format (as long as you get the byte order right, of course). Never done it in Java or Ruby, I'm afraid, only Perl.
Remember that ESRI concepts won't necessarily translate directly into OSM's data model. For example, you can have polygons with 'holes' (e.g. for built-up areas containing green space). To begin with, it may be most sensible only to import a subset of the shapefile data - probably just polylines.
In so far as one can generalise, shapefiles are probably more likely to contain copyrighted data than GPX files are. I'd therefore suggest that the warning about "don't submit any copyrighted data" is amplified for this feature.
Reporter: tom[at]tom-carden.co.uk
[Submitted to the original trac issue database at 8.52pm, Wednesday, 14th December 2005]
http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf
The text was updated successfully, but these errors were encountered: