<html>
<head>
<title></title>
<meta name="GENERATOR" content="MSHTML 8.00.6001.18876"></meta>
<meta name="SKYPE_FRAMEID" content="UKSDOXEVME"></meta>
<meta id="skype_v3_tb_marker_id" name="SKYPE_PARSING_HAS_FINISHED" content="metacontent"></meta>
</head>
<body>
<div align="left">Hallo</div>
<div align="left"> </div>
<div align="left">I have thought that I should raise some ideas about the line reference functions after this release. I mention it noe because it is a close subject.</div>
<div align="left"> </div>
<div align="left"><span style="FONT-SIZE: 12pt">I would like to rewrite the linereferencing functions like <span style="FONT-FAMILY: Courier New; FONT-SIZE: 12pt"><strong>ST_Line_Substring</strong></span> to do the measure in all 3 dimensions. I am not sure I suggest that there should be a different behaviour in that function but rather make a new that also handles the measure in units like meters instead of parts of the whole line.</span></div>
<p><span style="FONT-SIZE: 12pt"> </span></p>
<div><span style="FONT-SIZE: 12pt">But the thing that was connected to this question was this about measuring in 2 or three dimensions. Does this customer wants it in 2D measuring or will he or she only work in 2 D so it doesn't matter. </span></div>
<div><span style="FONT-SIZE: 12pt"> </span></div>
<div><span style="FONT-SIZE: 12pt">What I mean is that if we want to go against 3Dmeasuring at line referencing maybe that should be included in the bbeginning on this one?</span></div>
<div><span style="FONT-SIZE: 12pt"> </span></div>
<div><span style="FONT-SIZE: 12pt">Just a thought.</span></div>
<div><span style="FONT-SIZE: 12pt"> </span></div>
<div><span style="FONT-SIZE: 12pt">What is needed as I understands it is just another function like distance3d_pt_pt that uses 3 dimensions in pythagora theorem.</span></div>
<div><span style="FONT-SIZE: 12pt"> </span></div>
<div><span style="FONT-SIZE: 12pt">In this function it would not matter that is only following the ground or a line that has the same angel to the ground all the way. But it would be a difference on a line following the ground and then suddenly continuing ut on a mountain or something like that.</span></div>
<div><span style="FONT-SIZE: 12pt">Just a thought</span></div>
<div><span style="FONT-SIZE: 12pt"> </span></div>
<div><span style="FONT-SIZE: 12pt">/Nicklas</span></div>
<div align="left"><br />
2010-01-22 Paul Ramsey wrote:<br />
<br />
All,<br />
><br />
>I have a client who needs a custom function added. Since we're well into release, obviously the SQL API can't change, or really any code in underneath any existing SQL functions. <br />
>However, I can implement the function as a completely additive thing (and in fact have), so it affects the stability of existing functions not at all. And I can leave the SQL API alone, and simple ship the CREATE FUNCTION code directly to the client. <br />
><br />
>http://trac.osgeo.org/postgis/attachment/ticket/390/addmeasure.patch<br />
><br />
>They get the benefit of a quick turnaround on a new feature, we maintain our contract with respect to leaving the API unchanged through minor releases.<br />
>I'd like to apply this patch into stable branches so folks who want it can have it, by running the CREATE FUNCTION code themselves.<br />
><br />
>Paul<br />
><br />
>--<br />
>Paul Ramsey<br />
>OpenGeo - http://opengeo.org<br />
>The secret sauce is called... PostGIS.<br />
><br />
>_______________________________________________<br />
>postgis-devel mailing list<br />
>postgis-devel@postgis.refractions.net<br />
>http://postgis.refractions.net/mailman/listinfo/postgis-devel<br />
><br />
></div>
</body>
</html>