Fundamental spatial coordinate systems. WGS84 vs RA/DEC

Hi,
I have some sort of fundamental question about the Oracle Spatial feature and its coordinate model. As far as I am aware of, Oracle use WGS84 coordinate reference but I am pretty much interested on RA/DEC. RA/DEC are used for astronomy as a reference system and my question is whether anybody knows how to map RA/DEC into WGS84 and in the other way around. I know that LATITUDE=DEC but LONGITUDE !=RA.
I know that we can assume that a negative longitude in WGS84 is west of Greenwich than we'd get LONGITUDE = RA*15 and LATITUDE = DEC. The celestial longitude RA=0 through the vernal equinox would then be projected on the meridian of Greenwich. The problem is that I don't know about the accuracy of this assumptions.
I post this query here because I am using GeoSPARQL and Oracle semantic database to try to model part of the Sky. Maybe I should post the query on the Spatial forum, but please let me know!
Cheers

Hi,
I would suggest that you post this question on the spatial forum.
Thanks,
Matt

Similar Messages

  • How to add coordinate system SVY21(SRID: 3414) to Oracle Spatial 11g/12c

    Can any one please help me for "How to add coordinate system SVY21(SRID: 3414, for Singapore) to Oracle Spatial 11g/12c'?

    Why don't you start with the documentation: Coordinate Systems (Spatial Reference Systems)
    Especially paragraph 6.9 (6.9 Creating a User-Defined Coordinate Reference System ) should be helpful for you.
    HTH,
    Stefan

  • Problem with transforming coordinate systems

    Hiho,
    i've got a problem with transforming coordinate systems.
    When I'm trying to transform a sdo_geometry object to another coordinate sytem and then back to the old system, the coordinates are not the same.
    Here's an example:
    StartSystem SRID is 8220 (Longitude / Latitude (DHDN))
    TargetSystem SRID is 8307 (Longitude / Latitude (WGS84))
    Original object:
    Polygon: {ExteriorRing: LineString: { (0.0, -90.0) (1.5, 0.0) (0.0, 90.0) (4.5, 0.0) (0.0, -90.0)} }
    Transformed object:
    Polygon: {ExteriorRing: LineString: { (0.0, -5156.620156177403) (85.94366926962347, 0.0) (0.0, 5156.620156177403) (257.8310078088704, 0.0) (0.0, -5156.620156177403)} }
    Transformed back to old system:
    Polygon: {ExteriorRing: LineString: { (0.0, -5156.620156177403) (4924.209525017614, 0.0) (0.0, 5156.620156177403) (14772.628575052844, 0.0) (0.0, -5156.620156177403)} }
    Any ideas what to do?
    Thanks for the help in advance.
    Dirk

    Hi Dirk
    Since the transform you are trying to do is just a datum conversion of lat./long. coordinates, even the first transform yields obvious rubbish. What you have provided here does not illustrate how you submitted your polygon to CS_TRANSFORM.
    Provide the syntax of your construction of the corresponding SDO_GEOMETRY object and your SQL select statement that gave these results.
    Bruce

  • How can I get the coordinate in the layer coordinate system while doing the iterate?

    I found that the position(x,y) the iterate function tell me is not right sometimes.
    Actually,it happens when the top of the layer is negative. The "y"is in the comp coordinate system(maybe?) but not the layer.In another word, the position with y=0 is not the top.
    More specifically, I have got the color map of a layer. I am able to get the color of any pixel in the layer. But I can't set the color one for one when I use "iterate",because there is an offset.
    Am I supposed to get the offset? Is there any way to access the whole layer directly if I use iterate function?

    so indeed it's the offset at play.
    AE will diminish the buffer at 20% increments, and not for each pixel that
    goes out of sight. it's not really in relation to the upper left corner,
    it's all about what part of your layer buffer is out of sight.
    there's also an "iterate offset function". check it out. perhaps it will
    save you some trouble.
    On Fri, Dec 19, 2014 at 2:45 PM, Hinanawi Tenshi <[email protected]>

  • Select data with SDO_RELATE in lat long coordinate system(8307) in 10gR2

    Hi all,
    I have problem with selecting data from table.
    Data are in lat lon coordinate system 8307.
    These requests don't return any data:
    SELECT ISSUE_ID FROM MAP_ISSUES WHERE SDO_FILTER(GEOMETRY, sdo_geometry (2003, 8307, null, sdo_elem_info_array (1,1003,1),sdo_ordinate_array(-180,-90, 180,-90, 180,90, -180,90, -180,-90)) ) = 'TRUE';
    SELECT ISSUE_ID FROM MAP_ISSUES WHERE SDO_RELATE(GEOMETRY, sdo_geometry (2003, 8307, null, sdo_elem_info_array (1,1003,1),sdo_ordinate_array(-180,-90, 180,-90, 180,90, -180,90, -180,-90)), 'MASK=ANYINTERACT' ) = 'TRUE'
    Optimized polygon does return all data correctly:
    SELECT ISSUE_ID FROM MAP_ISSUES WHERE SDO_FILTER(GEOMETRY, sdo_geometry (2003, 8307, null, sdo_elem_info_array (1,1003,3),sdo_ordinate_array (-180,-90,180,90)) ) = 'TRUE'
    Smaller polygon select data correctly too.
    SELECT ISSUE_ID FROM MAP_ISSUES WHERE SDO_FILTER(GEOMETRY, sdo_geometry (2003, 8307, null, sdo_elem_info_array (1,1003,1),sdo_ordinate_array (52,-7, 54,-7 , 54,-5 , 52,-5, 52,-7)) ) = 'TRUE'
    I have tried changed polygon to be clockwise, counter clockwise, make the area a bit smaller( 160 instead of 180, 89 instead of 90) nothing has helped.
    My explanation than was, that Earth is sphere and each defined polygon defines TWO polygons in the sphere and there is convention that the smaller is chosen to select data. It would make sense along the previous results, but than I found one post which says that this is bug http://www.frontoracle.com/oracle-database/703/180703-size-of-are-of-interest-smaller-equals.html
    I have found in other thread that max only 1/2 of Earth could be selected Different results using SDO_RELATE with polygon and rectangle type but it seems not true, because optimized bounding box works fine!
    What is right? Is there anything in official documentation?
    Is it bug.
    Max 1/2 of Earth could be selected in one request.
    Each polygon defines two areas in the Earth and the smaller one is used to do spatial SDO_RELATE operation?
    Thanks!
    Regards,
    Zdenek

    Zdenek,
    A bug, or limititation, whichever you choose. IMHO if you ask for something, and don't get what you expect, it is a bug that could be fixed.
    But for 10g anywho, the following applies, which is why I choose 120 degree breaks for my code as it is less than 180...
    The following size limits apply with geodetic data:
    ■ No polygon element can have an area larger than one-half the surface of the Earth.
    ■ In a line, the distance between two adjacent coordinates cannot be greater than or
    equal to one-half the perimeter (a great circle) of the Earth.
    If you need to work with larger elements, first break these elements into multiple
    smaller elements and work with them. For example, you cannot create a geometry
    representing the entire ocean surface of the Earth; however, you can create multiple
    geometries, each representing part of the overall ocean surface. To work with a line
    string that is greater than or equal to one-half the perimeter of the Earth, you can add
    one or more intermediate points on the line so that all adjacent coordinates are less
    than one-half the perimeter of the Earth.
    Bryan

  • Connection between 2 points in a geodetic coordinate system

    In a geodetic coordinate system the connection between two points is a geodetic line or "great circle" (the shortest connection between two points on the surface of the earth).
    Since Oracle 9i distances and queries like "Is a point outside or inside the polygon" are computed correctly for a geodetic coordinate system.
    Even though a circle or arc is not allowed in a geodetic coordinate system (like WGS84 - SRID 8307)
    arcs and circles are used in geographic applications like aeronautical maps.
    Frequently a special area is defined like this "10 nautical miles around airport XXXX"
    and this area is shown as a circle in aeronautical maps (in the projection).
    The function SDO_UTIL.CIRCLE_POLYGON (in Oracle 10g) is very useful to construct such kind of areas and for queries like
    "Does the area belonging to airport XXXX overlap with the area belonging to airport YYYY?".
    For Oracle 8i we had to write special PL/SQL code.
    Another type of connection between two points that is frequently used is a line of equal latitude (parallel).
    Many boundaries are defined like "from meridian (longitude) 30°E to meridian 31°E along parallel 47.5°N".
    If this line is a border of a polygon and if we use a direct connection (geodetic line) and we ask if a point is
    inside or outside the polygon, we will not get the correct answer if the point is close north to this line.
    We have to approximate the line and add points e.g. every 0.1° longitude (30.1,30.2,30.3...), then the answer will be correct.
    My question:
    Are there plans to support circles of equal latitude or generally rhumb lines as a type of connection between two points?
    Karl Mann

    There are no plans to support rhumb lines, also know as loxodromes, and including the special case of parallels of latitude, at this time. Note that it is easy to simulate such rhumb lines with a sufficiently dense set of sampled points. Such a densification is implemented implicitly for parallels in the VIEWPORT_TRANSFORM function so that the concept of the "geodetic minimum bounding rectangle" can be supported, primarily for visualization applications.

  • Selecting a coordinate system

    Oracle 9i provides a big set of projected and geodetic coordinate systems. We've got a database full of points (latitudes and longitudes), mostly in the USA, and we're adding Oracle geometries to our database so we can do spatial indexing and quick nearest neighbor calculations. We want to use a projected coordinate system, for speed, but the question is: What's the best coordinate system for our purpose?
    Most of our locations are < 10 miles apart, so we probably don't need location-specific projections like "Massachusetts Mainland Zone" .. unless there's a way to let Oracle decide which projection to used based on the latitude/longitude (that would be nice, eh?)
    Anyway, I'm just a bit overwhelmed by the number of options here, as usual with Oracle.
    Thanks!
    Greg

    Hi,
    I'm not an expert on coordinate systems, but at first look I would leave the data in long/lat and
    use a geodetic R-tree index. R-trees are excellent for nearest neighbor calculations, and
    although it does take Spatial a bit longer to do the distance calculations for geodetic data
    vs. projected data, the simplicity and accuracy of the solution would be compelling reasons
    to leave the data as is. Also, unless the data is extremely dense the extra time associated with
    geodetic distance calculations will get lost in the noise. The best case would be if the query
    window is also a point - the timing will degrade if the query window is a complex polygon.
    Any single projection for an area as large as the US will have distortions that may effect the
    validity/accuracy of the data, but it will be fast...
    Hope this helps,
    Dan

  • Java coordinate system.

    I'm trying to code a program that crops a selected rectangle of a given image. The way I thought to do this was first I created an array holing the pixels of the image. Then I would use the size of the selected area to define the size of a second array and then use the origin of the selected area to reference where to start the second array copying the pixels across.
    This was based on the assumtion that the coordinate system worked in pixels, that given that the image and program window have been set to 640 X 1200 any given point in a 640 X 1200 array would corresspond to it's equivilent on the screen. Yet when I call the getX() method on the selected area object it returns a double.
    why a double?
    Edited by: FyodorK on Dec 5, 2008 4:46 AM

    Which class are you calling the getX() method on? If the documentation says it returns a double, then it does.
    As a side note, Graphics2D (in java.awt) objects can have what is called an affine transform, i.e. rotation, translation, skewing, etc. And that's why the logical coordinate system and the physical coordinate system (pixels on the screen) may be different.
    s

  • Datum vs coordinate system

    Hi guys,
    i just still don't get what is the different between datum and coordinate system.
    anyone could help?
    what i know is, datum is part of geodetic coordinate system that could be transformed. Does datum = geodetic coordinate system? or is there any "things" inside the geodetic coordinate system?
    Thanks

    There are the following related concepts:
    - ellipsoid
    - datum
    - coordinate reference system (not to be confused with coordinate system)
    An ellipsoid describes the shape of the earth (or any other object, for that matter), as approximated by an ellipsoid. This is more accurate than using a sphere. The shape of the ellipsoid is defined by any two of the parameters "semi major axis", "semi minor axis" and "inverse flattening".
    A datum is based on an ellipsoid, but also specifies the ellipsoid's shift, rotation, and scale adjustment, as compared to WGS84. Furthermore, it also specifies the prime meridian.
    A coordinate reference system might be GEOGRAPHIC2D, GEOGRAPHIC3D, PROJECTED, COMPOUND, etc.
    We might look at GEOGRAPHIC2D, which is most closely related to a datum. The CRS is based on the datum, but also specifies a unit of measure (such as degree or radians).
    Note that in the syntax of a WKT, the prime meridian appears to be a parameter of the CRS, rather than the datum. EPSG considers the prime meridian a parameter of the datum.
    A PROJECTED CRS refers to a GEOGRAPHIC2D base CRS, as well as a projection method.
    A CRS also has a coordinate system (CS) as a parameter. It might be ellipsoidal, for a GEOGRAPHIC2D CRS, or cartesian, for a PROJECTED CRS. This CS defines the unit of measure used for the CRS.
    The tables SDO_ELLIPSOIDS, SDO_DATUMS, SDO_COORD_REF_SYS and SDO_COORD_SYS will tell you about the EPSG model. Note that not all models are the same. WKT, for instance, defines projection operations as parts of projected CRS. In EPSG, they are defined, separately.

  • ORA-13487: SRID not found for source coordinate system metadata

    Hi,
    When executing the following
    DECLARE
    g SDO_GEORASTER;
    BEGIN
    SELECT raster INTO g FROM CADRE_AWIFS_GEORASTERS
    WHERE row_id = 3 FOR UPDATE;
    SDO_GEOR.IMPORTFROM
    g, 'SRID=8307',
    'GEOTIFF','FILE',
    '/Oracle2/usr/local/src/cadre/raster_import_orcl/BAND2.TIF'
    UPDATE CADRE_AWIFS_GEORASTERS SET raster = g
    WHERE row_id = 3;
    COMMIT;
    END;
    I get the error ORA-13487
    How can I find the SRID that's making it blow up?

    your file is geotiff, so you should remove "SRID=8307' from the storage parameter. instead, always apply blocksize.
    to find out what kind of coordinate system is inside your geotiff file, you can use many tools. if you don't have the tools, recommend listgeo.exe or gdalinfo. both are open source and can be dowloaded and installed in minutes.
    you may call sdo_cs.find_srid to search the equivalent CS in oracle spatial. or simply check the WKTEXT in the cs_srs table to find out.
    Jeffrey

  • MapViewer and AUTO:42004 coordinate system

    How can I use Oracle MapViewer against an external WMS server using the coordinate system AUTO:42004?
    I have tried it, but the min/max longitude values in the BBOX parameter become wrong.
    - Ingebrigt -

    Ingebrigt
    The AUTO keyword is not supported in the current release.
    From the MV doc Sec D.2.1.14 SRS Parameter
    "The namespace AUTO, for projections that have an arbitrary center of projection, is not supported. "
    Jayant

  • What function to set coordinate system in 6i with API?

    #define D2FP_COORD_SYS 72
    here's the define that relates to what i want to do.
    what are the names of the functions that set/get the coordinate system. (i want to set it to character and change the default units)
    thanks,
    [email protected]

    The Other missing Header file :-) - d2fcrd.h - In fact this is shipped in the Forms API lauchpad on the Forms section on OTN. But here it is anyway:
    /* Copyright (c) Oracle Corporation 1996.  All Rights Reserved. */
       NAME
        D2FCRD.H -- Dev2K Forms API CooRDinate system declarations
       DESCRIPTION
        Contains the public declarations for the Forms API CooRDinate system
       PUBLIC FUNCTIONS
        d2fcrdcr_Create          - Cover for d2fobcr_Create
        d2fcrdde_Destroy         - Cover for d2fobde_Destroy
        d2fcrddu_Duplicate       - Cover for d2fobdu_Duplicate
        d2fcrdex_Extract         -
        d2fcrdap_Apply           -
        d2fcrdg?_Get*Prop        - Cover for d2fobg?_Get*Prop
        d2fcrds?_Set*Prop        - Cover for d2fobs?_Set*Prop
        d2fcrdhp_HasProp         - Cover for d2fobhp_HasProp
        d2fobcs_CharSize
        d2fobss_StringSize
    #ifndef D2FCRD
    #define D2FCRD
    #ifndef ORATYPES
    # include <oratypes.h>
    #endif
    #ifndef D2FPRIV
    # include <d2fpriv.h>
    # endif
    /* C++ Support */
    #ifdef __cplusplus
    extern "C"
    #endif
    ** Object: Coordinate Info
    ORA_RETTYPE(d2fstatus) d2fcrdcr_Create( d2fctx *pd2fctx, d2fcrd **ppd2fcrd );
    ORA_RETTYPE(d2fstatus) d2fcrdde_Destroy( d2fctx *pd2fctx, d2fcrd *pd2fcrd );
    ORA_RETTYPE(d2fstatus) d2fcrddu_Duplicate( d2fctx *pd2fctx,
                                               d2fcrd *pd2fcrd_src,
                                               d2fcrd **ppd2fcrd_dst );
    ORA_RETTYPE(d2fstatus) d2fcrdex_Extract( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                             d2ffmd *pd2ffmd );
    ORA_RETTYPE(d2fstatus) d2fcrdap_Apply( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                           d2ffmd *pd2ffmd );
    ORA_RETTYPE(d2fstatus) d2fcrdgb_GetBoolProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                 ub2 pnum, boolean *pprp );
    ORA_RETTYPE(d2fstatus) d2fcrdgn_GetNumProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                ub2 pnum, number *pprp );
    ORA_RETTYPE(d2fstatus) d2fcrdgt_GetTextProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                 ub2 pnum, text **pprp );
    ORA_RETTYPE(d2fstatus) d2fcrdgo_GetObjProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                ub2 pnum, dvoid **pprp );
    ORA_RETTYPE(d2fstatus) d2fcrdgp_GetBlobProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                ub2 pnum, dvoid **pprp );
    ORA_RETTYPE(d2fstatus) d2fcrdsb_SetBoolProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                 ub2 pnum, boolean prp );
    ORA_RETTYPE(d2fstatus) d2fcrdsn_SetNumProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                ub2 pnum, number prp );
    ORA_RETTYPE(d2fstatus) d2fcrdst_SetTextProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                 ub2 pnum, text *prp );
    ORA_RETTYPE(d2fstatus) d2fcrdso_SetObjProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                ub2 pnum, dvoid *prp );
    ORA_RETTYPE(d2fstatus) d2fcrdsp_SetBlobProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                                ub2 pnum, dvoid *prp );
    ORA_RETTYPE(d2fstatus) d2fcrdhp_HasProp( d2fctx *pd2fctx, d2fcrd *pd2fcrd,
                                             ub2 pnum );
    ** These will eventually move to d2fob.h
    ORA_RETTYPE(d2fstatus) d2fobss_StringSize( d2fctx *pd2fctx,
                                               text *str,
                                               d2ffnt *pd2ffnt,
                                               d2fcrd *pd2fcrd,
                                               number *width,
                                               number *height );
    ORA_RETTYPE(d2fstatus) d2fobcs_CharSize( d2fctx *pd2fctx,
                                             number width,
                                             number height,
                                             d2ffnt *pd2ffnt,
                                             d2fcrd *pd2fcrd,
                                             number *char_width,
                                             number *char_height );
    /* Begin convenience macros  */
    #define d2fcrdg_char_cell_hgt(ctx,obj,val) \
               d2fcrdgn_GetNumProp(ctx,obj,D2FP_CHAR_CELL_HGT,val)
    #define d2fcrdg_char_cell_wid(ctx,obj,val) \
               d2fcrdgn_GetNumProp(ctx,obj,D2FP_CHAR_CELL_WID,val)
    #define d2fcrdg_coord_sys(ctx,obj,val) \
               d2fcrdgn_GetNumProp(ctx,obj,D2FP_COORD_SYS,val)
    #define d2fcrdg_dflt_fnt_scaling(ctx,obj,val) \
               d2fcrdgb_GetBoolProp(ctx,obj,D2FP_DFLT_FNT_SCALING,val)
    #define d2fcrdg_real_unit(ctx,obj,val) \
               d2fcrdgn_GetNumProp(ctx,obj,D2FP_REAL_UNIT,val)
    #define d2fcrds_char_cell_hgt(ctx,obj,val) \
               d2fcrdsn_SetNumProp(ctx,obj,D2FP_CHAR_CELL_HGT,val)
    #define d2fcrds_char_cell_wid(ctx,obj,val) \
               d2fcrdsn_SetNumProp(ctx,obj,D2FP_CHAR_CELL_WID,val)
    #define d2fcrds_coord_sys(ctx,obj,val) \
               d2fcrdsn_SetNumProp(ctx,obj,D2FP_COORD_SYS,val)
    #define d2fcrds_dflt_fnt_scaling(ctx,obj,val) \
               d2fcrdsb_SetBoolProp(ctx,obj,D2FP_DFLT_FNT_SCALING,val)
    #define d2fcrds_real_unit(ctx,obj,val) \
               d2fcrdsn_SetNumProp(ctx,obj,D2FP_REAL_UNIT,val)
    /* End convenience macros  */
    /* C++ Support */
    #ifdef __cplusplus
    #endif
    #endif /* D2FCRD */

  • 3D Coordinate System

    Hello everyone,
    I am new to Java 3D and was trying to create a simple 3D Coordinate system that has an x, y, and z axis. Can anyone help me or point me in the right direction regarding this issue? Appreciate the help.
    Moe.

    http://www.cs.brown.edu/exploratories/freeSoftware/catalogs/repositoryComponents.html
    has some coordinate systems available
    alain

  • Need ruling on screen coordinate system to use with AWTVideoSizeControl...

    Hi -
    I’m working on a tru2way application and a nagging question keeps popping up with stack vendors on the usage of the AWTVideoSizeControl interface. I was hoping you could provide a definitive answer (note that Bill Foote is the author of the interface spec).
    In short…my reading of the javadocs for AWTVideoSizeControl is that all values passed to and received from it are to be expressed in the graphics plane coordinate system. Stack vendors don’t always agree.
    Periodically, I run into a stack vendor who expects AWTVideoSize (as passed to AWTVideoSizeControl.setSize) to be expressed in video plane coordinates – I’ve so far been able to convince these folks that the spec requires graphics coordinates. I’ve just run into an interesting situation, though, where although the vendor agrees that AWTVideoSize should be in graphics coordinates, they’re feeling that the Dimension returned from AWTVideoSizeControl.getSourceVideoSize() should be based on the video plane coordinate system. Their thinking is that while ‘x’ and ‘y’ are coordinates (and therefore are called out as needing to be expressed relative to the graphics screen), ‘height’ and ‘width’ aren’t.
    Perhaps I’m wrong, but that seems incorrect. I would expect the Dimension height and width to be relative to the graphics screen as well.
    I’d appreciate it greatly if you could provide a ruling on this that I could take back to them (and others).
    Thanks.

    You would have to check with the manufacture of your system to see if they have an app available in the Apple App store to access their system. Since you do not indicate the system name or other information, you would need to also search the app store based on the answer the manufacturer provides for you. No one here would be able to guess at what you have.

  • Coordinate System of template form

    Hi there,
    we are currently using Headstart 3.4.2 that was adjusted to our clients requirements. One of the requirements was not to work with a real MDI look and feel, that means every Forms-Module is sized to fit exactly into the MDI Window and then maximized. The surrounding MDI window is sized to a 800x600 screen resolution and centered on the screen.
    To achieve this the consultant changed the coordinate system to pixel and therefore a number of program units in the PLLs had to be changed.
    For us this change had a lot of drawbacks especially, because a lot of the delivered Headstart modules make some sizing stuff based on the inch coordinate system.
    On the other hand a pixel based coordinate system seems much more natural to SW developers and therefore I am not sure how to nadle this task after migration to a newer Headstart version.
    Any opinions or experiences out there?
    Thanks in advance
    --Thomas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    @MLBrown,
    I disagree. Although the "Oracle Developer: Advanced Forms and Reports" book by Peter Koletzke and Paul Dorsey was written at the time of Forms 6 and was written primarily to the Client Server topology, this book does cover the topic "Design for the Web" (Chapter 13) which is still valid today. Additionally, there are other topics that are still relevant with web deployed forms, such as Reducing Network Traffic, Message Diff'ing and Optimize the Class File Loading just to name a few.
    Yes, this is an old book, but with the lack of any better books available - it is still a good place to start to get a basic understanding of how to design an Oracle Form for the web; not to mention it is still a good reference for using some of the more advanced features of Oracle Forms like "Basing a Block on a Procedure" or a "From Clause Query", just to name a few. These Forms features haven't changed much since they were introduced.
    @jbleg,
    With respects to the "Template System" referred to in the book. This was not a commercially available product, but a reference to a set of templates that Peter created. The point was to enforce the need to create standards and partially enforce them through the use of Templates. The use of Templates in you design/development process is still a very valid approach and I suggest you review Chapters 10-12 again.
    Craig... B-)

Maybe you are looking for