search

unige-geohealth / accessmod

accessmod 5 : anisotropic accessibility analysis.
GNU Lesser General Public License v3.0
41 stars 14 forks source link

stack conflict table #158

Open noliphant-unicef opened 8 years ago

noliphant-unicef commented 8 years ago

Hi, I get the following error (or warning?) when I attempt to add layers for land cover and roads to the stack. What does "no lines available" mean? What might I be doing wrong? Do you have suggestions of how I can fix this issues? Thanks! Nick

From the log: 2016-09-18@01_52_28 error no lines available in inputCallread.table(text = execGRASS(r.category, map = m, intern = T),sep = \t, stringsAsFactors = F)

noliphant-unicef commented 8 years ago

I reordered that stack. and that has allowed the merged file to be created but I still get the "no lines available" error.

2016-09-18@02_42_02 error no lines available in inputCallread.table(text = execGRASS(r.category, map = m, intern = T),sep = \t, stringsAsFactors = F)

Also in the Accessibility tab view, no facilities are showing in the facilities selection tab. The facility vector imported fine but perhaps it has not read the data...it seems to think there is no start points (i.e. no data).

2016-09-18@21_12_13 error The command:r.walk.accessmod --overwrite -s -t elevation=rDemdem@PERMANENT friction=rSpeedtest output=rTravelTimetest start_points=tmp_hf max_cost=1800produced an error (1) during execution:Walking costs are a=0.72 b=6 c=1.9998 d=-1.9998Lambda is 1Slope_factor is -0.2125Reading raster maps <rDemdem@PERMANENT> and <rSpeed__test@Nick_Test>,initializing output... 0% 3% 6% 9%12%15%18%21%24%27%30%33%36%39%42%45%48%51%54%57%60%63%66%69%72%75%78%81%84%87%90%93%96%99% 100%Reading vector map <tmp_hf@Nick_Test> with start points...ERROR: No start points found in vector <tmp_hf>CallexecGRASS(r.walk.accessmod, parameters = amParam, flags = flags)

fxi commented 8 years ago

Hi, thanks for reporting those issues.

  1. No lines available. Did am5 returned a visible error or there is only a log entry on this ? This seems to be related to an internal library not able to read raster values. If there is no sensible information in your dataset, please share it in the dropbox. I've added a folder with corresponding issue number (158).
  2. The error says that there is "no start points". So no facility has been found. This should clearly have been determined at the importation time. So, if you want to share your data, I can analyse the file and add a new verification step to handle this case.

This is great to add some "fresh" data set in am5: the more we add "unknown" data, the more we will have something resilient. Resilient for covering the most common cases. Speaking of spatial data, there is so much special cases, maybe I should have targeted only those instead of the common one...