by SamDee » Thu Dec 13, 2012 1:32 pm
Ushadow, I think this applies across all the documentation. Any function description you pull up, assumes that you already know what to do and how to do it. If that was the case, why the documentation? For example, the description for the function being discussed says:
FindClosestStreetFirst(X,Y,Radius, Num, Filter, Options):String
Searches the Streets data bases within the specified radius, and finds the street segment that is closest to
the user specified point X,Y (Lon/Lat). The radius (miles) is useful in restricting the search operation
which, if not bound, could take a considerable length of time. The procedure performs an exhaustive
search, and calculates the distances to every street in the grids within "Radius", even if only portion of
such a grid is within that radius. The passed parameters in detail are:
X,Y – Longitude and Latitude of the center of search in degrees
Radius – The radius of search in miles
Num – The maximum number of hits (matches) to be returned
Filter – The CFCC code that should be used for filtering
Options – 0 Search is based on the visibility of the street in the viewport
1 All streets are searched regardless
2 The CFCC filter is used
What grids within "Radius" is the explanation referring to? For Options=0, does it mean if I see it on the map it will be used in the search? If so, what if I am looking at the Southwest, but am making the function call for a point in Seattle, WA? If Options=2, when the CFCC filter is used, is that in combination of the "visible" search, or with the "all" street search?
Do you see my generic problem with the way and the level of detailed information being provided, or is it just me?