You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -213,7 +213,7 @@ To update database dump files (with the `.pgdump` extension), do the following:
213
213
214
214
## Regenerating infraLinks.sql
215
215
216
-
After updating dump file for the network & routes database, you may consider updating the seed data for infrastructure links which is located at `./test-db-manager/src/dumps/infraLinks/infraLinks.sql`.
216
+
After updating dump file for the network & routes database, you may consider updating the seed data for infrastructure links which is located in azure blob storage stjore4dev001's jore4-dump container. Download with `scripts/development.sh infralink:download`, after which the file is at `./infraLinks.sql`.
217
217
218
218
To do that:
219
219
@@ -226,6 +226,7 @@ To do that:
226
226
COPY infrastructure_network.infrastructure_link (infrastructure_link_id, direction, shape, estimated_length_in_metres, external_link_id, external_link_source) FROM stdin;
227
227
```
228
228
- Copy the command and the immediately following rows of data (over 150 000 rows in total) and replace the same command in the `infraLinks.sql` file to update infrastructure seed data. Make sure you only copy infrastructure link data!
229
+
- upload the infraLinks.sql to azure (stjore4dev001's jore4-dump container) and update the location to development.sh (INFRALINKS_FILENAME constant).
0 commit comments