New answers tagged

1

I figured it out. Using the staging database, type7arcs & type6arcs feature classes use the domain IrParcelLineCategory which has coded values 0, 1, 2, 3, 5, 6. Well, if you type this field as 7 (as it says you need to do), you will get the error noted above. It just happened to work fine with type6arcs because you type the field as 6, which is a ...


0

I understand your topology is valid, but have you tried a check geometry on those parcels? I ran into several parcels which wouldn't load due to complex geometry. I wound up having to explode multi-part and import each of those separately.


1

Yes, use the integrate tool but make a backup copy of your data since this tool will alter the geometry. For example, if you have a polygon smaller than the tolerance the polygon will collapse.


0

The pgr_nodeNetwork code was modified on version 2.1 I confirm there is a bug on that modification. SELECT pgr_nodeNetwork('edge_table', 0.001); NOTICE: PROCESSING: NOTICE: pgr_nodeNetwork('edge_table', 0.001, 'id', 'the_geom', 'noded', '<NULL>', f) NOTICE: Performing checks, please wait ..... NOTICE: Processing, please wait ..... NOTICE: ...



Top 50 recent answers are included