Fixing type issue on unnamedFeature model

sdl60660 · Jan 6, 2022 · 68e9348 · 68e9348 · vercel · Jan 6, 2022
1 parent 9269237
commit 68e9348
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/name_server/src/models/unnamedFeature.js b/name_server/src/models/unnamedFeature.js
@@ -1,7 +1,7 @@
 const mongoose = require("mongoose");
 
 const unamedFeatureSchema = new mongoose.Schema({
-  nameid: {
+  levelpathid: {
     type: Number,
     required: true,
   },

diff --git a/src/components/utils/mapUtils.js b/src/components/utils/mapUtils.js
@@ -25,8 +25,6 @@ export const sendQueryData = async (lat, lng, startingSearch, query_error = fals
 };
 
 export const sendUnnamedFeatureData = async (startCoordinates, featureNames) => {
-  console.log({ featureNames });
-
   // Get list of unidentified, unique features
   const unidentifiedFeatures = featureNames
     .filter((d) => d.includes("Unidentified River "))
@@ -35,7 +33,7 @@ export const sendUnnamedFeatureData = async (startCoordinates, featureNames) =>
   console.log({ unidentifiedFeatures });
 
   const featureData = unidentifiedFeatures.map((feature) => ({
-    name_id: feature.split("Unidentified River ")[1],
+    levelpathid: Number(feature.split("Unidentified River ")[1]),
     current_name: feature,
     route_start: JSON.stringify(startCoordinates),
   }));