[Geomoose-users] Latitude and Longitude Error... no playing at the poles

[Matej Mailing]

Hi,

the problem is solved. The data is in the epsg:2170 which seems to be
based on epsg:4326 and now when using epsg:2170, everything seems to
be alright.

Thanks,
Matej

2012/10/12 Jim Klassen <klassen.js at gmail.com>:
> If you are trying to run the GeoMoose map in 4326 something else is wrong.  In this case both coordinates (X,Y) and (Lat,Lon) should be in 4326.  That they match (except for reversed order) is good and means the projection stuff is probably ok.
>
> What isn't ok is a latitude of 164000 North and a longitude of 535000 East.
>
> Check your scales, max_extent, and initial_extent in your mapbook configuration make sense for your projection (4326).
>
>
> For example:
> The largest Max_extent that would be reasonable would be "-180,-90,180,90". (If anyone is near the international date line we may need to look at this.)
>
> I'd expect reasonable scales to be in the 0.7 to 0.000005 range.
>
>
> On Oct 12, 2012, at 4:21, Matej Mailing <mailing at tam.si> wrote:
>
>> Hi,
>>
>> the entire error message is:
>> "X,Y: 535806, 164720Lat, Lon: 164719.711, 535805.778USNG: error
>> lat164719.71065803 must be between in (-90,90)... no playing at the
>> poles, yet"
>>
>> Is our EPSG:4326 proj4 definition wrong?
>>
>> Thanks,
>> Matej
>>
>>
>> 2012/10/11 Jim Klassen <klassen.js at gmail.com>:
>>> The only place I know of a "no playing at the poles" error is in the USNG/MGRS coordinate display code.
>>>
>>> However, if this is the case it should display:
>>> USNG: error lat [something] must be between in (-90,90)... no playing at the poles, yet
>>>
>>> If this is the case the [something] would give us a hint as to what is going on.  It should be the same as what is displayed for Lat:.  Often when there is a projection definition problem (or you have panned/zoomed outside where the projection is valid) this number will be nonsense and/or NaN.   Just out of curiosity, do lat and lon happen to be reversed?  At some point (at least with WMS 1.3) the interpretation changed from Easting, Northing (like virtually every coordinate system) to Northing, Easting because someone decided that Lat, Lon sounded more natural to say.  I'm curious if proj4js maybe made the update.
>>>
>>> Secondly, there is a bug in the USNG code because it should be trapping the range (-80, 80) ( or 78???) instead of (-90,90) because Zones A and B are not implemented yet (they are based on polar stereographic instead of the rest of the zones that are based on UTM and I wasn't sure how to handle that correctly).
>>>
>>> On Oct 11, 2012, at 6:33 AM, Matej Mailing wrote:
>>>
>>>> Hi,
>>>>
>>>> I have a GM project with EPSG:4326 data. The file EPSG4326.js exists
>>>> on the server and is loaded when the site loads (checked with logs and
>>>> also with Firebug)
>>>> The file content loaded is:
>>>> Proj4js.defs["EPSG:4326"] = "+proj=longlat +ellps=WGS84 +datum=WGS84 +no_defs";
>>>>
>>>> In Mapbook I have set
>>>> <param name="projection">EPSG:4326</param>
>>>>
>>>> The Identify works with no problems.
>>>>
>>>> What else should I have to change to get it working?
>>>>
>>>> Thanks,
>>>> Matej
>>>> _______________________________________________
>>>> Geomoose-users mailing list
>>>> Geomoose-users at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>>>