POST
|
USE KHUB SELECT [ActivityType], count([ObjectId]) as Edits FROM [RH].[LRS_EDIT_LOG_evw] WHERE TransactionDate BETWEEN '1/1/2020' AND '1/1/2021' group by ActivityType order by ActivityType 1 930 2 649 3 489 4 793 5 433 6 1003 7 534 12 24
... View more
2 weeks ago
|
2
|
0
|
13
|
POST
|
Good idea. To do this you will want to track edit changes and ensure your portal group security is working with the change tracking, and yes protect your default and manage LRS Locks in event editor with a lockroot subversion from default and conflict prevention enabled in the ALRS Settings. I would configure event editor applicatons, secured and delivered to members assigned to portal groups, and customize the cartographic content to facilitate the workflow to the maximum extent possible. Also configure the event editor with full ability of the editor to create a version, post and reconcile, manage locks, and delete a version all with event editor buttons. What I do is publish the services with a shared user that is only used for publishing services, not a data owner user or an active directory user but a named user in the database with privileges set for editing event data in versions. I think in a multi-user environment you would definitely want to have at least a version per user, sometimes more depending on the situation and the number of EE configurations you set up. It is possible to configure event editor using portal maps that can combine read-only services with the ALRS service, but snapping in the Event Editor might not work on those non-alrs services. You can also probably add read-only connections when publishing the service to enable the reference layers to support snapping, maybe. For our installation it was difficult to get the federated portal all set exactly how it had to be for ADFS users and conflict prevention to work but now that we have that figured out I wouldn't want to do it any other way, and it appears this approach is going to work well to achieve your goal, and mine too, of supporting program areas in such a way that they can utilize the event editor and spread the workload horizontally into the agency.
... View more
09-24-2020
03:59 PM
|
1
|
0
|
146
|
POST
|
Shawn recently developed a geocoder based on the route concurrency table, so that concurrency route segments can be geocoded as intersections. We are also ironing out the process of maintianing GIS refposts in a hosted feature dataset (facilitating easy Collector/Quick Capture app access) and locating those features to the refpost control state LRM routes as events for geocoding and offsetting. here are the ingredients we use ON_ROAD/Route AT_ROAD/Milepost OFFSET DIRECTION here is the formula: 1. Geocode ON/AT roads as intersections using esri geocoder 2. Obtain Projected XY Coordinate 3. Buffer the point in by offset distance 4. Intersect the buffer outline to the road centerline segments as points 5. In SQL, query the matching ON road (standardized) to the centerline segment road name. CASE Select coordinate directions from DIRECTION (ie N, E, S, W, NE etc) and RANK the offset coordinates so that you are selecting the most "east" of the intersected points, or keep the intersection if it is the most east. I'll try to find some actual SQL that does the offsetting. With this method we can locate a few hundred thousand crash records in about a workday.
... View more
06-25-2020
08:41 AM
|
0
|
0
|
70
|
POST
|
You end up with a lot of potential options. To update everything you could end date everything and start sate new records Later than the end date of the last thing. Some of the Esri feature service and app capabilities let you play data through time using this sort of method, so you can see changes in conditions or measurements over time. It gets complex when you compare multiple "related" historical things, were they always related? What if somebody finds a record from the past that should have been a different value? You can deal with all this but you have to organize virtual history, real history, and reconcile why things changed over time, and how actual changes factor in to predictive analytics vs virtual changes. An example we deal with a lot is crashes at an intersection, then the intersection is improved, then the factors contributing to crashes can really change significantly because of real changes. Say we change the name of the highway at the intersection, that doesnt change the actual history, just the relationship of the history to what the name was at the time vs now.
... View more
06-13-2020
02:19 PM
|
1
|
0
|
57
|
POST
|
start date and end date fields. For collection and data entry we might interact with those date fields. For mapping use we might publish a layer with a current date query, most data reviewers want a simple current status. Playing with date fields let's you know more but adds a lot of complexity. Also we use a more static ID than the object ID field if possible.
... View more
06-13-2020
09:52 AM
|
1
|
2
|
57
|
IDEA
|
I just discovered the scale bar does not have an easy option for displaying Nautical Miles like it does for feet, miles, kilometers, etc. Very disappointing!
... View more
05-12-2020
04:08 PM
|
0
|
0
|
62
|
POST
|
also commented out here is a half baked process to derive a statewide state highway network from the county network. I think we are working on altering the approach we are taking at that, but the process can be added with just a few additional steps in this process if those steps are done in just the right sequence. I think we currently are ironing out our expectations and requirements for the data of this derivation process to serve interfaces, and we are thinking of adding an event to maintain the state network history as derived from the county network.
... View more
05-05-2020
10:27 AM
|
0
|
0
|
54
|
POST
|
I wanted to share an update to our scripted process, now we have included a point event for flagging opposite directions of inventory primary routes on dual carriagway. By putting the event flag on the real primary noninventory route side, we then adjust the route concurrency table on the segment we flag, overriding the default concurrency rules that would have the inventory direction in both directions across the right of way for two different routes. An example of this in KAnsas is where US54 intersects US69 and they run opposite on dual carrigway north of Fort Scott Kansas. For us, US54 is the primary inventory route, so we flag US54 non inventory and alter US69 inventory to turn into US54 noninventory. rather than paste all that code again, here is a link to the code on github: pydev106/GeodbMaintenanceQC.py at master · KDOTGIS/pydev106 · GitHub another important step I want to point out in our proess is this other script to copy metadata updates beween dev, test, prod, transactional, and publiction environments, pydev106/CopyMetadata.py at master · KDOTGIS/pydev106 · GitHub
... View more
05-05-2020
10:20 AM
|
0
|
1
|
54
|
POST
|
1. we see undesired segmentation in the primary routes process when this tool fails. Amit describes it perfectly in his post. In our system, we encounter his Example #2 - we can find it when we run route concurrency and inspect that table for overlaps. For events problems, I suppose you could have trouble ensuring that events are recorded to the primary route. 2. if routes are appended to overwrite existing routes and the geometries are slightly different and not overlapping within tolerance, unexpected results can occur. It might be more time consuming to clean that up than to take time to do extensive hands-on edits. 3. I think it involves zooming in to XY tolerance levels and making minor edits to achieve precise geometry overlap. 4. no time is really any safer than another time. If you are running it for the first time then a good time is when you have some time to edit routes, troubleshoot, and somehow fix the situations. 5. the thing we check most often is if the segment route length equals the segment shape length. We have Data Reviewer so we can run non-monotonic checks I think? Kevin, I will chat with a couple of my editors today and try to clarify some of these responses.
... View more
04-21-2020
07:00 AM
|
0
|
0
|
86
|
Online Status |
Offline
|
Date Last Visited |
Tuesday
|