|
POST
|
The order of the road class in the map supports cartographic display and does not imply a hierarchy. Its designed to support the map. The domain in the information model closely matches the functional classification of roads as adapted from the FHWA.
... View more
06-13-2013
09:19 AM
|
0
|
0
|
1668
|
|
POST
|
I would encourage you to start with the maps and layers required for each editing map or application, then use the map dictionaries to determine which feature classes and tables are required in the underlying local government information model. The map dictionaries will also indicate whether map joins are used, or whether actual geodatabase relationship classes are used. The Data Dictionary provided with the information model provides additional detail on each feature class, relationship class, etc. To address the specific questions about the _Attach tables in the GDB. These are system defined tables for features that have geodatabase attachments (photos, videos, etc.) enabled. From a schema perspective, you don't need to worry about these. The FacilitySite features are modeled in a consolidated way because these features are used in a variety of applications throughout local government and a simple flexible design is necessary for an enterprise implementation. We have also found that many of the attributes for the core features (government buildings, parks, schools, etc.) are the same; and the detailed characteristics for each of these features (park services, hours of operation, contact information, etc.) can be maintained independently and then related to the features in a focused map or application. So in summary, don't start with the data model and the details within. Start with the maps and apps and then work your way back in to the specific features in the information model. Here is more information that may be helpful.
... View more
06-13-2013
09:11 AM
|
0
|
0
|
867
|
|
POST
|
Thanks for starting this thread gang. Please feel free to use the ArcGIS Ideas site to log major enhancements you'd like to see as well.
... View more
06-13-2013
08:43 AM
|
1
|
0
|
1712
|
|
POST
|
Michele - One more note, here is an example of how the City of Southfield, MI did a similar thing. They used the campus features in the local government information model and the campus place finder to deliver this service to citizens in their community. Scott
... View more
06-13-2013
08:39 AM
|
0
|
0
|
1133
|
|
POST
|
Yes, you can define how the spaces are used either by using the space name or by adding a series of extended attributes to organize how the space is used.
... View more
06-13-2013
08:36 AM
|
0
|
0
|
1133
|
|
POST
|
The behavior of the attribute assistant can be configured by interacting with the Dynamic Value table and the rules within it. Here is a link to the help that describes how to do this in more detail.
... View more
06-13-2013
08:31 AM
|
0
|
0
|
494
|
|
POST
|
David - This is most likely related to the initial extent you have set for the app. The extents behave differently on phones than then do in desktop browsers because of the pixel resolutions and screen sizes. The best solution right now is to shrink the size of your browser to essentially the size of a smartphone and then use the extent helper to grab the coordinate values for your community. Scott
... View more
04-26-2013
04:37 AM
|
0
|
0
|
527
|
|
POST
|
David - I would contact Esri Support Services to get help with this specific issue. They can help you troubleshoot the issue more deeply. One quick check - I would assume you're trying to add the parcels as a dynamic service in the operational layers area of the config?And I assume you're service is in the same projection as your basemaps, etc.? Scott
... View more
04-26-2013
04:32 AM
|
0
|
0
|
1979
|
|
POST
|
Just want to add some clarity to Ryan's comments. Signals are actually in a standalone table that is related to a single Pole feature class with a map join in ArcMap. You'll want to take a look at this design and then think about your deployment approach - I did a recent forum post about sign inspections that may be applicable to your deployment. Crosswalk striping may also be mapped in the PavementMarkingLine feature class. Scott
... View more
04-26-2013
04:20 AM
|
0
|
0
|
947
|
|
POST
|
Just to add to post here - the GitHub repositories only have the app source code in them. The AGOL items contain the entire download (maps, geodatabase, app) for each map and app.
... View more
04-26-2013
04:15 AM
|
0
|
0
|
659
|
|
POST
|
Matt - Did you configure your webmap as we outlined in the help? Scott
... View more
04-26-2013
04:13 AM
|
0
|
0
|
491
|
|
POST
|
Brian - There is a bug right now with attachments that precludes the schema from being copied to Oracle without error. As such, we're shortening several feature class names in the 10.2 release so users don't run in to this bug. In the meantime, I would track down any feature class/table in your schema that may be longer than 30 characters (including the _ATTACH and _ATTACHREL extensions). I know I made changes to the landusecodeviolation and damageassessment features in the 10.2 version to accommodate. Scott
... View more
04-26-2013
04:11 AM
|
0
|
0
|
1113
|
|
POST
|
We removed the physical geodatabase relationships between poles and signs because we're relating multiple tables (signs, lights, signals) in the geodatabase to a single pole feature class. As such, we'd instead suggest you do a map join in ArcMap before you publish the service so you don't see all three features (signals, signs, and lights) in your service. If you're interested in using AGOL and the Collector to tackle a sign inventory project, you'll have to flatten out the structure a bit more and essentially collapse the pole feature class and sign table in to a single Sign feature class. The Collector app does not support related tables at this time. This workflow will work really well for your sign inventory, but won't help you with subsequent inspection workflows. The best solution right now if you want to use AGOL and the Collector app for ongoing inspections is to create a SignInspection feature class and capture point features for each inspection activity. Scott
... View more
04-26-2013
04:01 AM
|
0
|
0
|
2118
|
|
POST
|
Merek - The stormwater features in the current release of the local government information model represents a basic implementation of a storm water network. Our focus initially was on the water and sewer network and over time, we continue to evolve the stormwater features to meet the needs of the community. For example, a county in FL gave us some good feedback this spring and we incorporated weirs and other stormwater features in the next release. If you're willing to share your current model (features / domains) with us, we'll take a closer look and see how we can help meet the UIC needs. Feel free to send it directly to me - soppmann@esri.com. Thanks Scott
... View more
04-26-2013
03:51 AM
|
0
|
1
|
1015
|
|
POST
|
Kevin - Here is a link that will help you set the spatial reference properly for the local government information model. Scott
... View more
04-09-2013
11:23 AM
|
0
|
0
|
924
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 02-09-2026 08:43 AM | |
| 1 | 12-22-2025 06:52 AM | |
| 2 | 06-26-2025 04:17 AM | |
| 2 | 06-24-2025 05:57 AM | |
| 1 | 06-18-2025 11:10 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|