From b30090d6e597ff8f9d7359d5b62a89e79067106c Mon Sep 17 00:00:00 2001 From: Rick Hays Date: Wed, 25 Sep 2019 20:55:29 -0500 Subject: [PATCH] Update 'README.md' Finished basic readme.md file for project. --- README.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8745c83..547a9ac 100644 --- a/README.md +++ b/README.md @@ -13,8 +13,8 @@ application. ### Business Requirements 1. The API will receive a latitude/longitude, using the provided list in pharmacies.csv the API will calculate the closest pharmacy to the input latitude/longitude. -2. The API will return the closest pharmacy (with name and address) in a consumable response packet. 3. The -API will include the distance (in miles) between the input latitude/longitude and the selected closest pharmacy +2. The API will return the closest pharmacy (with name and address) in a consumable response packet. +3. The API will include the distance (in miles) between the input latitude/longitude and the selected closest pharmacy in the response packet. @@ -38,3 +38,15 @@ create table pharmacies Longitude REAL not null ); ``` + +----- + +Call: https://rhays.us/Examples/RX_API_Call/RX.php?K=RLH1234&Latitude=39.1030&Longitude=-95.3222 + +This is a basic lookup system to find the closest pharmacy to a given Lat/Lon + +My assumptions: +1) No clear request for distance, options are drive distance or straight line distance, I chose: straight line distance. +2) No request trap errors, I added a few, validation, key check, request check, and a basic DB check. +3) Output was requested as a packet but not the type, so I just passed the requested data back as text and not JSON. +