4 ms·
Maybe they gave a simplified explanation of their service, but if all they do is parse the country code of a phone number to return the geocoordinates for the
by adamwk 4y ago
Maybe they gave a simplified explanation of their service, but if all they do is parse the country code of a phone number to return the geocoordinates for the center of that country then maybe just deprecate phone number inputs. I can’t think of why that’d be actual useful (a function that accepts a phone number country code and returns the center of the country’s geocoordinates) but if they have customers who use it direct them to input the country code directly
- fwlr 4y agoMy understanding is that the original issue was the YouTube tutorials used some other service to convert the country code of a phone number into a string of the country’s name and submitted just the country’s name, getting back a valid but useless geolocation. This new problem with ChatGPT is that it just writes code that submits a phone number to an api that expects a latitude and longitude and it explodes right away. I don’t think at any point the api had a call that accepts a phone number.
- squeaky-clean 4y agoThey don't do anything with phone numbers. You can give them lat/lng coordinates and get the address, or an address and get the coordinates. So "7 Carmine St, New York, NY 10014" will return "(40.7305290, -74.0020706)" and vice versa. There are youtube tutorials claiming you can do phone lookups using their service. What these youtube tutorials really do is use some other library to determine the country name from the phone number. Then they call the OpenCage geolocation API with the country name as the address input.