[gpl_list] Comments regarding the recent DOT Transportation Layer

[BRADY Chad W * ODOT]

All,

I have been asked to respond to the "observations" below.

First of all, OR-Trans (OT) is not, in the form it was given to DAS, a cartographic product.  It is a GIS dataset for analysis.  The USGS transportation layer is a cartographic product.  Comparing them is like comparing apples and oranges.

The OT data given to DAS GEO was made into a layer file based on whether or not a road was a highway or not and what type of road a record is (Road, Street, Avenue etc).  This is not the best way to mimic the a road networks true functional use.  There are some avenues that carry more traffic than others and a street may carry more traffic than a road in one case and visa versa in another.  The best way to symbolize a road network is through the use of a combination of factors.  You can see ODOT's product that incorporates that appropriate cartography while using OT here:
https://gis.odot.state.or.us/transgis/<blocked::blocked::https://gis.odot.state.or.us/transgis/>   This is available as a service and was used in the Raptor application for the Olympic trials in Eugene.

In the version of OT that was given to DAS GEO, there are only 25 of the 36 counties data that is in that service, plus state data and federal data.  So there will be roads and in fact entire counties worth of data missing.  We are limited in distributing data at this point by not having data sharing agreements with all of our data sources.  ODOT worked with a contractor that had significant dealings with the local data development for county and 911 purposes and were able to leverage that for getting DSA's signed to share data.

The good thing for state agencies is that we have "gentlemen's" agreements with the other 11 counties to be able to distribute data to state agencies for official state business and only that.  Since this is published as a service it was decided to show the lesser dataset (That is what we decided wasn't it Erik?).

Railroads in ODOT data are a GIS analytical. dataset and not a cartographic dataset again.  We have done some work to make the GIS data look a little more cartographically pleasing in the TransGIS link above.

Since these are services, I will have to defer creating "light" and "dark" version to Erik.  But I am sure that is feasible.

Since cartography wasn't the mark we were trying to hit, it stands to reason that we can't compete in that venue.  But as one can see, TransGIS does a much better job getting to a cartographic product even though we are using a dataset meant for analysis.  But that service is not ODOT's cartography and for that matter the data isn't ODOT's data we are merely the folks that were tasked to compile a whole bunch of data that gave folks a complete census of the roads (to the extent possible) in Oregon using data developed locally that is usually the most timely and most accurate (spatially and attributes).

I hope that clarifies what the appropriate uses for OR-Trans should be.  And explains some of the observations seen.  Please if you have specific questions/concerns like these talk to me.  Chances are I will probably have an answer for you.

Thank you

Chad


________________________________
From: gpl_list-bounces at listsmart.osl.state.or.us [mailto:gpl_list-bounces at listsmart.osl.state.or.us] On Behalf Of HILL Milton E * EISPD GEO
Sent: Thursday, July 12, 2012 9:15 AM
To: 'gpl_list at listsmart.osl.state.or.us'
Subject: [gpl_list] Comments regarding the recent DOT Transportation Layer

>From Dorothy:


--- Milt

From: Dorothy Mortenson [mailto:dorothy.c.mortenson at state.or.us]
Sent: Thursday, July 12, 2012 9:13 AM
To: HILL Milton E * EISPD GEO
Subject: FW: Comments regarding the recent DOT Transportation Layer

Milt,
Can you send this to the GPL? I do not have permission to send and Bob is out for a couple of weeks. Thank you.
Dorothy
-----------------------------------------------


I have taken a closer look at the transportation rest service:
http://navigator.state.or.us/ArcGIS/rest/services/Framework/Trans_GeneralMap/MapServer

I have compared it to the USGS transportation layer that was used for the recently published topographic maps:
http://services.nationalmap.gov/ArcGIS/rest/services/transportation/MapServer

Comments:
1) In comparing the two in ArcMap, USGS wins in that:
* The grouping of layers is done very well in the USGS version, with the ability to turn different layers on and off (interstate, county roads, etc. and their respective labels).
* It appears to be more complete.  I found that when I zoomed in, there were connecting roads missing, whereas they are filled in and seamless in USGS. An example is attached.
* The documentation is pretty good, tho could stand for a little improvement.
* The railroads are much cleaner, tho maybe not as technically correct. USGS wins cartographically; ODOT might be a good choice for query analysis.

2) Both could use a "light" and "dark" version, depending on what the background will be.

3) I believe the ODOT version is missing the mark cartographically at the statewide level, but could be greatly improved if it used a similar strategy as the USGS as far as how the layers are broken out. The symbology for the Highway Network theme and the Signed Routes are a little too bold to be used with anything else. As a guide, look at any of the Street Map services.


I have not looked at the downloadable data yet.

Dorothy



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ><(((('>
Dorothy Mortenson
Oregon Water Resources Department
(503)986-0857

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omls.oregon.gov/pipermail/gpl_list/attachments/20120716/3d2f0bb5/attachment.html>