3vivekb / osm_sidewalk_staging

tools to prepare sidewalk data for OSM staging with Open Sidewalks schema

About

tool to prepare sidewalk data for OSM staging with Open Sidewalks schema

Setup:

• aquire appropriate files (streets network with sidewalk left and right data) and boundary specification file
• fill out sources.json with information about your data and the type of tasks you are trying to create
• download the packages not on pip. These are currently these packages

  • https://github.com/AccessMap/crossify/tree/crossify_new

  • https://github.com/AccessMap/sidewalkify

  • https://github.com/AccessMap/accessmap-database-bootup/tree/master/

  • download them from github and then locally run command: pip3 install [path to local package folder] or run this command in your terminal to directly install them to pip.

  • pip3 install git+git://github.com/AccessMap/crossify/tree/crossify_new.git

  • pip3 install git+git://github.com/AccessMap/sidewalkify

  • This package needs to be installed with the first method since we want to insatall it's sub backage.

  • https://github.com/AccessMap/accessmap-database-bootup/tree/master/

  • for this final package we need to download a sub folder of accessmap-database-bootup called data_manager so the pip command will be pip3 install [path to downloaded reop]/data_manager

• download all remaing used packages with pip. The latest versions used are specified in requirements.txt. command is pip3 install -r requirements.txt
• run with python 3

if you get an error about libspatialindex, you need to 'brew install spatialindex' then run

Basic Workflow

input required:

• streets center line data set with sidewalk left and right data
• sources.json file in source_json_examples folder edited to have appropriate parameter information

input optional:

• bondary of data to stage like a nighborhood to stage

output:

• osm.xml files split into tasks (by intersection or block) to be uploaded to Open Sidewalks tasking manager tasks.opensidewalks.com

sources.json specification

Look at examples in sources_json_examples

City Name

• Example: "city": "Seattle"

Import Name

• The name of the folder where the resulting osm.xml are found
• Example: "import_name": "University District"

Bondary Specification

• Give details of the boundary of the data you want staged

Path

• Example: "path": "./source_data/seattle/neighborhoods.shp"

Selection

• Specify if you want a slection of your data staged (True) or all of it (False).
• Example "selection": "True"

Attribute Selector Colum Name

• Example "attribute_selector": "name",

Attribute Selector value

• Example "attribute_selector_value": "University District",

Buffer Distance Meters

• If you are trying to create a boundary a cetain distance around a point, then the selected feature above must be a point, and here you select how large of a buffer. If your above selection is a polygon then set this value to zero.
• Example "buffer_distance_meters": 850

Task Information

• decides if sidewalks and crossing data are staged together or in separate tasks

"joined": "False",

• Also give type of tasking for blocks and crossing data. "blocks_type": "block" and "crossings_type": "voronoi"

"joined" "True"

• Also give type of joined tasking either "type": "voronoi" or "type": "block"

Layer Information

Streets

Path

• Example: "path": "./source_data/seattle/streets.shp"

Source

• Description of where the data is from
• Example: "source": "King County GIS Data Portal Streets Network"

Sidewalk Coding Information

• Sidewalk coding is used to understand what the sidewalk values represent.

• In the absent["code"] field, you specify all values that represent that there is no sidewalk. A value of zero means anything less than or equal to zero.

• In the offset["type"] field, you specify what offset coresponds to each sidewalk code. The optional values are "feet", "meter", and "category". "feet" and "meter" values are interpreted to be the offset distance in that unit. "category" values are translated using the way type. The way type code is translated to one of five waytypes using the categorymap of the way type column and then each waytype is translated to an offset distance using "category_offset".

  • Example: "swk_coding": {

    "absent": {

      "code": [0, 2]
    

    },

    "offset": {

      "type": "category",
    
      "category_offset": {
    
          "freeway": 0,
    
          "primary_arterial": 20,
    
          "minor_arterial": 11,
    
          "colector_arterial": 8,
    
          "local": 6.25
    
    	}
    

    }

  }

Metadata

1. primary key

• colum name
• null value

2. sidewalk left value

• column name

3. sidewalk right value

• column name

4. way type (if category used as offset type)

• column name
• category map (translate each category key to associated type)