Requirement
An option disable the geocode / reverse geocode requests being sent to https://nominatim.openstreetmap.org every time we pin / move markers on the frontend interface and a route is plotted.
Reasons / Motivations:
-
Don't want to put unnecessary load on the openstreetmap core server; want to do our bit in helping the community by at least not unnecessarily adding burden to the servers.
-
Target users need to see lat-longs of manually pinned locations and copy-paste them in a convenient way; cannot expect them to figure out and decode from the complicated URL.
-
Company policy requires prior approvals for all egress destinations from the company's servers; pings to uninvolved 3rd parties like nominatim.openstreetmap.org every time the application is used cannot be justified and might get flagged by securty/audit folks. Blocking them non-elegantly causes error messages, bad UX in the application.
Requirement
An option disable the geocode / reverse geocode requests being sent to https://nominatim.openstreetmap.org every time we pin / move markers on the frontend interface and a route is plotted.
Reasons / Motivations:
Don't want to put unnecessary load on the openstreetmap core server; want to do our bit in helping the community by at least not unnecessarily adding burden to the servers.
Target users need to see lat-longs of manually pinned locations and copy-paste them in a convenient way; cannot expect them to figure out and decode from the complicated URL.
Company policy requires prior approvals for all egress destinations from the company's servers; pings to uninvolved 3rd parties like nominatim.openstreetmap.org every time the application is used cannot be justified and might get flagged by securty/audit folks. Blocking them non-elegantly causes error messages, bad UX in the application.