dear all,
I develop in PHP and have almost no idea about Python and Perl, but thank
you anyway for the information.
best regards,
Pere
2009/4/21 discuss-requ...@lists.osgeo.org
Send Discuss mailing list submissions to
discuss@lists.osgeo.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.osgeo.org/mailman/listinfo/discuss
or, via email, send a message with subject or body 'help' to
discuss-requ...@lists.osgeo.org
You can reach the person managing the list at
discuss-ow...@lists.osgeo.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of Discuss digest...
Today's Topics:
1. Re: parsing coordinates (Tim Michelsen)
2. Re: Re: parsing coordinates (Mateusz Loskot)
3. Re: Re: parsing coordinates (Mateusz Loskot)
4. Re: parsing coordinates (Arnulf Christl)
--
Message: 1
Date: Mon, 20 Apr 2009 23:09:42 +0200
From: Tim Michelsen timmichel...@gmx-topmail.de
Subject: [OSGeo-Discuss] Re: parsing coordinates
To: disc...@mail.osgeo.org
Message-ID: gsioam$7u...@ger.gmane.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
* 40:26:46N,79:56:55W
* 40:26:46.302N 79:56:55.903W
* 40°26'21N 79°58'36W
* 40d 26' 21 N 79d 58' 36 W
* 40.446195N 79.948862W
* 40.446195, -79.948862
* 40° 26.7717, -79° 56.93172
I'm aware that parsing and interpreting free-text coordinate
descriptions is quite complex, maybe someone knows a script (or a remote
service) that does a similar job?
I did some of this for python.
What langauge will you use?
Please report if you find some useful libraries.
Kind regards,
Timmie
--
Message: 2
Date: Tue, 21 Apr 2009 09:26:21 +0100
From: Mateusz Loskot mate...@loskot.net
Subject: Re: [OSGeo-Discuss] Re: parsing coordinates
To: OSGeo Discussions discuss@lists.osgeo.org
Cc: disc...@mail.osgeo.org
Message-ID: 49ed832d.7060...@loskot.net
Content-Type: text/plain; charset=UTF-8; format=flowed
Tim Michelsen wrote:
* 40:26:46N,79:56:55W
* 40:26:46.302N 79:56:55.903W
* 40°26'21N 79°58'36W
* 40d 26' 21 N 79d 58' 36 W
* 40.446195N 79.948862W
* 40.446195, -79.948862
* 40° 26.7717, -79° 56.93172
I'm aware that parsing and interpreting free-text coordinate
descriptions is quite complex, maybe someone knows a script (or a
remote service) that does a similar job?
Long time ago I made a script solving similar problems:
http://mateusz.loskot.net/software/gis/pydecimaldegrees/
It is very easy to extend it to support all the format
variations you've listed above.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
--
Message: 3
Date: Tue, 21 Apr 2009 09:26:21 +0100
From: Mateusz Loskot mate...@loskot.net
Subject: Re: [OSGeo-Discuss] Re: parsing coordinates
To: OSGeo Discussions discuss@lists.osgeo.org
Cc: disc...@mail.osgeo.org
Message-ID: 49ed832d.7060...@loskot.net
Content-Type: text/plain; charset=UTF-8; format=flowed
Tim Michelsen wrote:
* 40:26:46N,79:56:55W
* 40:26:46.302N 79:56:55.903W
* 40°26'21N 79°58'36W
* 40d 26' 21 N 79d 58' 36 W
* 40.446195N 79.948862W
* 40.446195, -79.948862
* 40° 26.7717, -79° 56.93172
I'm aware that parsing and interpreting free-text coordinate
descriptions is quite complex, maybe someone knows a script (or a
remote service) that does a similar job?
Long time ago I made a script solving similar problems:
http://mateusz.loskot.net/software/gis/pydecimaldegrees/
It is very easy to extend it to support all the format
variations you've listed above.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
--
Message: 4
Date: Tue, 21 Apr 2009 16:39:43 +0200
From: Arnulf Christl arnulf.chri...@wheregroup.com
Subject: Re: [OSGeo-Discuss] parsing coordinates
To: OSGeo Discussions discuss@lists.osgeo.org
Message-ID: 49eddaaf.9030...@wheregroup.com
Content-Type: text/plain; charset=ISO-8859-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
pere roca ristol schrieb:
hi all,
I'm developing a webapplication that let's user upload their point data
and
play with it.
It currently works with lat/long in a CSV with this format (eg: *0.44,
-79.9
*) but we find users with some of these also valid and acceptable ways to
write geographic coordinates:
- 40:26:46N,79:56:55W
- 40:26:46.302N 79:56:55.903W
- 40°26'21N 79°58'36W
- 40d 26' 21 N 79d 58' 36 W
- 40.446195N 79.948862W
- 40.446195, -79.948862
- 40° 26.7717, -79° 56.93172
I'm aware that parsing and interpreting free-text coordinate descriptions
is
quite complex, maybe someone knows
