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
There will be users that will have data that uses existing identifiers from the various geographies (e.g. ASGS 2016 meshblocks). e.g. CSV table of population count for a set of meshblocks.
For users to use excelerator, they would need to have a column of Loc-I identifiers, which will need to be prepopulated somehow - manually or automated.
To ease this workflow, a locify tool would help prepare the data ready for excelerator (and other tools perhaps). Example workflow:
User uploads CSV file > 2. User selects which column has the identifiers > 3. User selects the spatial object and version (e.g. ASGS 2016 MB) > 4. User submits and gets a CSV returned with the first column having the Loc-I identifier.
Not sure if this belongs as part of the excelerator tools, but this issue is to explore a new feature that will allow users to locify their CSV data.
The text was updated successfully, but these errors were encountered:
There will be users that will have data that uses existing identifiers from the various geographies (e.g. ASGS 2016 meshblocks). e.g. CSV table of population count for a set of meshblocks.
For users to use excelerator, they would need to have a column of Loc-I identifiers, which will need to be prepopulated somehow - manually or automated.
To ease this workflow, a
locify
tool would help prepare the data ready for excelerator (and other tools perhaps). Example workflow:Not sure if this belongs as part of the excelerator tools, but this issue is to explore a new feature that will allow users to
locify
their CSV data.The text was updated successfully, but these errors were encountered: