cross-street-indexer

Cross Street Indexer

Light weigth reverse geocoding for cross street 100% sourced from OSM QA Tiles.

Features

• Blazing fast 1/20th of a millisecond search (275,000 ops/sec)
• Processed United States OSM QA Tiles in 35m 13s (189714 tiles)
• Easy to use CLI to build index
• Node 6 & 7 compatible
• Only uses Tile Reduce + Turf
• Ready for S3 Upload or LevelDB
• Bundled 5MB QA-Tiles for testing purposes

Process

• Step 1: Filter data from QA-Tiles (lib/qa-tiles-filter.js)
• Step 2: Extract road intersections from QA-Tiles (lib/intersections.js)
• Step 3: Normalize street name ABBOT AVE. => abbot avenue (lib/normalize.js)
• Step 4: Convert intersections into multiple points using a combination of road & ref tags (lib/geocoding-pairs).
• Step 5: Group all hashes into single Quadkey JSON object (lib/reducer.js)
• Step 6: Publish to S3 or LevelDB

Install

npm

$ npm install --global cross-street-indexer

yarn

$ yarn global add cross-street-indexer

Quickstart

$ cross-street-indexer latest.planet.mbtiles --tiles [[654,1584,12]]
$ cross-street-search "Chester St" "ABBOT AVE." --tiles [[654,1584,12]]
-122.457711,37.688544

CLI

Cross Street Indexer

$ cross-street-indexer --help

  Cross Street Indexer

  Usage:
    $ cross-street-indexer <qa-tiles>
  Options:
    --output    [cross-street-index] Filepath to store outputs
    --bbox      Excludes QATiles by BBox
    --tiles     Excludes QATiles by an Array of Tiles
    --debug     [false] Enables DEBUG mode
    --verbose   [false] Verbose output
  Examples:
    $ cross-street-indexer latest.planet.mbtiles

Cross Street Search

$ cross-street-search --help

  Cross Street Indexer

  Usage:
    $ cross-street-search <name1> <name2>
  Options:
    --output    [cross-street-index] filepath to Cross Street index output folder
    --tiles     Lookup index files via Tiles or Quadkeys
    --bbox      (not implemented) Lookup index files via BBox
  Examples:
    $ cross-street-search "Chester St" "ABBOT AVE." --tiles '["023010221110"]'

Normalization Process

Normalization should follow the following standards:

• Drop any period if exists
  • ave. => avenue
• Street suffix to full name
  • ave => avenue
  • CIR => circle
  • ln => lane
• Name should be entirely lowercase
  • Parkside Avenue => parkside avenue
• Direction to full word
  • N => north
  • S => south
  • NE => northeast

Index (JSON Lines)

The Cross Street Index is stored in an easy to read key/value JSON Lines format.

• key: Normalized road pairs (<name1>+<name2>)
• value: Longitude & Latitude

{"abbot avenue+chester street":[-122.457711,37.688544]}
{"chester street+abbot avenue":[-122.457711,37.688544]}
{"chester street+lisbon street":[-122.45821,37.68796]}
{"lisbon street+chester street":[-122.45821,37.68796]}
{"hoffman street+lisbon street":[-122.456764,37.687179]}

OSM Attributes

• name: Street name (Abbot Avenue)
• ref Reference number normaly used to tag highways numbers
• highway classification (residential, primary, secondary)
• bridge yes/no
• tunnel yes/no
• @id OSM ID of street (way)

Debugging

Adding --verbose will stdout a JSON object for each QA-Tile with the following information:

{
  tile: [ 655, 1586, 12 ],
  quadkey: '023010221131',
  features: 9626,
  intersects: 1053
}

Adding --debug will store .geojson items for each process & for each QA-Tile:

• debug/<quadkey>/features.geojson - raw GeoJSON of QA-Tile
• debug/<quadkey>/lines.geojson - Filtered (Multi)LinesString from QA-Tile
• debug/<quadkey>/intersects.geojson - Point which are intersecting roads
• debug/<quadkey>/index.json - Final Cross Street index

Limitations

Loops

Loops would return multiple cross street matches, only the last matched point is stored.

Turning Circles

Turning Circles without any names are exclude, thus not finding any matches.

References

• Natural Node to create fuzzy mathes
• Carmen to normalize roads
• LevelDB as storage