|
|
|
|
|
by tarotuser
1228 days ago
|
|
No, because any further details would highlight where I work and specifically what office. Lets just say the data intersection of: density and geocoding of users, density and location of office sites, travel time bands, and service level expectations all have a part in the final calculation. The data is either base layers imported, or calculated layers. There is no one "comprehensive layer" nor does that concept make sense. Different groups handle their own data. We import it in and use their data for our final result. (In fact, its the OSM approach of everything as 1 layer and tags everywhere is why a DB import and data handling is so obnoxious.) |
|
I worked in a GIS Lab with an ESRI endorsed all Arc stuff textbook author/instructor for a number years. Working on similar projects, for anything remotely complicated, I could implement anything he could do, with some python and PostGIS SQL, usually faster, and instantly reproducible.
ArcGIS is a crutch for people who can’t and aren’t willing to program. This goes for all data manipulation tools that aren’t focused on visualization.
If you have an ETL pipeline, probably best to get GIT involved.