* The process does not account for poor placement of objects. Placing a lake on the side a mountain, or crossing two ridges will give odd looking results.

* Sharp angels on ways can create render artifacts.

* Render times can be slow depending on the size of the area and the scale being used.

* Low point flood fills can be slow and memory intensive.

* Currently, no less-than sea-level elevations can be used.

* Hydraulic erosion currently has one strength setting for the entire map. (Note: Adding an erosion-strength layer, could solve the issue).

* Currently no wind erosion. (Note:Add a blur layer?)

* No current method for blending two neighboring areas from different renders so that they appear natural.

* Creating a caldera results in a filled mound (no drainage) or a mound with an unrealistic channel cut in one side (with drainage). (Note: create a fill strength layer? Or add "drain" : an elevation with < ocean-level value in the middle.? )

• Large area renders may fail due to lack of memory. (Tile the process?)

* Flats can be too flat. (Add noise options?)

* Sink holes appear in some renders resulting in waterways vanishing rather than flowing to sea-level. This appears to be caused by either a base layer point with an elevation under sea-level or noise from a later object pushing the elevation under sea-level.

* Loss of detail on complicated lake and flat shapes.

* Lake and flat granularity is based on object size yielding inconsistent results.

* Rendering at different scales gives noticeably different results.

* Ridge-top shear. Position shear on nodes, set elevation, rotation and angular altitude.

*Add user settings to control Y-axis Noise.

* Add user spread jitter settings.

• Trim height-map to territory outline to remove any elevation data that extents beyond target territory.

• Automatic lakes. Mark naturally flat areas as lakes based on settings criteria.

* Dam objects. Should not erode. A lake would fill behind it. (Require hardness layer 100%?)

* Increase render speed by saving objects and loading them if their settings and positions have not changed.

* Hardness layer to allow variable erosion strength. Could be set at the same time as the initial base layer, or set based on object footprints.

* Boolean objects to shape topography?

* Break results in to tiled files to avoid memory issues allowing larger overall areas with more detail.

* Simulate faults. How?

• Set object render order based on a user-set priority queue. That would allow specified ridges to be rendered later in the process and be placed over flats and lakes. This would make islands in lakes possible.

* Use height map data to generate OSM land-cover data. Latitude and elevation can be used to estimate temperatures, elevations, slopes. Temperature, topography and a prevailing wind direction can be used to estimate rainfall. All of the above can be used to predict a likely biome/ground-cover at each point of the map. A version of this was attempted several years ago, but with problematic results when exporting to OSM. I stopped working the updated version when I switched focus back to the underlying topography.

Ground-cover Estimates	JOSM version
	Link to pictured partial JOSM File

* Lake outlines could be traced and exported to JOSM files.

* Convert water paths to OSM data for export to the map. If water volume can be calculated, waterway widths could also be estimated based on adjacent topography, and exported to a OSM file.

* Watershed map: Starting at sea-level and tracing water paths upstream along all tributaries would create a watershed map.

• River long profile: Use water flow paths and elevations to generate chart showing a river's elevation along its entire length.