|
I looking for a way to add sensors to a map using its geolocations. What is the best object to represent a sensor in OSM? It doesn't need to be visible, but it needs to be readable in some way. Is that a command line which I could use in order modify a OSM file adding/updating a sensor with all its characteristics, as values, name, ID, location, tag, etc? The idea is to build a software that plans a route based on the values of each sensor. The OSM file will be read by the OSRM project in order to accomplish it. I currently have spread sensors over a city. Each sensor has its own geolocation (lat and lng) and its own values. The values are updated at a certain frequency, which makes it impractical to open a map editor like Potlatch or JOSM every time that the values of each sensor need to be updated and for this purpose only. So it's needed a faster way to update these sensors. Thanks! |
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 10 Oct '16, 21:02
question was seen: 1,137 times
last updated: 11 Oct '16, 04:40
Related questions
NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum
what is "in OSM" for you? Do you mean in the public, central database of openstreetmap.org? Why do you think your sensors should be in there (and usable by everybody)? How often do you want to update a sensor in the OSM database?
Are you just intending to navigate between sensors, or does the sensor value affect navigation somehow ? Do you expect to use OSRM as-is, or are you only using part of the OSRM software, like the extractor ?
The sensors will be added to my local OSM file only. The OSRM engine will make use of the local OSM file only. The sensors are geolocated (lat and long) and the values measured by the sensors would be interpreted as an additional weight/cost of a street/path where the sensor is placed.
Each sensor measures a condition of the street, in this case, the air quality along the path. The worse is the air quality, the higher is the weight/cost of such street and the more difficult it would be for this street to be chosen by OSRM engine as a possible route for a vehicle or pedestrian.
I intend to use the sensors as a tool to keep track of polluted areas and use the OSRM engine to avoid such areas. The values from the sensor would be updated every 5 minutes (need to search a feasible update frequency).
I'm using the whole OSRM engine as the main software for such purpose. And also using a web interface in order to show the results for a user.
Once the OSRM identify that are a certain number of sensors in a street and, at the same time, its air quality, then the engine would evaluate if is worthy or not choose such path, depending on the total cost for the pedestrian/vehicle.