Compiling map articles

Fixing Error E019: Street cannot intersect with itself! Split this element

FIXING cGPSmapper MAP COMPILATION ERRORS

This occurs when a polyline is broken up into more than one non contiguous polyline (or non connecting polyline).

This is the same error as:-


Error R014: Several DataX for routable roads not permitted!



In fact running a different cGPSmapper compiler version generates a different error message for the same error!



The rest of the article is the same as Error R014 with different screen shots - you can skip it if you have already read the R014 error article



The error message box from cgpsmapper is shown in the diagram below









Note this is not the same as “spliting polylines” – which is ok.




This causes compilation to stop and crash and won’t continue until it is fixed.

To find where it is on the map

1. Click ok on the error message box
   
   
   
   
   
   
   
   No point in reporting it, best to find the error and fix it yourself!!!
   
   
   
2. Double click on the compiler box which should take you to the line where the error occurred.
   
   
   
   
   
   
   
   
   
   
3. Highlight and copy a set of coordinates
   
   
   
   
   
   
   
   
   
   
4. Close both the cgpsmapper box
   
   
   
5. Go back to the source file and press “CTRL+G” to “Go to Position” and paste the coordinates that you have copied into the box.
   
   You should then be taken to the polyline that caused the problem
   
   
   
   

   How to fix this R019 error

   
   
   

   1. To do this, Tools – Select Objects
      
      

   2. Click on the Polyline which should turn magenta
      
      
   3. Right click and you should notice that “Extract All Elements” is bolded indicating that there is a problem with this polyline where there are more than one element.
      
      
   4. Just to confirm this (you don’t need to do this everytime – this is just for illustrating this tutorial), click on Properties, then select Elements tab
      
      
      
      
      
      
      
      
      
      
   5. You will notice that there are five sets of data for this one polyline when there should only be one!
      
      Eg There is more than one set of Data0=….. line within the same polyline, these must be removed
      
      
   6. Click Close and then click on the line again to select it
      
      
   7. Right click again
      
      
   8. Click on “Extract All Elements” and this should fix the problem
      
      
      
      
      
      
      
      
      
      
   9. That’s all you need to do.
      
      

   The problem with a file that has multiple instances of this is that you will need to re-run the compiler after fixing one error polyline and wait for it to report another instance and go through all the steps above to fix it before continuing.

   
   
   
   
   

   Just imagine doing this through Mapcenter2 – it will take days or weeks to get a finished product!

   
   
   
   
   

   This iterative process is very time consuming if you have many instances of this problem.

   
   
   
   
   

   I do hope that someday, GPSMapedit adds a functionality under the Tools – Verify Map to check for this to allow a mapper to eliminate these "multiple dataX" errors before sending the file for compilation.

   
   
   
   
   

   Alternatively, you could search for these lines using a text editor but searching for multiple Data0=xx line within [polyline] and [end] tags require some programming knowledge and a customised script to do that.
   
   Anyone out there able to help write this? :-)

   
   
   

   UPDATE MAR 2010 !

   
   
   
   

   Actually, I found a way to seek out these error using a good text editor such as Notepad++ or Editpad Pro. Windows notepad or other similar editors won't cut it!
   
   Hint: Search for this using "regular expression".
   
   
   

   This is what the SOURCE DATA looks like in a text editor
   
   [POLYLINE]
   
   Type=0x5
   
   EndLevel=2
   
   CityIdx=7
   
   RoadID=12030
   
   RouteParam=3,0,0,0,0,0,0,0,0,0,0,0
   
   Data0=(18.02133,102.61046),(18.02146,102.61080),(18.02231,102.61154),(18.02162,102.61304)
   
   Nod1=0,236539,0
   
   Nod2=3,236538,0
   
   Data0=(18.01393,102.60218),(18.01456,102.60254),(18.01498,102.60286),(18.01541,102.60324),(18.01582,102.60369),(18.01643,102.60440),(18.01655,102.60459),(18.01685,102.60485),(18.01711,102.60506),(18.01736,102.60507),(18.01764,102.60498),(18.01783,102.60482),(18.01827,102.60476),(18.01855,102.60494),(18.01867,102.60535),(18.01918,102.60685),(18.01979,102.60737),(18.02015,102.60781),(18.02073,102.60947),(18.02133,102.61046)
   
   Nodes1=(0,236552),(19,236539)
   
   Data0=(18.00955,102.59857),(18.00977,102.59852),(18.01105,102.59955),(18.01147,102.59989),(18.01197,102.60041),(18.01220,102.60068),(18.01261,102.60142),(18.01287,102.60173),(18.01386,102.60216)
   
   Nodes2=(0,21852),(7,236543),(8,236553)
   
   
   
   
   
   
   HOME