grant-humphries / rlis2osm Goto Github PK

apparently not having one can discourage people from using your code:
http://docs.python-guide.org/en/latest/writing/structure/
http://choosealicense.com/

not sure if this is going to work out, but there's some info on taking that approach here:
http://stackoverflow.com/questions/428895

loading the big osm file that this project creates requires extra memory for josm
details on how to do that at the following links:
https://josm.openstreetmap.de/wiki/Download#VMselectiononWindowsx64
http://forum.openstreetmap.org/viewtopic.php?id=25677

see the comments at bottom of the expand module for details

from debugging on a windows 7 machine

• on windows machines when running buildout you sometimes get the below error, the solution is to simply run buildout again

  WindowsError: [Error 5] Access is denied

• for this script to work the GDAL_DATA environment variable must be set, the folder it should be set to varies depending on the operating system and gdal install, but it will always be the folder that contains the file: coordinate_axis.csv

RLIS has a separate layer: bike_routes that can be tied back to the centerline from which bike infrastructure information can be derived, use this tag add that info as OSM tags

Unknown abbreviations from the RLIS trails dataset:

SYSTEMNAME field

• PBH Incorporated Trails

TRAILNAME field

• FAOF Canberra Trail
• TBBV Path

rlis files are in epsg:2913, but many apps assume geojson to be in epsg:4326, may need to switch to another write format to accommodate this, originally went to geojson to handle longer field names that are required for osm and that shapefiles could not handle

Within rlis the bike data set generally uses the segments from streets to describe on street bike infrastructure and retains the unique id from streets. However, sometimes bike feature differ within a single street segment so rlis splits the segments and prepends a unique number to the existing id. Right now I'm simply stripping that leading number and adding the information to a dictionary so whichever infrastructure piece is added to the dictionary last is what is used for the entirety of the original street segment. I need to switch this up to use the geometries from bikes instead of streets in these situations.

to give user status updates etcetera

and consider using zest.releaser to aid in the process of it's use

Since a few months I took over maintenance of ogr2osm and I noticed this project shows up in the github dependency graph, but it turns out you're depending on your own fork of the project. While github detects the wrong dependency, your setup script may work correctly, I didn't test this.
However, given ogr2osm is now available on pypi and its version is greater than 0.1.0, the risk exists that users have the wrong version installed. There is no obligation of course but as a solution I'd suggest depending on my fork in stead, some issues are fixed regarding both performance and functionality and you can directly use this version as a library in stead of using subprocess.check_call.

In tests that breaks words into individual rows in Postgres table

I’ve been thinking that it would be very useful to have a version of the RLIS OSM data that only includes streets or trail segments with a recent value for “UP_DATE” and/or “CR_DATE.” This would make it really easy to find and add new streets and trails in JOSM. Perhaps you could add an additional optional setting to the tool to include only streets that were updated or created after a user specified date. It might be good to be able to choose either CR_DATE, UP_DATE, or both, as I'm not sure if a recent UP_DATE field really indicates that there have been physical changes that merit an OSM update.

Thanks!

apparently it is one, from my ubuntu virtual box:

Traceback (most recent call last):
  File "./bin/rlis2osm", line 22, in <module>
    sys.exit(rlis2osm.main.main())
  File "/home/ubuntu/rlis2osm/rlis2osm/main.py", line 228, in main
    dissolver.dissolve_ways(paths.combined, paths.dissolved)
  File "/home/ubuntu/rlis2osm/rlis2osm/dissolve.py", line 40, in dissolve_ways
    dissolve_geom = linemerge(geom_list)
  File "/home/ubuntu/rlis2osm/eggs/Shapely-1.5.17-py2.7-linux-x86_64.egg/shapely/ops.py", line 113, in linemerge
    result = lgeos.GEOSLineMerge(source._geom)
  File "/home/ubuntu/rlis2osm/eggs/Shapely-1.5.17-py2.7-linux-x86_64.egg/shapely/geometry/proxy.py", line 33, in _geom
    self.__geom__, n = self.factory(self.context)
  File "/home/ubuntu/rlis2osm/eggs/Shapely-1.5.17-py2.7-linux-x86_64.egg/shapely/geometry/multilinestring.py", line 134, in geos_multilinestring_from_py
    geom, ndims = linestring.geos_linestring_from_py(obs[l])
  File "/home/ubuntu/rlis2osm/eggs/Shapely-1.5.17-py2.7-linux-x86_64.egg/shapely/geometry/linestring.py", line 197, in geos_linestring_from_py
    ob = required(ob)
  File "/home/ubuntu/rlis2osm/eggs/Shapely-1.5.17-py2.7-linux-x86_64.egg/shapely/coords.py", line 31, in required
    return numpy.require(ob, numpy.float64, ["C", "OWNDATA"])
NameError: global name 'numpy' is not defined