פרילנסר /ית להתאמת כתובות למסלול נסיעה
פרויקט מס' 203546
Job Statistics
11 Bids |
תקציב
עד 2,500 ₪
|
תוקף הפרויקט
3
ימים,
6
שעות,
7
דקות
|
טווח הצעות
110
₪
-
420
₪
לשעת עבודה
|
הצעה ממוצעת
230
₪
לשעת עבודה
|
Job Info And Actions
תאריך פרסום:
09:28, 6 מרץ, 2025
הצעות תתקבלנה עד:
08:39, 25 אפריל, 2025
פרילנסר /ית להתאמת כתובות למסלול נסיעה
תיאור העבודה כתבתי באנגלית:
Hi, I have a new task for you:
My technologies are mainly react native, node.js, mongodb
I need you to create for me 2 screens:
screen 1:
. A component called "Save Addresses" where you can:
Enter a starting address and a destination address (via Google Maps AutoComplete) and two save buttons, one called "Send as Driver" and a second button called "Send as Customer" which saves the two coordinates of the addresses in mongodb (via node.js).
And also saves the route between the two points. (The route should be done by API with OSM so that I don't have to pay Google for each route creation and also find a way that I can send a lot of API calls to OSM without getting blocked when I have a lot of calls from many users)
screen 2:
Component 2 is called "Find Customers for Driver":
In this component, I see all the pairs of addresses saved as "Send as Driver" and when I click on one of them I get a list of all the address pairs that match the route saved as "Send as Customer".
There are 7 levels of matching of customer addresses with the driver:
Let's say the driver's starting address is "Point A" and the driver's destination address is "Point B":
Level 1:
The customer's point A and point B are within a radius of 500 meters of the driver's two points.
Level 2:
The customer's point A and point B are within a radius of 1 kilometer of the driver's two points.
Level 3:
The customer's point A and point B are within a 5 km radius of the driver's two points - "and are" in the same city name as the city names in the driver's two points.
Level 4:
The customer's point A and point B are within a 5 km radius of the driver's two points - "and are not" in the same city name as the city names in the driver's two points.
Level 5:
The customer's point A and point B are in the same city name as the city names in the driver's two points.
Level 6:
The customer's point A and point B are along the entire length of the driver's route.
Level 7:
The customer's point A and point B are along the entire length of the driver's route but are not directly on the route but within a 10 km radius of the entire route.
Important point:
It goes without saying that the driver's starting point A should always be near the customer's starting point A - and the driver's starting point B should always be near the customer's starting point B.
And what I mean by this is that even if (as in level 7) there is a large distance between the driver's point A and the customer's point A and the driver's point B and the customer's point B - the customer's route direction from A to B will still be the same as the driver's "direction" from A to B. So that the driver can receive more customer work "on the go on his current route".
Hi, I have a new task for you:
My technologies are mainly react native, node.js, mongodb
I need you to create for me 2 screens:
screen 1:
. A component called "Save Addresses" where you can:
Enter a starting address and a destination address (via Google Maps AutoComplete) and two save buttons, one called "Send as Driver" and a second button called "Send as Customer" which saves the two coordinates of the addresses in mongodb (via node.js).
And also saves the route between the two points. (The route should be done by API with OSM so that I don't have to pay Google for each route creation and also find a way that I can send a lot of API calls to OSM without getting blocked when I have a lot of calls from many users)
screen 2:
Component 2 is called "Find Customers for Driver":
In this component, I see all the pairs of addresses saved as "Send as Driver" and when I click on one of them I get a list of all the address pairs that match the route saved as "Send as Customer".
There are 7 levels of matching of customer addresses with the driver:
Let's say the driver's starting address is "Point A" and the driver's destination address is "Point B":
Level 1:
The customer's point A and point B are within a radius of 500 meters of the driver's two points.
Level 2:
The customer's point A and point B are within a radius of 1 kilometer of the driver's two points.
Level 3:
The customer's point A and point B are within a 5 km radius of the driver's two points - "and are" in the same city name as the city names in the driver's two points.
Level 4:
The customer's point A and point B are within a 5 km radius of the driver's two points - "and are not" in the same city name as the city names in the driver's two points.
Level 5:
The customer's point A and point B are in the same city name as the city names in the driver's two points.
Level 6:
The customer's point A and point B are along the entire length of the driver's route.
Level 7:
The customer's point A and point B are along the entire length of the driver's route but are not directly on the route but within a 10 km radius of the entire route.
Important point:
It goes without saying that the driver's starting point A should always be near the customer's starting point A - and the driver's starting point B should always be near the customer's starting point B.
And what I mean by this is that even if (as in level 7) there is a large distance between the driver's point A and the customer's point A and the driver's point B and the customer's point B - the customer's route direction from A to B will still be the same as the driver's "direction" from A to B. So that the driver can receive more customer work "on the go on his current route".
תחומי הפרויקט
קבצי הפרויקט
אנא היכנס לאתר לקבלת גישה לקבצי הפרויקט
הלקוח
אנא
היכנס לאתר
לקבלת גישה ללקוח
עדכונים
אנא היכנס לאתר לקבלת גישה לעדכונים בפרויקט
Private Bid
0 פרויקטים
|
|
Private Bid
0 פרויקטים
|
|
Private Bid
0 פרויקטים
|
|
Private Bid
0 פרויקטים
|
|
Private Bid
26 פרויקטים
|
|