Given a road network and a set of address points as line delimited geojson; output an interpolation network.
Input line-delimited geojson features of points. Each point should have a property called street
containing the street name
and number
containing the street address.
Note: pt2itp is designed to be run on numberic address points. Unit numbers should be stripped out before being fed into pt2itp. Alternatively they
can be stripped using a map file. Examples of bad addresses and their correct counterparts include: 16A => 16
(US Unit #), 1/3 => 3
(NZ Unit #), 12-4 => 12
, etc
If non-numeric input is detected in addresses, a fatal error will be thrown.
{ "type": "Feature", "geometry": { "type": "Point", ... }, "properties": { "street": "Main Street", "number": 10 } }
{ "type": "Feature", "geometry": { "type": "Point", ... }, "properties": { "street": "Main Street", "number": 11 } }
...
Input line-delimited geojson features of lines. Each line should have a property called street
containing the street name.
{ "type": "Feature", "geometry": { "type": "LineString", ... }, "properties": { "street": "Main Street" } }
{ "type": "Feature", "geometry": { "type": "LineString", ... }, "properties": { "street": "Main Street" } }
...
./index.js map --in-network=<FILE.geojson> --in-address=<File.geojson> --output=<File.geojson> --tokens=./lib/tokens/en.json"
PT2ITP follows the Semver spec for it's CLI interface.
This means that breaking changes to the CLI tools will result in a MAJOR
release.
New features will result in a MINOR
release and bug fixes a PATCH
.
Internal functions may change in breaking ways with a MINOR
release so long as they
don't change/break the CLI interface.