|
DOC
|
this list is from the old RHUG site google sheet, it would be good to enter each of these to an individual geonet "idea" and retire this list.
... View more
12-12-2018
02:42 PM
|
2
|
0
|
1537
|
|
DOC
|
Enhancement or Issue Description ESRI Ideas Link Initial Notes Notes Level of Effort Application* Completed Support for Alpha and related routes Support Alpha/Fish Route in Roads and Highways 10/26/16 Will: A single route with a gap is another viable workaround (in addition to spliting into two routes) for fish routes. R&H current supports Lollipop routes. Fish routes require significant development effort to accomodate the various R&H logic, processes. FHWA has indicated that gaps along routes are not acceptable for HPMS. Some DOT's reporting event measure issues using the single route workaround. Will is willing to follow up on these issues and believes R&H should support. There is currently an overarching issue including various types of routes: Alpha, Loop, Branch, Fish, Lollipop, etc. / NC - R&H does not support fish routes. ADOT currently limits bifurcations in it's route system. It would be interested in native support from Roads and Highways as it would allow some "real world" route geometries to be modeled. June 2017: Requires code level support in in all tiers of the software: Route editing, calibration, event editing, Product Team work is underway and targeted for 10.6 release. RHUG: Top Priority among High LOE for next release. Should also be supported at 10.5 (at least) through patch. Needed to meet FHWA HPMS requirements and support Agile integration. Very High ArcMap Better query capabilities are needed. In Select by Attributes the options are limited. i.e. Query a route where the FC is a certain value. Ability to run, save, load queries in Roads & Hwys - RCE NC: Advanced query capability needs to be native to the application, not per Esri's current design. June 2017: Esri understands this enhancement to involve the ability to query multiple fields across multiple event tables.RHUG: OH, NC, WV, NM, MN all cite as a high priority Medium RCE R&H Create Route tool - add a warning when creating physical gaps related idea: R&H - Concurrent Route Event omission from from Gap checks 10/26/16- Will: Low effort to check for this ahead of save. This enhancement is for routes as opposed to events. The 10.5 Data Reviewer functionality works on R&H events not routes. July 2017: Esri is targeting for 10.6 Low ArcMap Ability to change symbology in RCE 10/26/16 - Will: This is a medium level of effort. Possible in existing environment. ADOT - This is a must for ability for users to really be able to make informed decisions. No matter how much effort is put into trying to set layer symbology to appropriate needs prior to RCE map use since RCE is main editing environment (not just for display) it is incredibly limiting. Enhancements to add ArcGIS Professional capabilities to the web based editing in RCE detract from the effort for building an ArcGIS Professional Desktop experience to edit events. June 2017: Symbology changes may be made to web map directly from Event Edtior in 10.6. Updates may be made for point, line. polygon layers RHUG: Understand the benefit of focusing on ArcGIS Pro here. Will likely lower priority for current RCE environment. Medium RCE Don't reset the page on Data Grid back to 1 after saving changes (keep it on whatever page it was on) NC: Assumed that issue is referencing editing through the event attribute table. June 2017: Esri is targeting for 10.6. ? RCE Route Locking - Automate lock release upon delete version operation ADOT - If version which holds lock is deleted the lock is now useless. Auto clean up. June 2017: Product Team work underway and targeted for 10.6. Low ArcMap When domains are populated with a numeric value and have an associated text definition, we would like to see the definition when querying. Currently, the definition appears in the attribute table, but the numeric value appears when performing a select by attribute sql query. There is no way to determine the definition associated with each number. ODOT questions if this is an issue with how the domains were set up. ADOT - The concept of domain values is to normalize and simplify data input. It is very counterintuitive to ask the user to have full knowledge "memory" of all domain values in their system. June 2017: Esri Product Team would like to clarify the issue and where it is happening. Arizona indicated they would provide screenshots of the issue. Low ArcMap/RCE Make the table/grid undockable for a two screen experience June 2017: Esri is working to expand RCE browser to cover multiple screens creating more "real estate" for the application. High RCE Add definition query ability in RCE June 2017: Esri is looking at this enhancement for 10.6 Medium RCE Support for making edits on a route in non sequential order (i.e. perform an edit on a route effective November then later on perform an edit on the same route effective May) ADOT - this limitation of Roads and Highways essentially removes much of the temporal abilities of the product. It is not realistic to expect that all editing of events/LRS can be done in perfect chronological order nor is it realistic to expect the user of the system to wade through time to ensure proper integration of data out of sequence. Add more flexibility with editing the effective date of a route in case it doesn’t work with another system/user (i.e. we make a change on a given date, someone else who uses the network needs the date changed earlier or later than we have it input). Provide the capability to change the date forward or backward without retiring and redoing the entire edit or reloading data RHUG: Workflow/business process changes have been used to address this in implementing states but a fix remains an important priority High ArcMap GP Tool to establish a new event layer on the R&H ALRS Register Event Feature class GP Tool This would allow event layers to be created through scripts. Kansas DOT ArcGIS Integration with vendor neutral street level imagery (eg. Google StreetView, Cyclomedia) Many DOTs are licensed for and have access to commercial street-level imagery (like Google Street View, Cyclomedia and others). RCE should provide easy integration capabilities to allow for users to update the config file to enable and view interactive street-level imagery that connects to RCE. Below are a few of the functions we are interested in: • As routes are queried/identified, this communicates changes of RCE location to imagery viewer, allowing it to update its imagery/perspective. • Functionality that communicates changes of RCE location to imagery viewer, allowing it to update the imagery/perspective. • Provide functionality to overlay a semi-transparent view cone to indicate imagery viewer direction. District of Columbia RCE "Cover" event behavior 10/26/16- Idaho DOT highlighted this issue as having a large impact on event QA/QC processes. Existing workarounds do not work for external events and there was general consensus that adding the "cover" behavior would be a be time saver for managing continuous events. Several DOTADOT - this "cover" behavior should closely mimic the behavior already in place for cartographic realignments. MN: What is your definition of "cover"? NC: Move behavior can leave little gaps when it's supposed to be full coverage- Cover would ensure full coverage of the event after the edit. June 2017: As planned, "Cover" behavior would apply Realign and Extend route edits. Realign stretchs or compresses events on the realigned portion propotionally. Extend from beginning would use the event at the start measure to cover. Extend from the end would use the event from the end meaure to cover. Behaavoir will honor concurrency rules. Product Team work is underway and targeted for 10.6 release. High ArcMap Implemented at Version 10.6 or 10.6.1 Establish a Roads and Highway"Locate Features Along Routes" tool that respects established ALRS route dominance rules. R&H - Concurrent Route Event omission from from Gap checks Added by NYSDOT: Establish a Roads and Highway"Locate Features Along Routes" tool that respects established route dominance rules. New York ArcGIS Toolbox Create an “Undo” if data is entered incorrectly (undo for all work since last save). 10/26/16 Will: Not supportable in current environment; planned for ArcGIS Pro (including new architecture for ArcGIS web services) using new "branch" versioning capabilities. Requesting undo for all work since last save, not simply an undo of the last action. Requires migration to ArcGIS Pro architecture. RHUG: Most likely need to defer for ArcGIS Pro. Move down in priority. High RCE Ability to edit event data within desktop 10/26/16- Will: This is a fairly major effort to implement in ArcMap. Planned for ArcGIS Pro but following network maintenance. ODOT staff believes this refers to increased editing capabilities in ArcMap. ODOT vendor has advised staff not to do this but ODOT staff believes this is sometimes necessary and certainly easier. ADOT - The limitations imposed within the RCE severely limit the productivity of the Roads and Highways platform. Allowing for desktop editing would take away many of these limitations. NC: May be restricted by state security. RHUG: Not the highest priority right now. Group will probably defer to ArcGIS Pro. High ArcMap Prevent user from accidentally editing network or event layer instead of centerline Prevent user from accidentally editing network or event layer instead of centerline MnDOT - Trying to avoid accidental network updates. This can be an ongoing issue when there is a large group of network editors. NC: Mitigated at NCDOT by making event layer not editable and data reviewer checks. Follow up with Kevin with our approach to avoiding this issue. RHUG: Nice to have but not the highest priority. High ArcMap Ability to choose multiple centerlines at once for editing Ability to choose multiple centerlines at once for editing ODOT: This includes moving multiple coincident vertices. ADOT - This is a tricky one but could be done if ESRI used some of the logic in old route builder geoprocessing tool. NY: Allow user to select centerlines more easily. Centerlines should be able to be selected regardless of measure order and set direction of route as it is built. RHUG: Would be nice to have but not the biggest impact for a large number of DOTs. Lower priority for current environment. Medium ArcMap Prevent editors from saving if route measure anomalies exist. ODOT staff agrees that this would prevent induced errors. ADOT - At least give warning. MnDOT - Data Reviewer is a good tool to effectively address. RHUG: Need more details to understand what the conditions and expectations are for this issue. Priority: TBD ? ArcMap When editing existing events the RCE interface should warn the editor if they are about to create LRS overlaps within the data. This could be integrated as an event specific test managed by the user (check box on form like the "prevent measures not on route" option. This would allow the user the functionality to block overlapping events when wanted. RHUG: Is new Data Reviewer functionality the fix? Medium RCE Add JSON as an output option for the Export Network web service. This would allow users of this service to no longer use the FGDB API. This API has been the source of most of the issues AgileAssets has had with implementing and updating an interface between Roads and Highways and our asset management system. The benefit of this to the DOTs is a quicker and less troublesome update of the AgileAssets/R&H Interface for each new release of Roads and Highways. This affects at least the following DOTs: Alaska, Georgia, Indiana, New York, North Carolina, & West Virginia. Phil from AgileAssets logged ENH-000097436 as an enhancement request with Esri. RHUG: Medium Spatially derive event values based on polygon layers, etc. in RCE Medium RCE Ability to hide columns in attribute grid in RCE Ability to hide columns in attribute grid in RCE High Priority for OH Medium RCE Ability to digitize a centerline and create a new route in a single workflow in Roads & Hwys Desktop Ability to digitize a centerline and create a new route in a single workflow in Roads & Hwys Desktop RHUG: Would be nice to have…but not highest priority Medium ArcMap When using Re-assign Route and you enter the Route ID and click on “Use Whole Route” then enter the New Route ID sometimes it say the Route cannot be found. But if you un-check and then re-check the Use Whole Route it will then find the route. Not sure what this is. ? ArcMap Add Event Widget to Include Options for Retire Medium RCE Ability to lock fields. Details: Keep certain fields in view at all times as you scroll across a data layer. Access and dBase will allow you to “lock” certain fields to the left as you move across. Similar to the “freezing” the top row/rows in Excel. High Priority for OH Medium RCE On the Split Line events you should be able to add additional lines of data. Currently you can only make one break and then you have to re-initialize the Split Line events to make a second break. Medium RCE Range domains are not validated when entering data. Esri solution to use data reviewer; original requirement to handle validation in the model via a range domain. Esri software does not support range domain validation. Range Domain Validation Enforce range domains Range domains are supported by the current released version. Range Domain Validation to DataReviewer team. Low RCE Automatically set the width on columns in the table so text doesn't wrap related, but slightly different: Increase length and width of Add Linear Events/Attribute's widget table, RCE And/or control individual columns (need to be able to use this like Excel). Medium RCE Double click a date field to automatically populate today's date (like in ArcMap) Automatically populate today's date when creating a new route. Low RCE Recalibrate Route Downstream checkbox becomes configurable to be checked/unchecked by default Recalibrate Route Downstream checkbox Currently is checked (on). Low ArcMap Confirmation message upon save and rec/post in RCE ADOT - Feedback is much better than ambiguity Low RCE Ability to view scrolling measures along route on hover in Roads & Hwys Desktop Dynamic readout. MN: Would like this in R&H too. Medium/Low ArcMap Line events not retiring properly Not sure what this is. ? RCE Add ability to utilize Route Dominance to move current events on non dominant routes to dominant routes where occurs. Useful. Unsure of overall priority Medium ArcMap Add ability for quick event behavior access/adjustments to be made. Currently opening each event's behavior window is not time efficient (over 90 event tables). Add option for change in matrix form like snapping window. Medium/High ArcMap When a route ID is entered in ”Find Route” and then you go to “Line Events” the route ID should appear. You should not have to re-enter the route ID again. Low RCE Select by Attributes Tool (Query Across Multiple Events) Medium RCE Merge coincident events changing temporality of events Not sure what this is. ? RCE Physical Gap Routes - Support Driven Distance mileage NY: or at least entered mileage Medium ArcMap Use of GP tools to Post SDE data outside ArcMap or RCE fails to release locks Separate GP tool to release locks? Low ArcMap Add the capability to generate an Edit Audit Trail. This would be a report that users could get that lists when an edit was made, who made it, what the edit was, and what were the specifics of this edit (routes, measures, etc.). The need for this has come up a good bit with users doing testing as they are trying to correlate the event results with what they remember of the edits. Phil (from AgileAssets) logged this as Case #01817538 with Esri. Medium Need to ensure that Event GUIDs are unique. Many of the Roads and Highways tools expects uniqueness. Not sure what this is. ? RCE/ArcMap Rectangle button shutting off and leaving users just panning on map: Transcend acknowledged that this doesn’t behave in the desired manner, and that the tool becomes inactive often. They are documenting the steps to replicate the issue and are sending it to Esri as a defect. As a workaround, specific steps (such as visually verifying that the button is selected) can be used to perform the needed actions. Not sure what this is. ? RCE Fix Redlining behaviors, or determine best practice There are two options to configure RCE for redlining according to ESRI (http://desktop.arcgis.com/en/arcmap/latest/extensions/roads-and-highways/deploying-redline-routes.htm) “To enable web redlining of routes using the Roadway Characteristics Editor (RCE), you should author a web map using ArcMap and include a redline feature class. You can achieve this in one of the following ways: • Include the redline layer in the same map service along with your routes and event layers. • Create a separate map service for the redline. The advantage of publishing a separate map service for the reline layer is that the feature access will only be exposed for the redline layer, not for other layers such as network and event layers. You can make the decision based on your security practices.” Notice the underlined statement by ESRI. It points out the advantage of the second approach. If we rephrase the statement to point out the issue with the first approach, it goes like this: Publishing redline layer in the same map service for network and events exposes editing feature access to network layer, redline layer, as well as event layers. In a typical configuration, users who are authorized to do redlining has the possibility of changing network and any events in the Roads and Highways database without explicit authorization, permission or through LRS business logic. In other words, it opens door for unexpected data loss and data corruption. I think ESRI is fully aware of this security issue in RCE redline configuration. The trouble is that the first approach is a very poor security practice. Even it gives capability of adding events to redline without turning redlines to routes (http://desktop.arcgis.com/en/arcmap/10.3/guide-books/extensions/roads-and-highways/adding-linear-events-to-a-route-redline.htm) DOT’s should be aware that 1) approach one is not an acceptable option because of the potential of data loss and data corruption. 2) Redlining workflow resulted from approach 2 may not be effective enough for many to do redline and maintain its event attributes by the same user who does not manage the network. ? RCE/ArcMap/RHCore In the grid or in split line events you should be able to code data even if it did not exist before. Adding events in grid. Low/Medium RCE File and attachment support in RCE NC: Need more information as to what the implementation would be. Need more details to understand what the conditions and expectations are for this one. ? RCE Ability to run, save, load queries in Roads & Hwys Low/Medium RCE R&H Tools: Create Route GUI - Auto pop. Route name Need more details to understand what the conditions and expectations are for this one. ? ArcMap Snapping Functionality for DGN and DWG layers RCE Linear Event Editing- Must enter exact station of the end of the route to attribute to the end of the route RCE Make Certain Functions Always Visible in RCE RCE The Merge Coincedent event setting does not always work. RCE Add Route/Referent offset geocoder. RCE/ArcMap Add ability to replace route geometry while still invoking event behavior rules and/or new currently missing event cover behavior ArcMap Be able to edit fields in a point data attribute sets RCE Keep SQL query in Select by Attributes populated when changing the layer if the field exists in both the new and old layer RCE Ability for alias names configured in MXD to be viewable while building query in Roads & Hwys - RCE RCE When using “Find Route” the route is highlighted but when you close the attribute box the highlight disappears. The highlight should be able to be toggled on and off. RCE Clip routes/events based on polygon layers for mileage reporting in Roadway Reporter Roadway Reporter RCE's editing tab currently opens with the default attribute set. It would prevent many user errors if this defaulted to nothing and the user had to choose which attribute set they want to edit. RCE Can't view a range of two dates (view historical data) RCE Editing Linear Events with Stationing- select beginning of route as reference RCE Grid field width does not maintain it's size when there's a change. RCE Selectable on/off parcel boundary layer RCE Append Events GP tool shows target event error ArcMap Line event attribute values changing to null RCE Linear event widget does not provide for a remove conversion action RCE RCE Invalid Retire Records Created for Events RCE Request to make the RCE base map widget configurable RCE Add ability to clean up timeslices of routes/events that are benign. ArcMap The situation is in a R&H geodatabase all the tables or feature classes or other objects are stored at the root level while in a generic geodatabase datasets can be created to group objects. As a R&H geodatabase is getting more widely used and keeps growing, there could be hundreds of objects in it. When looking for a specific table in the geodatabase, for example, it may take the editor minutes to scroll down and get it. So the request for Esri is can R&H be configured to support the usage of dataset? The measure tool as a whole is very clumsy and frustrating to use. This is the core measure tool. Esri advised OH to log a support ticket. ArcMap Expand the attribute grid in Add Linear Events (get rid of the white space below the grid) RCE When in Select by attributes sometimes you cannot arrow over within the select box to change the typed data. Instead of moving through the text it actually “pans” the map. RCE Web App Builder widgets for Search, Query with dynamic segmentation, and Convert Measures All Ability to turn off base maps in RCE. ODOT questions if this is a configuration setting. ADOT - Our experience is once turned on cannot turn off. RCE Add an autocomplete where we type in the name and get a list of possible matches to the Advanced Find Route tool in RCE. This would then mirror the functionality found in R&H in ArcGIS desktop. RCE Update the Remove Centerline Geometry Duplication tool to maintain attribution ArcMap Metric Value Converstion RCE Create an “Undo” if data is entered incorrectly (undo for only the last single transaction). RCE Ability to prevent editing certain Route systems by user without having to create a separate LRS. ArcMap Time-enabled eyedropper in RCE RCE Recalculate events based on referents being changed ArcMap Adding imagery from local drive to RCE ADOT - Unsure if this is a product limitation or can be accomodated already. RCE Use “Add Data” to add two or more DGN and DWG files to RCE and see these listed in the Layers panel. RCE RCE - Add CAD Data Functionality RCE DGN Rendering Engine for RCE RCE RCE measure tool not converting correctly RCE Select Routes in Make Road Char Layer Widget (duplicate rte issue) RCE RCE eyedropper tool copies populated event data only https://geonet.esri.com/ideas/10113 n Roads and Highways - Roadway Characteristic Editor, when using the eyedropper tool to copy attributes from one record to another in RCE, it would be useful if there was a toggle switch to let the user either copy all attribute values or only the ones that are populated. The way the tool functions now is that records will be created with null values where there are nulls in the existing record. The toggle should cause the software to realize the attribute was null and not present the attributes in the first place on the copies record. Otherwise, the user has to uncheck all the blank options so as not to create null records. This is in 10.2.2 patch 1. RCE R&H Tools - All - Recalibrate Route Downstream ArcMap Add NC OneMap Statewide Latest Imagery to Banner's Base map Widget RCE R&H Tools - Multi-field Route ID Input dialog - Reorder dropdown values ArcMap Linear Event Editing- Selecting Route to edit on bidirectional routes RCE R&H Tools - Multi-field Route ID Input dialog - Allow shortcut key for searching Maintenance County Code ArcMap Markup Manager Tool in RCE- Zoom to Markup option ArcMap RCE Markup Manager- Saved Map Markups Tables do not Automatically Refresh RCE RCE Markup Manager - Add Title to Delete and Load Markup Windows RCE RCE Markup Manager - Additional filter to loading markups RCE RCE Markup Manager - Grey Out "Delete Saved Markup" option RCE RCE Markup Manager - Ability to edit graphical elements RCE Markup Manager Tool - Ability to place a markup pin based on a Latitude/Longitude coordinate RCE Linear Event Widget Jumps Around RCE add bookmark function in RCE https://geonet.esri.com/ideas/11457 In Roads & Highways Server - Roadway Characteristics Editor (RCE), add ability for users to create, save, and do basic management of spatial bookmarks within the web interface. This will allow event editor to create bookmarks for reference when working in multiple regions of a network. from ideas page RCE Concurrent Route Event omission from from Gap checks https://geonet.esri.com/ideas/10113 ALDOT has many On-System Concurrent Routes. Managing events on those routes are difficult. As QC for events on ALL routes the "Check Events on Route" tool is used to check for gaps, overlaps and invalid measures and returned to employees as a work flow. Focusing on gaps with this idea I would like to have the ability for the RCE to remove gaps returned due to events being on the subordinate route. The following shows ALDOT's State Route system checked for gaps for one event, F_System (Highway Functional Classification). This returned 446 gaps. A CSV is created from the results and put into workflow. The issue is that a very low percent of these are actual gaps on the dominate route. The editor must investigate each gap though to ensure it is on a subordinate route. It is very time comsuming and costly in man hours. It is counterproductive and erodes efficiency RCE Offset measures w/split tool https://geonet.esri.com/ideas/10543 In the Roadway Characteristics Editor (RCE) the ability to use offset measures with the split tool. This would be used a lot in our local jurisdictions and with construction plans. Also, a related enhancement would be to split all the events in a specified attribute set with similar events RCE Increase length and width of Add Linear Events/Attribute's widget table, RCE https://geonet.esri.com/ideas/11795 Roadway Characteristic Editor (RCE), when dealing with the Add Linear Events/Attribute's widget. It would be great to not only make this Wider but also Longer? I ask this, because when using the scroll bar as I am going down the list to enter data in the fields it will try and jump back up to the top. This gets to be a problem at times, slowing the rate of getting data fixed or entered into RCE. RCE
... View more
12-12-2018
02:40 PM
|
1
|
4
|
1995
|
|
DOC
|
This is the list of bugs and issues we complied from the previous RHUG site. I would like to break up this list and report each bug or issue as an individual discussion item with tags for version numbers affected and status.
... View more
12-12-2018
02:34 PM
|
1
|
0
|
1435
|
|
DOC
|
ID Activity or Function Issue Workaround Module 10.3.1 10.4.1 10.5 10.5.1 10.6.1 Plan Submit by Priority Bug-000101699 Export Network Service The Export Network tool does not get the latest geodatabase version state when executed as a service. Change the recycle frequency of the GP Service to minimize the impact of the issue in the current environment. Server found patch 4 exists exists fixed NYSDOT High BUG-000110742 Realign Realigning a route to create a gap calibrates the To Measure on event incorrectly Desktop @fixed NCDOT Medium BUG-000106791 ArcMap Symbology Creating a layer from the Create Layer From Selected Features option does not honor the selection and displays all the features. Desktop fixed resolved NCDOT high BUG-000108601 TFS-53113 Export Network Service Tool fails to run if there is a complex route concurrency (one loop, one lollipop, plus a typical route shape that is partially concurrent with the loop and lollipop routes) across different time slices . Previous thought bug was due to Production Mapping being installed in ArcGIS Desktop 10.5, but that is not the case Remove route concurrency by reassigning to bogus route id or retiring Server found patch 1 fixed NCDOT high BUG-000106993 TFS #54450 Network Edit - Reverse Route Reverse Route causes calibration point measures to change beyond 6 decimal places. Manually edit calibration point and recalibrate downstream Desktop found fix NCDOT high NCDOT case 01889567 Relocate Events Service Relocate events service stretches events beyond end of route. The issue relates to a defect that is fixed in 10.5.1. However, cartographic realignments done in Roads and Highways pre-10.5.1 with the condition that there is more than one calibration point downstream of the edit will exhibit the symptom in this support incident. Edits on 10.5.1 of Roads and Highways will not have this symptom. Hotfix estimated August 4, 2017 that will mask the symptom of pre-10.5.1 cartographic realignment edits from external systems, such as AgileAsset’s system(s) Server found hotfix* NCDOT BUG-000101392 TFS51810 Route Edit - extend, realign Extending a route to create a concurrency then realigning the other route to remove the concurrency on the same date results in incorrect event behaviors for the non-concurrent events on the realigned route Use reassign instead of extend if possible Desktop found patch 4 exists exists fix NCDOT high TFS51854 Route Edit - Reverse, Reassign Reverse and Reassign to Create Gap Causes Measures Downstream From Gap to be Incorrect. Issue also occurs doing a reverse and retire to create a gap Reassign, then reverse if possible Desktop found patch 4 exists exists fix NCDOT high TFS51855 Realign, Cartographic Realignment Realign then cartographic realignment results in retired routes becoming NaN. Cartographic realignment of route at new alignment (retired route becomes NaN); Cartographic realignment of route at old alignment (active route becomes NaN); Possibly fixed in 10.4.1 (based on testing at 3rd party vendor site) Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly) Desktop found patch 4 fix NCDOT high TFS52078 Retire, Cartographic Realignment Retire to create gaps then cartographic realignment results in routes becoming NaN. Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly) Desktop found patch 4 fix NCDOT High TFS52077 Reassign, Cartographic Realignment Reassign then cartographic realignment results in retired routes becoming NaN. Retired and active routes become NaN. Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly) Desktop found fixed NCDOT High BUG-000101941 Extend, Cartographic Realignment Extending a route, and performing a cartographic realignment on the extended portion results in a Not a Number (NaN) calibration Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly) Desktop Patch 4 fixed NCDOT High BUG-000102184 Launch a URL (i.e. instance of RCE) from Workflow Manager Online ArcGIS Workflow Manager for Server opens browser (IE) in server when executing Launch URL step in a client environment. Causes server instability. ArcGIS services become unresponsive. Database validation fails for datastores Dynamically examine the memory usage and periodically eliminate the ‘zombie’ server processes; alternatively, reboot server. server found exists exists fixed NCDOT High BUG-000101393 TFS51811 Realign, Retire Realigning a route to create a concurrency followed by retiring the other route to eliminate the concurrency on the same date results in the snapped events getting incorrect measures. Use reassign instead of realign if possible Desktop found exists exists exists exists in plan NCDOT High TFS45251 NCDOT case 01888502 Calibration Vertex measures flip when recalibrating none Desktop found fixed NCDOT High NCDOT case 01904018 Add Machine to an ArcGIS Server site After upgrading an ArcGIS 10.3.1 site to 10.5, the Add Machine operation fails with error: "\relational-datastore-types" folder cannot be located Using Windows commands on the config-store file share, create an empty file folder in the config-store named "relational-datastore-types". Proceed normally with adding the new machine. Server found ? ? not in plan NCDOT High Reassign or Retire Retire or Reassign route to create gap causes the ends at the gap to have same measures even though Euclidean Distance has been set. This issue is not in 10.3.1 Patch 4. Desktop found not in plan NCDOT Medium NCDOT case #01906828 Realign, Cartographic Realignment Events shift downstream of realignment if a cartographic realignment is subsequently performed Desktop found not in plan NCDOT BUG-000102964 Display Route Events Display Route Event tool maps 2 event items with identical log values to 2 different LRS measured vertices (2 events log = 1.335 but 1 gets mapped to 1.335 other is 1.334 In LRS processes leading up to Display Route Event tool needs, increase the M-value scale by 1 (chang from 0.001 to 0.0001) Desktop found exists exists exists exists not in plan Ohio DOT Bug Undefined Editing Error Upon running a linear overlap validation tool in desktop (built by Transcend Spatial) we are discovering where records are being duplicated behind the scenes. This tool is designed to check specified tables for gaps and overlaps. By design R&H extension should not cause gaps and overlaps to occur and thus there is an underlying flaw yet to be identified. Weekly run of this tool followed by manual editing to correct the issues Desktop found exists exists exists exists not in plan Ohio DOT Bug Add Calibration Point Identified a situation where a new calibration point was added along an existing route (around the 1 mile mark) in desktop. As a result of the desktop edit we found in RCE a record (0.00-0.633) in an event table was retired incorrectly. Upon noticing this we removed the retired date to bring back the incorrectly retired record. The next day we discovered there were 2 records in the event table for the same segment (0.00-0.633) Manual delete of the newly duplicated record to retain a single record that correctly exists and isn't retired RCE/Event Editor found exists exists exists exists not in plan Ohio DOT Bug Same Location Calibration Points Identical Measure Value Multiple Calibration Points at the same location with the same measure deleting 1 of the CP's causes issues 1. Turn off the Roads and Highways extension in ArcMap by going to Customize > Extensions > Roads and Highways. Make sure ArcCatalog is closed on that machine as well. 2. Add your CPs to a MXD 3. Verify in the edit log that no timestamped activity was logged for adding the feature to the map. 4. Delete the CPs via the attribute table. You can do this in a geodatabase version and rec/post the deletions if you prefer. 5. Verify again that there is no deletion activity logged in the RH edit log. 6. Save your edits and rec/post as needed. 7. Turn on the Roads and Highways extension. Desktop found exists exists exists exists not in plan Ohio DOT Bug Same Location Calibration Points Different Measure Value Multiple Calibration Points at the same location with different measures deleting 1 of the CP's causes issues Desktop found exists exists exists exists not in plan Ohio DOT Bug Modify Measure with leave/re-enter issue When modifying a measure on an existing leave/re-enter situation in desktop the system will not allow user to adjust the measure on the re-enter point as it wants to create a non-monotonic route. Desktop found exists exists exists exists not in plan Ohio DOT Bug Recalibrate Downstream When using the realign tool and selecting the recalibrate downstream option the updated measure values are not calculated correctly if there is a leave/reenter or overlap situation on the route. Even when the calibration point is specified to use 3 decimal precision, when users open the attribute table it initially shows 3 decimal precision in the from/to fields, however, if users select the from/to fields on records associated with the recalibration downstream process the full 16 decimal precision is shown Desktop found exists exists exists exists not in plan Ohio DOT
... View more
12-12-2018
02:30 PM
|
0
|
3
|
1776
|
|
DOC
|
from the RHUG site I had info for Arizona on the basic implementation status, but not the detailed status from the most recent survey. I can help you add that content if necessary.
... View more
12-12-2018
02:23 PM
|
0
|
0
|
1048
|
|
DOC
|
I just copied the content from the RHUG google site to new, editable documents in this site. There are two versions, one has more details.
... View more
12-12-2018
02:16 PM
|
2
|
0
|
1048
|
|
DOC
|
AGENCY STATUS Current Version Next Version Asset Management Other Comments Mileage Desktop Editors Event Editors Status Updated URL New York State DOT In Production (Network Editing only) 10.5.1 AgileAssets 7.0 SP4 Testing integration with AgileAssets. Designing integration with Oracle Primavera Portfolio Manager. Preparing to begin event editing in 10.5.1 later this Summer 130000 2 0 8/1/2017 North Carolina DOT Working with Esri to resolve issues at 10.5 Patch 1 10.5 Patch 1 10.5.1 Integrated with Agile Assets 6.9; testing 7.1 SP 5 Upgraded to R&H 10.5 in preparation for release of 10.5.1 160,000 6 15 5/25/2017 RoadNC North Dakota DOT In Production (Network/HPMS) 10.6 None SQL Server backend with AD. In the process of implementing Portal/Roadway Reporter 104,500 2 4 3/14/2018 Indiana DOT In Production 10.5.1 AgileAssets 7.0 SP 6 Testing auto generated Milepost LRM, (GENLOG) working on Agile integration and Deighton integration 109,000 2 100+ 6/12/2018 Public Data Viewer Maryland MDOT/SHA Implementation (Planning to be live in Spring/Summer 2017) 10.3.1 None at this time Possibly moving to 10.5 or 10.5.1 at go live 31,050.96 4 50 1/26/2017 http://imap.maryland.gov/Pages/road-centerlines.aspx West Virginia DOT In Proudction (Network editing only, preparing for editing roadway characteristics data soon) 10.3.1 Patch 4 10.4.1 AgileAssets 6.9 (Preparing for upgrading to 7.0 SP4) 35958 5 11 2/8/2017 Ohio DOT In Production 10.5.1 Went to 10.5.1 on 10/4/17 121,000 9 9 10/4/2017 Minnesota DOT In Production 10.5.1 Integrating with Agile Assets 7.0 SP4 Our desktop editors also perform event edits. 142,463 5 10 5/10/2018 Georgia DOT In Production 10.4.1 10.5.x Plan to implement Agile v. 7.2 due to feature class support 128,133 10 15 9/1/2017 Utah DOT Evaluating / Implementing 10.4.1 Prototype Deployment Phase I complete, Evaluating Phase II complete June 2017, Possible Implementation 2018 46,297 3 5 8/2/2017 Kansas DOT Implementing iteration 3 go live RH 4/2019, go live with business system interfaces 3/2020 10.4.1 Using NG911 road centerlines, cleansing data with 1Spatial Desktop, implementing RH plus Transcends TDS apps 142,000 2 20 1/14/2019 Nevada DOT R&H soft roll-out by April 2018. 10.5.1 10.6.x EAMS by Agile Assets to be implemented by Dec. 2018 LRS unification and R&H implementation by Arcadis to be implemented by Jun 2018. 6 2/14/2018 https://www.nevadadot.com/ ITD (Idaho Transportation Department) Live in production 10.6.1 AgileAssets 7.0 SP5 - will not be integrating with AgileAssets 6 30 11/2/2018 http://itd.idaho.gov Alabama DOT In Production 10.4.1 10.5 In house 102,019 7 6 3/2/2017 Michigan DOT Implementing 10.4.1 10.5.1 Implementing DTS VueWorks Scheduled for Production in Fall 2017 124,393 2 6 8/1/2017 Iowa DOT In Production 10.4.1 10.5.1 None at this time Cross event data validations, dynamic segmentation, and HPMS submittal done using Transcend's TDS App Suite 114,000 4 20 8/2/2017 Bonneville County ID Still in Implementing Process 10.4.1 10.5.1 None at this time Working at getting portal installed, then moving to Esri Cloud 800 1 1 8/2/2017 New Mexico Preparing data migration from legacy data base 10.4.1 Agile Assets and MS2 for Traffic 69,000 8/2/2017 Rhode Island DOT Implementation (Planning to be live in Summer 2017) 10.5 Patch 1 10.5.1 VueWorks 2017.1 Conflating MIRE, HPMS, and other events registered to their own LRS to the ALRS 3300 8/2/17 California DOT Phase 1 implementation (22 months) of two phase effort 10.5.1 None at this time R&H must be able to support the Caltrans Postmile System to be implementable 196,000 4 6 8/2/2017 Louisiana DOTD In Production (working through day by day) 10.4.1 10.6.x Agile Assets and Transmetric Integrating with Transmetric. Investigating integration with Deighton and Project Management System. Configuring Portal. Maintaining one linear referencing system and processing a secondary linear referencing system. Performing lrs and event editing. 104,000 5 5 8/2/2017 Manitoba Infrastructure Scoping Phase, production by 2019, 3 phase effort targeting 10.5.1 or later none We need to re-sync our highway inventory with our new conflated road network as part of this project 11875 2 5 8/3/2017 Alaska DOT & Public Facilities In Production (excluding some linked end-user applications) 10.5 ? Agile Assets 7.2 (implementing, production in spring of '18) 14,000 2 3 8/3/2017 Maricopa County AZ In Production (still have more implementation tasks including Workflow Mgr and Reporting) 10.4.1 10.5.1 None at this time Need to implement Workflow Manager and custom reports. 2,400 1 3 8/7/2017
... View more
12-12-2018
02:14 PM
|
0
|
0
|
885
|
|
DOC
|
Agency R&H Primary R&H Business Objectives External Business System Integrations 3rd Party Tools to Extend R&H Functionality Agency Developed Custom Software (related to LRS/RI) Other Comments Centerline Mileage LRS Editors Event Editors Total Editors Status Updated General Status Version Maintain LRS Network Number of LRM Maintain State Only, or State & Local Maintain Events Number of Events Being Maintained (ex - NHS, roadway width, shoulder, etc.) Number of Unique Event Editor Applications Top 3 Benefits to Business Top 3 Performance Impacts Business Bridges Pavement Maintenance Capital Projects Financial System Traffic Monitoring Collector Integration Vendor 1 Software Purpose Performance Status Vendor 2 Software Purpose Performance Status Vendor 3 Software Purpose Performance Status Name Purpose Technology Performance Status Willing To Share (provide contact info / location) System (version x) Integration Type Performance Status Additional Needs System (version x) Integration Type Performance Status Additional Needs System (version x) Integration Type Performance Status Additional Needs System (version x) Integration Type Performance Status Additional Needs System (version x) Integration Type Performance Status Additional Needs System (version x) Integration Type Performance Status Additional Needs Assets in Collector Integration Type Performance Status Additional Needs Ohio DOT Production 10.5.1 Yes - R&H Desktop Extension 1 State & Local Yes - R&H 83 1 1. Potential integration functionality 2. Potential workflow management 3. Potential replacement for labor intensive BTRS process 1. Issues with core R&H product result in significant productivity losses (ex - ALRS inconsistencies & related event behavior performance) 2. API limitations (lack of interaction with LRS_EDIT_LOG) 3. Inconsistent workflows / use of tools across ArcMap tools and R&H tools Benteley InspecTech Manual Automatic Integration Needed Deighton dTIMS Manual undecided Agile Assets 6.9 None Not exploring Custom In-House Manual Works, labor intensive Automatic Integration Needed Custom In-House Manual Works, labor intensive Automatic Integration Needed MS2 Manual 2-way integration In development TBD ESRI Collector Manual 1 - way custom python script / REST Acceptable Automatic Integration Needed Transcend Spatial Solutions Validation Assistant data quality checks enables data validations BTRS distributes LRS & RI data to enterprise Mainframe, Java, DB processes, scripting Labor intensive Currently having system configuration & workflow issues resulting in significant data quality issues 121,759 9 9 9 4/26/2018 WVDOT Production 10.5.1 Yes - R&H Desktop Extension 2 State & Local No 0 0 1. One authoritative LRS 2. Seamless integration w/ other ESRI ArcGIS applications 3. Flexibility to manage events 1. Async of LRS due to business rules 2. Challenging integration 3. Lack of accuracy from GIS Benteley InspecTech Manual Integration Needed Deighton dTIMS Manual Integration Needed Agile Assets 6.9 1 way (under development) Integration Needed Custom In-House Manual Works, labor intensive Integration Needed Custom In-House Manual Works, labor intensive Integration Needed Transmetric Manual 1-way integration Integration Needed ESRI Collector Manual Integration Needed None Implementing Event Editor for managing roadway characteristics; implementing a workflow to publish LRS 38,000 5 5 4/26/2018 MnDOT Production 10.5.1 Yes - R&H Desktop Extension 1 State & Local Yes - R&H 40 4 1. Authoritative Source 2. Manage events effectively 3. Utilizing the LRS .API 1. Constant issues with core R&H product 2. Complexity of training new people for R&H 3. Challenging integrations SIMS undecided - dependent of carto-realignment fixes undecided n/a Agile Assets 6x 1 way working Custom In-House Semi-Automatic works FMIS Automatic via ETL Works Jackalope (High Desert Traffic) None In development Carto-graphic realignment issues caused Traffic to not integrate ESRI Collector Manual Integration Needed Our Desktop editors also perform event edits. 138,794 5 10 10 4/23/2018 Kansas DOT Testing 10.6.1 Yes - R&H Desktop Extension 2 State & Local not yet, performing network cleanup ops 100 0 1. combine separate LRS systems to one system 2. Implement REST interfaces to LRS based busines systems 3. utilize partnerships with NG911 and GIS offices 1. implementation 2. Centerline/Network attribute and measure validation 3. Temporality AASHTOWARE BRM test develop test Internal, Custom custom development test custom custom develop test custom In-House custom develop test custom In-House and FMIS custom develop test Jackalope develop develop test Signs, Rail crossings, sidewalks, lights, bells, parking lanes, turn lanes, high water marks, WiFi access points... manual portions in production, other portions vailable but not implemented documentation, educational materials, communications Transcend Spatial Solutions implementing 1spatial 1spatial 1integrate data validation and enhancement, conflation, change detection, correction processing interface between RH centerline and source NG911 centerline geometry 143,000 5/9/2018 Indiana DOT Production 10.5.1 Yes - R&H Desktop Extension 2 production +1 development State & Local yes - R&H 98 9 1. Single source of truth 2. Integrates with other systems 3. Is accessible 1. ALRS System administration skills pool depth 2. Mission and redundancy planning 3. Stakeholder involvement in the network edit process Bentley InspecTtech Internally developed 2 way integration Phase 1 Acceptable Phase 2 in development Deighton dTIMS System, on demand development test Agileassets 7.0 SP6 1 way development test Custom In-House custom production method made redundant by dTims integration and scoping workflows Custom financial app integration with Event Editor for FMIS Auto notifications with manual project locations entry Effective but Event Editor is labor intensive method made redundant by dTims integration and scoping workflows MS2 2 Way integration development test ADA, Retaining Walls, Cores, Slides, Luminaries, dTIMS Recommendations, Small Culverts, Patching Rx, Random Notes and Stuff, Special Markings and many more None planned with the exception of a new Maintenance planning playbook. Small Culverts (largest inventory) -performance is terrible. Others are OK. further testing of our collector / ALRS integration scripts/process Transcend Spatial Solutions Productivity tools suite, Road Analyzer Intersection manager and strip map IM - process is in development RA is in production HNTB python scripting Integrate Collector with Federal Rail Administration to maintain crossing data that the INDOT Rail division is responsible for Operational May 2018. Many internally developed systems interface with the ALRS for authoritative inventory and attributes. C#, python production Not really stand alone or realistically distributable, N/A Adding Rail network to R&H, May be adding trail networks to R&H 109,000 2 100+ 100+ 6/12/2018 New York DOT Production 10.5.1 Yes - R&H Desktop Extension 1 State & Local yes - limited asset events in Event Editor. Roadway Inventory to be established in R&H in 2018 using custom interface. 4 2 AgileAsset 7.0 COTS R&H / Agile Agile system in production; integration pending Agile upgrade to 7.3 linear bridge event locations are currently being verified in Event Editor AgileAsset 7.0 COTS R&H / Agile Agile system in production; integration pending Agile upgrade to 7.3 Current custom New system wil be AgileAssets 7.3; expected 2019
... View more
12-12-2018
02:10 PM
|
0
|
4
|
2103
|
|
DOC
|
CATEGORY TERM Reference Number DEFINITION LRS & R&H ALRS 1 Acronym for the Advanced Linear Referencing System, a linear referencing system implemented by Roads and Highways on the ArcGIS platform that supports multiple linear referencing methods and event measure behaviors. Asset 1 A type of linear referenced event that represents a physical object, such as a sign, guardrail, or bridge. Calibration Point 1 A point feature that defines the measure for a specific locaiton on an LRS route. Roads and Highways uses calibration points to define the measures on the routes. Centerline 1 A polyline feature that defines part (or all) of the geometry of an LRS route. Concurrency 1 Concurrency occurs when two route segments share the same pavement/centerline features. Route segments in a concurrency are called concurrent routes or overlapping routes. Divided Highway 2 A multi-lane facility with a curbed or positive barrier median, or a median that is at least 4 feet in width. Dominant Route 1 In a route concurrent there are at least two routes travelling the same pavement. The one that events are assigned is called the dominant route. In a route concurrency there is only one dominant route. Most DOTs follow the rule that events are associated with dominant routes only. Event 1 Data that is located by its association to an LRS route and measure location. Event Behavior 1 Configuration that defines how event measures and route assoications respond to changes or edits in the LRS network in Roads and Highways. Export Network Service/Tool 1 A web service or geoprocessing tool that enables external systems to synchronize with the Roads and Highways LRS Network to update routes, gaps, concurrencies, and measure translations. Used for system integration. External Event 1 An event that resides outside the geodatabase where the ALRS is configured. External System 1 Databases and other data storage systems of event data that are outside the management of Roads and Highways. Internal Event 1 An event that resides inside the geodatabase where the ALRS is configured. Linear Event 1 An event that represents a segment of a route from a starting measure (or from measure) to an ending measure (or to measure) LRS 1 Acronym for linear referencing system, the method of storing geographic locations by using relative positions along a measured linear feature. LRM 1 Acronym for linear referencing method, a method for defining measurements along linear features for the purpose of linear referencing. LRS Network 1 A collection of routes, measured to a specific LRM in Roads and Highways. Measure 1 Or mile point or milepost. A location along a route based on a distance from a known point of origin. Point Event 1 An event that represents a single point location on a route at a specific measure. RCE 1 Acronym for Roadway Characteristics Editor. This application was renamed to Event Editor at the 10.5 release. It's a web based event editing application included with Roads and Highways. Relocate Event Service/Tool 1 A web service or geoprocessing tool that allows external events to be synced to route edits in Roads and Highways. Used for system integration. Roadway 3 The portion of a highway intended for vehicular use. R&H Acronym for ESRI ArcGIS Application Roads & Highways Roadway Characteristics 3 Or roadway attributes. A set of attributes characterizing roadways in a highway system. Examples include surface type, number of lanes, and lane width. Route 1 A linear LRS feature defined based on a LRM. Route ID 3 A value to uniquely identify a route. Some DOTs implement an intelligent/descriptive route ID definition by incorporating information about the route type, county, municipality, route number, and directionality while some use sequential numbers or GUIDs (Globally Unique Identifiers) generated in databases to differentiate routes. Route Dominance Rules 1 A set of rules that decide which of the concurrent routes in a route concurrency is the dominant route for events and the rest subordinate route(s). Route dominance rules can be preset in Roads and Highways by using attribute fields in an LRS network or the internal event layers that are registered to the network. Station 1 Reference points that are placed along the horizontal measurement of a route, centerline, or baseline at a regular interval. Station numbers increase from West to East or South to North based on the cardinal direction of the overall highway. Stationing 1 The fundamental system of measurement used by surveyors. For highway projects, a starting reference station is first established and then all distances along the route centerline are measured from that point location. Subordinant Route 1 In a route concurrent there are at least two routes travelling the same pavement. The route that doesn't have events assigned is called a subordinant route. In a route concurrency there is at least one suborinate route. Most DOTs follow the rule that events are assigned to dominant routes only. INTEGRATION System Integration 4 Or integration, a process of linking together Roads and Highways with different computing systems and software applications physically or functionally to act as a coordinated whole. One Way Integration 4 An integration that supports data in Roads and Highways consumed by an external system. Two Way Integration 4 An integration that supports data exchange between Roads and Highways and an external system. Automatic Integration 4 An integration that is carried out by code or computer programs so human interruption is minimal. Manual Integration 4 An integration that is mainly carried out by manual work performed by human beings. Semi-Automatic Integration 4 An integration that is carried out by both code/computer programs and manual work. GENERAL TERMS Bug 4 Or software bug. A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Sometimes it is an alternate saying of "software defect". Defect 4 Or software defect. A software defect is a condition in a software product which does not meet a software requirement (as stated in the requirement specifications) or end-user expectations (which may not be specified but are reasonable). In other words, a defect is an error in coding or logic that causes a program to malfunction or to produce incorrect/unexpected results. Sometimes it is an alternate saying of "software bug". Development Environment 4 The development environment (dev) is the environment in which changes to software are developed, most simply an individual developer's workstation. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. Enhancement 4 Or software enhancement. In software development, software maintenance refers to modifying software products after delivery in order to correct faults, improve performance or other attributes, or to adapt the product to a modified environment. Process 4 It is a series of actions or steps taken in order to achieve a particular end. Production Environment 4 The production environment (PROD) is also known as live, particularly for servers, as it is the environment that users directly interact with. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. Staging Environment 4 The staging environment (STAGING) is an environment for final testing immediately prior to deploying to production. It seeks to mirror the actual production environment as closely as possible and may connect to other production services and data, such as databases. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. Testing Environment 4 The test environment (TEST) is an environment for human testers to exercise new and changed code via either automated checks or non-automated techniques. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. Validation 4 Or data validation. It is an iterative process that uses formal methods of evaluating a dataset's adherence to a defined quality standard. Workflow 4 It is the sequence of industrial, administrative, or other processes through which a piece of work passes from initiation to completion. A workflow consists of an orchestrated and repeatable pattern of business activity enabled by the systematic organization of resources into processes that transform materials, provide services, or process information. REFERENCES 1. Essential Roads and Highways Vocabulary 2. HPMS Field Manual 3. ARNOLD Reference Manual 4. Wikipedia or Internet Last updated by Yueming Wu of WVDOT on 04/23/2018
... View more
12-12-2018
02:09 PM
|
0
|
0
|
1183
|
|
POST
|
Most US Departments of Transportation should be able to produce grade data from the pavement data collection systems required by HPMS as a byproduct output from raw GPS data. However I do not think the grade data is required for HPMS as an official dataset of record, it would need to be generated from raw data, which would make it difficult to just request and obtain a ready to use dataset with an open records request. If you just needed over/under logic, the bridge data for NBI contains over/under information.
... View more
12-12-2018
11:09 AM
|
0
|
0
|
1146
|
|
POST
|
I'm drinking your Ohio Department of Transportation sake Kemosabi.
... View more
12-12-2018
10:53 AM
|
0
|
0
|
817
|
|
IDEA
|
It almost sounds like this is describing the attribute transfer mapping and attribute transfer tool in the spatial adjustment toolbar: Transferring attributes between features—Help | ArcGIS for Desktop About spatial adjustment attribute transfer—Help | ArcGIS for Desktop This is queued up for incorporation in ArcGIS Pro at version 2.3 or 2.4 according to this idea https://community.esri.com/ideas/15253
... View more
12-12-2018
08:56 AM
|
0
|
0
|
926
|
|
POST
|
I had a problem with retaining edit tracking for hosted feature services upon republishing. I use an XML Geodatabase modeling tool (Sparx EA) to make geodatabse model updates, and python to stage the data, actually a jupyter notebook. first I do something like this: #add edit tracking to all the feature classes AND DISABLE EDIT TRACKING
from arcpy import ListFeatureClasses, ListDatasets, EnableEditorTracking_management, DisableEditorTracking_management, env
#NewDatabase = r'c:\temp\CollectorGDB_2018081502.gdb'
env.workspace = NewDatabase
print (env.workspace)
datasets = ListDatasets()
for ds in datasets:
for fc in ListFeatureClasses(feature_dataset=ds):
print ('adding Edit tracking fields added for {0}'.format(fc))
EnableEditorTracking_management(fc, "Creator", "CreationDate", "Editor", "EditDate", "ADD_FIELDS", "UTC")
DisableEditorTracking_management(fc)
print ('Edit tracking fields added and disabled for {0}'.format(fc)) Then I do this to keep records of previous edit tracking fields #add edit tracking to all the feature classes AND DISABLE EDIT TRACKING
from arcpy import ListFeatureClasses, ListDatasets, EnableEditorTracking_management, DisableEditorTracking_management, env
#NewDatabase = r'c:\temp\CollectorGDB_2018081502.gdb'
env.workspace = NewDatabase
print (env.workspace)
datasets = ListDatasets()
for ds in datasets:
for fc in ListFeatureClasses(feature_dataset=ds):
print ('adding Edit tracking fields added for {0}'.format(fc))
EnableEditorTracking_management(fc, "Creator2018", "CreationDate2018", "Editor2018", "EditDate2018", "ADD_FIELDS", "UTC")
DisableEditorTracking_management(fc)
print ('Edit tracking fields added and disabled for {0}'.format(fc))
then I do lots of other stuff to download and append and stage the updates, then I do these steps: #back calculate edit tracking to static fields
from arcpy import ListFeatureClasses, ListDatasets, env, ListFields
from arcpy.management import CalculateField
#NewDatabase = r'C:\temp\CollectorGDB_2018081502.gdb'
env.workspace = NewDatabase
print (env.workspace)
datasets = ListDatasets()
for ds in datasets:
print (ds)
for fc in ListFeatureClasses(feature_dataset=ds):
print (ds, fc)
CalculateField(fc, "Creator2018", "!Creator!", "PYTHON3", None)
CalculateField(fc, "CreationDate2018", "!CreationDate!", "PYTHON3", None)
CalculateField(fc, "Editor2018", "!Editor!", "PYTHON3", None)
CalculateField(fc, "EditDate2018", "!EditDate!", "PYTHON3", None) this step moves the appended, historical edit tracking to my last year/historical edit tracking, not managed by Esri. Then I enable edit tracking back on the original edit tracking fields: #RE-ENABLE EDIT TRACKING with EDIT TRACKING HISTORY
#arcpy.EnableEditorTracking_management("C:\\gisdata\\Railroads\\CollectorGDB_2018080203.gdb\\Railroad\\MastCrossbuckAssembly", "Creator", "CreationDate", "Editor", "EditDate", "NO_ADD_FIELDS", "UTC")
from arcpy import ListFeatureClasses, ListDatasets, EnableEditorTracking_management, DisableEditorTracking_management, env
#NewDatabase = r'C:\gisdata\Railroads\CollectorGDB_2018080203.gdb'
env.workspace = NewDatabase
print (env.workspace)
datasets = ListDatasets()
for ds in datasets:
for fc in ListFeatureClasses(feature_dataset=ds):
print('enable new edit tracking data to fields in {0}'.format(fc))
EnableEditorTracking_management(fc, "Creator", "CreationDate", "Editor", "EditDate", "NO_ADD_FIELDS", "UTC")
... View more
11-14-2018
01:38 PM
|
0
|
0
|
1828
|
|
POST
|
The attached diagram can be referred to as a straight line diagram. You could produce that a number of different ways. One way to produce a straight line diagram like that would be to use data driven pages in arcmap. Draw a straight line. Make route events along the straight line and offset them. Trick the data driven pages into looking at the straight line as each route section as desired per page, and refer the events along the route from a percentage of the whole route to a unit percentage of the straight line. I dont think you need to union the events or combine them to do this.
... View more
11-14-2018
01:20 PM
|
0
|
0
|
791
|
|
POST
|
One more thought, if the route happens to be a railroad, and if you happen to have some inertial measured data, you could potentially use the inertial at-ground distance measurement as the length of the route, to accurately build your LRS Route.
... View more
10-25-2018
12:42 PM
|
2
|
1
|
1598
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-21-2025 06:20 AM | |
| 1 | 02-10-2025 06:22 AM | |
| 1 | 01-23-2025 07:01 AM | |
| 1 | 06-18-2024 03:18 PM | |
| 1 | 09-01-2023 11:54 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-09-2025
11:47 AM
|