-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with self-hosted server connection #123
Comments
Hello, I'm AFK right now, I'll have a look at it in early September. |
Hi, curl "<server-ip>:5111/route/v1/foot/40.6476940,-73.9803640;40.6551440,-74.0035490?steps=true" Thank you for your help, |
Ok thanks, library(osrm)
osrmRoute(src = c(-73.9803640, 40.6476940), dst = c(-74.0035490, 40.6551440),
osrm.server = "http://192.168.1.16:5111/",
osrm.profile = "foot") |
Hi,
Thanks for the response.
No, it did not work ad returned this error:
Error: Error in curl::curl_fetch_memory(utils::URLencode(url), handle = req_handle) :
URL using bad/illegal format or missing URL
September 5, 2023 3:53 AM, "Timothée Giraud" ***@***.*** ***@***.******@***.***>)> wrote:
Ok thanks,
Does this snippet work ?
library(osrm) osrmRoute(src = c(-73.9803640, 40.6476940), dst = c(-74.0035490, 40.6551440), osrm.server = "http://192.168.1.16:5111 (http://192.168.1.16:5111/)", osrm.profile = "foot")
—
Reply to this email directly, view it on GitHub (#123 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ACXN4CQ3UP4AMEP32IGJGZLXY3LBHANCNFSM6AAAAAA3UACKCA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
That said, when I input {"message":"URL string malformed close to position 1: \"\/\"","code":"InvalidUrl"} And yet I am positive that is the address on which OSRM is published. Here is the version: "3"
services:
osrm-backend:
image: osrm/osrm-backend:latest
container_name: rte
restart: unless-stopped
command: "osrm-routed --algorithm mld /data/nyc.osrm"
volumes:
- "/mnt/sam/cch/rte:/data"
ports:
- 5111:5000
labels:
- com.centurylinklabs.watchtower.enable=true And the container's log shows no error. |
This message is returned by OSRM, so it's OK. OSRM is published and accessible at this address... Anyway the problem does not seem to be linked specifically to |
hey there,
each time. what's weird is this:
when in reality those should be (when I use the online routing server)
similarly:
always returns zero distance. the API seems to run correctly:
|
oh no, just realised that the API is returning zero distance all the time! so that's the problem here... |
nevermind, I reconfigured the package in a new location and on a new openstreetmap, now it works. strangely only the R package works, the curl calls always return zero distance... |
Hi @asitemade4u , |
Hi, |
Hi,
I have issues executing
osrm::osrmNearest
with my self-hosted OSRM server.Here are the details:
5111
as it was colliding with another of my self-hosted servers.Nevertheless, it works fine and responds to a
curl
to its local IP address (192.168.1.16:5111
) such as:curl "192.168.1.16:5111/route/v1/foot/40.6476940,-73.9803640;40.6551440,-74.0035490?steps=true"
I assume the OSRM API responds well then.
docker-compose.yml
file.osrm
plugin in R. My R installation is also served by a self-hosted server using CodeServer -- and works just fine./
).curl
instruction from thebash
terminal of my R coding environment and it returned a correct result. So I assume I can connect to the API from my development environment, from where the below code is executed.thetmp
thetmp
into asf
geometry usingsf::st_as_sf
: the columnthetmp$geometry
replaces the two coordinate columns, as a result.thetmp
dataframe and add nearest coordinates of each trackpoint into a new column to the dataframe,thetmp$new
:new
dataframe column is always the same, and obviously not what I was expecting:What am I doing wrong?
S.
PS1. I also tried to prefix the server address with
http://
but it yields the same result.PS2. Nous pouvons communiquer en Français si cela est plus facile pour vous, car je suis un compatriote vivant aux US. ;o))
The text was updated successfully, but these errors were encountered: