merge script should merge direct to topojson if not boundary changes #34

New issue

Closed

opened 2021-01-26 07:36:33 +11:00 by hughrun · 1 comment

hughrun commented

2021-01-26 07:36:33 +11:00

(Migrated from github.com)

Merging changes from library_services.csv directly into the topoJSON file is the most likely workflow needed: once initial data mistakes settle, boundary changes will be unusual (e.g. demergers or mergers of library networks).

TODO as part of this:

titlecase all library names inlibrary_services_information.csv so we can match directly
rename short_name to just name in the CSV so we don't have a superfluous attribute
get rid of the empty attribute at the end that is also taking up space for no reason (presumably this is a blank column in the CSV)
create Action to automatically update the topoJSON when there is a successful PR (see #18)

Merging changes from `library_services.csv` directly into the topoJSON file is the most likely workflow needed: once initial data mistakes settle, boundary changes will be unusual (e.g. demergers or mergers of library networks). TODO as part of this: 1. titlecase all library names in`library_services_information.csv` so we can match directly 2. rename `short_name` to just `name` in the CSV so we don't have a superfluous attribute 3. get rid of the empty attribute at the end that is also taking up space for no reason (presumably this is a blank column in the CSV) 4. create Action to automatically update the topoJSON when there is a successful PR (see #18)

hughrun commented

2021-01-26 17:49:49 +11:00

(Migrated from github.com)

Done!