[gdal-dev] [EXTERNAL] Re: [GSOC] Support for m coordinates in OGRGeometries

[Edson Ticona]

Hi
I checked PostGIS and it implements all M related stuff in a component
called lwgeom, the other functions are called from geos. I think that
it might be better to work, first, on fully compatibility with PostGIS
and then start to see other drivers because of the time it takes to
get familiar with other drivers. I am working on a more detailed plan
that is based on what's done on lwgeom, I am sending it to the list on
the weekend to get some feedback.
Just for referece, MySQL doesn't support M; Oracle and GML do!

Edson

On Wed, Mar 18, 2015 at 6:15 AM, Smith, Michael ERDC-RDE-CRREL-NH
<Michael.Smith at erdc.dren.mil> wrote:
> Oracle definitely supports M.
>
> Mike
> ----
> Michael Smith
>
> US Army Corps
> Remote Sensing GIS/Center
> michael.smith at usace.army.mil
>
>
>
>
>
> On 3/17/15, 11:20 PM, "Even Rouault" <even.rouault at spatialys.com> wrote:
>
>>Selon Daniel Morissette <dmorissette at mapgears.com>:
>>
>>> FWIW I think support for M would be a very welcome addition. An
>>> immediate use I'd see for it would be support for time on GPS tracks in
>>> GPX files.
>>>
>>> Note that if supporting the M dimension doesn't seem enough for a SoC
>>> project, making sure that all formats that support M (or as many as
>>> possible) are upgraded to properly implement it may very well fill the
>>> rest of the summer.
>>
>>Good point. At least the following ones for sure support M: Shapefile,
>>ESRI
>>Personal Geodatabase, FileGDB / OpenFileGDB, PostGIS (and PGDump and
>>CartoDB),
>>Spatialite, GeoPackage
>>Likely (but not verified): GML, Oracle
>>Maybe: MSSQL, MySQL
>>And as pointed by Daniel, the GPX and KML / LIBKML drivers could also use
>>the M
>>dimension for storing track times. Probably the GPSTrackMaker one also,
>>but not
>>verified.
>>So indeed quite a few drivers to get familiar with!
>>
>>>
>>> My 0.02$
>>>
>>> Daniel
>>>
>>>
>>> On 2015-03-17 9:04 PM, Even Rouault wrote:
>>> > Selon Edson Ticona <xcr33d at gmail.com>:
>>> >
>>> >> Hi
>>> >>
>>> >> I was looking for the ideas list on the site and found this one
>>> >> interesting: "Adding support for "M" dimension in OGR Geometries" but
>>> >> it's from 2014. Is it still relevant for the project? I searched on
>>> >> the code and it isn't implemented.
>>> >> For example, the class OGRGeometry needs the methods isMeasured,
>>> >> LocateAlong and LocateBetween according to the definition on the OGC
>>> >> simple standard. I couldn't find an ISO standard talking about M
>>> >> coordinates. Which one do you refer on the page?
>>> >> What do you think? Some feedback would be helpful.
>>> >
>>> > Edson,
>>> >
>>> > Yes it is still relevant. Perhaps SQL/MM Part 3 mentions it ? I didn't
>>> check.
>>> > You'll find the link to a draft doc on
>>> > http://trac.osgeo.org/gdal/wiki/rfc49_curve_geometries
>>> > What has been done in PostGIS might also be interested looking into.
>>> > M only might be a bit light for a whole SOC, so adding support for
>>> > POLYHEDRALSURFACE and TIN might also been interesting for completness
>>>(and
>>> full
>>> > PostGIS interoperability).
>>> >
>>> > Even
>>> >
>>>
>>>
>>> --
>>> Daniel Morissette
>>> T: +1 418-696-5056 #201
>>> http://www.mapgears.com/
>>> Provider of Professional MapServer Support since 2000
>>> _______________________________________________
>>> gdal-dev mailing list
>>> gdal-dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>>>
>>
>>
>>--
>>Spatialys - Geospatial professional services
>>http://www.spatialys.com
>>_______________________________________________
>>gdal-dev mailing list
>>gdal-dev at lists.osgeo.org
>>http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev