In the Greek myth Neleus is the twin brother of Pelias, in this case it's a fork of the famous open source geocoder Pelias. What Neleus solves is to find geocoding and reverse geocoding solutions based on orographic structures such as valleys, canyons, peaks, ridges, plateaus and without excluding hydrographic elements such as torrents, rivers and lakes.
In addition will also be taken into consideration elements typically useful in outdoor contexts such as paths and points of interest in the natural landscape such as waterfalls, caves and monumental trees.
if you know how a normal geocoder works to understand what Neleus proposes, it is a geocoding for visitors to the mountains and nature in general, oriented to the tourist and hiking context. Neleus is based on the same microservices architecture as Pelias with small differences, the datasources are very different but in common they have their open source soul and open data support.
These tools are separate projects and are used by neleus to build and organize its internal database
OpenValleyMap a shared geospatial database with the borders and toponymy of all the valleys. The most important datasource supported by Neleus to classify areas and natural elements
GeoPicker A super fast http rest interface to pick Geospatial data, it is used to obtain which valley a certain position is located and decorate with some orographic information from terrain models a certain point or orographic element.
Reverse geocoding: giving orographic information on a specific position, for example in the context of web tools in the tourism sector to inform the user in which valley it is located
Geocoding: giving information on landscape elements usually ignored or poorly managed by normal geocoders focused on administrative limits, not very useful in a hiking context, in the outdoor context elements such as bivouac or shelters, paths and equipped routes
many others: contribute to extend the usage scenarios.
Different types of orographic elements and how they are managed at the geo-spatial data level, during importing data phase each of these elements is enriched with some metadata altitude, aspect and landuse.
| element | geometry | geocoder | reverse |
|---|---|---|---|
| valleys | polygon | ||
| canyons | linestring/polygon | ||
| mountains | polygon | ||
| peaks | point | ||
| massif | polygon |
| element | geometry | geocoder | reverse |
|---|---|---|---|
| lakes | polygon | ||
| wetland | polygon | ||
| torrents | linestring | ||
| springs | point |
| element | geometry | geocoder | reverse |
|---|---|---|---|
| forests | polygon | ||
| meadow | polygon | ||
| ancient tree | point |
| element | geometry | geocoder | reverse |
|---|---|---|---|
| reserve | polygon | ||
| shelter | point | ||
| trail signs | point |