From 7b57463b68f582b3b830a95382d781771dd009e0 Mon Sep 17 00:00:00 2001
From: "Wigal, Jacob (CIV)" <jacob.wigal@nps.edu>
Date: Wed, 20 May 2020 09:24:23 -0700
Subject: [PATCH] Update why_we_use_git_and_gitlab.ipynb
---
why_we_use_git_and_gitlab.ipynb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/why_we_use_git_and_gitlab.ipynb b/why_we_use_git_and_gitlab.ipynb
index 3988750..c296f7a 100644
--- a/why_we_use_git_and_gitlab.ipynb
+++ b/why_we_use_git_and_gitlab.ipynb
@@ -180,7 +180,7 @@
"<ul>\n",
"No. You should convert to GeoJSON. Besides, you can always convert back if you ever needed to!\n",
"<br>\n",
- "Also, unlike shape files which have dependent files (.shx, .dbf, .prj) at risk of getting misplaced or left untracked, with GeoJSON there is only one file to track (.geojson). GeoJSON files are just text, so we can visibly see any edits made to the files in GitLab as they are made. We can also easily manipulate the files using programming languages like Python or R! These are a few reasons we ask that any geospatial data you have be converted to GeoJSON before pushing it to the repository. Conversion is painless, and there is a Jupyter Notebook in this folder to help.\n",
+ "Also, unlike shape files which have dependent files (.shx, .dbf, .prj) at risk of getting misplaced or left untracked, with GeoJSON there is only one file to track (.geojson). GeoJSON files are just text, so we can visibly see any edits made to the files in GitLab as they are made. We can also easily manipulate the files using programming languages like Python or R! These are a few reasons we ask that any geospatial data you have be converted to GeoJSON before pushing it to the repository. Conversion is painless, and if you need help you can reach out to someone on the CID team for a conversion utility.\n",
"</font>"
]
},
--
GitLab