bnordgren / toposm Goto Github PK

Display mile markers when zoomed in enough..

@asciiphil The repository is missing the definition of shields_get_single_filename. Would it be possible to get it added? Or perhaps a description of what it's supposed to do?

Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "./toposm.py", line 392, in run
    mapnik.load_map(map, self.mapname + ".xml")
RuntimeError: Postgis Plugin: ERROR:  function shields_get_single_filename(text, text, unknown, integer) does not exist
LINE 1: SELECT * FROM (SELECT way, shields_get_single_filename(netwo...
                                   ^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
in executeQuery Full sql was: 'SELECT * FROM (SELECT way, shields_get_single_filename(network, ref, 'cutouts', 20) AS route_shield
               FROM osm_line
	       WHERE osm_id < 0
                 AND route = 'road'
                 AND (network = 'US:I' AND char_length(ref) BETWEEN 1 AND 2)
               ORDER BY ST_Length(way) DESC
	    ) AS shields LIMIT 0'
  encountered during parsing of layer 'shields-very-low-zoom' in Layer at line 837 of 'features.xml'

Create an overlay (for the basemap or for the aerial imagery) from the Montana cadastral dataset. Should at least show the parcels and ownership at appropriate scale.

Would like to render a features layer with a transparent background to overlay on aerial imagery. By default, just include everything that's in "features.xml.templ", but may need to adjust.

Seeding the map cache for Mineral/Sanders/Missoula counties is not quite done yet. Starting to play with the data some, I'm seeing some things I want to address. I'm currently leveraging the following layers from:

• TopOSM's hypsorelief (as a base layer)
• aerial imagery, from NAIP (base layer)
• TopOSM's features layer (transparent raster overlay)
• TopOSM's contours layer (transparent raster overlay)

I've only downloaded and imported these over my local area for the sake of time and/or space. However, it does look as if I will have more room on my 64Gb card. Additionally, the existing software stack I've set up for the RPi cannot render map tiles. It relies on having them pre-rendered. If you wander out of the preconfigured area, you just see a blank screen.

For Rev 2.0, I want:

• to define a "home area" where all data are available (e.g., aerial imagery)
• the ability to spontaneously wander into new areas without explicit preparation,
  • accepting that less data may be available once I leave the home area
  • ideally, some level of map detail should be available for all of CONUS,
  • minimally, some level of map detail will be available for the western 11 states
• to be able to render map tiles when necessary
• to cache map tiles

This set of requirements implies a number of things:

• a different software stack is necessary (check out https://switch2osm.org/serving-tiles/building-a-tile-server-from-packages/)
• more stuff will be running on the RPi
  • postgis
  • mapnik renderer
• outside the home area, a different map projection may be necessary.
• it may be necessary to string together more than one RPi to accomodate the extra software

The OSM import was just for the state of Montana. It would be useful to have data on the Idaho side too.

Currently, OSM contains a whole lot of roads which may not be drivable, and it's hard to distinguish open from closed, passable from not, etc. I'd want to distinguish a few important items:

• Location and type of obstructions (gates, kelly humps, etc)
• Road status:
  • Open road sections
  • closed road (permanent)
  • closed road (seasonal)
  • whether a closed section is passable or not (possibly "what would it take to make the road passable?")
• The "effective date" of the above.