Hello,

I am currently working on updating the charging_station POIs arround me. Also I am testing with an experimental UI which shows the kind of data optimised for that.

Special for this use case I ask myself if there is any function within OSM to create "dynamic" POIs. What I have in mind is that (as for example ChargeNow) the status of the station (free, out of service etc.) comes from the operator. From my perspective it is great that all the mappers update all the tags, but some information must be delivered by the operator as they are nearly realtime.

Is there any way to archive this requirement and if not where can I discuss my proposal how this could be done?

Best regards

Malte

PS.: Technically it could be set a tag with a REST endpoint which delivers some Key / Values which match the OSM tags.

On the POI: dynamic_data:url = ttps://api.operator.com/station/1234

Response from operator: socket:type2 = 2 socket:type2:free: 1 in_service: true

asked 30 Oct '16, 14:32

derBroBro's gravatar image

derBroBro
11112
accept rate: 0%


I think the proper way to do this is having existing tags like these on the POI:

operator=XYZ Corp
ref=1234

Then you'd write a charging station map that knows "if I want to know the status of a charging station run by operator XYZ, I need to call this URL..." - and take it from there.

permanent link

answered 30 Oct '16, 14:44

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
74.4k866721152
accept rate: 24%

I think this is a great "option C". But I would like to prefer a more standard way. If there is no existing solution for this, where is the right place to make a proposal?

(30 Oct '16, 16:35) derBroBro
1

To solve this in a "standard" way, you would not only have to add the URL of the service to OSM but also the algorithm how to parse the response. This is out of scope for OSM.

(30 Oct '16, 17:07) Frederik Ramm ♦

I am absolutely with you but the interface should be defined. If I create it just for me no one else will be able to use it. Also I think the "problem" of just holding handpicked data is not only affecting this use case (which was only an example). It could bring the project forward if 3rd parties have a standard way of providing data.

What I am looking for is just the interface how to set the "link" in osm to a system which holds the data and define how a default answer could look like. It is for me totaly out of scope to include this to the rendered tiles nor to make it part of osm in general by deliver the data to the API request.

I am already a little bit confused how to come forward with this. From my persepective it is not direct an osm topic but (possibly) a related project which should also make use of the exsting osm experience and ideas.

So, my question is still where to discuss this? There are forums, wikis, mailing lists and irc etc.. It is still totaly unclear where to start and I am also getting already the feeling that such ideas are not welcome.

(30 Oct '16, 18:18) derBroBro

The URL doesn't belong into OSM. What if the API changes? Then you have to update every URL. Instead just go for Frederik's suggestion by adding just the operator and ref tags. This is already sufficient. The client just needs to query all objects for the operator he is interested in and then construct the corresponding URLs based on the ref tags.

(30 Oct '16, 19:31) scai ♦

The ref tag should be one documented elsewhere too.

(30 Oct '16, 19:43) yvecai
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • 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:

×164
×6

question asked: 30 Oct '16, 14:32

question was seen: 1,469 times

last updated: 30 Oct '16, 20:32

powered by OSQA