Timeline for Proper way to check if a Factory Code is Projected or Geographic
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:33 | history | edited | CommunityBot |
replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
|
|
Sep 15, 2015 at 18:53 | history | edited | TSJ | CC BY-SA 3.0 |
Added helpful link
|
Sep 1, 2015 at 22:02 | vote | accept | TSJ | ||
Aug 31, 2015 at 2:21 | answer | added | Michael Stimson | timeline score: 2 | |
Aug 28, 2015 at 16:52 | answer | added | TSJ | timeline score: 1 | |
Aug 28, 2015 at 15:56 | comment | added | mkennedy | Yep, that's the way to do it. To check if a WKID is valid, the software has to create the object anyway then check its type. | |
Aug 28, 2015 at 15:11 | comment | added | Vince | That's what EAFP is about. Alternatively, you can let the user provide a projected code or a geographic code, and trap the error if they've given a bad one. | |
Aug 28, 2015 at 15:08 | comment | added | TSJ | So I am correct in thinking the only way to do this is to try one of the two methods (Geographic or Projected), see if it fails, then try the other? This is using Try and Catch for program flow though, which seems inappropriate. There's no other way? | |
Aug 28, 2015 at 15:06 | comment | added | Vince | You cannot determine the coordinate system properties until you instantiate it. Those two questions do appear to solve your issue. What more do you need? | |
Aug 28, 2015 at 14:53 | history | asked | TSJ | CC BY-SA 3.0 |