I recently started working for a small municipality that has an opensource web map created from SDF files, but uses Arcmap as well when needed. I was recently hired to help transition the GIS to industry standards, but am struggling to game plan for the best route to take. We are currently exploring the options to either get an Esri Enterprise account and set up ArcGIS Server, or just transition to using ArcGIS Online and having local .mxd document to maintain and update. I have downloaded the Local Government Information Model and am wanting to import our shapefiles into this model, but as the formatting of some of the data is inconsistent, I am wondering the best way to go about this. I am looking for advice regarding a starting point for importing existing data into the Local Government Information Model and establishing consistent data standards, and eventually publishing this data as a web map. Do I need an enterprise account and ArcSDE before I can do this successfully? Can anyone help with a starting point for this? Thanks!
Solved! Go to Solution.
Ahhh... A data standards thread. As I usually say, "The thing about standards is there are so many to choose from..."
I was hired by a county to examine the use of the LGIM and it's okay, but trying to stuff an incrediably broad range of data and data-uses into a one-size fits all model isn't just challenging, it's pretty much next to impossible. Hence my opening quote.
On the other hand, LGIM may be Heaven sent in your case. How data-rich and mature is your organization? Are there established workflows that experienced GIS analysts have used and would like to continue to use? Do you share data with other agencies or obtain data from agencies? If so, what model or standards are used?
It sounds more like your situation could use a standard and since the LGIM is avaialble, why not use it? Consider also that you can use the LGIM as guide rather than a hard-fast model. Use the components that work for you, and disregard those that don't. There are number of ESRI tools that were developed to dovetail into the LGIM, so consider them as well.
As far as migrating your exisiting data into the LGIM or any other model: take your time. Examine your absolute bare bones needs, add what-ever fluff would be nice and then build or use a cross-walk like the Simple Data Loader or the Append tool that map your existing fields to the target feature class.
Echoing what Joe said, the LGIM is a great starting point. If the data you currently have is in terrible shape, the LGIM is a good place to go. I did a similar thing with my current organization (transitioning from multiple copies of the same data, all with different levels and qualities of attribution) to the LGIM. The task was not easy and took quite a bit of time.
To manage the task, I made a series of Excel spreadsheets showing the schema of each layer in the LGIM. For layers we were planning on using, I placed that schema along side the LGIM schema and drew lines from our existing fields to the LGIM fields. That way, when I was working on the project and got interrupted, I'd know where I was, what I was doing, and where to go back to when I had free time again. I'm happy to share those spreadsheets with you.
Since this time, I've appended/added to the LGIM to work better for our organization in terms of additional columns in some layers as well as additional layers.
Also, downloading the sample data from Naperville really helped me understand what sort of data went into each layer and how the data is used by other LGIM products. That would be a great starting point.
It would be really nice if the LGIM was still published as a complete data model that could be examined in a geodatabase, even as more components shift to AGOL-only. The Solutions Deployment Tool in Pro works really well if you don't have to modify the table schema and don't have existing data to contend with. However, it is easier to use a geodatabase as a reference if you have large amounts of schema changes and/or legacy data to import...At least until I learn more about the data management tools in Pro (or as more tools are developed).
Here is a quick example of a dilemma I recently encountered with the Solutions Deployment tool as compared to using the local GDB schema:
We have been using the LGIM model as a starting point for most new layers. That said, many of the new solutions are simply using the modern Esri COTS apps (Collector, Explorer, Web AppBuilder, etc) rather than the individual custom web apps / MXDs that were used when the LGIM was started. Therefore I can see why the underlying data model is less important. But we would still find the full LGIM model useful, provided we can easily decipher their design in a geodatabase.
It would be really nice if the LGIM was still published as a complete data model that could be examined in a geodatabase
This download is current as of March 2017. It includes the model as an XML document that you can import to a fGDB.