Changes between Version 44 and Version 45 of CookBook join BDMAP_CCM v2


Ignore:
Timestamp:
Nov 10, 2010 4:34:27 PM (14 years ago)
Author:
cedric
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CookBook join BDMAP_CCM v2

    v44 v45  
    4141 
    4242== 2. getting distance sea and distance source for bd_carthage == 
    43 Les identifiants des noeuds de dataEDAcommun\amorce_mer\bassin final\source\dataEDAcommun\amorce_mer\bassin final\source\troncon_parcouru_source.txt ne correspondent probablement plus aux nouveaux identifiants des noeuds.  
    44 Je regarde ce qu'avait stocké laurent... 
     43Below after some search, but we have to trust the last data in the bd_carthage 
    4544{{{ 
    4645load(paste(datawd,"/dataEDAcommun/chainage/parcours_source/noeud&troncon_final.RData",sep=""))  
     
    175174== 4. include distance source constraint when doing the projection == 
    176175 
    177 ideally it should be a two step process, first projection to be used ["CookBook join BDMAP_CCM"][[BR]] 
    178 Then within those dams selecting those with conflicting distances... 
    179  
    180 First an analysis of the distance source from  
    181  
     176Below this table does not only select minimum distance but all ccm segments which are within a 300 m distance from the electrofishing station. [[BR]] 
     177  
     178{{{ 
    182179DROP TABLE IF EXISTS bd_map.bdmap_ccm2; 
    183180CREATE TABLE bd_map.bdmap_ccm2 as ( 
     
    190187); 
    191188alter table bd_map.bdmap_ccm2 add column id serial; 
     189}}} 
    192190 
     191The table from the request joining bd_map.bd_map_bd_carthage with the bd_map.bdmap_ccm2 is exported there 
    193192 
     193We are trying to see if distance_source distance_sea and strahler are consistent between bd_carthage and ccm 
     194