Currently, we have the user pass in a single z_index value when calculating SLOPE or ASPECT. However, this will not produce good results if the layer contains multiple tiles and/or the tile(s) span different latitudes/longitudes.
We should create a method that'll find the ideal z-index for each Tile in a layer based on it's Extent and CRS. In addition, we should implement another method that'll allow the user to pass in a dict of lat/lng: z-index and then have that be interpolated to produce the remaining z-indexs.
jbouffard
commented
6 years ago
Currently, we have the user pass in a single
z_indexvalue when calculatingSLOPEorASPECT. However, this will not produce good results if the layer contains multiple tiles and/or the tile(s) span different latitudes/longitudes.We should create a method that'll find the ideal
z-indexfor eachTilein a layer based on it'sExtentandCRS. In addition, we should implement another method that'll allow the user to pass in adictoflat/lng: z-indexand then have that be interpolated to produce the remainingz-indexs.