Rev 2.0 mapping stack #7
Description
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