A REPLY TO "Ronald Eric de Gracia" <[EMAIL PROTECTED]>
FROM Karl Lusebrink [EMAIL PROTECTED]
i have a question for road network editor.. how would you like the data
(roads, structures, etc) to be displayed? on a table? other suggestions
are welcome
---

I have managed this kind of work so I’ll take a crack at this; but there are conditions or dependencies not clear in the question.  Suggestions follow in increasing complexity.

-1- Editors can efficiently work from a table of data when the edits are simple and the number is small, for example, an hour's worth of changes to attributes on existing geometry or simple realignment of geo to given reference points. Too many edits can be mind-numbing and call for tightened QC.  Data must include (a) foolproof way of locating and identifying roads/structures in the database; e.g. coordinates, segment & node IDs, street names, intersecting street relationship, road class attributes, ferry/bridge/tunnel type if applicable, etc. and (b) the edit required clearly described.

-2- Preferably, the edit request will include a diagram showing what each completed edit should look like and how it should be attributed.  Reduce the likelihood of misunderstanding by giving them a graphic if possible.

-3- Whole scale network edits generally require source material in the form of marked-up plots or maps, or digitally drawn on a coverage layer.  The editors each work on attribution changes through contiguous geographic areas to reflect the marked sources, then adjacent areas boundaries are matched up.  This seems to work well when editing one attribute on many roads in a city, State or Province, for example.

-And- QC should be by manual inspection sampling following the software checks.  Road networks with specific connectivity rules can have complex situations with one-way, limited access roads, time and turn restrictions, etc. They can be quite tricky for software to fully cover, but can be spotted if you are looking for them.  Also, Updating road network geo and attributes can have rolling impact on adjacent data, and editors have to know about the impact each edit may have on road segments and attributes in the vicinity.  They should always visually cross check that no defects are created in the edit process by displaying the connectivity of attributes around and through the edited segments.   

Cheers, Karl

 



Local listings, incredible imagery, and driving directions - all in one place!
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking

Reply via email to