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
Just talked Alden through the new RME output format (i.e. flattened IGO and DGO tables). We agreed that people want these data in other analysis packages and the easiest way to do this is via CSV. I walked him through exporting the IGO attribute table to CSV and opening it in Excel. It worked. He liked it.
We could document this workflow, but we could also just include the CSV in the RME outputs folder, given that it's going to be extremely useful for folks who want to take the data and perform their own (non-GIS) analysis.
Task
Include the IGO attribute table (with IGO point lat and long as columns) as a CSV in the RME outputs. Make sure this gets referenced in the RME project file and also in the business logic.
Just talked Alden through the new RME output format (i.e. flattened IGO and DGO tables). We agreed that people want these data in other analysis packages and the easiest way to do this is via CSV. I walked him through exporting the IGO attribute table to CSV and opening it in Excel. It worked. He liked it.
We could document this workflow, but we could also just include the CSV in the RME outputs folder, given that it's going to be extremely useful for folks who want to take the data and perform their own (non-GIS) analysis.
Task
Include the IGO attribute table (with IGO point lat and long as columns) as a CSV in the RME outputs. Make sure this gets referenced in the RME project file and also in the business logic.
FYI @jtgilbert @joewheaton
The text was updated successfully, but these errors were encountered: