In the example links on https://comaps.at/api
https://comaps.at/map?v=1&ll=22.17319,-159.65687&n=Kalalau%20Camping&ll=22.17168,-159.66096&n=Dream%20Beach&ll=22.17182,-159.65776
But it opens in the middle of the ocean (a default) and with no name.
In the example links on https://comaps.at/api
https://comaps.at/map?v=1&ll=22.17319,-159.65687&n=Kalalau%20Camping&ll=22.17168,-159.66096&n=Dream%20Beach&ll=22.17182,-159.65776
But it opens in the middle of the ocean (a default) and with no name.
On omaps.app/api it doesn't work either
Same with route: https://comaps.at/route?v=1&sll=50.183933,8.942871&saddr=Start%20Point&dll=49.998912,8.278198&daddr=EndPoint&type=vehicle
I think this is an upstream issue. It looks like the "api" is only really implemented in the mobile app itself, and not on the web, as keywords like "saddr" and "route" and "dll" simply don't exist in the url-processor source code: https://omaps.app/route?sll=50.183933,8.942871&saddr=Start%20Point&dll=49.998912,8.278198&daddr=EndPoint&type=vehicle
There have been some proposals to replace url-processor with some web services, like #16 -- I wonder if that's a better idea, especially if one of them is easily self hostable, or is hosted by an aligned organization we could partner with.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?