|Failed to load latest commit information.|
|src||Forgot to change lon to lat here.|
|.classpath||Removing eclipse stuff from source control.|
|README.txt||Update readme. 0.8.5|
|pom.xml||prepare for the next development iteration|
|run.sh||Switching to use the wildcard for extra args. Thanks to Frank.|
SHP to OSM 0.8.5 Copyright Ian Dees, All rights reserved 20 August 2011 Project website: http://github.com/iandees/shp-to-osm Dependencies Dependencies are handled by the Maven pom.xml file included. The JAR distributed at the above site includes all of the required classfiles to run out of the box. Rules file The rules file is a simple comma-separated text file: Field: Description: 1 The shapefile type to match (outer, inner, line, point) 2 The source attribute name to match 3 The source attribute value to match. Can be empty to match all values. 4 The name of the tag to apply when the source key/value pair match. 5 The value of the tag to apply. Use a single dash ("-") to use the original value. As of shp-to-osm 0.8, the rules file can contain an "exclude" rule. It is very similar to the field list above: Field: Description: 1 The type of OSM primitive (node, way, relation) 2 The word "exclude" 3 A tag key to match for exclusion. If this is empty, all untagged elements will be excluded from the output OSM file. 4 A tag value to match for exclusion. If this contains "*", then all elements that have the tag key specified in field 3 will be excluded, regardless of value. Use the --copyTags argument to copy all the attributes from the shapefile's .dbf to tags in the resulting OSM file. An optional string argument to --copyTags will add a prefix to all copied tag. Tags will only be copied if their value is non-empty or non-null. Running Use the following command line to run the app. Also, you can use the .bat or .sh run files to issue the same command as long as you give it the same set of arguments. The [-t] at the end of the command here is an optional flag to tell the application to only include ways that have had a tag applied to them. For now, it is required to be at the end of the arguments list. java -cp shp-to-osm-0.8.5-with-dependencies.jar com.yellowbkpk.geo.shp.Main --shapefile <path to input shapefile> \ --osmfile <prefix of the output osm file name> \ [--copyTags <prefix>] \ [--rulesfile <path to rules file>] \ [--outdir <root directory for output>] \ [--outputFormat <osm|osmc>] \ [--maxnodes <max nodes per osm file>] \ [--glomKey <key to glom on (see README)>] \ Glomming As of shp-to-osm 0.7, the applications supports what I call "glomming": the ability to connect ways that share some key/value pair. The command line argument --glomKey specifies a single OSM tag name that should be used when checking for matches. It is important to note that the glom key is an OSM tag name, not a shapefile attribute name. The tag must be created by your rulesfile or it won't be useable as a glomming key. For example, if my shapefile has a large river system where each segment of river is split at the point where rivers come together, then we can use glomming to connect the ways of rivers that share similar name (or in the case of NHD data, reachcode) values.