helper function for_loc._udp useful for browser UI to resolve & connect to service to display single map points.
should map URL schema to geo: (note no forward slashes)
take coords from LOC RR lat & long attributes, geo:25.245470718844146,51.45400942457904
this well known mapping will work for any browser on any platform that has a schema handler defined for geo:
mobile phones (android & ios) auto-associate this with their map apps (gmaps, open street maps)
example: geo:25.245470718844146,51.45400942457904
For any browsing domain that wishes to define one or more _loc._udp service type instances, a PTR record of (eg)
_services._dns-sd._udp. PTR _loc._udp.
must exist.
For any browsing domain that has has no _loc._tcp service types existing or last remaining has been deleted, then PTR record of
_services._dns-sd._udp. PTR _loc._tcp.
should be deleted.
this is useful for example in browser rendering single map points.
helper function for_loc._udp useful for browser UI to resolve & connect to service to display single map points.
should map URL schema to geo: (note no forward slashes) take coords from LOC RR lat & long attributes, geo:25.245470718844146,51.45400942457904
this well known mapping will work for any browser on any platform that has a schema handler defined for geo: mobile phones (android & ios) auto-associate this with their map apps (gmaps, open street maps)
example: geo:25.245470718844146,51.45400942457904
For any browsing domain that wishes to define one or more _loc._udp service type instances, a PTR record of (eg)
_services._dns-sd._udp. PTR _loc._udp.must exist.
For any browsing domain that has has no _loc._tcp service types existing or last remaining has been deleted, then PTR record of
_services._dns-sd._udp. PTR _loc._tcp.should be deleted.
this is useful for example in browser rendering single map points.