Assigned
Status Update
Comments
an...@google.com <an...@google.com>
is...@google.com <is...@google.com>
je...@google.com <je...@google.com> #2
Apologies for not getting back to you earlier.
We are interested to know if this is still a desired feature and if so, could you please provide your use case?
We are interested to know if this is still a desired feature and if so, could you please provide your use case?
js...@gmail.com <js...@gmail.com> #3
Hello,
thx for picking this up again.
Yes we are certainly still interested: we are developing a tracking
device for freight wagons.
This device sends the approximate coordinates of the vehicle to our server.
The server then snaps these coordinates to the nearest railway, so we
can pinpoint the wagon on its exact railway track. (This is often
called "map matching".)
Right now we have 2 ways to do this:
One works with Here maps, and involves setting all the railways in the
vicinity of the tracker as a geo fence, and then checking which geo
fence is closest.
The other method works with OpenStreetMaps, where we just recover the
railway segment closest to the tracker with a QL query, run on an OSL
public server.
However, the first method is tedious, and for the second we cannot get
any performance guarantees.
This is why we would like a simple SnapToFeature function to be
available in Google Maps. I can imagine other customers of yours would
be interested in snapping to waterways, footpaths, borders, etc.
Thank you,
with kind regards,
Joeri Spitaels
thx for picking this up again.
Yes we are certainly still interested: we are developing a tracking
device for freight wagons.
This device sends the approximate coordinates of the vehicle to our server.
The server then snaps these coordinates to the nearest railway, so we
can pinpoint the wagon on its exact railway track. (This is often
called "map matching".)
Right now we have 2 ways to do this:
One works with Here maps, and involves setting all the railways in the
vicinity of the tracker as a geo fence, and then checking which geo
fence is closest.
The other method works with OpenStreetMaps, where we just recover the
railway segment closest to the tracker with a QL query, run on an OSL
public server.
However, the first method is tedious, and for the second we cannot get
any performance guarantees.
This is why we would like a simple SnapToFeature function to be
available in Google Maps. I can imagine other customers of yours would
be interested in snapping to waterways, footpaths, borders, etc.
Thank you,
with kind regards,
Joeri Spitaels
je...@google.com <je...@google.com> #4
Thanks for your suggestion!
We have passed the suggestion on to the product team for further consideration.
Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
We have passed the suggestion on to the product team for further consideration.
Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
in...@gmail.com <in...@gmail.com> #5
my API is not working properly
plz do something
plz do something
no...@icloud.com <no...@icloud.com> #6
Can this be brought up for consideration again? :)
This can serve a lot of purposes, whereas snapToRoads are only useful for cars.
This can serve a lot of purposes, whereas snapToRoads are only useful for cars.
ni...@gmail.com <ni...@gmail.com> #7
Also very interested.
Description