[Talk-us] [Imports] TriMet will begin OSM improvements in the Portland area
stephanie.jean.houser at gmail.com
Fri Mar 4 00:38:31 GMT 2011
First, let me say that ESRI has been great regarding the OSM Editor. I
contacted them with our problems, they responded within minutes, and now
we're working together on determining if our problems are operator-based or
We encountered 5 main problems:
1) Revision table does not explicitly store all changes, especially node
-using the topology edit tool (with all of the OSM layers taking place in
-selecting a point (node), moving that item, only indirectly moving the
edge. The node would move (and move its connected ways along) whether it was
attached to only one way or to multiple ways.
-This error occurred in several different locations that we tested.
-Don't bring revision table into ArcMap.
-Not all changes explicitly stored in excel table. Would be good to conduct
some testing on this.
-make sure edits pass the core topology tests
-Maybe a simple table refresh issue? ESRI has noticed occasionally that no
“edits” appear in the revision table while it is open and docked in the
application. Once you close the table and reopen it again the dialog usually
shows all the rows."
should indicate what types of edits should and should not show up in
2) schema lock on revision table
-occurs after at least one successful upload
-occurs while trying to save edits
-Avoid issue by keeping revision table out of table of contents to avoid
-Don't open table in ArcMap.
-If it does lock, try compact database. This removes schema locks, returning
.gdb to "pristine" state.
-Switch off background geoprocessing. ESRI still got the locking message
after a couple of successful data uploads.
should warn of potential for schema lock and potential remedies
3) Performance speed of geoprocessing in ArcMap
Select by location excruciatingly slow with OSM derived dataset in table of
ESRI is unable to replicate. Still needs to be explored.
4) Performance speed of downloading data - RESOLVED.
Download speed is intentionally optimized for older machines. Testing never
went beyond 150MB/s
Should include expected minutes/MB for download.
5) Moving ways creates new nodes without deleting old ones. - RESOLVED
Actually an OSM anomaly resulting from peculiarities of one-layer data
model. When editing in ArcMap (if we ever decide to do this), good to know
when it's more efficient to move existing nodes vs creating new ones by
moving way and deleting existing nodes.
should mention that line edits won't follow expectations for vector data
model (points lines polygons)
By the way, our machines run Windows XP and have Intel Core 2 Quad CPU and 4
GB of RAM. We use ArcMap 10 with SP 1 installed, ArcView license.
Tom, as for your issue, did you give OSM time to update their tiles? For
some of our edits, we had to wait at least 10 minutes for them to show up at
openstreetmap.org, and even then, some of the tiles hadn't been updated.
Otherwise, it sounds like you might be having a similar problem to us. After
you upload, check the revision table. See if anything is written in it. As
far as I was able to understand, the revision table should have something in
it if your changes registered.
I am going to forward this email to our ESRI contact, by the way.
GIS intern, 503-962-5711 (office)
On Tue, Mar 1, 2011 at 4:17 PM, Tom Ponte <tgis at bendbroadband.com> wrote:
> I would be interested in what kind of “significant problems” you had with
> the ArcMap extension if it is not too much trouble. It might save myself and
> others some time and effort trying to figure out what are operator issues
> and what are software issues. I have been working with that extension and
> recently tried to convert some roads to trails and add a boundary for a
> small BLM wilderness area as a test. The extension said the upload was
> successful but nothing showed up in OSM. If you are worried about being
> exiled to Los Angles for listing the significant problems with the ESRI
> extension you could email me directly.
> I will be looking forward to seeing your updated workflow.
> Tom Ponte
> GIS Analyst
> 541 419-2113
> TGIS at BendBroadband.com
> *From:* PJ Houser [mailto:stephanie.jean.houser at gmail.com]
> *Sent:* Tuesday, March 01, 2011 3:30 PM
> *To:* Dave Hansen
> *Cc:* imports at openstreetmap.org; talk-us at openstreetmap.org
> *Subject:* Re: [Imports] [Talk-us] TriMet will begin OSM improvements in
> the Portland area
> Hi Dave & Talk-US & Imports,
> We decided against using Trimet in our name since as Richard pointed out,
> OSM is a collection of individuals. This is us right now. I will let you
> know if we change our names. Should we include RLIS (the data source) in our
> user names? We are all using our personal emails, so we have kept everything
> really informal so far.
> http://www.openstreetmap.org/user/Grant Humphries
> And our workflow is changing a lot since we ran into significant problems
> with ArcMap OSMEditor, though we are working with ESRI to improve the
> editor. I hope to send an updated workflow really soon for input! Not many
> changes to OSM have been done because we are still trying things out.
> But most importantly, all changes are being done one at a time. Nothing is
> bulk. Every change is done "by hand". I am doing my best to make sure nobody
> else's hard work is overwritten or deleted!
> PJ Houser
> Trimet, GIS
> On Sat, Feb 26, 2011 at 1:31 PM, Dave Hansen <dave at sr71.net> wrote:
> On Thu, 2011-02-10 at 18:28 -0800, PJ Houser wrote:
> > OSM User Names: TriMet_PJH, TriMet_MSB, TriMet_GNH, TriMet_BB
> Hi PJ,
> I was just looking for your user pages so I could spy on your
> for instance. Did you end up using some different usernames, or have
> you just not created them yet?
> -- Dave
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Talk-us