New answers tagged

4

Looks like you're trying to add data to the insert cursor one column at a time. Cursors think about the world one row at time. I recommend the following code. A few other notes... Python code runs in order, so make sure you declare your outpath variable before you set your env.workspace to outpath. Also, this code is going to create a shapefile with the ...


0

Problem solved. Geoserver had problems with the projection. The tiffs were in EPSG:32633. It works after reprojecting the tiffs to EPSG:3857.


1

Here is the answer I got back from NOAA. It's in the form of java code, and the order of parameters has to be inferred, but in case it proves useful to someone else here it is: public static final HTDP NAD83 = new HTDP(0.9910, -1.9072, -0.5129, 0, 0, 0, 1.25033e-7, 0.46785e-7, 0.56529e-7, 0.00258e-7, -0.03599e-7, -0.00153e-7, 0, 0, 1997); public static ...


2

There are no default transformations in the EPSG Geodetic Parameter Registry. Sometimes you can use the remarks and or the accuracy value to determine which is the currently accepted transformation as defined by the government or the most accurate transformation. For instance, in Belgium, there are two transformations between BD72 and ETRS89: 1652 and ...


1

Yes, they will be square in both projections! Breaking it down: UTM stands for Universal Transverse Mercator. From the Wikipedia article: The Universal Transverse Mercator (UTM) conformal projection ... i.e. UTM is "conformal." As for what "conformal" means, again from Wikipedia: Conformal, or orthomorphic, map projections preserve angles ...


1

There's a reason UTM projections don't extend to infinitive and engulf the whole globe. As you move further away from the UTM's central meridian the distortion becomes more and more apparent. In the case of a transverse Mercator projection the distortion, as its a conformal projection, is applied equally both in the X and Y axis, therefore your angles ...


2

The transverse Mercator Projection is conformal and preserves angles. So the square should still be a square. Area will change though.


1

SQL Server spatial functions implementation is in its current state not able to reproject or transform between different coordinate reference systems. The spatial data types are nothing more than a CLR (Coomon Language Runtime) data type implementation of the OGC Simple Feature Access specification plus some extended functions plus the spatial index. You can ...


2

The EPSG Geodetic Parameter Registry has two coordinate reference systems that match that well-known text. The first that I looked at was MGI 1901 / Balkans 7, EPSG:3909. The other one was Macedonia State Coordinate System Zone 7, EPSG:6316, which has the same definition. Using that information, I was able to find that the data is in Skopje, Macedonia. ...


0

The surveyor wording is a bit unclear, and I have not done this on UTM yet, so without testing and verifying this, I cant be certain i have it right, but the formula is correct. May just need a slight tweak (i.e. subtracting the shift values instead of adding OR using the inverse of the scaling instead of the actual). Take your current UTM Northing (0.0) ...



Top 50 recent answers are included